Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About Egonaut

  • Rank
    InsanelyMac Protégé
  • Birthday December 12

Profile Information

  • Gender
  • Location
    Tampa, FL
  1. There's a rumor going around that 0x0306A0 is no longer supported/working in 10.13 - as to its validity, I don't know. I personally use it along with -xcpm and I managed to get everything working fine. Our systems are different, albeit slightly, but the lack of a correct FakeCPUID or a missing NullCPUPowerManagement kext are the only things that have triggered that particular error on my system - The general rule of thumb is that you shouldn't install or add a boot flag/patch/DSDT/SSDT/whatever, as long as you explicitly know what it is and why you need it. Using other users config files is a really easy way to break that rule, and therefore, your system, even if they have the exact same hardware, it should only be used as a reference, not a template. But, I really can't speak authoritatively on it for you, as the system is different and I don't know all the details. Again, I've never had to mess around with bootstrap patches before with my G3258 & XCPM, AFAIK, even on Sierra. Have you attempted any clean installs? I recommend getting a hard drive that you can use a sandbox to test configurations/installations on before actually updating your main system, this is a whole new beast entirely when it comes to previous macOS releases. If you'd like to talk in real time about the issue, I may be able to get you set up with someone who knows a bit more about those kinds of patches, read my signature for details.
  2. Thank you! Hoping to populate the forums with some more fixes throughout High Sierra and hopefully into the future. I've spent days at a time working on issues from other users, not necessarily from this forum, but the bottom line is I tend to enjoy helping out anyone I can, and as much as I can.
  3. Haven't seen these in one spot yet, so here's what you'll need if you have this combination of components (A relatively popular one as it used to be featured on logicalincrements.com, but not anymore) For booting into Clover, you'll need the FakeCPUID 0x0306A0. There's no other real, non-complicated way around this. You'll also need the iMac 13,2 SMBIOS (Ivy Bridge Model). Use XNU Power Management instead of AICPM, the boot flag for this is: -xcpm You'll also need some kexts, so go ahead and put these in your EFI folder Audio Chipset: Realtek ALC662 (VoodooHDA - Attached) LAN Chipset: Realtek 8111GR (RealtekRTL8111.kext - Attached) NullCPUManagement.kext (Attached) OsxAptioFix2Drv-64 (Should be installed when you install Clover) BIOS on UEFI defaults, with CSM set to UEFI. With all of this, you should get a working installation up in no time. The rest depends upon your GPU, etc. I went ahead and wrote this up in a couple of minutes just a quick reference, I'll probably add more to this though. Realtek ALC662 Audio Fix.zip RealtekRTL8111.kext.zip NullCPUPowerManagement.kext.zip
  4. BEFORE TRYING THIS, DO THE OBVIOUS SOLUTION! REPLACE YOUR OPTIOFIX EFI FILE WITH VERSION 2, OR WITH VERSION 1. ONLY PROCEED IF DOING THIS DOES NOT WORK. Alright, so my first attempt at helping people that isn’t in a private discord. Hope this goes well. No one has posted this as a direct solution to someone asking for help with this error, so I thought I’d be the one to share it.

 I encountered this problem when I rebooted after making some minor changes and discovered I couldn’t boot back into the disk. All over the web, people keep suggesting clover-side tweaks and replacing kexts, and while they may solve the problem for some, absolutely nothing was working for me (and a few others), even when booting with no kernel cache at all. No boot flags worked, no .efi files would solve it. 

Holding spacebar in clover, no change. So, the solution ended up being system side, and not clover related. You needed to delete your prelinked kernel from the HDD and rebuild it. 

To do this, you just have to be able to get to your recovery drive or use an install USB that’ll give you access to the disk. Clover got me into my recovery drive just fine, another hint that it wasn’t related to clover - but regardless, whatever works for you. After you’re in a terminal, type the following commands.

 Df -h This will list all of your volumes, make sure you’re targeting your installation drive.

 If your volume has a space in the name, such as "Mac OS HS", you'll need to format it as such: "Mac\ OS\ HS" - This is simply how the command line associates spaces. touch /Volumes/[NAME HERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE]

 In my case, I replaced [NAME HERE] with my installation drive - "macOS\ 10.13". Chances are, this command will give you the error "Child process [directory] has exited due to signal 10" The line immediately after that will give you another bit of extremely important information that you need to take note of. "Error 107 rebuilding /System/Library/PrelinkedKernels/prelinkedkernel" That directory is what we're going to be targeting to fix our system. So, time to nuke it. rm -rf [location to /prelinkedkernel/prelinkedkernel] MAKE SURE YOU DOUBLE CHECK IT IS EXACTLY WHAT WAS OUTPUT WHEN YOU TRIED THE COMMAND ABOVE.

 IMPORTANT: YOU MAY RECEIVE A READ ONLY ERROR! DO NOT PANIC. I've done this on multiple machines and it really is hit or miss whether or not this will appear. Regardless, the solution is simple. The following code tag only applies to if you encounter this issue. Fsck mount -uw / RE-ENTER THE FOLLOWING COMMAND! You need a more specific location now. rm -rf /Volumes/[NAME]/System/Library/PrelinkedKernels/prelinkedkernel touch /Volumes/[NAME]/System/Library/Extensions && kextcache -u /Volumes/[Name] Now you should be receiving "/Volumes/[NAME] locked; waiting for lock." This is a good thing. Wait a few seconds, you'll receive "Lock acquired; proceeding." After that, you'll be back at -bash-3.2#, and it will appear as if nothing happened. Again, this is expected. For people who didn't have to use the Fsck command, simply type the following and receive the usual "Waiting for lock; Lock received" response. touch /Volumes/[NAMEHERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE] Now, use your up arrow on the keyboard to re-enter this command. If nothing happens, you're golden. If it detects kexts with invalid signatures, that's still okay - but for future reference, don't go the ##### approach/philosophy of installing kexts to your system drive. Take this as a warning. Go ahead and reboot, and start your installation just like normal. You'll now get past the 0x1 error. Congratulations! If you get hung up anywhere, go back to clover and add “-f” to the boot flags, then boot again. You should make it back to your desktop with no damage whatsoever.

 Like nothing ever happened! Now, as for what causes this, I honestly have no idea. All I know is when you have a working system, make some kind of modication/tweak/installation that HS doesn't agree with, you can possibly get this error on some systems. It's rare, but exists, and unfortunately this is the only way I've been able to get past it. It's not too much work, so don't be too intimidated. You'll have your system back in no time. If you'd like some personalized 1-on-1 support, read my signature and contact me that way. I'm more than happy to help, or at the very least take some time out of my day to analyze your issue and give my thoughts. Thanks for reading my first guide, I'm hoping to publish some more fixes to make High Sierra as painless as possible for every user.