nashit.blogg.se - Gigabyte motherboard won t boot

#GIGABYTE MOTHERBOARD WON T BOOT PDF#
#GIGABYTE MOTHERBOARD WON T BOOT UPDATE#

I reconnected all hard drives and the CD drive (the pdf said the 'system' will redetect all devices).

#GIGABYTE MOTHERBOARD WON T BOOT UPDATE#

Update BIOS to F10B, disabling the "Remember DMI" option.

Attempt to boot from the SATA hard drive that has Ubuntu on it, using each of the SATA ports.

Disconnect IDE, reconnect original hard drives.

Just IDE connected, disable SATA controller.

Tried this with "As SATA Type" and with "IDE" set for the port4/5 type

Just IDE connected, mess with the peripheral settings by changing "OnChip SATA Type" to ATHCI, RAID, or IDE.

Disconnect CD drive with SATA and IDE attached, same message.

Disconnect CD drive with only SATA attached, same message.

Disconnect CD drive with only IDE attached, same message.

Disconnect all hard drives, connect IDE, and set BIO to opimised defaults.

Connecting all the hard drives back, with and without the IDE hard drive.

Have the IDE be given priority over other hard drives.

I got a "AMD Data Change.Update New Data to DMI!" message. I disconnected all hard drives, connected the IDE, installed Ubuntu, and rebooted. So today I installed Ubuntu 12.04LTS on an old IDE 160gb hard drive that I had laying around, which would be perfect to use since there is exactly one IDE port on the motherboard. Then I read that it's easiest to have a setup where the OS/Amahi is installed on one small hard drive while the large hard drives are used to keep the files on, this makes it easy to update the OS without worrying about the files. It was using the four SATA hard drives and everything was running smoothly. What happened: I had an Amahi home server running on this PC with Ubuntu 12.04LTS as the OS. Four SATA hard drives, three 2tb and one 1tb.But that's not working right now.Įrror message: AMD Data Change.Update New Data to DMI! So I've previously had this problem when I added new SATA hard drives to an old one, all I had to do was switch hard disk priority to the one I wanted to boot from.