Comment 4 for bug 19861

Message-ID: <email address hidden>
Date: Wed, 19 Oct 2005 21:31:12 +0200
From: Sven Luther <email address hidden>
To: Josh Wilmes <email address hidden>, <email address hidden>
Subject: Re: 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-xxxx
> 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