ultrazone's Master Audio Build: Gigabyte GA-Z77X-UD5H - Core i7-3770k - 32GB RAM - Gigabyte GTX 650

[Ritey]

Hi Stork
You are absolutely right
I don't recomment Beta Bioses
But i don't think that the two modded bioses for GA-Z77X-UD5H are Beta
They are modded (non Beta) F14 bios versions.

View attachment 55884

Right now i'm testing a modded Beta version for my board

View attachment 55885

If you gonna try this be carefull.

---------------------

On that bios update, it doesn't update the intel lan rom or the Marvell SATA3 rom does it?

Ritey ..

 

[arehep]

---------------------

On that bios update, it doesn't update the intel lan rom or the Marvell SATA3 rom does it?

Ritey ..

I really don't know.
How do i check that ?
I noticed though that the first time i booted to windows after i flashed with that modded F12e bios that Windows was doing a Chck disk check on the NTFS disk connected to the Marvell (AHCI) sata connector.

That's the first time i've seen that since i made my build so that may indicate that something has changed.

The main reason to try this Bios was to se if that solved the USB3 issue described here in this
post in Stork's Golden Build thread.

But it didn't

 

[huuphong33]

You're using an Ivy Bridge mobo with a Sandy Bridge CPU, so you'll need a proper system definition plus a compiled SSDT for your concrete hardware. Have a look at this thread:

http://www.tonymacx86.com/mountain-lion-desktop-support/86807-ml-native-ivy-bridge-cpu-gpu-power-management.html

Good luck!

Thanks Ultra, for great help, i'll try it, and save money to upgarde to Ivy CPU.

 

[ultrazone]

We've both got the same motherboard, both using the same bios. (Mine is 1.1)

I have an ATI 7950 video card. If I use your DSDT, what should be changed in the aml file?

I am curious to see if your DSDT will repair the USB 3.0 locking the system with a USB 3.0 external drive.

Hi ! My mobo's revision is 1.0 and my DSDT is extracted and based on BIOS version F14. I don't know if my DSDT will work for you, so I just can tell you to try it. If the system refuses to boot you can always boot in single user mode and delete my DSDT from /Extra folder. This way everything would be as it was before.

Please tell me your findings and hope it helps !

 

[Ritey]

I really don't know.
How do i check that ?
I noticed though that the first time i booted to windows after i flashed with that modded F12e bios that Windows was doing a Chck disk check on the NTFS disk connected to the Marvell (AHCI) sata connector.

That's the first time i've seen that since i made my build so that may indicate that something has changed.

The main reason to try this Bios was to se if that solved the USB3 issue described here in this
post in Stork's Golden Build thread.

But it didn't

---------------------------------------------------

OK. That is good feedback. I think the one post from the source where the modded bios page left the reader assuming flashing the modded bios would flash not just the motherboard (intel) bios, but also the Marvell sata controller and the other ethernet roms.

I don't think that is the case, as the Marvell rom apparently requires a separate flash to update it.

I had updated MB 5.3 with the USB fix, and it was working fine. Then I plugged in a new Seagate external USB 3.0 drive and it crashed the system. USB 2.0 and at least one other USB 3.0 (Toshiba) devices play nice with the MB 5.3 driver, but the Seagate apparently has newer USB 3.0 firmware in it's own controller that once plugged in halts the system. I think it is an IRQ issue on the Marvell USB 3.0 chip, or at least how hardware resources are being shared within OS x.

That means there are still issues with OS x and the Marvell controller at the hardware level which aren't being addressed by the MB 5.3 USB 3 driver, or the native OS x 10.8.3 driver.

Ritey ..

 

[Ritey]

USB 3.0 Related ..

http://www.tonymacx86.com/mountain-lion-desktop-support/65552-intel-usb3-issue-ga-z77x-up4-th.html

Ritey ..

 

[arehep]

---------------------------------------------------

OK. That is good feedback. I think the one post from the source where the modded bios page left the reader assuming flashing the modded bios would flash not just the motherboard (intel) bios, but also the Marvell sata controller and the other ethernet roms.

I don't think that is the case, as the Marvell rom apparently requires a separate flash to update it.

I had updated MB 5.3 with the USB fix, and it was working fine. Then I plugged in a new Seagate external USB 3.0 drive and it crashed the system. USB 2.0 and at least one other USB 3.0 (Toshiba) devices play nice with the MB 5.3 driver, but the Seagate apparently has newer USB 3.0 firmware in it's own controller that once plugged in halts the system. I think it is an IRQ issue on the Marvell USB 3.0 chip, or at least how hardware resources are being shared within OS x.

That means there are still issues with OS x and the Marvell controller at the hardware level which aren't being addressed by the MB 5.3 USB 3 driver, or the native OS x 10.8.3 driver.

Ritey ..

Have you tried to delete that Generic USB3 kext ?
You also have to delete xhcdump file located in (hidden) usr/local/bin.
Repair diskpermissions and rebuild cache.
Then use xHCI Mode = Smart Auto in bios.
Boot into Windows with the latest Chipset and USB3 drivers from Gigabyte with your USB3 devices attached.
Reboot to OS X
I'm almost sure that will solve your problem

 

[arehep]

USB 3.0 Related ..

http://www.tonymacx86.com/mountain-lion-desktop-support/65552-intel-usb3-issue-ga-z77x-up4-th.html

Ritey ..

The UP4-TH is using a VIA VL800 USB chip

 

[Ritey]

Hi ! My mobo's revision is 1.0 and my DSDT is extracted and based on BIOS version F14. I don't know if my DSDT will work for you, so I just can tell you to try it. If the system refuses to boot you can always boot in single user mode and delete my DSDT from /Extra folder. This way everything would be as it was before.

Please tell me your findings and hope it helps !

--------------------------------

I may get around to creating my own DSDT, since the motherboard revisions are different the hardware abstract layer will probably be different as interpreted by the DSDT as well.

The ONLY hardware issue I have right now is that the newer Seagate USB 3.0 drives are halting the system, but they still work on USB 2.0

Ritey ..

 

[Hall8000]

nice looking powerful beast you have there!
I have recently built a similar audio DAW system with same MB, integrated graphics though, 16GB RAM, i5-3570K.
I have a Presonus Firebox Firewire audio interface that doesn't function without audio drop-outs using the onboard firewire port. For this reason I got one of the recommended Startech firewire PCIe cards but this causes the sleep/wake/shutdown/restart problems so its not ideal although the audio performance is without problems.
So you have no issues with audio drop-outs using the onboard firewire port?

Hi, I have the same audio DAW only that my cpu is an i7 3770k, i have problems with firebox audio interface and firewire chip VIA onboard in MB, i think that i wiil have the same problem with the startech firewire card, i dont have any solution for the drop out audio.

regards.