Re: Recovery from bad kernel
Hi,
I am an idiot and had to recover quite a few times. I just:
- netboot the machine with the images you can find on the ESIEE site (these
are the images you can use to do a netinstall)
- then mount the partition on /mnt
- then chroot /mnt
- recompile a new kernel
- hope it works this time
Seems complicated, but it isn't. I needed to set up a bootp-server anyway,
as my 712 doesn't have any peripherals.
Of course, you can interact with IPL if this sounds more suitable. A
detailed explanation is in:
http://tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/paloearlyboot.html
regards,
Kenneth
----- Original Message -----
From: "Matthew Wilcox" <willy@debian.org>
To: "Aidan Delaney" <adelaney@cs.may.ie>
Cc: <debian-hppa@lists.debian.org>
Sent: Wednesday, October 23, 2002 8:52 PM
Subject: Re: Recovery from bad kernel
> On Wed, Oct 23, 2002 at 07:13:35PM +0100, Aidan Delaney wrote:
> > Let's suppose (for a moment) that I'm an itiot who had a perfectly good
system
> > but recompiled the kernel and booted into it.
> > Suppose also that the palo.conf file points to "2\vmlinux-2.4.18" and a
> > recovery kernel at /boot/vmlinux-2.4.17-r39 (or somthing).
> >
> > If the 2.4.18 kernel fails halfway through boot, how do I get palo to
revert
> > to using the recovery kernel?
>
> you need to `interact with isl' (maybe specify `ipl' on the boot line,
> depends what kind of firmware you have), then edit the command line using
> the fancy editor paul designed, and specify 2\vmlinux-2.4.17-r39 instead.
> I think ;-)
>
> --
> Revolutions do not require corporate support.
>
>
> --
> To UNSUBSCRIBE, email to debian-hppa-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
Reply to: