Run the post-install a second time. Sometimes that's necessary for it to work.Just installed public beta on my iMac 9,1. I still have no USB support after running post install. Any ideas?
Run the post-install a second time. Sometimes that's necessary for it to work.Just installed public beta on my iMac 9,1. I still have no USB support after running post install. Any ideas?
Run the post-install a second time. Sometimes that's necessary for it to work.
Huh, does it rebuild the caches when rebooting?Tried it. No dice. It's also done in like 10 seconds
[doublepost=1468000287][/doublepost]Is it because I upgraded and didn't do a clean install?
Yeah, it may be because you did an upgrade. Let me see if I can figure out a way to ensure the kextcache is rebuilt.
Yeah, it may be because you did an upgrade. Let me see if I can figure out a way to ensure the kextcache is rebuilt.
Ah, I figured it out. I'm updating the post-install patch now.I suppose I'll have to dig out the 09 MacBook. Or is there a terminal command I can try?
Ah, I figured it out. I'm updating the post-install patch now.
Ok I'll dig out my MacBook and update my installer there.
I'm sure this has been answered, but for those of us who are currently running Beta 1 on unsupported macs do we just run the public beta installer from within the Applications folder..? Or is it necessary to make the installer USB again?
Also, as I understand it we should not use Disk Utility to format the disk beforehand, but instead should just run the installer and select the Mac drive...is this correct?
Remake it and yes
Ok I will remake the USB - I am assuming using the patcher just the same as before. I am currently running a Bootcamp setup (everything is backed up). ..I would however like to keep my setup if possible. If I upgrade using the installer (without formatting the disk) and then use Gdisk to rebuild my hybrid MBR should it work?
Alright, just updated the tool. It now rebuilds caches whenever the post-install tool is run, so that should resolve the problems when doing an upgrade-install.
Just type "rm /Volumes/<target volume>/System/Library/prelinkedkernels/prelinkedkernel" in Terminal.Ok I'll let you know. I'm gonna try to do the rebuild caches terminal command. My MacBook is stupid slow
Alright, just updated the tool. It now rebuilds caches whenever the post-install tool is run, so that should resolve the problems when doing an upgrade-install.
Just type "rm /Volumes/<target volume>/System/Library/prelinkedkernels/prelinkedkernel" in Terminal.
Alright, just updated the tool. It now rebuilds caches whenever the post-install tool is run, so that should resolve the problems when doing an upgrade-install.
I meant just installing Sierra on a volume that contains an install already, without erasing it. That way, all files and settings will remain in tact. You still have to create a patched USB and boot from it, but just skip erasing the disk with Disk Utility.Can you just clarify what you meant by upgrade-install? Is there an option to install by running the beta installer directly from Applications...or is the only possible way to remake a new USB by following your old instructions from beta 1?
I meant just installing Sierra on a volume that contains an install already, without erasing it. That way, all files and settings will remain in tact. You still have to create a patched USB and boot from it, but just skip erasing the disk with Disk Utility.
No, as long as it works, you're fine.I did an upgrade to PB using yesterday's (2.5?) patcher. Looks like it's running fine. Seems like you made a bug fix to purge kext caches for my upgrade (from DP1) scenario. Should I remake and post install? Any reason to worry?
I meant just installing Sierra on a volume that contains an install already, without erasing it. That way, all files and settings will remain in tact. You still have to create a patched USB and boot from it, but just skip erasing the disk with Disk Utility.