On Thu Nov 12 1998 at 08:42, "Dmitry Jhuliabin J." wrote:
> Added new kernel to lilo.conf:
>
> image=/usr/src/linux/arch/i386/boot/zImage
> label=pr
> root=/dev/hda6
> append="ether=5,0x318,eth0"
> read-only
No, don't do it like that.
mv /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.35
or label the image with some other suitable name.
Point is that you should move it onto your root partition. So your lilo
entry becomes:
image=/boot/vmlinuz-2.0.35
> And have problem:
> Choosing label pr, I've got:
> Loading pr - stopping without any message
Can't find the image?
> or
> Loading pr ...........
> Uncompressing kernel .......
> Error unknown packed format
Kernel image out of reach? (ie, the 1024 cylinder problem?)
> root=/dev/hda6
/dev/hda6 ??
It very well could be over the 1024 (512Mb) BIOS limit.
You should really aim to have your root partition set up on a primary
partition, and that partition to be completely within reach of your BIOS.
Check the kernel howto, and the lilo docs, man pages, and howto for more
details about this.
> or
> Loading pr ...........
> Uncompressing kernel .......
> Error: no signature
> etc.
Not good.
Good luck.
Cheers
Tony
Certainly lilo I started. And have a new BIOS. Today I has followed an
advice of Tony Nugent has do so: mv /usr/src/linux/arch/i386/boot/zImage
/boot/vmlinuz2025 and has changed lilo. Kernel become be loaded but has
appeared other problem when loading:
>>> kernel : mounting root filesystem <<<
VFS: Cannot open root device 03:06
kernel panic : VFS : unable to mount root fs on 03:06
Old kernel stored at / and named vmlinux.
New kernel at /boot and named vmlinuz2025.
May be I should link /boot with / ? How I can do this?
Thanks, Dmitry .
[EMAIL PROTECTED]
