Cannot Load Any OpenCore Drivers - Invalid Parameter!

[mnfesq]

I have been running Sequoia on my Chrome Box 3 N7068U.  Here are the basic hardware specs:  Intel 8th Gen. i7-8850U CPU - Kabylake-R with Intel UHD 620 integrated graphics, 16 GB DDR4, HDMI output, USB and USB-C, Broadcom wifi and bluetooth.  I have removed the ChromeOS firmware and replaced it with the MrChromebox UEFI Full Rom Firmware version 2512.5 (2026.01.25).  An earlier version of the same firmware worked fine but I updated to the newer firmware because it is now much more configurable.

 

I am using Open Core version 1.0.7 with the most up-to-date kexts. But I cannot get OC to load anymore.  As soon as it starts, I get an error message stating that the .efi drivers cannot load - Invalid Parameter. Halt on critical error.  When I disable all of the .efi drivers, it starts to load but then hangs because the OC Runtime driver is not loaded. There does not appear to be anything in the OC documentation regarding an invalid parameter error when loading .efi drivers.  I am assuming that there is something in the MrChromebox firmware that is incompatible with the settings I am using for OpenCore.

 

Here's my OC config.plist:  config.plist.zip

 

Here's the settings on my firmware:

 

 

Any ideas?  I am trying to find out if there is a depository of old versions of the MrChromebox firmware because I could at least revert back to the earlier version that worked but so far I haven't found one online and may need to depend on my ability to contact the developer. For now, this computer is unusable and inaccessible. Thanks for any help you can offer.

 

 

[Slice]

Same with Clover?

[deeveedee]

@mnfesq when I run ocvalidate on your config.plist, I see this:

 

OCS: Missing key ClearTaskSwitchBit, context <Quirks>!
OCS: Missing key Unload, context <UEFI>!
Serialisation returns 2 errors!

Could this be the problem?

[deeveedee]

@verdazil I didn't notice that the config.plist included Driver ApfsDriverLoader.efi.  

 

@mnfesq Why are you loading driver ApfsDriverLoader.efi?  It may be correct - it's just that I've never used it with OpenCore on any of my hacks.

 

EDIT: @verdazil According to the sample.plist that is included with Open Core 1.0.6, the order of the drivers in mnfesq's config.plist should be as follows:

• OpenRuntime.efi (Item 2 in sample.plist)

• HFS+ Driver (Item  9 in sample.plist)

• OpenCanopy.efi (Item 10 in sample.plist)

• CrScreenshotDxe.efi (Item 21 in sample.plist)

• OpenLinuxBoot.efi (item 46 in sample.plist)

• ResetNvramEntry.efi (Item 48 in sample.plist)

• ToggleSipEntry.efi (item 49 in sample.plist)

 

I'm not sure where AfsDriverLoader.efi should be placed since I've never used it with Open Core.

Edited February 11 by deeveedee

[mnfesq]

1 hour ago, deeveedee said:

@mnfesq when I run ocvalidate on your config.plist, I see this:

 

OCS: Missing key ClearTaskSwitchBit, context <Quirks>!
OCS: Missing key Unload, context <UEFI>!
Serialisation returns 2 errors!

Could this be the problem?

 

Thanks. My desktop is so cluttered with failed attempts to edit my config.plist that I must have uploaded the wrong one.  The one I'm using has those 2 missing elements. Here's what I am currently using.

 

config.plist.zip

[deeveedee]

@mnfesq wow.  that was the wrong config.plist.  I don't have any more time to review today, so hopefully someone else figures this out.  good luck!

 

EDIT: @mnfesq Without any further review, we know that you don't need ApfsDriverLoader.efi, so you can remove/disable this.

Edited February 11 by deeveedee

[Avery B]

disablesecuritypolicy=true under uefi/quirks if it is for any of the recent mrchromebox firmwares.

 

Also you may want to compile a custom version with the HECI interface enabled.

Edited February 11 by Avery B

[mnfesq]

2 hours ago, Avery B said:

disablesecuritypolicy=true under uefi/quirks if it is for any of the recent mrchromebox firmwares.

 

Also you may want to compile a custom version with the HECI interface enabled.

 

Thank you very much!!!! This was the fix and it was so easy.

 

Thank you also @Slice.  Clover did not have this problem but I did not have Clover set up on this computer and I ran into some unrelated issues getting it to boot with Clover.

Edited February 12 by mnfesq

[Avery B]

@mnfesq
Just as an FYI, I had issues with electron apps breaking after sleep and some other goofy issues on my KLED. Had to make sure the IMEI/HECI interface was enabled in the coreboot firmware. It's pretty easy to build (and I might be able to build it if you can give me the board name) - ended up writing a quick little tutorial here a year or two ago: https://docs.chrultrabook.com/docs/installing/macos-firmware.html#building-manually

Basic gist is just running `make menuconfig` to disable the `Disable HECI1 at the end of boot` option.

Edited February 12 by Avery B

[mnfesq]

17 hours ago, Avery B said:

@mnfesq
Just as an FYI, I had issues with electron apps breaking after sleep and some other goofy issues on my KLED. Had to make sure the IMEI/HECI interface was enabled in the coreboot firmware. It's pretty easy to build (and I might be able to build it if you can give me the board name) - ended up writing a quick little tutorial here a year or two ago: https://docs.chrultrabook.com/docs/installing/macos-firmware.html#building-manually

Basic gist is just running `make menuconfig` to disable the `Disable HECI1 at the end of boot` option.

 

Maybe you saw the post I made in the Hackintool subforum but I think what you are describing is what I have been experiencing, which set me on this odyssey in the first place.  I will try to make my own .rom file using Ubuntu Live but, if I run into any real problems, I may take you up on your offer to compile a .rom file for me that allows IMEI/HECI so that I might also solve my wake from sleep issues.  Thanks. You have been a lifesaver (or at least a major time-saver.) 😀

 

BTW, my board name is TEEMO.

Edited February 12 by mnfesq