There was mention recently about some changes to APM to fix some "broken"
behavior regarding the way it set/reset values. Some of these were cases
where APM seemed to blindly set values instead of leaving them as is. I
don't remember just how long ago, but you might try looking over the archives.
If this is the case, then it's possible that the APM code was checking
status, and then blindly setting things to suit that status instead of what
was read. Makes sense, but potentially broken. If the BIOS is broken and
doesn't set these values correctly, then this could produce the symptoms
you describe. Check for a BIOS upgrade anyway - usually a good manufacturer
will have some sort of changelog with the BIOS, so if there is a new
version, you might find APM was broken and fixed.
It's also possible that this never made it into those kernels, and they've
been using the broken behavior since 2.4.10 which is causing your problems.
I'd also suggest checking out the latest of the 2.4.14pre* kernels. My
memory of the list (I may be wrong) makes me think the discussion was quite
recent.
Good luck.
AMC Enterprises P/L - Stuart Young
First Floor - Network and Systems Admin
3 Chesterville Rd - sgy@amc.com.au
Cheltenham Vic 3192 - Ph: (03) 9584-2700
http://www.amc.com.au/ - Fax: (03) 9584-2755
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/