> crash and a serious root fs corruption 10 hours after boot? At least
> with E820 (if we do not expect to work for all machines) people will see
> at boot time that memory was misdetected.
Not when the machine reports ROM as writable and other stupidities
-
To unsubscribe from this list: send t
Alan Cox wrote:
>
> > 2.2.18-pre with good results on Thinkpad 600x. No adverse consequencies
> > (memory is reported correctly, suspend/hibernate work fine). I also had
> > a chance to use it on several big SMP and UP servers (where e801 memory
> > reporting works fine) Intel, Compaqs and IBM. N
> 2.2.18-pre with good results on Thinkpad 600x. No adverse consequencies
> (memory is reported correctly, suspend/hibernate work fine). I also had
> a chance to use it on several big SMP and UP servers (where e801 memory
> reporting works fine) Intel, Compaqs and IBM. No adverse consequencies
> e
Alan, can we integrate e820 memory detection into 2.2.18 / 2.2.19? The
backport (from 2.4) patch is available at
http://www.pell.portland.or.us/~orc/Memory/2214.fancy.diff .
It applies cleanly to 2.2.14-2.2.18pre. I have been using it with
2.2.18-pre with good results on Thinkpad 600x. No adver
On Wed, Oct 11, 2000 at 12:01:23PM -0500, Sudhindra Herle wrote:
> > The BIOS E801 memory reporting is buggy on a lot of these
> > boards. Since the
> > vendors dont appear to care you probably want to pass
> > mem=383M or mem=384M
> > depending if the BIOS uses top of memory for stuff on boot
Thanks Alan!
In fact, I tested mem=384M and it seems to _not_ crash. So, I assume that it
works.
> The BIOS E801 memory reporting is buggy on a lot of these
> boards. Since the
> vendors dont appear to care you probably want to pass
> mem=383M or mem=384M
> depending if the BIOS uses top of me
> The weird thing is Linux only sees 64MB of RAM! The BIOS sees 384MB of RAM.
> I am working around this by saying "mem=384M" on the cmdline.
The BIOS E801 memory reporting is buggy on a lot of these boards. Since the
vendors dont appear to care you probably want to pass mem=383M or mem=384M
dep
I am running 2.2.17 + reiserfs patches on Athlon-700 on FIC-SD11 with 384MB
of RAM.
The weird thing is Linux only sees 64MB of RAM! The BIOS sees 384MB of RAM.
I am working around this by saying "mem=384M" on the cmdline.
Additional h/w include: 3 Quantum 15GB disks, 52x IDE CDROM, Dlink
Quad-et
8 matches
Mail list logo