|
Hi Horms, Thanks for the quick reply – yes, 286939 and 291928
are the same bug, experienced with different builds of Debian Installer, so you’re
right to merge them. Thanks for the tips on closing and adding to bugs. To answer your questions – yes, my understanding is
that all the fakeraid drivers (ataraid and one of medley, silraid, hpt etc.)
rely on a low-level driver to talk to the hardware – the fakeraid drivers
are really just doing some on-the-fly address translations. So in my case
medley.o expects either siimage or sata_sil to be loaded. Secondly, yes, the Debian Installer (in expert mode) always
offers me the chance to load siimage and sata_sil, and I always load one of
them before manually trying “modprobe medley”. It’s never
occurred to me to try loading medley without either of them loaded, but it’s
worth a try (my understanding above might be wrong, or something). There’s one other piece of the puzzle, which I
mis-remembered in my original 286939 bug report: manually loading the medley
driver worked fine with Debian Installer RC1 (which I think used the same
kernel 2.4.27) – but at that time I had only a 240Gb array (2 x 120Gb). Is
it possible that the step up from 240Gb to 320Gb breaches some 32-bit
addressing limit? I looked at the medley.c source and saw quite a bit of stuff
about 48-bit addressing not being fully implemented, although that doesn’t
explain why it works under Knoppix, nor why the error given is “No usable
RAID sets found” rather than any of the “array too big”
errors in medley.c If the medley source hasn’t changed, I have no idea
why it works in one setup and not in another. I’m willing to try different
things, but I’m right at the limit of my expertise here. Is there an
idiot’s guide to customising your Debian Installer CD image with a
different kernel?? I could try putting the Knoppix version of medley.o onto a
floppy and loading it into the Debian Installer to see if that works … Any hints much appreciated (is there an easier way to do
this in 2.6 yet??), CC The original of this email was scanned for viruses by the Government Secure Intranet (GSi) virus scanning service supplied exclusively by Energis in partnership with MessageLabs. On leaving the GSi this email was certified virus-free |