More problems with GA Z77X-UD5H

[will_sutton]

System is now a dual boot and it worked ok ( used F12 key to select Ubuntu boot ) . It boots into Windows just as quick and is stable but I cannot get into the BIOS. Delete key just cause the UEFI screen start to come up but it locks with just a mouse cursor . Same things happen if I hit the F12 key ... it locks

Debug LED codes show this message "D5" which is "no space for legacy Option Rom initialization"


I have overclocked the CPU using easy tunes and its stable when gaming or anything else related to windows 7 ... just cant get into the BIOS or bring up boot options ( F12 )

[hms]

Re: More problems with GA Z77X-UD5H

Can you get to BiOS if you unplug everything exept keyboard? Connected usb hubs are known to cause havok. If removing extra usb periphals won't help you need to reset(clear) CMOS to get back to factory settings.

[will_sutton]

Re: More problems with GA Z77X-UD5H

have it back to stock and in to it last night but today similar problem

and yes, USB seems to be the culprit yet again as I had the steering wheel plugged in but slightly different problem ...this time it brought the f12 screen up with all the options but its locked and same error message " d5"

yes, I can fix and work around this but they are annoying the hell out of me, what is it with Gigabyte and USB ?

dont they test their mobos with USb's ????

and does anuone know ehat the D5 message means "no space for legacy Option Rom initialization"

[virtualfred]

Re: More problems with GA Z77X-UD5H

Your BIOS has surely been corrupted while tryings OC, so you have to swith on the B Bios, and flash B Bios to main Bios with Alt + F10 or this method.
You don't give any info about your BIOS version, last betas was F15r mod4 and F16c mod2.

[will_s]

Re: More problems with GA Z77X-UD5H

Not sure if I want to muck around with BIOS anymore, originally had problems like reboot cycle that I fixed through the BIOS and dont want to put back a fresh BIOS that may still have those settings. Not on the PC in question atm so not sure what BIOS I have ( but its not a beta ) ....... I guess if it boots into windows mode and it gives no problems I should leave well alone.
Anyway just googling for D5 error and found one from these forums in May last year and he found the solution was http://forums.tweaktown.com/gigabyte...-freezing.html

"It appears the problem was an old USB joystick. I unplugged it and the problem seems to have gone away."

and another was Gigabyte G1. Sniper 5/5M/3/M3 Owners Thread/Club

I am having a slight problem with my new G1 Sniper 3 board.... I can't go into the bios without it failing on me. Boot up is fine but going into the bios causes a freeze (error code d5). d5 according to the manual is: No Space for Legacy Option ROM initialization.

Anyone have a clue? Where can I find the latest BIOS for the board... maybe updating it will fix me... of course I can't use Q-Flash since it won't load.

Edit: Go figure, I had to remove my Joystick from the USB port and my problems went away... so weird.

and from wikipedia found this

An Option ROM typically consists of firmware that is called by the system BIOS. For example, an adapter card that controls a boot device might contain firmware that is used to connect the device to the system once the Option ROM is loaded.

You know what would be great , if some brilliant person from this group would post a list of what these debug codes actually do or mean . shouldnt take no more then a year or so :-)

[profJim]

Re: More problems with GA Z77X-UD5H

Pages 117 - 120 in the mobo user manual list the debug codes.
RTFM

Some codes are informational, i.e. a process has started and some are error codes.
An individual error code can have more that one cause.

[will_s]

Re: More problems with GA Z77X-UD5H

RTFT :-)

I have read the manual and the question is what does it mean ie. what does " No space for legacy Option ROM initialization mean" ?


"Legacy ROM" refers to the format of the OPROM on the storage controller. There are two firmware standards for PCs, the legacy BIOS standard and the new EFI/UEFI standard. These are standards which specify behaviour, not implementations which must be handled by the manufacturer. Since firmware is minimalistic by design, the motherboard firmware only contains code to initialize the devices on the motherboard. Both standards specify a method of loading a BIOS/EFI compatible OPROM (Option ROM) from an external device such as a VGA adapter, dedicated RAID controller, or add-in storage controller.

Since the specification for BIOS and EFI are different it would be possible to mismatch a BIOS OPROM with an EFI firmware. EFI contains the ability to load and execute BIOS compatible devices, but BIOS does not contain the ability to load EFI devices. Thus, many device manufacturers ship devices with two OPROMs, one which is BIOS compatible and called the "Legacy ROM" and one that is EFI compatible. If the OPROM format is set to "Legacy ROM" it will always use the legacy OM on the device, if it is set to "EFI Compatible" it will use the newer EFI ROM if one is present and the Legacy ROM if one is not.

EFI ROMs are necessary for some of the new firmware level security features as well as for proper EFI boot sequences. For example, installing Windows from an optical disk which is attached to a non-EFI compatible storage controller can cause problems if it is installed to a storage controller which has an EFI compatible ROM.

[will_s]

Re: More problems with GA Z77X-UD5H

Legacy BIOS Option ROM Allocation Considerations
In Legacy BIOS boot mode, PC architecture constraints are placed on Legacy Option ROM allocation. These constraints are not placed on UEFI Option ROMs, which are commonly referred to as UEFI drivers.

The system BIOS allocates 128 Kbytes of address space for Option ROMs. This address space is shared between on-board devices and PCIe plug-in cards. This fixed address space limitation is imposed by the PC architecture and not by the BIOS itself. You can to exhaust the available address space when installing PCIe plug-in cards. When the address space is exhausted, the BIOS displays an Option ROM Space Exhausted message, which means that one or more devices cannot load Option ROMs.

For example, if you install a SCSI PCIe card, you might encounter the following message in Oracle ILOM event log:

Option ROM Space Exhausted - Device XXX Disabled

By default, all on-board Options ROMs are enabled in the BIOS. However, you can disable most of these Option ROMs, unless they are required to support booting from the associated device or to provide some other boot-time function. For example, it is not necessary to load the Option ROM for the on-board network ports unless you mean to boot from one or more network ports (even then, you can disable the Options ROMs for the remaining ports).

To minimize server boot time and reduce the likelihood of exhausting the available Option ROM address space, disable the Option ROMs for all devices that you do not intend to boot from. Enable Option ROMs only for those devices from which you intend to boot.

If you encounter the Option ROM space exhausted condition even after disabling all devices you do not intend to boot from, then disable additional Option ROMs. Under some circumstances it might be necessary to disable Option ROMs for all devices except for the primary boot device.

Related Information

Setting Up the Server With BIOS Setup Utility

Configuring Option ROM Settings

Modify Device Configuration

after a lot of googling I found the above and its interesting that it says that these constraints are not part of uefi