Jump to content

mickeyd453

Members
  • Content count

    106
  • Joined

  • Last visited

About mickeyd453

  • Rank
    InsanelyMac Geek
  1. Hi - not really sure what i set to be honest - i seem to remember its just default bios settings with AHCI enabled. Re the clover installer i simply create my install USB with createinstallmedia and then install clover onto that. I dont check install into ESP so the EFI partition is part of the main disk. Apart from that its just standard kexts in the installer. What issues are you having?
  2. success - swapped out the patched com.apple.telemetry.plugin and its booted!
  3. Thanks for the tip - is there anyway to do this in config.plist and leave the com.apple.telemetry.plugin untouched as i note this in that example config.plist <dict> <key>Comment</key> <string>Fix Core 2 Due CPU</string> <key>Disabled</key> <false/> <key>Find</key> <data> KAcAAIU= </data> <key>InfoPlistPatch</key> <false/> <key>MatchOS</key> <string>10.14,10.14.x</string> <key>Name</key> <string>com.apple.telemetry</string> <key>Replace</key> <data> yAYAAIU= </data> </dict> If not i presume i can just replace my current com.apple.telemetry.plugin with the patched one linked to in that other thread? thanks
  4. I have this old board running a media server that has run 10.13 and everything previously without issue. I installed the latest clover and did an in place upgrade and everything seemed to go fine. On first reboot after install it panicked and rebooted and i could not see the error. I selected dont reboot after panic in clover and managed to get the following screen shot out of a video as the error scrolls past too quickly. I installed a clean 10.13 onto a different disk and this was succesful and so with the same clover and kexts i installed a clean 10.14 and exactly the same error occured. I have 2 other machines on 10.14 without issue so can anyone help out understanding the cause of this panic? The install of 10.14 runs fine its just on first boot after install that the machine panics and reboots. thanks for any help!
  5. I found this thread while searching for a problem with my Gigabyte p55 LGA motherboard and Mojave. This board has run fine up until this point with HS 10.13 and everything before hand. I upgraded to Mojave and the installer ran fine, on reboot however after some time of seemingly booting OK the machine just rebooted. Booting into verbose mode from clover its hard to see where it actually reboots as it scrolls past too quickly and then just reboots. Are there any tips that may indicate why 10.13 is fine but 10.14 seemingly installs fine but then reboots on boot?
  6. Thought I'd give it a go and with latest clover it worked perfectly! App Store update to latest beta so there is life in this old machine yet!
  7. mickeyd453

    Mac os High sierra installation attempts

    i posted how to fix this previously - make sure your user is in sudoers, you might need to boot recovery partition and then add your user to sudoers manually then when in 10.13 just ... sudo dscl . -create /Groups/admin GroupMembership <youruser>
  8. mickeyd453

    Mac os High sierra installation attempts

    I didn't need to fix it - it just works. Mine is an iMac 14,2
  9. mickeyd453

    Mac os High sierra installation attempts

    Yes - appears to be working for me. What issue are you having?
  10. Why dont you just buy a 710? Its native OOTB in 10.12 and 10.13 and they are a cheap card.
  11. mickeyd453

    Mac os High sierra installation attempts

    well i have a 710 and it works OOTB
  12. mickeyd453

    Mac os High sierra installation attempts

    specifically which card?
  13. mickeyd453

    Mac os High sierra installation attempts

    Update from Developer Beta 2 to Public Beta 1 via official public beta download went without issue.
  14. mickeyd453

    Mac os High sierra installation attempts

    I had that after the beta 1 update - I sorted it by booting from the recovery partition, manually adding my user into the sudoers file and then after a normal boot running the following to make myself an admin again via terminal sudo dscl . -create /Groups/admin GroupMembership <username> - but replace <username> with your username
×