CONFIG_INTEL_MEI is missing starting with kernel 7.0. Is this intentional?

admin@ASUS-TX-FX608-PC:~$ grep INTEL_MEI_GSC_PROXY /boot/config-6.19.14-300.fc44.x86_64 
CONFIG_INTEL_MEI_GSC_PROXY=m
admin@ASUS-TX-FX608-PC:~$ grep INTEL_MEI_GSC_PROXY /boot/config-7.0.4-200.fc44.x86_64 
admin@ASUS-TX-FX608-PC:~$
 [    1.677329] i915 0000:00:02.0: [drm] GT1: can't init GSC proxy due to missing mei component
[    1.845266] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)
[    1.865521] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init
admin@ASUS-TX-FX608-PC:~$ grep INTEL_MEI /boot/config-7.0.4-200.fc44.x86_64 
# CONFIG_INTEL_MEI is not set
admin@ASUS-TX-FX608-PC:~$ grep INTEL_MEI /boot/config-6.19.14-300.fc44.x86_64 
CONFIG_INTEL_MEI=m
CONFIG_INTEL_MEI_ME=m
CONFIG_INTEL_MEI_TXE=m
CONFIG_INTEL_MEI_GSC=m
CONFIG_INTEL_MEI_VSC_HW=m
CONFIG_INTEL_MEI_VSC=m
CONFIG_INTEL_MEI_LB=m
CONFIG_INTEL_MEI_HDCP=m
CONFIG_INTEL_MEI_PXP=m
CONFIG_INTEL_MEI_GSC_PROXY=m
CONFIG_INTEL_MEI_WDT=m

https://fatboysoffroad.com/how-to-disable-intel-management-engine/ has:

The Intel Management Engine (IME) is essentially a separate, small, and proprietary operating system running on a dedicated microcontroller within your Intel processor’s chipset. It’s been a part of Intel platforms since 2006. This tiny OS, often referred to as “firmware,” operates at a deeper level than your Windows or Linux installation, and it’s always on, even when your computer appears to be powered down.

Its primary function is to manage various hardware features, including system boot-up, thermal management, and Intel Active Management Technology (AMT). AMT is particularly noteworthy, allowing remote administrators to control your computer, install operating systems, and even access data regardless of whether the main OS is running. This powerful capability, while useful for IT departments, presents a potential security vulnerability for individual users seeking absolute privacy.

Does disabling the kernel MEI module mean disabling IME? Disabling the kernel MEI module only disables communication with IME, right?

This commit adds MEI back, but it is still unclear why it was disabled in the first place.

Looks like it was disabled in Making sure you're not a bot! but without anything specific in the changelog.

Given that the config has already been put back, I’d guess that it was a mistake.

That’s my understanding. I think disabling the management engine usually involves firmware changes/flashes rather than anything at a kernel level.

It may be as simple as Intel being slow to update their MEI support for new kernels.

Once you wade through the AI slop on that page, it advocates using a third-party tool to hack and re-upload the BIOS firmware.

That should be treated with a huge health warning - it’s easy to brick your machine this way. Not a great substitute for a kernel option!

The article does give ample warning of the risks. The main point is that IME is useful for IT managing large deployments, but contrary to the principles embraced by linux.

Before Linux has its own complete hardware manufacturing supply chain, the principles embraced by Linux must first not conflict with users’ everyday use.

Did only see the topic titles, but if it is this: 2468995 – Regression: Intel MEI modules missing in kernel 7.0.4-200.fc44 causing i915 / Meteor Lake system freezes

… then it should be fixed in Making sure you're not a bot!

… and you might want to test it before it is pushed to stable and provide feedback in bodhi.

→ if you go to the second link (=bodhi), and log in there, then you can add thumbs up and down to BZ#2468995 and post.

Keep in mind this is a testing kernel, and has to be considered as such.

Once it has entered bodhi (blue " pending → testing " becomes yellow “testing”), a link will be available on the page to install the kernel with dnf, if you want to help in testing and provide feedback early.