Re: screwed custom kernel image, recovering getting bad
TR <tony@the-sphere.org> writes:
> I have the following sid screwed system:
> / in hdb1
> /home in hdb2
> swap in hdb3
> grub floppy is used to boot.
If you haven't figured it out yet, you should be able to use the GRUB
floppy to boot from an old kernel:
root (hd1,0)
kernel /boot/vmlinuz-<TAB> root=/dev/hdb1
initrd /boot/initrd.img-<TAB>
boot
(where <TAB> means "press the tab key, and fill in the right old
image", and you can skip the initrd line if your old kernel doesn't
use an initrd.)
> Now the booting seems to run much more smoothly, until it gets
> stucked at the scsi loading step, with inmediate panic.
As in, kernel panic? That's no good...
> 1. (grub floppy + loading old image 2.4.18) leaves me without a
> bunch of commands, for example, says that dpkg is not known, etc.
That seems like a surprising failure mode, particluarly since /usr
isn't a separate partition for you.
> The problem is: I don't know what exactly I should do to get back to
> the previous image booting sequence. I had done mv
> /lib/modules/2.4.21 as usual. I have changed the names of the
> directories sevral times, but I still can tell which is which: The
> old one has some alsa directory inside.
...you're not using kernel-package? Then you could have multiple
kernels with different "names" installed (using --append-to-version),
or just install a newer or older kernel using dpkg directly. It
sounds to me like your modules directory disagrees with your kernel,
and that's why you're losing; kernel-package would help you avoid
this.
--
David Maze dmaze@debian.org http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
Reply to: