From: Pavel Machek <pavel@suse.cz>
To: "John D. Kim" <johnkim@aslab.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dax Kelson <dax@gurulabs.com>, linux-kernel@vger.kernel.org
Subject: Re: APM oops with Dell 5000e laptop
Date: Sat, 18 Nov 2000 22:02:14 +0100 [thread overview]
Message-ID: <20001118220214.E382@bug.ucw.cz> (raw)
In-Reply-To: <E13wTbc-0008BC-00@the-village.bc.nu> <Pine.LNX.4.04.10011161254110.2078-100000@mail.aslab.com>
In-Reply-To: <Pine.LNX.4.04.10011161254110.2078-100000@mail.aslab.com>; from John D. Kim on Thu, Nov 16, 2000 at 01:04:41PM -0800
Hi!
> > > Is there a way to uniquely identify the affected BIOSes at boot time and
>
> > Im looking at one with some pointers from Dell. It won't be in 2.2.18 so its
> > quite likely a fixed BIOS will be out first anyway.
>
> Wherever the fix comes from, I sure hope it comes soon, because it's
> getting harder and harder to find cpus for the original 5000 series. And
> this new model's been sitting on my desk for couple of weeks now
> collecting dust.
Disable apm and be done with that!
I do not see why this is a problem. Just add comment to apm.c, there
are more comments about b0rken machines in there.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
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/
next prev parent reply other threads:[~2000-11-18 22:31 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 [this message]
2000-11-16 20:08 ` Brad Douglas
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=20001118220214.E382@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dax@gurulabs.com \
--cc=johnkim@aslab.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