Bug#318326: initrd-tools: Same here. (3W-6200)
Package: initrd-tools Version: 0.1.82 Followup-For: Bug #318326 I have a 3ware 3W-6200, and after a kernel upgrade i found that my system would no longer boot. Since i'd (stupidly) removed the old working kernel package, recovery was a real pain in the neck. I finally did figure out that the problem was corrected by adding 3w- to /etc/mkinitrd/modules and running mkinitrd to re-generate the initrd with this module included. I've never had this problem before, so i'm guessing that a default has changed somewhere! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2.1 The GNU core utilities ii cpio 2.6-6 GNU cpio -- a program to manage ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F ii dash 0.5.2-8The Debian Almquist Shell ii fileutils 5.2.1-2.1 The GNU file management utilities ii util-linux2.12p-8Miscellaneous system utilities initrd-tools recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318326: initrd-tools: Same here. (3W-6200)
On Wed, Oct 19, 2005 at 03:12:45PM -0400, Josh Wilmes wrote: Package: initrd-tools Version: 0.1.82 Followup-For: Bug #318326 I have a 3ware 3W-6200, and after a kernel upgrade i found that my system would no longer boot. Since i'd (stupidly) removed the old working kernel package, recovery was a real pain in the neck. I finally did figure out that the problem was corrected by adding 3w- to /etc/mkinitrd/modules and running mkinitrd to re-generate the initrd with this module included. Can you try yaird or the upcoming initramfs-tools with the 2.6.12 kernel in etch/sid. 2.4 kernels are no more the default choice even on x86, and initrd-tools is going to be phased out in favour of yaird or initramfs-tools pretty soon, since kernels newer than 2.6.13 have no devfs support which initrd-tools needed. I've never had this problem before, so i'm guessing that a default has changed somewhere! Indeed, or maybe the name of the module ? A /sys reading ramdisk generating tool like yaird should not have this problem. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
