I don't know about booting macOS on one of these, but just bought one for the nostalgia. Can't wait for it to arrive. Brings back memories of the 2600 we had growing up. I didn't even know this was a thing! Thanks for sharing but damn you for bringing this to my attention. ;)
1. Correct. But the image in the first post has F_USB30 labeled as HS/SS 10/11. For me, they show up as HS/SS 09/10 and HS11 is the USB 2.0 headers on the bottom of the board. Probably just a typo.
2. HS12 showed up with a device number, which I assumed was part of the internal WiFi/BT (one for...
I just went through the exercise of mapping myself today and a few things got my attention. I started following @UtterDisbelief's New Beginner's Guide and then saw Hackintool had some similar information/guide so I followed that.
You have two HS11 - One on the F_USB30 and one for F_USB1/2. My...
I changed my SMBIOS to iMacPro1,1 and disabled IGPU and it appears to be working. It didn't work at first, but I once I re-authenticated with Apple, it started working. So, yeah... the SMBIOS trick worked for me.
Only remaining issue is downloading TV+ content. Keep getting this error
Well, that was uneventful :thumbup:
I'm basically using your EFI from the Mojave build, except I'm not using the JGP/quicklook kext and I just updated to Clover r5098. Downloaded the update, ran the installer... rebooted twice I think... then, Catalina desktop. Took about 30-40 mins I think.
I don't know what happened to my EFI folder or what changes in env happened between shutdown and startup. I ended up doing just that... taking @psedog's EFI from a guide because he has the closest match to my setup. And that worked. Got me into the system. I eventually just copied his EFI over...
Ugh, I'm feeling the pain of the "Couldn't allocate runtime area." My install was running fine about 3 weeks ago when I unplugged it and moved 600 miles. I just got the chance to hook it up and turn it on and immediately got this error. I've been banging my head against the desk for hours trying...
I have to chime in here, I couldn't use ANYthing other than the free2000.efi driver... until I removed a bunch of other drivers I'm not using (FileVault2) and switched back to FakeSMC. Not sure what did the trick (and I don't really have time for 15 reboot cycles to test ATM) but...
I see you have the VirtualSMC.kext, but have SCMHelper.efi driver installed. These are not compatible. Remove SMCHelper and install VirtualSMC.efi in its place. Not sure it will solve the RandomSeed issue, but should fix anyway.
Have you tried adding the "Black Screen Patch Vega 56/64, RX580 etc. (c)Pike R. Alpha" to your KextsToPatch in Clover?
<string>Black Screen Patch Vega 56/64, RX580 etc. (c)Pike R. Alpha</string>