Contribute
Register

Clover Booting Guide: Z77X-UD5H- HD4000+GT640

Status
Not open for further replies.
For ultrazone.
all bios settings

Thanks a lot, I'll try this afternoon once I get to my studio.

Some doubts:

- Since I'm not using HD4000 at all, could I disable it?

- On another thread I read that an user was getting better performance with it connected... does that make any sense?

- Will the HD4000 be responsible of sleep not working?

Thanks again! Let's make an awesome Z77X-UD5H + Clover thread!
 
Xpamamadeus has explained that this brings a few different things in earlier posts. UEFI GOP HD4000 support and a few different ROM upgrades. If you would like to boot with CSM Disabled it is recommended that you use F15r. This also solves some sleep/wake issues.

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

What 'different' ROMs are updated other than the AMI BIOS ROM?

Are you sure about this?

Ritey ..
 
------------------------------------------------------------

What 'different' ROMs are updated other than the AMI BIOS ROM?

Are you sure about this?

Ritey ..

Update with...
1. Intel® RAID ROM 11.6.0.1702
2. Intel® VGA ROM 2137
3. Marvell SATA3 ROM 1.0.1.0025
4. Atheros LAN ROM 2.0.6.6 and 2.1.1.1 PXE 2.0 Build 083
5. Intel® LAN ROM 1.3.95 PXE 2.1 Build 091
 
Update with...
1. Intel® RAID ROM 11.6.0.1702
2. Intel® VGA ROM 2137
3. Marvell SATA3 ROM 1.0.1.0025
4. Atheros LAN ROM 2.0.6.6 and 2.1.1.1 PXE 2.0 Build 083
5. Intel® LAN ROM 1.3.95 PXE 2.1 Build 091

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

Are you flashing the patched BIOS onto your primary (A) BIOS, or the secondary (B) bios?

I know that Marvell has it's own controller patch, and it is based on the Marvell Sata controller chip revision. In this case, it would be relevant based on the revision of your GA-Z77X-UD5H (1.0 or 1.), since each motherboard revision has different Marvell controllers.

As you know, this makes a difference when using patched bios as the revision of the motherboard is important.

This is the reason for me asking if / how the patched bios can update the firmware of EACH of these separate firmware bios in ONE FLASH.

Ritey ..
 
----------------------------------------

Are you flashing the patched BIOS onto your primary (A) BIOS, or the secondary (B) bios?

I know that Marvell has it's own controller patch, and it is based on the Marvell Sata controller chip revision. In this case, it would be relevant based on the revision of your GA-Z77X-UD5H (1.0 or 1.), since each motherboard revision has different Marvell controllers.

As you know, this makes a difference when using patched bios as the revision of the motherboard is important.

This is the reason for me asking if / how the patched bios can update the firmware of EACH of these separate firmware bios in ONE FLASH.

Ritey ..
There are no primary and secondary bioses.
They are just same and it does not matter on wich one u flash.
Both marvel SATA roms are in this bios.
(9192 Chip Version ) can be updated to Marvell SATA3 ROM 1.0.1.0025
But for (9123 Chip Version) there are no updating needed since it have SATA3 ROM 1.0.0.1033 already in bios.
This bios its modded by STASIO soo u dont need to be scared about using it.
STASIO do this job for very long time.
Good luck!!
 
This bios its modded by STASIO soo u dont need to be scared about using it.
STASIO do this job for very long time.
Good luck!![/FONT][/COLOR]

I second STASIO's work, I have been using BIOS mods from STASIO for a while now. Never a problem.
 
Hi !

So I applied xpamamadeus' exact settings (with the exception of my over clock to 4,5Ghz on all cores) to my motherboard. These are my findings:

First of all, my GTX650 now boots from the HDMI port. Before disabling CSM it was booting via DVI. This is just a minor change and it's not a problem at all.

Since I applied your settings, the internal Firewire port is always detected and appears in System Profiler, no matter if I disable or enable it in BIOS. It's always there. It is worth mentioning that I had lots of problems with this VIA Firewire chipset (mainly random freezes), so I added a Startech 2-port 400Mbps PCIe adapter, which has been working without a single problem. I've been working with this Startech adapter and the internal Firewire disabled in BIOS for five months without a problem (please remember that I work with Firewire audio interfaces).

But now, with CSM disabled it seems like the internal Firewire can't be disabled. The option to disable internal Firewire appears in BIOS, but it seems to have no effect, since the device always appears in System Profiler. What's more, in Console I can see the following:

Code:
5/22/13 7:34:14.000 PM kernel[0]: FireWire (OHCI) VendorID 1106 ID 3044 PCI now active, GUID 0000000000000000; max speed s400.
5/22/13 7:34:14.000 PM kernel[0]: FireWire GUID 0000000000000000 is invalid!

This message appears at boot, and the second line gets repeated every few seconds. By the way, the Startech PCIe adapter is correctly configured, since the log shows this (and nothing more regarding this adapter):

Code:
5/22/13 7:39:37.000 PM kernel[0]: FireWire (OHCI) VendorID 197b ID 2380 built-in now active, GUID 001b8d1000004c54; max speed s400.

I've been reading about this error and it seems to happen with beta BIOSes in which the insertion and/or injection of the GUID is bypassed, so the device can't be enabled. I don't know if this is what is actually happening, but anyway it happens. So the solution for me would be to just disable the internal Firewire in BIOS, but it's impossible: the device always appear in System Profiler and the errors always appear in Console.

Thinking about it I was wondering if at least there's a way to inject this GUID Firewire thing via Clover, in order to make these errors disappear from Console. I know the device's GUID, since when booting with CSM enabled I get this in Console:

Code:
5/22/13 7:39:37.000 PM kernel[0]: FireWire (OHCI) VendorID 1106 ID 3044 PCI now active, GUID 0049e550ae644b00; max speed s400.
5/22/13 7:39:37.000 PM kernel[0]: FireWire (OHCI) VendorID 197b ID 2380 built-in now active, GUID 001b8d1000004c54; max speed s400.

Related to all this, I saw on one of xpamamadeus' shared folders a file in "kexts" called "AppleFWOHCI.kext". The original file is a plugin within "IOFireWireFamily.kext", and xpamamadeus' version is the same as in 10.8.3, but with some modifications: concretely a line within IOKitPersonalities which adds "GUID" and "1000000000000000" as number. Would this be a way to add the Firewire GUID? I've tried putting this modded file from xpamamadeus in /CLOVER/kexts, in /CLOVER/OEM/Z77X-UD5H/kexts and in /CLOVER/OEM/Z77X-UD5H/UEFI/kexts, but the result is the same. Do I have to add my GUID in this file?

Or maybe all these problems are due to the beta state of F15r mod4 I'm using…

Regarding the sleep problem itself (the only original problem with my build and Clover), these are my findings:

- With CSM disabled + internal Firewire enabled = Firewire Console errors + sleep don't work (the system goes to sleep, but I get black screens after waking up, have to reset manually).
- With CSM disabled + internal Firewire disabled = Firewire Console errors + sleep works (at least it has worked once or twice).
- With CSM enabled (Other OS): no Firewire Console errors + sleep doesn't work (no matter if internal firewire is enabled or disabled: sometimes I get black screens and others the screens wake up for a second and then the whole system restarts by itself).

Sorry for the long post, but it seems like I have Clover almost ready but at some point (BIOS or whatever) something is wrong.

Thanks a lot xpamamadeus ! Cheers from Spain !
 
About firewire...
This its reported to gigabyte but still no answer about they gonna fix it,and when.

When CSM Support set to Always firewire ROM looks like this

Code:
[FONT=Helvetica]04 04 a3 ad 31 33 39 34 f8 00 a2 42 00 [COLOR=#ff0000]34 2b 90 cf 31 3b 00[/COLOR] 00 09 27 04 38 00 00 04 03 00 0a 27 81 00 00 07 17 00 00 0a 81 00 00 0d 0c 00 83 c0 8d 00 00 11 d1 00 00 13 d1 00 00 15 00 07 ac 75 00 00 00 00 00 00 00 00 41 70 70 6c 65 20 43 6f 6d 70 75 74 65 72 2c 20 49 6e 63 2e 00 05 dd de 00 00 00 00 00 00 00 00 4d 61 63 69 6e 74 6f 73 68 00 00 00 00 02 04 db 00 34 2b 90 cf 31 3b 00 00 02 f8 d2 12 00 00 5e 13 00 00 01 00 02 c8 b1 12 00 00 5e 13 00 00 02[/FONT]

And i see FW GUID in system is 342b90cf313b00

When CSM Support set to Never firewire ROM looks like this

Code:
[FONT=Verdana]04 04 6c 09 31 33 39 34 e0 00 80 42 00 [COLOR=#ff0000]00 00 00 00 00 00 00[/COLOR] 00 09 27 04 38 00 00 04 03 00 0a 27 81 00 00 07 17 00 00 0a 81 00 00 0d 0c 00 83 c0 8d 00 00 11 d1 00 00 13 d1 00 00 15 00 07 ac 75 00 00 00 00 00 00 00 00 41 70 70 6c 65 20 43 6f 6d 70 75 74 65 72 2c 20 49 6e 63 2e 00 05 dd de 00 00 00 00 00 00 00 00 4d 61 63 69 6e 74 6f 73 68 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 02 f8 d2 12 00 00 5e 13 00 00 01 00 02 c8 b1 12 00 00 5e 13 00 00 02[/FONT]
FW GUID in system is 00000000000000
This is omission or Firewire OpRom initialization bug

But firewire always working like a charm.
I am using it alot with 3 diferent cameras for capture,no single problem.

Sleep also works like a charm.
Are u sure u have make internal CPU PLL overvoltage to Disabled ?
U use my dsdt or u make one for u with USB 2-3 Multiplex Intel 7 patch?
Maybe u use generic usb kext or something?

About that firewire kext it wass just expiriment.

For fixing this GUID 000000000 error,i think we need to extract firewire rom and modify it,and then try to load with Clover??
Dont know.
I found solution somewhere to stop error spaming console but that just cosmetic,error its still there ofcourse.

I think we can just w8 for Gigabyte to start sell new 8 series boards,and maybe then we get some non beta bioses,or we will need go to new platform and hope they make things even better-more fun(for fixing things) than now.
:oops:
 
I am curious, what do you guys really gain by replacing those modules in your ROMs? i get UEFI GFX on my HD4000 natively when I disable CSM and haven't flashed anything.
 
About firewire… This its reported to gigabyte but still no answer about they gonna fix it,and when.

FW GUID in system is 00000000000000
This is omission or Firewire OpRom initialization bug

But firewire always working like a charm.
I am using it alot with 3 diferent cameras for capture,no single problem.

Thanks a lot for all your help and expertise. So it's just cosmetic… It would be good to remove the Console spamming messages, so I'll google it a little just in case.

Sleep also works like a charm.
Are u sure u have make internal CPU PLL overvoltage to Disabled ?
U use my dsdt or u make one for u with USB 2-3 Multiplex Intel 7 patch?
Maybe u use generic usb kext or something?

Ok, I'll try your DSDT, since I've been using mine, which is based on F15r (extracted from Ubuntu) and patched the way you describe in your EFI.zip. I'm not using any usb kext, plain vanilla install. I'll also double-check the internal CPU PLL thing.

About that firewire kext it wass just expiriment.
Good to know !
For fixing this GUID 000000000 error,i think we need to extract firewire rom and modify it,and then try to load with Clover??
Dont know.
I found solution somewhere to stop error spaming console but that just cosmetic,error its still there ofcourse.

I think we can just w8 for Gigabyte to start sell new 8 series boards,and maybe then we get some non beta bioses,or we will need go to new platform and hope they make things even better-more fun(for fixing things) than now.

Ok thanks again for all the info. We'll have to wait for an official update from Gigabyte.

In the meantime, do you know if it is possible to have UEFI GFX via GTX650 (with UEFI BIOS) in BIOS version F14 (CSM disabled, of course…) ? If this is possible I would go back to F14 BIOS until Gigabyte comes with a newer official version.

Cheers !
 
Status
Not open for further replies.
Back
Top