EDIT: found it
How could I check this?
sudo nvram TestVar=HelloWorld
sudo nvram -p | grep 'TestVar'
I have never understood how to repair the Thunderbolt firmware. The attachment is the Thunderbolt firmware of my ThinkPad t580 jhl6240. Can you help me fix it? If you can, please advise why this is done. Thanks a lot!Great! That means something might be wrong with the EFI partition of the internal Mojave SSD.
- Please mount EFI partition of Mojave SSD.
- Compress and upload the CLOVER folder. You may remove serial numbers from SMBIOS section of config.plist before compressing and uploading the CLOVER folder. Be sure to keep the original config.plist safe.
Bom dia/good morning @ummario,& @CaseySJ,Solved!
Following your recommendations here's what I did:
- after changing SecureBootModel to DEFAULT, mac didn't boot up.
Used USB Pendrive with EFI Opencore, to make changes on Mac config.plist
- Tried option 2, (but at that time forgot to enable the created patch), mac didn't boot up.
After a couple reboots, and without any reason Bluetooth came to life! Still don't understand why.
Meanwhile noticed that still had OpenCore 0.6.2 instead of 0.6.3, so followed your mini guide "Procedure for In-Place Upgrade of OpenCore from Earlier Version to New Version"
After update to OpenCore 0.6.3, noticed that the patch for Aquantia 10Gbps Ethernet was not enabled, so after enabling it and a restart, everything works now.
If you've installed any software that adds extensions that load at boot, that could be a contributing factor. Keep in mind that software generally won't tell you that it's doing this like Little Snitch, I believe, or drivers for some hardware. External hardware you may have attached to the system could also be a culprit.
Ok so I followed the update instructions, made the Boot test USB, deleted the extra kexts from /Library/Extensions and rebuilt the kext cache, then booted from the USB bootloader into my Mojave disk (which is a CCC backup). I got as far as bringing up the Catarina installer, but then it said Catarina couldn't be installed on the disk because it wasn't formatted AFPS. Turns out my CCC backups were not being formatted as APFS for some reason, and the disk was Journaled. So unable to convert the disk, I formatted it as APFS and redid the CCC backup from my main disk. I rebooted and tried to boot into the disk again but it failed. I made another USB to see if that was the problem. Then I realised I'd forgotten to delete the kexts this time. So I booted back into the disk, deleted the kexts and ran sudo kextcache. When I booted again it loaded for a bit then gave me the no-entry sign. I reformatted the disk, did the CCC clone again, deleted the kexts and ran sudo kextcache again, and when I try and boot from the USB bootloader I get the no entry sign again. I tried removing the USB and just booting from the drive and I get "error loading kernel cache".If Mojave was a fresh install, then an in-place upgrade to Catalina would be perfectly okay. But you would need to follow the Mojave-to-Catalina upgrade guide carefully. To unlock MSR 0xE2 (CFG-Lock) it is strongly recommended to install BIOS F9g in which this is already done by default. To find BIOS F9g, open the Quick Reference spoiler at the top of Post 1 and select the 9th bullet in Section 1.
@CaseySJ , I'm wondering if there is a guide to properly migrate from Clover to OC? Does it simply boil down to manually rebuilding/cleaning up of the EFI folder and config.plist file? Can we reuse the config.plist that has been used with clover, or does it require creating a completely new one?
Are you running Clover or OpenCore? Which version?