How do you know that megaraid_mbox is failing? How does it fail (lockup,
lockup...for rhas5.1 it got to loading the megraid_mbox module and no
further, if I set the raid controller to I2O and not mass storage it goes
until the install, but cant see any disk to partition, if it was a
conflict I'd expect either way to lock up, but I could be wrong.
Ditto debian 4.0r3 netinst cd....it gets to detecting hardware and no
longer responds. No issue with a netinst or 3.1r3.
For a 2.6 kernel off a running install it boots to the raid controller
either no longer responds, or goes into a loop saying its resetting and
waiting 300secs....just does this over and over....yet images 2.4.27-3
-4 boot fine...
Perhaps a single kernel command line parameter is all you need to boot.
The megaraid driver might be using the wrong I/O ports or IRQ's or
It is possible...however I have no idea how to address this....since 2.4
kernels work the iomem/interrupts would seem to be Ok...I'd suspect it is
If I can/could I'd like to search against the changelogs? of 2.4 and 2.6
sources looking for a change in the megaraid module. Then compile a
before and after that change(s). If the one before works but the later
does not it would strongly suggest an introduced bug.
There maybe a better way? but my skills around compiling kernels are very