mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: <linux-kernel@vger.kernel.org>, "Jeff Lessem" <Jeff.Lessem@Colorado.EDU>
Cc: "Philipp Rumpf" <prumpf@mandrakesoft.com>
Subject: Re: PCI oddities on Dell Inspiron 5000e w/ 2.4.x
Date: Sat, 24 Feb 2001 17:28:56 -0500	[thread overview]
Message-ID: <003601c09eb1$2e8063e0$1601a8c0@zeusinc.com> (raw)
In-Reply-To: <200102240941.CAA09708@ibg.colorado.edu> <Pine.LNX.4.10.10102240532030.30331-100000@penguin.transmeta.com> <20010224095447.A28983@mandrakesoft.mandrakesoft.com> <200102241725.KAA19514@ibg.colorado.edu> <20010224115507.B28983@mandrakesoft.mandrakesoft.com>  <200102241836.LAA27025@ibg.colorado.edu>

> In your message of: Sat, 24 Feb 2001 11:55:07 CST, you write:
> >
> >Careful, you're overwriting ACPI data now (and using it as normal RAM).
>
> Hmm, I guess that would be bad.
>
> >Can you try one of a) LILO b) a fixed version of grub c) this patch ?
>
> I tried LILO and the problem did indeed go away when using that.  I
> guess I'll stick with LILO until Linux or grub (whichever is broken)
> is fixed.  There is just something appealing about a proper boot
> console on a PC...

Even though I wasn't much help on this, it's nice to know what was different
on your config that was causing problems while I wasn't seeing any issues.
I sat here for almost an hour last night trying to figure out why your
machines memory map would different than mine (I have 320MB of RAM as well,
so they should have been the same).  The thought that you might be using a
different boot loader never even crossed my mind.  I've always used LILO so
that's why I didn't see any problems.

It's nice to know it wasn't just working for me by accident.

Later,
Tom



      reply	other threads:[~2001-02-24 22:31 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
     [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 [this message]

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='003601c09eb1$2e8063e0$1601a8c0@zeusinc.com' \
    --to=ttsig@tuxyturvy.com \
    --cc=Jeff.Lessem@Colorado.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prumpf@mandrakesoft.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®