Re: update to latest etch caused multiple problems - can't boot, no sound

["John Lee" <john.cylee@gmail.com>]

Thanks for your help, Florian.

Actually the system dropped me to the ash because it cannot mount
root. I tried it for quite a while before I used the old
initrd.img-2.6.18-4-686.bak and I'm pretty sure all the modules are
still there (I did modprobe sd_mod).  The linux-image is not updated
this time and the old initrd is using exactly the same kernel.

After my last post I checked the aptitude log and found out that the
only thing related to the boot procedure that got updated this time is

udev 0.105-3 -> 0.105-4

Since my boot and sound problems are all related to udev, I rolled
back to udev 0.105-3. Now everything is back to normal.  :-)

-- John

On Mar 31, 2:10 am, Florian Kulzer <florian.kul...@icfo.es> wrote:
> On Fri, Mar 30, 2007 at 02:28:20 +0800, John Lee wrote:
>
> My guess is that some sound(-related) module from the old initrd does
> not work properly with the new kernel. I would not spend time trying to
> get sound to work until you can create a working initrd for your current
> kernel. It seems that the new initrd is missing the sd_mod module (and
> maybe others). You can make a backup of the old .bak initrd (just in
> case) and then try to generate a new initrd by running
>
> dpkg-reconfigure linux-image-2.6.18-4-686
>
> Do you get any error messages? You can also try to use the other initrd
> creator, i.e. mkinitrd.yaird instead of the normal mkinitrd (or vice
> versa, depending on what you currently use).
>
> --
> Regards,
>           Florian
>
> --
> To UNSUBSCRIBE, email to debian-user-REQU...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org