mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Douglas <brad@neruo.com>
To: barryn@pobox.com
Cc: Tom Sightler <ttsig@tuxyturvy.com>,
	Jeff Lessem <Jeff.Lessem@Colorado.EDU>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
Date: 23 Feb 2001 00:40:27 -0800	[thread overview]
Message-ID: <20010223084216Z129272-30605+335@vger.kernel.org> (raw)
In-Reply-To: <200102230701.XAA02164@cx518206-b.irvn1.occa.home.com>

On 22 Feb 2001 23:01:14 -0800, Barry K. Nathan wrote:
> Tom Sightler wrote:
> > What's strange is that I have the exact same type of machine and I don't see
> > this problem, could you forward me your kernel config as well?  I'll compare
> > that, and your info from your previous message to mine and see if we can
> > find a difference.
> 
> Another variable, perhaps, is the BIOS version. (If you have Quick Boot or
> whatever it's called enabled (which is the factory default), you'll have
> to hit F2 when the "Dell" screen appears at startup, to try to enter the
> BIOS setup (before Setup starts, it will show the BIOS version number and
> a bunch of other stuff).)
> 
> I have a working machine, with BIOS A04. (Strangely enough, my Inspiron
> 5000e came with BIOS A03, and a floppy disk with A04, along with
> instructions with a "do not use this BIOS flasher unless you have [some
> werid video-related problem]" type of disclaimer. Since I was having those
> APM oopses under Linux, I decided to try upgrading. It didn't fix the
> oopses, though.)

I have a BIOS that'll fix your APM problems, at a minimum.  Anyone who
wants it can email me privately, since the site I put it up on no longer
exists...

Brad Douglas
brad@neruo.com
http://www.linux-fbdev.org



  reply	other threads:[~2001-02-23  8:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22  7:18 Jeff Lessem
     [not found] ` <000201c09d0c$d53a73c0$25040a0a@zeusinc.com>
2001-02-23  3:27   ` Jeff Lessem
2001-02-23  4:45     ` Tom Sightler
2001-02-23  7:01       ` Barry K. Nathan
2001-02-23  8:40         ` Brad Douglas [this message]
     [not found]   ` <200102230340.TAA19644@penguin.transmeta.com>
2001-02-23  4:06     ` Jeff Lessem
2001-02-23  4:37       ` Linus Torvalds
2001-02-23  5:34         ` Jeff Lessem
2001-02-23 17:48           ` Linus Torvalds
2001-02-24  9:41             ` Jeff Lessem
2001-02-24 13:36               ` Linus Torvalds
2001-02-24 15:54                 ` Philipp Rumpf
2001-02-24 17:25                   ` Jeff Lessem
2001-02-24 17:55                     ` Philipp Rumpf
2001-02-24 18:36                       ` Jeff Lessem
2001-02-24 22:28                         ` Tom Sightler

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=20010223084216Z129272-30605+335@vger.kernel.org \
    --to=brad@neruo.com \
    --cc=Jeff.Lessem@Colorado.EDU \
    --cc=barryn@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttsig@tuxyturvy.com \
    /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®