Just copying isn't enough, AFAIK, You have to tell the
bootloader where the kernel physically is. I dont remember how
to do without lilo - with lilo is clear - rerun lilo.
Matth
On Wed, 17 May 2000, cls--colo spgs wrote:
> debs,
>
> i'm just upgrading my slink lapbox to potato (on the
> 2.0.36
> "cls--colo" == cls--colo spgs <[EMAIL PROTECTED]> writes:
cls--colo> i'm just upgrading my slink lapbox to potato (on the
cls--colo> 2.0.36 kernel). my boot hangs at scsi.
cls--colo> i copied a scsi-free kernel into /boot. but it still
cls--colo> tries to boot the scsi ke
debs,
i'm just upgrading my slink lapbox to potato (on the
2.0.36 kernel). my boot hangs at scsi.
i copied a scsi-free kernel into /boot. but it still
tries to boot the scsi kernel and then hangs.
i renamed /boot/linux to /boot/vmlinux-2.0.36, the name
of the kernel that i had been using. ..
3 matches
Mail list logo
