mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Douglas <brad@neruo.com>
To: Dax Kelson <dax@gurulabs.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: APM oops with Dell 5000e laptop
Date: 17 Nov 2000 04:08:55 +0800	[thread overview]
Message-ID: <20001116203922Z129069-521+734@vger.kernel.org> (raw)
In-Reply-To: <Pine.SOL.4.30.0011161054420.16124-100000@ultra1.inconnect.com>

> Alan Cox said once upon a time (Thu, 16 Nov 2000):
> 
> > > I just got a Sceptre 6950 (also known as a Dell 5000e), I just installed
> > > Red Hat 7.0 on it, and got an APM related oops at boot.
> >
> > Yep. This is not a Linux problem
> 
> The kernel works around/ignores/disables other broken hardware or broken
> features of otherwise working hardware with black lists.  There will be
> many *many* of these laptops sold.

Unlike other BIOS, this cannot be fixed up and I don't believe there is an easy way to identify every single "version" of this machine (Stephen Rothwell, can you comment here?).
That broken call is a major part of the Linux APM system.  The simplest (and arguably, best) solution is to just not compile it into the kernel or add "apm=off" to lilo.conf until the problem is fixed.

> Is there a way to uniquely identify the affected BIOSes at boot time and
> turn off APM?  According to Brad Douglas, the 32-bit Get Power Status
> (0AH) call is broken.

I do not believe so.  I tend to think that detecting these broken models is a waste of kernel code (especially, if there's an effort to correct the problem).

> Supposedly there will be a BIOS update in the "future" to correct this
> problem.

This is what we have been led to believe.  I have no ETA at this time.

Brad Douglas
brad@neruo.com
brad@tuxtops.com


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-16 20:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 22:34 toshoboe.c typo in linux-2.4.0-test11-pre4 Adam J. Richter
2000-11-13 22:54 ` APM oops with Dell 5000e laptop Dax Kelson
2000-11-13 23:04   ` Brad Douglas
2000-11-16 16:06   ` Alan Cox
2000-11-16 17:59     ` Dax Kelson
2000-11-16 18:17       ` Alan Cox
2000-11-16 21:04         ` John D. Kim
2000-11-16 21:21           ` Barry K. Nathan
2000-11-18 21:02           ` Pavel Machek
2000-11-16 20:08       ` Brad Douglas [this message]
2000-11-16 21:43         ` Alan Cox
2000-11-16 23:40           ` Brad Douglas
2000-11-17 10:49             ` Alan Cox
2000-11-17 18:57               ` Brad Douglas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001116203922Z129069-521+734@vger.kernel.org \
    --to=brad@neruo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dax@gurulabs.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®