Hi all,

Originally asked this on debian-user, no responses...

I have a Promise 20376 SATA RAID on my Asus A7V8X mobo.  My root
partition is mounted on it.  The driver is provided by Promise.  During
the Debian install, I was able to put the ft3xx.o module (built on
another machine) onto a floppy, and the installation script created
an initrd, which boots, loads the driver, mounts /, and carries on.
(So much for Debian's install being
crap!)

This has been great for months, and I've built several versions of
2.4.18 since, which load fine using that initrd.  However, I'm now
trying to uplevel to 2.4.22, for a 802.11b driver that I'd like to use.
Only problem is, on bootup, I get:
<Promise driver "about" line>
scsi1: ft3xx
scsi1: device driver called scsi_done() for a synchronous reset.

Then a hang.  This is _exactly_ at the point when the RAID root partition
should take over.

I must admit to not being an initrd expert.  Do I need to recompile the
ft3xx module against the 2.4.22 headers, even though I'm booting from
the same initrd as before?  And if I do, how do I create a new initrd
with that module in it?  I've read TFM on initrd, but just can't get it
to work, even for such a simple task (load a module, hand root to RAID
partition).

I build kernels The Debian Way (i.e. make-kpkg --initrd), but the initrd
that is created from that is useless - i.e. doesn't take into account
that I need to load ft3xx.o.  So usually I point lilo to
/boot/initrd.debinstall, which worked for my 2.4.18 kernels.

So, either:
1. My 2.4.18 initrd with ft3xx module that's causing the problem?  OR
2. There's a problem in 2.4.22.

Hope I'm making sense to somebody - kernel config diff is attached.

A

PS A CC would be much appreciated.

-- 
Now playing: Dream Theater - Learning To Live