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

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...@xxxxxxx> 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...@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmas...@xxxxxxxxxxxxxxxx


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: Problem booting RAID1/mdadm system when one disk is unplugged
    ... My System has 2x120GB IDE disks with the an up-to-date Sarge install, running kernel 2.6.8-3 and configured for mirroring. ... some friends of mine do not agree that my initrd is the problem because they point out that I can still boot when two disks are present. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ... disk BIOS presents, and partition number 6 on that disk. ...
    (Debian-User)
  • Re: booting from ISO image on HD?
    ... >> through customized initrd files for each one. ... > between the loopback device and the underlying file (the iso image). ... I have to insmod the loop kernel module(e.g. ... how can you boot it from an initrd??? ...
    (comp.os.linux.misc)
  • Re: fsck fails during boot with 2.6.9-34.0.1.EL kernel because root filesystem is already rw mou
    ... I think there was a little fault in building the new initrd. ... The mount-command of the init-script is wrong and makes confusing, e.g.: first the root-filesystem must mount read/write, it accepts. ... It looks like in the early stage of the booting, when the kernel is using the initrd to load the ... I still do not understand why in my new initrd file, with the new kernel, the root filesystem is ...
    (RedHat)
  • Re: booting from ISO image on HD?
    ... I'm not going to write the pivot root script, ... > through customized initrd files for each one. ... I have to insmod the loop kernel module(e.g. ... The idea is that either you build what you need to boot into your ...
    (comp.os.linux.misc)
  • Re: 2.6.26-rc5-mm1
    ... In my case it turns out to be gcov patches - in which I'm interested ... initrd overwrites kernel: When kernel and initrd are loaded to static ... minimal memory configuration any more. ...
    (Linux-Kernel)