[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem with grub configuration
From: |
erich |
Subject: |
Re: problem with grub configuration |
Date: |
Fri, 08 Feb 2002 12:21:45 -0800 |
Pavel Roskin <address@hidden> wrote:
> GRUB loads initrd (initial reamdisk) to the end of the memory. It uses
> 256M of memory. But you tell the kernel that you only have 254M of
> memory. That's why the kernel cannot load initrd.
>
> initrd is used on RedHat to support SCSI adaptors. If it cannot be
> loaded, then your SCSI devices are not accessible.
>
> The best solution would be to recompile the kernel to support your SCSI
> adaptor in the kernel. Besides, your kernel is old - consider applying
> all RedHat updates.
Actually, an easier solution is to, instead of adding the "mem=254M"
to the end of the kernel command-line, tell GRUB that it has less memory
to work with, and it will report that to the kernel.
Do this with the "uppermem" command, so instead of your entry looking
like the following:
title Red Hat Linux (2.4.7-10smp)
root (hd0,0)
kernel /boot/vmlinuz-2.4.7-10smp ro root=/dev/sda1 mem=254M
initrd /boot/initrd-2.4.7-10smp.img
...so I *think* it would instead look like this:
title Red Hat Linux (2.4.7-10smp)
uppermem 259072
root (hd0,0)
kernel /boot/vmlinuz-2.4.7-10smp ro root=/dev/sda1
initrd /boot/initrd-2.4.7-10smp.img
The "uppermem" command changes GRUB's idea of what is in the main region
of upper memory, for exactly this kind of purpose. Though, it has to
take it in kilobytes (and you have to remove the 1MB of the lower
memory).
So, I put in there 253 * 1024 (253 MBytes).
Hope this works for you.
--
Erich Stefan Boleyn <address@hidden> http://www.uruk.org/
"Reality is truly stranger than fiction; Probably why fiction is so popular"
Re: problem with grub configuration, Jeremy Katz, 2002/02/08