[KLUG Members] Not the sharpest tack in the box.

[Dirk H Bartley]

Buist Justin wrote:
> 
> > Unfortunately there is no smp enterprise rpm on the RH7.0 disk.
> >
> > Dirk
> 
> You might want to just grab the source RPM from the CD then, unpack it and do a 'make oldconfig'.  Then just head into your favorite kernel config system and enable high memory support for stuff up to 4GB.  If memory serves, your plain vanilla kernel source is going to build with just 1GB of RAM support, which explains why you can't use the chip that brings you past that limit.

I don't mind compiling a kernel.  Been there and what always happens is I have
to recompile to get support for something else important that I forgot.  If I
had a config file that was exactly the way the rpm kernel was compiled I am
using and then I could add large memory support to the config through make
xconfig.  I'd just hate to get an hour into a work day and find something not
working requiring a recompile.  Doesn't the exact config get put on the RPM?

> 
> I'm thinking mem= won't really do anything for you.  If I'm not mistaken all that does is tell the kernel that the BIOS is buggy and that you really do have X amount of RAM.  This used to be fairly common "back when" the jump from 2.0 to 2.2 was made... frequently anybody with over 64MB ram needed to use the mem= option due to buggy BIOSes, or maybe it was a bug in the kernel.  Whatever the cause is, I'm sure that "OS/2 support for over 64MB RAM" option that you see in BIOSes these days is related to something fruity with the x86 architecture.

What does make oldconfig do?  Does it check the parameters of the running kernel
or does it look at the last time the kernel configuration software was run?

Dirk
> 
> Hope that helps.
> 
> Justin Buist
> _______________________________________________
> Members mailing list
> Members@kalamazoolinux.org
>