More data..for what it's worth....
I have a Supermicro P6DGE bios 2.2 at home with dual PII 400s, 128 MB,
RedHat 6.0 with some package upgrades, and kernel 2.3.19. All
memory is identified. At work I've been building a Beowulf
with P6DBEs (256 MB) and a P6DGU (512 MB) both bios rev
2.2, dual PIII600s, and RedHat 6.1. These only identify 64MB and
I've had to use the "append" option.
Hermann Himmelbauer wrote:
> Sketch wrote:
> >
> > On Fri, 3 Dec 1999, Robert G. Brown wrote:
> >
> > > Finally I noted that I could boot the system with the linux-up kernel
> > > (uniprocessor) after a clean install. I discovered further that the
> > > kernel was only identifying the system as having 64 MB of memory instead
> > > of the 384 MB it actually has. No problem, I added the usual append
> > > line to lilo.conf and voila! The system would boot EITHER UP or SMP. A
> > > bit disappointing to learn a) that even a driver-free SMP 2.2 kernel +
> > > aic7xxx driver won't boot in at least this system with only 64 MB to
> > > boot in -- have no idea where the failure lives, but it is most annoying
> > > and occurs consistently with 2.2.5 (RH 6.0) 2.2.10 (homemade), 2.2.12
> > > (RH 6.1) and 2.2.13 (homemade); and b) that 2.2 kernels still don't
> > > autodetect memory on at least some systems that aren't THAT old.
> >
> > I have two Supermicro DBE (BX) boards at work with dual 400's, both with
> > 256MB of RAM. One is running RH5.2 upgraded to 2.2.13 with software raid1
> > on IDE, the other is a clean RH6.1 install with a Mylex DAC960. Both have
> > 3c59x NICs, and neither will recognize more than 64MB of RAM.
> >
> > My guess is it's either an issue with recent Supermicro (SMP?) boards, or
> > Redhat's LILO is broken and forces 64MB unless told otherwise. I have not
> > used Redhat with 2.2 on any non-supermicro boards with more than 64MB of
> > RAM, so I can't rule out the second possibility.
>
> The problem has definitely nothing to do with SMP, I recently
> experienced this on my old 486 with 96MB RAM.
>
> Put in the file "/etc/lilo.conf" the following line:
>
> append="mem=256M"
>
> The whole thing is somehow strange: On some machines the whole memory is
> detected and used without this parameter and on other systems it is not.
> AFAIK the problem does not depend on LILO, it depends on the kernel
> itself as this "append" parameter simply passes the "mem"-Variable to
> the kernel. I think the whole thing has something to do with a backwards
> compatibility issue.
>
> To my mind the real bad thing about this problem is that for sure many
> "Linux-newbies" do not check the memory usage and see their systems
> swapping and slowing down and do not experience Linux as it could be.
>
> Regards,
> Hermann
>
> --
> Hermann Himmelbauer
> E-Mail: [EMAIL PROTECTED]
> Addr. : A-3400 Klosterneuburg, Martinstr. 18/2 Austria (Europe)
> Tel. : ++43-2243-26562, ++43-2243-22305-24, Fax: ++43-2243-22305-27
> -
> Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
> To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/dmentre/smp-howto/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
