hp@xxxxxxxxxxxx wrote:
It doesn't quite work for me, the system locks up without discernible
error messages (Highpoint RocketRaid 2300 PCIe) . The drives come up,
and immediately get hyper active, and I get dumped in an initrd busybox
shell, when I try to tail /dev/sda it hangs, pvscan doesn't find any
physical volumes for LVM, on the upside, I don't get the PCI ERROR
messages anymore :) I'll try and get netconsole to work to get a proper
log.
...
Before this, you were booting from some other device,
and the sata_mv mostly worked for you there, right ?
Specifically, you wrote:
Now, because the chip on the thing is a Marvell 7042 I figured I just
add the PCI ID to the driver. I tried this, and, if I do not boot from
the device it does seem to work. I did however get the following errors
(a lot):
02:00.0 sata_mv PCI ERROR; PCI IRQ reason=0x00000000
I write this from memory, but the numbers are correct, sorry if they do
not EXACTLY match.
The disk drives do work, but they are dog slow, and when I try to boot
my ubuntu 7.10 system with this driver, it hangs during boot, right
after it tried to enable my software raid volumes.
I have tried both the 'stock' ubuntu kernel 2.6.22-14-generic (I guess
that won't mean much) but I also tried vanilla kernel.org 2.6.23.1
..
So at least that much should now be working much better for you.
I have not actually ever booted from a sata_mv controller yet,
so maybe there's still something peculiar about libata::sata_mv
early in the boot stages ?
I'm using sata_mv as a module here, but I *never* use initrd/initramfs images.
They just complicate things needlessly once I know my hardware config.
But it should work. I'll try booting from a sata_mv drive here
on your board and see what's up.
Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
