I couldn't seem to find any informative fixes for this error on Google, so I've compiled a simple list of possible fixes.
AFAIK the error can be related to improper encapsulation of kext packages, related to a bad Clover config, or could be a bad mixture of hardware (e.g. Using AMD CPUs or multiple GPUs). It may be a headache for new users (like me) so go through some of these simple fixes, hopefully at least one works :)
The One's not in bold are just speculated in various forums, so probably won't work, but worth a try
1) "-radvesa" or "-radoff" (DO NOT TRY TOGETHER, USE SEPARATELY!) Put any of these arguments in your launch options for clover (by pressing "o" in the Clover bootloader). This might work if your boot is getting stuck at the "GIOScreenLockState 3" line and not going to black-screen, but it will probably just show some IO/AudioBus related information and then get stuck if you was going to black-screen before. AMD-OSX.com Forum source
2) Change BIOS settings Some BIOS settings may cause this issue. Try the following: Disable "VT-d" Disable Legacy Boot Make sure UEFI is enabled! Disable "Secure Boot" (This is a windows feature) Follow this thread, tonymacx86 Forum source
3) Web Drivers Boot with Nvidia web drivers enabled in the launch options in Clover (if you have an Nvidia GPU)
4) Rebuld Kexts Cache This can work if you changed or updated your kexts and then experienced the GIOScreenLockState 3 issue: First boot in *single user mode** from the Clover bootloader options and then you'll find yourself in a command line environment as "root" user. This will let you change system variables and in this case force a re√Check of the kexts folder; OSX saves the kext's "state" in a cache for a faster boot next time. *In the command line type: sudo touch /System/Library/Extensions && sudo kextcache -u / If any errors occur, you might need to Google them, but if successful type: reboot * try to boot from clover as usual. Forum Source
5) Boot into Safe Mode and then Restart In the Clover boot options simply boot into safe mode by selecting the safe mode argument and then "boot with selected options". This is unlikely to work, but who knows.
6) Check EFI boot Settings (My own fix, worked for me) Only do this if you really know what you're doing (or if you've run out of options). I noticed a bunch of weird folders and files in the clover boot partition in Ubuntu, all with a "." processing the file or folder name, implying that they were supposed to be kept hidden. So try the following: * Firstly, boot into Windows or Ubuntu and make sure you have any settings enabled that lets you see "hidden files and folders" * Backup all the folders and files that are in the main partition of your USB stick and then delete the folders with the "." proceeding the folder name. * You should just be left with a "boot" file, and an "EFI" folder. * *If this doesn't work, delete all the folders apart from the "boot" file and the "EFI" folder.
6.5) Create a new USB with Clover's EFI vanilla boot (MS-DOS / FAT32) and a small list of verified working kexts You are probably using a large amount of kexts... and if you are coupling those with another automated kext updater/adder software then you might run into problems with duplicate kexts, mismatching kexts, invalid and incompatible kexts... you get the idea. * You don't need to do a fresh install, just a fresh Clover bootloader using this installation method
7) Uncheck all Graphics Apparently this user could only get their version working with this fix. * Uncheck everything related to Nvidia in the "graphics enable" option menu. If on AMD do the same thing for AMD checks. I'm not sure why this would work but hopefully it can help someone out there.
If anyone else has any fixes, please comment them as they might help others.
[link] [comments]
Post a Comment