4 Jul 2012 20:00
Voyage-0.8.5 not anymore booting with lilo!
Hello Voyage 0.8.5 lilo installation does not work anymore. Just installed new installation not upgrade of voyage-0.8.5 on alix plattform. Problem is kernel labeling with space does not work with lilo only with grub. But even with correcting this root is not found. Error is: [ 0.602598] Root-NFS: no NFS server address [ 0.604197] VFS: Unable to mount root fs via NFS, trying floppy. [ 0.605763] VFS: Cannot open root device "LABEL=ROOT_FS" or unknown-block(2,0) [ 0.606481] Please append a correct "root=" boot option; here are the available partitions: [ 0.607591] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) [ 0.608394] Pid: 1, comm: swapper/0 Not tainted 3.2.17-voyage #1 [ 0.609432] Call Trace: [ 0.610839] [<c12b99db>] panic+0x5a/0x14b [ 0.612185] [<c13cbb3e>] mount_block_root+0x15f/0x173 [ 0.612660] [<c108ffb7>] ? sys_mknod+0x13/0x15 [ 0.614339] [<c13cb1df>] ? parse_early_options+0x1c/0x1c [ 0.615571] [<c13cbc14>] mount_root+0xc2/0xcc [ 0.616939] [<c13cc63d>] ? initrd_load+0x2be/0x2c8 [ 0.617604] [<c13cb1df>] ? parse_early_options+0x1c/0x1c [ 0.618830] [<c13cbd5e>] prepare_namespace+0x140/0x171 [ 0.619532] [<c13cb2d0>] kernel_init+0xf1/0xfd [ 0.621161] [<c12bcbf6>] kernel_thread_helper+0x6/0xd(Continue reading)
Until voyage-0.8 there was no problem.
It seems that voyage kernel does not have anymore ext3 built in which in my
opinion is bad because it's the only which could be missing to mount
root since 0.6 or so
but this it not the actual problem I have...
Greetings
Beat
On 07/04/2012 03:24 PM, John Coltrane wrote:
> Hi Beat,
>
> uuh, lilo, it's about 10 years or so I had used it.
>
> As far as I can remember you have to actualize the list of blocks where
> the kernel resides (every time you have tinkered with the kernel). May
> be a simple "lilo -v" does this, but you should have a look inside
> lilo's manpage.
>
> Why can't you use grub ?
>
> Regarding initrd, if you have a kernel where all device drivers and
> other kernel modules mandatory for booting are statically linked in (not
> modules !), you do not need a initrd.
>
> cheers, John
>
RSS Feed