Then there's a new way to doing this as of the new revisions. If you set Scan entries to Disable then it don't come up on the Boot Screen. If you have Custom Entries you need to have them Scanned as well so Clover can pick them up. Try disabling your Custom Entries in ist then reboot Clean NVRAM with F11 firmly pressed for over 1 second until the screen goes blank and then refreshes. I'm on 5144 and Preboot and Recovery are automatically added. ProvideConsoleGop <- maybe this entry is needed too? There's one other one you have to deal with I don't have recall at the moment. I found in HIDE entry OSXRecovery disabled and hidden. I think the reason is because of the "ist/GUI/Custom/Big Sur/Type=OSX" -> I think this can't determine what is the OS version, while if I boot for example from Recovery it's working because no Type is specified, and the OS version is determined by Clover automatically. There is no "AddKextsInArray from 11" so the kexts won't load. Yep, just tried it and as you said, with Custom entry our kexts are won't load from CLOVER/kexts/11įrom log I can see that seems like kexts are being searched and added to the array, but won't load after that.Ġ:826 0:000 =Ġ:832 0:001 Added Kext=11\VoodooSMBus.kextĠ:833 0:000 Added Kext=11\AirportBrcmFixup.kextĠ:833 0:000 Added Kext=11\AppleBacklightSmoother.kextĠ:834 0:000 Added Kext=11\BrightnessKeys.kextĠ:834 0:000 Added Kext=11\HibernationFixup.kextĠ:835 0:000 Added Kext=11\IntelMausi.kextĠ:836 0:000 Added Kext=11\Sinetek-rtsx.kextĠ:836 0:000 Added Kext=11\SMCBatteryManager.kextĠ:836 0:000 Added Kext=11\SMCLightSensor.kextĠ:837 0:000 Added Kext=11\SMCProcessor.kextĠ:838 0:000 Added Kext=11\SMCSuperIO.kextĠ:839 0:000 Added Kext=11\VirtualSMC.kextĠ:840 0:000 Added Kext=11\VoodooPS2Controller.kextĠ:841 0:001 Added Kext=11\WhateverGreen.kextĠ:856 0:005 Added Kext=11\BrcmBluetoothInjector.kext 0:993 0:000 AddKextsInArray from Other I'd let you know in case I can report any progress.
#Clover configurator custom entries code
The OC code is open source so I honestly don't get anyway why they have not been able to implement OC's slick way of displaying Big Sur, and booting Big Sur (automatically via Preboot in the background by itself w/o any user side need for GUI hacking).
I might just need to let it slip for now until Clover allows to simply boot Big Sur by its volume label as custom entry. Not sure what to make of this issue, though.
#Clover configurator custom entries install
Your hint with Filevault might be it because I don't see any other difference to my setup, apart from that I also have Mojave installed in the same APFS container - but that install has it's own UUID folder inside Preboot. What's different is that your output for Preboot is missing the APFSTargetUUID=7434A65C-9925-47BB-A6FE-95753DA18597Īlso your UUID for the path is 7434A65C-9925-47BB-A6FE-95753DA18597 which is the apfsFileSystemUUID of your Volume with Big Sur DATA, Macintosh SSD - adatok.
0 kommentar(er)
