> After making some backups, I tried to upgrade the kernel again. > Guess what? It just works now.
arghhh! valentijn, that's *exactly* the "mistake" that i made :) actually in my case, i installed grub (and lvm2) which triggered off the postinst initramfs-tools hook. you cannot "back-recover" from this. i tried that - i tried down-grading a number of packages and then re-installing: nothing would reproduce the problem. ok, do you have complete and full backups of the entire system state? actually, the ironic thing is that it's not the system state *after* the faulty install that's needed, it's *before*. so. there are now *two* cases where an upgrade from 2.6.32 to 2.6.39 has resulted in initramfstools *not* placing an initrd-2.6.39-2-amd64 into /boot. one was using debian/testing and the other was using debian-backports. ok. valentijn, there's one more thing that will help to accurately determine a repro-case. could you tell us what you have - had - *before* you did the upgrade and *before* you added a line for debian backports - in /etc/apt/sources.list ? also please list any /etc/apt/sources.list.d files, as well as /etc/apt/apt.conf (and .d files) and if you have an /etc/apt/preferences file, that too. it would help enormously if it could be determined that your system is a basic debian/stable one: mine was mostly debian/testing and also has an EFI BIOS, so i had to upgrade to Grub 2. if your system is (was) debian/stable that would be extremely handy to know. l. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPweEDwyXooTp+Wy4wvTHeq9utrfwQtFxbG=p55svgq4d5u...@mail.gmail.com
