• Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!

Upgrade from Mavericks failed

Following this guide I finally managed to reach the High Sierra installer and installed a test system on an external SSD. It was possible to boot into it despite of a lot of error messages. WiFi, Sound and brightness didn't work, so I put these kexts into the EFI:
AppleALC
BrightnessKeys
SMCLightSensor
VoodooPS2Controller
IO8021HighSierra
SMCBatteryManager

That was apparently some too many, because I got a kernel panic because of Evoreboot that had been migrated with other files from Mavericks. Even after removing this kext which is incompatible with High Sierra the kernel panic appeared again with the same message. What kexts are really needed?

I can't upgrade from Mavericks before I'm sure everything will work.
HD 3000 has a native support on High Sierra and rest should be functional as well. You don't need the IO8021HighSierra. Also, before you upgrade, ensure you have a sufficient backup.
 
I risked installing High Sierra to the internal drive, of course after creating a new backup. But I could not boot into it because of the same error, should have deleted EvOreboot first. After many attempts I was able to boot into the external system again, in save mode, and deleted EvOreboot from the internal drive. Now I can boot into the upgraded system, but only in safe mode. There are still some old kexts to remove.
Attach the EFI to check.
 
Meanwhile booting in normal mode works, ethernet with an old kext and WiFi with AirportAtheros40.kext, AtherosWiFiInjector.kext and HS80211Family.kext, all 3 were necessary. Even the brightness keys are working with that kext, they never did with Mavericks and earlier. Sleep is not working yet nor is sound, sometimes there are glitches on the display and random freezes. Updates from the Appstore are not working, I can live with that. Here is a screenshot of my kexts. I'm still booting from an USB drive until everything works.
Would it make sense to add my old SMBIOS.plist to the Clover folder?
When I open the config.plist it looks changed, but it still works. Is it possible that MacOS changed it?
 

Attachments

  • Current kexts.png
    Current kexts.png
    96.1 KB · Views: 0

Forum statistics

Threads
2,115
Messages
19,609
Members
29,910
Latest member
mrjoh