Contribute
Register

Clean Install on Gigabyte Z68X-UD3H-B3

Status
Not open for further replies.
Joined
Jul 14, 2013
Messages
16
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Currently working on getting my Sandy Bridge setup running with Yosemite. Current process (EDITED for working process!):

Boot 0:
* Updated board to beta UEFI BIOS (since Gigabyte finally decided to get with the program \o/)
* Loaded defaults, made a couple changes (will point out once finished)
* Format, clean install of Yosemite. Unremarkable, reboot.

Boot 1:
* Boot via USB drive into Yosemite for the first time...and it works!
* Walk through iCloud setup...and this works too now? I had issues getting this to setup during install, but this time it let me. Good signs...?
* Glorious Yosemite! Ran Multibeast.
* Per recommendations previously, I did a DSDT-Free install. Added the AppleACPIPlatform Rollback; USB 3.0 Support; and TRIM support. No other changes, let Multibeast do it's thing.
* Removed USB key, rebooted. (Cross fingers!)

Boot 2:
* ...it's booting! No flags!
* ...it's really booting, holy crap. Fast boot, just like my Mavericks install. VERY good signs.
* ...but no device enumeration on USB 3.0, darn. This could be something simple, though, so we'll step away from it for now.
* Ethernet required the RTL81111 kext for reliable connections.
* No more HPET crash! But now I have to call Apple about iMessage too. :(
* Sleep isn't quite working yet either, but I get a feeling I missed a UEFI setting.

I'm currently up and running (for the most part) without any flags! Thank you jarotte for some of those suggestions!
 
Having the similar issue, my installation goes smooth, then fine reboots, booting from Unibeast, time machine restore, reboots Unibeast. after installing multi beast with noDSDT option it boot no more... :( - I used same options as in Mavericks...
 
Is the error screen like that?
I'm having same problem.
Sometimes "mbinit" appears after "PCI configuration Begin", and sometimes only "PCI configuration begin".
It is sometimes happened on hackintosh named "struck on PCI configuration begin" error.

Unfortunately there is no solution so far.

You can find another people having same problem here:
http://www.tonymacx86.com/yosemite-...-boot-sucessful-both-safe-mode-got-panic.html
 

Attachments

  • image.jpg
    image.jpg
    967.3 KB · Views: 1,093
I am getting this same error as well. I have tried a multitude of flags at boot and can not get in. I installed all my things the same way I did for mavericks and used the DSDT for my board.
 
This will be rough, but I'm documenting additional things I'm doing to get things working.

Disabled ALL extra hardware (audio, built-in video, firewire, serial, etc.), unplugged all but USB drive, keyboard, mouse. I was able to boot without other flags! And now I'm getting the HPET error that I think Mavericks had as well?

EDIT: I did a re-install without my DSDT file this time, which may explain the HPET issue. I'll be giving this another shot when I can and will provide another update.
 
I did keep the board in UEFI mode, since I've never had an issue with it otherwise. I don't have any more time tonight to mess with it, but thank you for pointing out the rollback. I think that rollback is where that HPET fix is at. I'll try my current config with a fresh install, MultiBeast with this DSDT and that ACPI Rollback and report either in the morning or tomorrow night.

EDIT: I'm pretty sure that rollback is what solved my Mavericks issue when I did the install as well.
 
Currently installing a clean Yosemite and I'm going to try the ACPI Rollback. I'll report back when I'm done.
 
Currently installing a clean Yosemite and I'm going to try the ACPI Rollback. I'll report back when I'm done.

Well, that did it. Thank you so much for the help.

To those of you searching for the answer for this fix, just check the ACPI Rollback for 5/6-series boards in MultiBeast.
 
Status
Not open for further replies.
Back
Top