search

corna / me_cleaner

Tool for partial deblobbing of Intel ME/TXE firmware images
GNU General Public License v3.0
4.47k stars 278 forks source link

Any way to unhide the heci/mei device with coreboot? I need this device to exist for hd4000 acceleration to work on osx. Its related to rcba settings?? Thx #367

Open kocoman1 opened 2 years ago

kocoman1 commented 2 years ago

Any way to unhide the heci/mei device with coreboot? I need this device to exist for hd4000 acceleration to work on osx. Its related to rcba settings?? Thx

yanovich commented 2 years ago

Check here: https://github.com/corna/me_cleaner/pull/282#issuecomment-985980845

However, talking to Coreboot developers did solve one mystery - that of the Management Engine showing up under the stock firmware but not under Coreboot. In the coreboot sources, under src/soc/intel/apollolake/cse.c, the function disable_heci1 (where HECI is Host Embedded Controlled Interface, the interface to the ME) is used to disable communications with the ME after Coreboot is done dealing with it. Commenting out the contents of this function (leave the function itself, it still gets called, you just don't want it to do anything) and recompiling, the MEI shows up under Coreboot and we're able to look into its state a little bit more. Once again, just like stock firmware, at present, the exander77 branch needs to be used.

DodoidOfficial commented 2 years ago

Do note, that method as I wrote it there is specific to the Apollo Lake platform. I am unsure how Coreboot handles hiding the MEI on other platforms and if your device is not Apollo Lake what file it's in and what you have to do could vary.