I have seen similar errors,
in my case I forgot to run lilo after each time after writing
a new kernel or ramdisk image into /boot.
it seems that lilo is rather "brain dead" as to file systems,
so it uses "hard coded" offsets to find the kernel & ramdisk locations
if you overwrite a new file using linux, the files system may change the
location,
but the information in the MBR is still pointing to the original
location,
which is now wrong. running lilo again will freshen the pointers, and the
kernel will
find your ramdisk again. (if this is indeed your problem too)
Jan
"Andrew" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
08/08/2002 11:38 PM
To: <[EMAIL PROTECTED]>
cc:
Subject: Help - initrd..
I have a problem that I have been wrestling with now for a number of days
with no solution, and I'm hoping someone can help.
I have a stock 2.2.20 kernel with ramdisk and initrd support compiled in.
RAMdisk size is 64MB although I've also tried 32MB and 128MB.
I have tried kernel builds with module support and without (everything
compiled in)
I'm using the latest lilo I can find with the following config:
boot=/dev/hdc
disk=/dev/hdc
bios=0x80
map=/map
install=/boot.b
backup=/boot.1600
prompt
linear
timeout=50
password=maintenance
restricted
image=/vmlinuz-2.2.20up
label=test
ramdisk=65536
initrd=/rootfs.img
root=/dev/ram
The server is a uni processor PIII server with 512MB of RAM
The sizes of my rootfs.img and kernel are:
8713856 Aug 7 12:55 rootfs.img (this is an ext2 compressed image)
787022 Aug 7 12:17 vmlinuz-2.2.20up (this is a monolithic bzImage
kernel)
My problem is that when my kernel loads, sometimes lilo doesn't seem to
load
the rootfs.img into RAM for the kernel to find. That is I don't get the
kernel message 'RAMDISK found at 0' message and thus Linux panics with
something like "root file system not found on dev 1:0".
Lilo when building doesn't report any errors in fact it says it
successfully
maps the RAMdisk ok
The only trick that I have been able to use to get around it, is to
selectively remove some files OR selectively remove some kernel components
when compiling - but it's not consistent. It almost seems like there is
some
finite size limit that my rootfs.img+kernel is greater than that stops the
RAMdisk being loaded or being found if it is infact being loaded.
I have not tried a 2.4 level kernel as I need this to work consistently
with
2.2.
Any help much appreciated.
Andrew.
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
