> Here are some of the lines from my lilo.conf:
> ---
> lba32
> boot=/dev/hda
> root=/dev/hda7
>
> image=/boot/vmlinuz-2.4.26-1-686
> label=2.4.26-1-686
> initrd=/boot/initrd.img-2.4.26-1-686
> read-only
> ---
>
Mmmh... and here starts my problem: I do not have such entries in /b
Sorry, but you'll get always this problem if you change to another kernel
image. Currently I wanted to update from 2.2.20 (boot disks from internet) to
2.4, and the message is the same.
Am Montag, 14. Juni 2004 21:09 schrieb Zenaan Harkness:
> On Tue, 2004-06-15 at 01:01, J. Preiss wrote:
> >
On Sun, 2004-06-13 at 10:50, Paul Tsai wrote:
> Zenaan Harkness wrote:
>
> >On Tue, 2004-06-15 at 01:01, J. Preiss wrote:
> >
> >
> >>I have exactly the same message on the screen.
> >>I think it has something todo with this initrd-option (which I ignored of
> >>course...). My device is 305 (3
On Tue, 2004-06-15 at 01:01, J. Preiss wrote:
> I have exactly the same message on the screen.
> I think it has something todo with this initrd-option (which I ignored of
> course...). My device is 305 (3,5).
man lilo.conf may help
> Am Montag, 14. Juni 2004 09:10 schrieb Jinzhi Lei:
> > Dear
I have exactly the same message on the screen.
I think it has something todo with this initrd-option (which I ignored of
course...). My device is 305 (3,5).
Am Montag, 14. Juni 2004 09:10 schrieb Jinzhi Lei:
> Dear all,
> While I update the the kernel from 2.2 to 2.6.6, I had the following
Dear all,
While I update the the kernel from 2.2 to 2.6.6, I had the following question:
VFS: Cannot open root device "1606" or unknown-block(22,6)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(22,6)
But I had root=/dev/hdc6 at the
6 matches
Mail list logo
