M2N-MX power management under XP

I've got a machine with an M2N-MX mobo. This thing doesn't seem to allow
power management under XP! Even basic things like Standby and Hibernate
are missing. When you press the "Turn Off Computer" button, the only
options are Restart and Turn Off; Standby is greyed out, and Hibernate
isn't even presented as an option in Power Management properties.

I've flashed it to the latest available AMI-BIOS (0704). I've set the
ACPI support from ACPI 1.0 to 2.0 to 3.0 and back down, nothing has
fixed the issue.

I've also got it running under Ubuntu 7.04 64-bit, and it's the same
issues there. Under it, the temperature sensor utilities tell me "no
sensors found". But interestingly the AMD Cool'n'Quiet continues to
work, I see the two processor cores (Athlon X2 4600+) changing speeds up
and down independently like normal.

I have another system with an Asus mobo, M2NPV-VM, with the same basic
chipset (Nforce 430), but with a Phoenix BIOS which is working perfectly.

Any ideas?

Yousuf Khan

Yousuf Khan wrote:
I've got a machine with an M2N-MX mobo. This thing doesn't seem to allow
power management under XP! Even basic things like Standby and Hibernate
are missing. When you press the "Turn Off Computer" button, the only
options are Restart and Turn Off; Standby is greyed out, and Hibernate
isn't even presented as an option in Power Management properties.

I've flashed it to the latest available AMI-BIOS (0704). I've set the
ACPI support from ACPI 1.0 to 2.0 to 3.0 and back down, nothing has
fixed the issue.

I've also got it running under Ubuntu 7.04 64-bit, and it's the same
issues there. Under it, the temperature sensor utilities tell me "no
sensors found". But interestingly the AMD Cool'n'Quiet continues to
work, I see the two processor cores (Athlon X2 4600+) changing speeds up
and down independently like normal.

I have another system with an Asus mobo, M2NPV-VM, with the same basic
chipset (Nforce 430), but with a Phoenix BIOS which is working perfectly.

Any ideas?

Yousuf Khan

If you go to Device Manager, and check the properties of "Computer",
does it say "Standard PC" or "ACPI Multiprocesssor PC" ? If the HAL
is "Standard PC", that would explain the limited options to turn off
the computer.

If you did a clean install, did you get an error message, about some
problem with ACPI ? Like "not compliant" ? I had that happen with one
Asus BIOS, where when I tried to install, the ACPI tables from the BIOS,
were not to the OS installer's liking. I ended up with a "Standard PC"
as a result, and had to endure that "it is safe to turn off your PC"
crap.

Once I tried a later version of the BIOS, then I could install an
ACPI HAL, as normal.

Some HAL changes are easy. Changing from one flavor of ACPI HAL
to another, is a "driver change". But I suspect that escaping from
"Standard PC" is not going to be so easy.

http://support.microsoft.com/kb/237556/en-us

During an OS install, you can press F5 to force a HAL. Normally
I think it would select an ACPI HAL without any coaching, if
the ingredients are there.

http://support.microsoft.com/kb/299340/en-us

Also, when using Ubuntu, did you examine the log messages that
occur during boot ? Were there any complaints about the ACPI tables
passed by the BIOS ? You might get more useful info from Linux, than
from Windows, if there is a problem.

There are also a couple of reports here, of weirdness with that
motherboard. One guy could not get both cores to be recognized
when using a dual core processor. (Make sure you report your problem
to Asus tech support, so maybe in three months time, you'll see
a new BIOS release with a fix. Asus is probably not monitoring
these forums, looking for trouble.)

http://vip.asus.com/forum/topic.aspx...ge=1&count=100

Paul

On Jun 8, 1:03 am, Paul wrote:
If you go to Device Manager, and check the properties of "Computer",
does it say "Standard PC" or "ACPI Multiprocesssor PC" ? If the HAL
is "Standard PC", that would explain the limited options to turn off
the computer.

It says ACPI Multiprocessor PC.

If you did a clean install, did you get an error message, about some
problem with ACPI ? Like "not compliant" ? I had that happen with one
Asus BIOS, where when I tried to install, the ACPI tables from the BIOS,
were not to the OS installer's liking. I ended up with a "Standard PC"
as a result, and had to endure that "it is safe to turn off your PC"
crap.

Yeah, it was a clean install, no problems, which is what's surprising
me about this problem. The only problem I see in the hardware is a
little yellow exclamation point on some USB composite device, but
everything else is working fine, including all USB devices.

Speaking of turning off your PC, when I do choose "Turn off PC", it
doesn't turn off, it reboots. I have to quickly press the power button
before it boots to an OS again.


Also, when using Ubuntu, did you examine the log messages that
occur during boot ? Were there any complaints about the ACPI tables
passed by the BIOS ? You might get more useful info from Linux, than
from Windows, if there is a problem.

No, I didn't check the messages in Ubuntu yet, but I did check the
Windows logs, and there were no alerts of any kind in there. I don't
know if I have to set some error-check level in Windows to see any
messages of this type though.

Throwing something else out from out of left-field. Earlier during the
installation process for this machine I was experimenting with trying
to get the Xen virtualization hypervisor going with Ubuntu. I couldn't
get it going, so I reinstalled Ubuntu from scratch without any of the
Xen stuff in there. I'm wondering if maybe some kind of Xen stub is
left behind that gets loaded automatically -- and invisibly -- with
Grub? This might explain the reduction of features in the PC: they're
being virtualized away. It's a very slim chance, I'll admit.

There are also a couple of reports here, of weirdness with that
motherboard. One guy could not get both cores to be recognized
when using a dual core processor. (Make sure you report your problem
to Asus tech support, so maybe in three months time, you'll see
a new BIOS release with a fix. Asus is probably not monitoring
these forums, looking for trouble.)

http://vip.asus.com/forum/topic.aspx...ard_id=1&model...

I guess I'll have to bite the bullet and call them.

bbbl67 wrote:
On Jun 8, 1:03 am, Paul wrote:
If you go to Device Manager, and check the properties of "Computer",
does it say "Standard PC" or "ACPI Multiprocesssor PC" ? If the HAL
is "Standard PC", that would explain the limited options to turn off
the computer.

It says ACPI Multiprocessor PC.

If you did a clean install, did you get an error message, about some
problem with ACPI ? Like "not compliant" ? I had that happen with one
Asus BIOS, where when I tried to install, the ACPI tables from the BIOS,
were not to the OS installer's liking. I ended up with a "Standard PC"
as a result, and had to endure that "it is safe to turn off your PC"
crap.

Yeah, it was a clean install, no problems, which is what's surprising
me about this problem. The only problem I see in the hardware is a
little yellow exclamation point on some USB composite device, but
everything else is working fine, including all USB devices.

Speaking of turning off your PC, when I do choose "Turn off PC", it
doesn't turn off, it reboots. I have to quickly press the power button
before it boots to an OS again.


Also, when using Ubuntu, did you examine the log messages that
occur during boot ? Were there any complaints about the ACPI tables
passed by the BIOS ? You might get more useful info from Linux, than
from Windows, if there is a problem.

No, I didn't check the messages in Ubuntu yet, but I did check the
Windows logs, and there were no alerts of any kind in there. I don't
know if I have to set some error-check level in Windows to see any
messages of this type though.

Throwing something else out from out of left-field. Earlier during the
installation process for this machine I was experimenting with trying
to get the Xen virtualization hypervisor going with Ubuntu. I couldn't
get it going, so I reinstalled Ubuntu from scratch without any of the
Xen stuff in there. I'm wondering if maybe some kind of Xen stub is
left behind that gets loaded automatically -- and invisibly -- with
Grub? This might explain the reduction of features in the PC: they're
being virtualized away. It's a very slim chance, I'll admit.

There are also a couple of reports here, of weirdness with that
motherboard. One guy could not get both cores to be recognized
when using a dual core processor. (Make sure you report your problem
to Asus tech support, so maybe in three months time, you'll see
a new BIOS release with a fix. Asus is probably not monitoring
these forums, looking for trouble.)

http://vip.asus.com/forum/topic.aspx...ard_id=1&model...

I guess I'll have to bite the bullet and call them.


Can you test with a spare disk and just install Windows on it ?
Just to see if sanity is at all possible.

Paul

On Jun 8, 7:43 am, Paul wrote:
I guess I'll have to bite the bullet and call them.

Can you test with a spare disk and just install Windows on it ?
Just to see if sanity is at all possible.

Just as an update. Well, I did get through to Asus tech support
finally. Told their tech support guy the symptoms under Windows XP. I
also then made the fatal mistake of mentioning that I had Linux
installed on the box. Well, it is usually a fatal mistake because tech
support is usually looking for any excuse to pass off the blame on
anything that they can. I told him that the same problems were
occurring under Ubuntu Linux, and to my astonishment, this technician
actually said that that proved to him that there was a problem with
the motherboard! He told me to get in touch with their RMA department.
Anyways, the techsup guy thinks that perhaps the sensor chips on the
board are defective.

Yousuf Khan

bbbl67 wrote:
On Jun 8, 7:43 am, Paul wrote:
I guess I'll have to bite the bullet and call them.
Can you test with a spare disk and just install Windows on it ?
Just to see if sanity is at all possible.

Just as an update. Well, I did get through to Asus tech support
finally. Told their tech support guy the symptoms under Windows XP. I
also then made the fatal mistake of mentioning that I had Linux
installed on the box. Well, it is usually a fatal mistake because tech
support is usually looking for any excuse to pass off the blame on
anything that they can. I told him that the same problems were
occurring under Ubuntu Linux, and to my astonishment, this technician
actually said that that proved to him that there was a problem with
the motherboard! He told me to get in touch with their RMA department.
Anyways, the techsup guy thinks that perhaps the sensor chips on the
board are defective.

Yousuf Khan


It'll be interesting to see if an RMA can fix it.
Usually on those boards, the hardware monitor is part of the SuperI/O
chip. If the SuperI/O was bad, you'd think there would be other
symptoms, such as defective floppy, serial port, parallel port etc.
It would be a bit strange for only the sensor section to be bad.

Paul

Paul wrote:
It'll be interesting to see if an RMA can fix it.
Usually on those boards, the hardware monitor is part of the SuperI/O
chip. If the SuperI/O was bad, you'd think there would be other
symptoms, such as defective floppy, serial port, parallel port etc.
It would be a bit strange for only the sensor section to be bad.


The thing is, it's possible that all of those things are bad too, but it
also happens to be a whole bunch of the things that we're *not* using.
No floppy drive attached on the system, no need for serial port, printer
services is obtained through USB or network, etc. Super I/O is old
legacy stuff these days.

Yousuf Khan

Paul wrote:
It'll be interesting to see if an RMA can fix it.
Usually on those boards, the hardware monitor is part of the SuperI/O
chip. If the SuperI/O was bad, you'd think there would be other
symptoms, such as defective floppy, serial port, parallel port etc.
It would be a bit strange for only the sensor section to be bad.

Paul

It didn't fix a thing. According to the worksheet, they replaced the
board with a new board, but the exact same issues are cropping up again.
I don't know if I want to bother with RMA'ing it again.

Yousuf Khan

Yousuf Khan wrote:
Paul wrote:
It'll be interesting to see if an RMA can fix it.
Usually on those boards, the hardware monitor is part of the SuperI/O
chip. If the SuperI/O was bad, you'd think there would be other
symptoms, such as defective floppy, serial port, parallel port etc.
It would be a bit strange for only the sensor section to be bad.

Paul

It didn't fix a thing. According to the worksheet, they replaced the
board with a new board, but the exact same issues are cropping up again.
I don't know if I want to bother with RMA'ing it again.

Yousuf Khan


What BIOS revision is installed in the board now ? I took a look
at the BIOS info on the Asus download site for M2N-MX, but the change log
doesn't mention anything close to your symptoms. Other than
changing BIOS versions, I would go back to software testing.

On shutdown, is it still automatically restarting again ?
Sometimes that is related to the Magic Packet wakeup feature
of a network interface, as some network interfaces basically
wake up when any packet is received. Disconnecting the network
cable, then testing shutdown, may show a difference in behavior,
if that is the case.

Paul

In article , says...
Yousuf Khan wrote:
Paul wrote:
It'll be interesting to see if an RMA can fix it.
Usually on those boards, the hardware monitor is part of the SuperI/O
chip. If the SuperI/O was bad, you'd think there would be other
symptoms, such as defective floppy, serial port, parallel port etc.
It would be a bit strange for only the sensor section to be bad.

Paul

It didn't fix a thing. According to the worksheet, they replaced the
board with a new board, but the exact same issues are cropping up again.
I don't know if I want to bother with RMA'ing it again.

Yousuf Khan


What BIOS revision is installed in the board now ? I took a look
at the BIOS info on the Asus download site for M2N-MX, but the change log
doesn't mention anything close to your symptoms. Other than
changing BIOS versions, I would go back to software testing.

On shutdown, is it still automatically restarting again ?
Sometimes that is related to the Magic Packet wakeup feature
of a network interface, as some network interfaces basically
wake up when any packet is received. Disconnecting the network
cable, then testing shutdown, may show a difference in behavior,
if that is the case.

Or mouse. My wife's ThinkPad was waking up randomly. It turned out
the mouse was set to wake it up. The slightest vibration, such as
waking by, would set it off.

--
Keith