Aopen Digital Engine DEX 4501 Mobo I45GMT-HC

[paredown]

This machine has AMI BIOS ver. 2.06, with very few options enabled.

Latest version of the Bios is ver. R. 1.06 downloadable here:
http://global.aopen.com/products_downloa...?auno=2890

In addition to a little more control, I also seem to have problems with the onboard NIC. I wondered if there had been something set to deactivate the NIC while it was in the field, and whatever that might be is not getting reset when flashing?

When I got the machine it had a branded splash screen and an older bios version. Flashing it to 1.06 gave me the Aopen "Digital Engine" splash screen, but I really struggled to activate the NIC. I did a clear Cmos, remove battery and "Load Optimal Setings" before it would activate. I just swapped in a faster processor, and the Nic stopped working again, and I had another struggle to get it working.  (I used the AFUDOS filename.ROM  /P /B /N /C recommended by Aopen.) I thought I might have better luck if I flashed it at the first released bios, but that did nothing either. Currently it is at 1.06--the latest version.

There is a companion bios for a slightly different I45GMT motherboard (have one of those as well)--and the bios for it is at release 1.07 here:
http://global.aopen.com/products_downloa...?auno=2664
(No troubles with the NIC on this one; it has the MoDT splash screen)
I can see no difference in functionality and in fact tried this bios on the DEX4501 as well, but it too did not magically make the NIC work consistently.

A modded bios for both or just for the DEX4501 would be appreciated.

(I originally posted this in the wrong forum-the Award forum--mods can delete...)

[BDMaster]

AMI Aptio tools :

https://www.bios-mods.com/downloads/

AMIBcp_v.3.46.exe

Follow this tutorial :


http://forums.mydigitallife.info/threads...MSR-unlock!

Follow CodeRush Suggestions :

It's certanly not so easy for BIOSes with another menu setup, but the whole idea is the same.
I could also recommend trying AMIBCP to modify menu entries vilibility from "Default" to "USER",
if your menu setup is more complex then a setup above.

I have to flash my image on the administrator commandline using afuwinx64 bios_mod.rom /GAN . . .
Otherwise it gives me a security error (Thanks again CodeRush)

Let me know
Regards

P.S. You can use Intel FPT too to make a Backup and rewrite back It !

[paredown]

AMI Aptio tools :

https://www.bios-mods.com/downloads/

AMIBcp_v.3.46.exe

Follow this tutorial :


http://forums.mydigitallife.info/threads...MSR-unlock!

Follow CodeRush Suggestions :

It's certanly not so easy for BIOSes with another menu setup, but the whole idea is the same.
I could also recommend trying AMIBCP to modify menu entries vilibility from "Default" to "USER",
if your menu setup is more complex then a setup above.

I have to flash my image on the administrator commandline using afuwinx64 bios_mod.rom /GAN . . .
Otherwise it gives me a security error (Thanks again CodeRush)

Let me know
Regards

P.S. You can use Intel FPT too to make a Backup and rewrite back It !

Well that was fun--although inconclusive.

I used AMIBCP to change visibility on some items--flashed the modified bios back and didn't brick the mobo.

What the bios does not seem to have is any settings for power management--no way to set s3,s4 etc. And it seems like the Nic gets stuck in the wrong state, so on boot it gets a link light, then at the point where Windows checks the card as it boots, it gets a wrong state error, and fails to finish loading the device (code 10).

The bios does have settings to turn Lan on/off, do Wake on Lan, and there is choice on boot to press F12 for network boot (which seems to do nothing). It's like the nic controls were only partially implemented. On the desktop there is no choice for Sleep...

I don't know what to do next--


 

[paredown]

AMI Aptio tools :

https://www.bios-mods.com/downloads/

AMIBcp_v.3.46.exe

Follow this tutorial :


http://forums.mydigitallife.info/threads...MSR-unlock!

Follow CodeRush Suggestions :

It's certanly not so easy for BIOSes with another menu setup, but the whole idea is the same.
I could also recommend trying AMIBCP to modify menu entries vilibility from "Default" to "USER",
if your menu setup is more complex then a setup above.

I have to flash my image on the administrator commandline using afuwinx64 bios_mod.rom /GAN . . .
Otherwise it gives me a security error (Thanks again CodeRush)

Let me know
Regards

P.S. You can use Intel FPT too to make a Backup and rewrite back It !

Well that was fun--although inconclusive.

I used AMIBCP to change visibility on some items--flashed the modified bios back and didn't brick the mobo.

What the bios does not seem to have is any settings for power management--no way to set s3,s4 etc. And it seems like the Nic gets stuck in the wrong state, so on boot it gets a link light, then at the point where Windows checks the card as it boots, it gets a wrong state error, and fails to finish loading the device (code 10).

The bios does have settings to turn Lan on/off, do Wake on Lan, and there is choice on boot to press F12 for network boot (which seems to do nothing). It's like the nic controls were only partially implemented. On the desktop there is no choice for Sleep...

I don't know what to do next--


 

The absence of 'Sleep' choice on desktop was user error--I had to reactivate stuff in the bios that I turned off while playing around.

Well, I found a thread on a Dell forum discussing NICs that get confused about sleep mode. For the record, I think I have a method that will get the embedded nic working--not 100%, but close. In my case, I have tried this with Vista x64 and Win7 x64. You need to install the latest Intel driver with proset (Last version that supports Vista is 18.2) and install. Reboot to desktop. Force the computer to enter sleep mode. Exit sleep mode, and shut down cleanly. Disconnect NIC, disconnect power. Hit the on button to drain any residual power in caps. Connect NIC cable. then power supply. Start computer and you should see the Nic fire up at the point in the boot cycle where it is recognized by Windows.

I have no idea if the problems are because they didn't implement the full code for the PXe environment, if something gets dropped between the laptop chipset auto power save features and Windows, or if there is some kind of bug in the earlier Intel driver set? (There is some internet chatter about some of these onboard Giga nics with persistent driver problems with negotiation..)

Anyways, not a bios problem per se, but it was fun to try out my very own modded bios!