On Fri, 2006-03-03 at 22:50 +0200, Omer Zak wrote:
> Today, after few days, I upgraded the Debian Testing (Etch) installation
> on ThinkPad R40e laptop to have the most recent package versions.
>
> The laptop has few kernels - among them I have 2.6.15-1, 2.6.12-1 and
> 2.6.8-2.
> The 2.6.15-1 never worked for me, when I try to boot it, it locks up
> sometime during hardware detection & initialization phase. The 2.6.12-1
> used to work for me until today.
>
> Today, after the upgrade I noticed that 2.6.12-1 ceased to work for me.
> I booted using kernel 2.6.8-2 and checked which files were modified by
> the upgrade in /boot and /lib.
>
> I determined that /boot/initrd.img-2.6.{12-1,15-1}-686 were modified by
> the upgrade as well as 2.6.15-1 modules (in /lib) and the
> directory /lib/udev (all files inside it are older, so I think that the
> modification consisted of touching the directory and/or deleting some
> files inside it).
>
> The modification of the 2.6.15-1 modules and other files was OK by me -
> they did not work for me and continued not to work for me.
>
> But modifying /boot/initrd.img.2.6.12-1-686 broke the process of booting
> with 2.6.12-1 kernel. And I did not keep a backup of this initrd.img
> file before today's upgrade :-(
>
> So, for now I am working with 2.6.8-2 kernel.
>
> Does anyone know what happened and how to repair the initrd.img?
> The current version of initrd-tools is 0.1.84. Should I try to
> downgrade it to a previous version?
> Thanks,
> --- Omer
Might not be related, but at least on my FC4 box(es), 2.6.15 required a
new udev (0.71).
Cheers,
Gilboa
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
