Perhaps windows is using VESA screen blanking instead of APM screen
blanking?
A perusal of the linux code seemed to indicate that VESA blanking would
be
attempted if APM blanking failed, but perhaps I wasn't reading as
carefully as I should have been?
--Scott
Vesa unblanking gets called regardless because the VESA routines are
used to get the right stuff back to the right console. I tried changing
to only get called if APM unblank failed, and got some weird screens :)
I also fiddeld with the time of the console blank interval and the BIOS
blank time to figure out what was blanking the X screen but not turning
off the back light. It is clearly the VESA stuff, indicating that APM is
failing, but I do not get an error msg. with Ox0100 setting. If X is not
running at all, APM works great, but if X is running and I'm on a non X
vc, the backlight goes off, but comes back on after a few minutes. Have
not tried upgrading X yet. (BIG DOWNLOAD). I don't do windows anymore,
but when I did it worked fine.
I do think that some of the problem may be in the vesa code rather than
the apm_bios.c code. Guess it time to bite the bullet on X.
-- Garst- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu