> > > > I don't think this is an SMP problem at all. Linux will
> normally only see
> > > > and ause the first 64 MB of RAM. In order to make it see
> and use more, you
> > > > have to tell it to do so.
> > > >
> > > > You do that by specifying the additional boot parameter to
> the kernel:
> > > > "mem=<YourMemorySize>"
> > >
> > > Is it really the case with 2.2.x kernels?
> > > I just set up a Bi-PII box with SuSE 6.1 and
> > > SMP-recompiled 2.2.10 stock kernel, which seems to recognize
> > > all the 256 Mo memory without specifiying "mem=xxx" anywhere?
> >
> > I have just installed RH6 on a 486/50 with 256 MB of RAM, and
> without the
> > mem=256MB parameter it didn't detect it. So yes, it is the case
> with 2.2.x
> > kernels.
> >
> > Gordan
> >
> > -
>
> There is something wrong with your hardware. We have redhat 6 with 2.2.5
> and 2.2.10 running on several machines. None have the lilo mem= option
> and all find the entire memory range just fine. My quad xeon has 512mb
> and has no problems at all... and my /etc/lilo.conf file has nothing about
> mem= in it. This was fixed in 2.1 development kernels and is a part of
> 2.2...
Well, I am not claiming that my hardware is totally standard (it is the same
machine that uses a wierd SMP support that Linux doesn't like), but I know
that mem= makes it work, and as long as it works, I am not too bothered
about it being slightly cludged...
Gordan
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
