lkml.org 
[lkml]   [1998]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Laptop APM failure

> 1) Display blanking:
> I believe this is an XFree bug. An upgrade to the latest version has
> been reported to fix this.

Sorry, I should have mentioned that I don't even have X running on this
laptop. This is strictly a console problem (so far).

> > And I also tried 0x0101, 0x0102 to no avail.

> I've had *one* bug report so far where a faulty BIOS didn't recognize the
> 'FF' lsb to mean 'all such devices' and interpreted 'FF' as 'device number
> 255'. This is clearly a BIOS bug. Upgrading the BIOS fixed the problem,
> but he could hack around it by chaning the above constant '0x01FF' to
> '0x100'.

Yes, I did also try 0x100, but perhaps with 2.1.8x only..

> Your BIOS is more seriously broken: it doesn't recognize the display
> devices at all, hence the 'unrecognized device id' message in the kernel
> logs, which comes straight from the BIOS.

Hmm. How can we explain the fact that it does work in winblows?

> [The mysterious linux-kernel developer you quote was me, BTW. ;-) ]

Hehe... sorry about that. I actually now remember, but had lost your
email address.

> If anyone has one of these marginal BIOSes -- especially one with a
> verified 'works in windows/BSD, not in linux' feature --- and can provide
> a decent disassembly of the BIOS code to allow me to track down this
> anomaly, I'd appreciate it.

Sorry I can't help any further other than to do testing for you.
Thanks for your help,
Dave



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:41    [W:0.020 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site