Questions about GIGABYTE products > X99 Motherboards
GA-X99-UD4 can't go to bios setup
dmdilks:
--- Quote from: Extradry on December 09, 2014, 12:42:34 pm ---Well so I pulled all the drives out and set the PCH to RAID and it worked! Although i had to go back to ACHI and into windows to change the registry from ACHI to RAID but it worked. Thanks alot mate that had me stumped for a while!
--- End quote ---
The thing is on that Intel controller the AHCI & Raid are basically the same. On the other controller you can only run that one IDE or AHCI. Now if it is working that way that is all that matters right.
Curvin:
I have just encountered this one as well.
Windows 7 Pro SP1 x64 , so it doesn't have nothing to do with Windows 8.
Samsung 850 Pro SSD / Seagate 1 and 2TB SATA HD's.
X99 UD4 Rev 1.0 BIOS F11 and F12 , it will not enter BIOS if any SSD's or HD's are attached. aThe work around of shifting the controllers to RAID from AHCI is not acceptable to me , Gigabyte need to address this directly and correctly.
I have a development/test system using the same board which is on an earlier BIOS ( F5 ), and it does not display the behaviour, so it is something that has been introduced in the later BIOS's.
An interesting point is that I had managed to do a final configuration of the BIOS after flashing the latest official F11 BIOS , with all HD's attached, but since that initial set up I have not been able to enter BIOS with SSD/HD's attached.
V.C
DropBear:
As it turns out, the Samsung 850 series SSDs are not currently on the qualified list of supported SSDs.
Follow the the 'SSD Support List' link on the page to check your SSD.
http://www.gigabyte.com/products/product-page.aspx?pid=5284&dl=1#
Curvin:
I am still currently trying to pinpoint the exact cause but I can inform those reading in that it has nothing to do with model/vendor of SSD.
I have also tested Intel 520 / Samsung 840 Pro, both on the compatibility list , with the same deployed Windows 7 SP1 Pro image and each SSD prior to imagining would enter BIOS fine , but as soon as it is imaged will display the same issue.
Reverting back to a base image and the issue is not present.
In short , an installation or configuration on Windows has somehow tripped this issue, which I need to clarify so that it does not happen on future installs. I am a specialist system builder, this is not a one off build, so I need to have the issue clarified and resolved before I can deploy systems to clients.
V.C
wrangler:
I haven't been able to try it yet but someone told me that a workaround is using F12, like your going to select a boot device and then selecting to enter setup as opposed to hitting the Del key to enter bios.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version