I am trying to take what is very close to my working kernel
configuration, and change it around slightly so that ramdisk and modules
are used for the XFS related items. The reason being that with these in
the kernel and not as module, the image is too large for floppy...I'm
going to attempt a 2 floppy boot setup. However, either mkinitrd.xfs is
failing, or something with lilo config is failing. The system is scsi,
but scsi is being compiled in and not as a module. System is RH 7.1
based. Here is what happens....
It boots normally for a while, looks like it is working, detects the
scsi controller, it even goes through some network and USB stuff. Then,
when it *should* be saying:
Start mounting filesystem: sd(8,6)
It will instead say:
Kernel panic: VFS: Unable to mount root fs on 08:06
Two lines immediately before this occur regardless of whether it is the
working version or the one that breaks when xfs is part of a module, and
*might* have something to do with this, though I doubt it (line repeats
twice):
fatfs: bogus logical sector size 0
fatfs: bogus logical sector size 0
I think that is related to a drive that is for windows only, and
unrelated.
The version that works I have as "2.4.6-pre1-xfs-2", the failed but
nearly identical version is labelled as "2.4.6-pre1-xfs-3". Here is the
lilo.conf (note that the i840 chipset must run with apic disabled to be
reliable...Intel seems to have broken the chipset):
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
vga=0x030c
default=2.4.6-p1-xfs-3
backup=boot.backup.when-2.4.6-pre1-xfs-3
image=/boot/vmlinuz-2.4.6-pre1-xfs-3
label=2.4.6-p1-xfs-3
initrd=/boot/initrd-2.4.6-pre1-xfs-3.img
read-only
root=/dev/sda6
append="ramdisk_size=25000 noapic"
image=/boot/vmlinuz-2.4.6-pre1-xfs-2
label=2.4.6-p1-xfs-2
initrd=/boot/initrd-2.4.6-pre1-xfs-2.img
read-only
root=/dev/sda6
append="noapic"
One thing that I wonder about, although lilo install did not generate
any error, is the append line of the -3 label. Before this, I have only
used:
append="noapic"
Now it appends two items at once, both "noapic" and
"ramdisk_size=25000". Is the space separation the correct delimiter
between multiple append items (man page does not say)? Or maybe what is
happening is that it thinks the whole "25000 noapic" is what to set
"ramdisk_size" to (in which case it probably ignores the parameter
entirely)?
There is also a kernel config item to allow initial ramdisk size to
default to something else, but is set to 4096 by default; thus the lilo
parameter should get around this for the larger ramdisk requirement.
Maybe I *must* also set this option during kernel compile also, and not
just for lilo?
D. Stimits, stimits@xxxxxxxxxx
|