So basically I worked all day to try to get my Ryzen 5 1600 working with an MSI B350M and MacOS Sierra. Could not find a decent guide, I really can't read over tons of pages about people discussing and not making a decent statement for trying to get it work, what is needed, no, really nothing. The only thing I managed to understand (which was pretty obvious) was a custom kernel, like the older AMD Hackintosh builds. So I found a site where people upload them, and used that kernel. Im not new to hackintoshes in the Intel world, never had particular problems managing them (Ivy bridge, Haswell, Skylake cpus)
The first try was custom homemade installer with clover which I always used for intel builds with the basic and usual kexts, but with some clover.plist found on the internet claiming to have options dedicated for Risens, but no luck. Just a reboot when trying to load the installer after the +++++ (Used the custom kernel in there)
So, the second try was using a dedicated iso found on the internet with integrated Ryzen support, and that got me to the installer, but only in legacy mode, could not install it in UEFI mode even after installing clover manually, with no apparent reason
The third try was to making one by myself, so I used the installer from the first try, but this time doing an hard trial and error work I managed to get it work by simply using the default clover.plist (lol) from the intel and replacing the kernel, and also updated the Clover bootloader otherwise clover does not load at all, I only had to put npci=0x3000, which that happens also in Intel builds. No need to use busratio=32 like I saw on the internet. So I managed to install MacOS successfully, this time, but weird problems happened when I tried to access the installed OS. I tried to open it a first time, no luck obviously, reboot! But that also happened when I replaced the kernel with the correct one. Like it does not load the proper kernel. So I started searching for a sort of kernel cache (the wrong kernel cache) and managed to delete from /System/Library/PrelinkedKernels a sort of cache. But after that, kernel cache error! No luck passing that screen. I tried to use the OSXAptio driver, the OSXAptio2, both of them but that just got me randomly to reboot after the ++++. So I also tried to delete ALL kernels from /System/Library/Kernels but this time, from the USB installer, and it could still work! It was trying to load the preloadkernel first! So I was right. But why this happens only with the installed OS? Basically the USB installer seems to deal great with the patched kernel building and (I think) replacing the old cache with the right one, making all working great. Deleting the prelinked kernel even after putting back in place the kernel in /S/L/E/Kernels got me back the kernel cache error, no luck using -f (which ignores the kernel cache? idk) this time. I also tried to get back the prelinked kernel extracting it from the iso but random reboot again! wtf? How that works honestly? Do you have to do something about rebuilding in some way the cache when replacing the kernel? Can someone tell me what the hell is happening there? I hope I just did a stupid thing.
Can it be that I tried to start the default kernel at first on the installed system? I've not did that with the USB installer (even if an existing cache was present, but I'm not sure about that)
[link] [comments]
Post a Comment