RE: Can't configure grub to use less memory

[Darren Gamble]

Good day,

That's interesting you should mention that,

I have just compared the logs of the grub-booted server vs. the lilo-booted
server.  The line where the grub-server crashes is where the lilo-booted
server instead loads the initrd image (although the error message doesn't
really show that).

The lilo-booted server logs:

Jan 23 09:37:31 ks kernel: RAMDISK: Compressed image found at block 0

Both log:

Jan 23 09:37:30 ks kernel: RAMDISK driver initialized: 16 RAM disks of 4096K
size 1024 blocksize

...earlier on.

Both lilo and grub have the same command to load the image.

This doesn't really mean much to me, but by the specificness of your
question, it sounds like it might to you. =)

============================
Darren Gamble
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948


-----Original Message-----
From: Erik Troan [mailto:address@hidden
Sent: Wednesday, January 23, 2002 3:55 PM
To: address@hidden
Subject: Re: Can't configure grub to use less memory


On Wed, 23 Jan 2002 15:19:58 -0700
"Darren Gamble" <address@hidden> wrote:

> Lastly, we also tried to manually add "mem=800M" onto the end of the
kernel
> boot line.  The GNU grub faq suggests to do this, and kickstart also does
> this if it's specified in its configuration.  If that's done, when the
> machine boots the root filesystem doesn't get found and the system halts.
> Bootup reports:
> 

This is the right idea. When you did this, is the initrd still getting
loaded? You should see messages from the initrd before you get this.

Erik

----------------------------------------------------------------------------
-
|               "Distracting? I'm inspiring"
|
|                              - Sally Bowles in Cabaret
|

_______________________________________________
Bug-grub mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/bug-grub