GA-MA790FXT-UD5P: Lower DDR3 voltage to 1.5v?

[Beekeeper]

I use many operating systems, as a PC hardware tech I come across lots of different op systems in use by customers, so I have about 5 installed at the moment.
Also I've been a Beta tester for Microsoft since Win 98SE.
When web browsing and doing day to day stuff Ubuntu AMD64 is my system of choice.

5 systems (what are these?) in one PC , how can you manage this? i look up to you. i tried myself Win XP + Ubuntu but it was not success, maybe i did not have enough patience and time to fight it.

[illogical]

dmesg output attached.

[stuart]

Many thanks for that - I now seem to have solved the problem: I upgraded from DOS, and all of the problems (Linux booting issues, NIC problems, etc.) went away.  To test this, I then downgraded and upgraded again using my original method - using the Gigabyte @BIOS tool under 64bit Windows 7 (which I have legitimately from a Microsoft Technet subscription).  Lo and behold, all of the problem returned.  On performing the upgrade from DOS again, the problems again went away.

My conclusion?  @BIOS should be considered dangerous, and should not be used.

The great news is that everything now seems to be working as intended - I just need a way to run my RAM at 1.5v!

[illogical]

No problem happy to be of assistance.
Beekeeper, the Operating systems I have currently installed are;
On the RAID array, I have Ubuntu AMD64 & Windows XP Pro 32 bit.
On one of my Seagate drives I have for partitions with 3 operating systems, these are all 64 bit;
Vista
XP
Windows 7 Enterprise.
I also have a small (40gig) IDE drive running OSX Panther.
The RAID array is using Grub to select operating system.
The Seagate is under control of the Windows 7 boot loader, I then use the F12 key to get BIOS based Boot Manager and select the Disc to boot from.
No way would I consider trying to use a boot manager for all the lot.

BTW anyone have a link fot the F7 BIOS I've searched everywhere and can find lots of people mentioning it but no link to access it.

[stuart]

G'ah! It's still happening, but no longer all the time now.  After loading Windows 7, a reboot into Linux triggers the APIC problem (although I also powered down an eSATA drive), but powering the machine off completely and starting Linux works correctly.

This is an improvement, since before I upgraded the BIOS from DOS this bad behaviour would occur on every boot.

It makes be think that the BIOS isn't completely resetting the state of the machine on reboot - what else could trigger these issues?

[Beekeeper]

........My conclusion?  @BIOS should be considered dangerous, and should not be used.......

fully agree m8!

[Beekeeper]

No problem happy to be of assistance.
Beekeeper, the Operating systems I have currently installed are;
On the RAID array, I have Ubuntu AMD64 & Windows XP Pro 32 bit.
On one of my Seagate drives I have for partitions with 3 operating systems, these are all 64 bit;
Vista
XP
Windows 7 Enterprise.
I also have a small (40gig) IDE drive running OSX Panther.
The RAID array is using Grub to select operating system.
The Seagate is under control of the Windows 7 boot loader, I then use the F12 key to get BIOS based Boot Manager and select the Disc to boot from.
No way would I consider trying to use a boot manager for all the lot.

BTW anyone have a link fot the F7 BIOS I've searched everywhere and can find lots of people mentioning it but no link to access it.

nice set of OS'es.

F7 bios is normally available at : http://www.giga-byte.co.uk/Support/Motherboard/BIOS_Model.aspx?ProductID=3005
while previous beta version (F7a) was mentioned in this post: http://forum.giga-byte.co.uk/index.php/topic,449.msg2499.html#msg2499