Re: iswraid calling modprobe when scsi statically compiled?

[Sergey Vlasov]

On Thu, 15 Jan 2004 18:47:57 +0100 Carlos Velasco wrote:

> I'm trying to use Intel Software Raid provided patch in:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106972332715043&w=2
> 
> However, it seems to be calling modprobe although SCSI support is
> statically configured in the kernel:
> 
> modules.conf:
> alias block-major-8 sd_mod
> 
> .config (kernel):
> CONFIG_SCSI=y
> CONFIG_BLK_DEV_SD=y
> CONFIG_SD_EXTRA_DEVS=40
> 
> Booting:
> 
> <6>iswraid: Intel(tm) Software RAID driver Version 0.0.6
> <3>kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
>        <-- ***
> <7>iswraid: No raid array found
> <6>SCSI subsystem driver Revision: 1.00
> <7>libdata version 0.81 loaded.
> <7>ata_piix version 0.95
> <7>PCI: Setting latency timer of device 00:1f.2 to 64
> <6>ata1: SATA max UDMA/133 cmd 0xC000 ctl 0xC402 bmdma 0xD000 irq 18
> <6>ata2: SATA max UDMA/133 cmd 0xC800 ctl 0xC402 bmdma 0xD000 irq 18
> <7>ata1: dev 0 cfg 49:2f00 82:7c69 83:7f09 84:4003 85:7c69 86:3e01
> 87:4003 88:407f
> <6>ata1: dev 0 ATA, max UDMA/133, 160086528 sectors (lba48)
> <6>ata1: dev 0 configured for UDMA/133
> <7>ata2: dev 0 cfg 49:2f00 82:7c69 83:7f09 84:4003 85:7c69 86:3e01
> 87:4003 88:407f
> <6>ata2: dev 0 ATA, max UDMA/133, 160086528 sectors (lba48)
> <6>ata2: dev 0 configured for UDMA/133
> <6>scsi0 : ata_piix
> <6>scsi1 : ata_piix
> ...
> 
> It can't succed because I'm booting without modprobe at all (Intel RAID
> card is the only one controller).
> Any help would be apreciated.

The problem is in the initialization ordering. iswraid must initialize
after SCSI, but it is located in the IDE drivers directory, and
therefore is initialized before SCSI. So it won't work when built into
the kernel.

If you build iswraid as module and load it from initrd (after the SCSI
subsystem is initialized and raw drives are detected), it should work.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/