I am having the strange problem (that I suspect is embarrassingly simple)
where I can only boot a kernel built on the same machine. For example
my setup looks like:
* machine 'A' (RH 8.0 P4 system):
- contains a 2.5 kernel tree on an exported NFS drive
- this is the machine where I do all my real work, and
do not want to run test kernels on
* machine 'B' (RH 8.0 P3 system):
- mounts the kernel tree on 'A' to make it easy to
install new kernels on for testing
If I 'make clean', 'make', install kernel and rerun lilo from the kernel
tree from 'B' then I can boot the new kernel with no issues.
If I 'make clean' and 'make' from the kernel tree from 'A' and then install
from 'B' then I get a boot failure when the kernel attempts to mount the
root partition with an error message complaining "LABEL=/" is not valid.
This has got to be something really basic.
--rustyl
Here is my lilo.conf ==>
prompt
timeout=50
default=linux-orig
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
message=/boot/message
linear
image=/boot/hack
label=hack
read-only
append="hdc=ide-scsi root=LABEL=/"
image=/boot/vmlinuz-2.4.18-14smp
label=linux-orig
initrd=/boot/initrd-2.4.18-14smp.img
read-only
append="hdc=ide-scsi root=LABEL=/"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 15 2003 - 22:00:52 EST