#163 closed defect (fixed)
3ware driver still not recognized; 3x_9xxx 3w-9xxx
Reported by: | mac_7 | Owned by: | Bruno Cornec |
---|---|---|---|
Priority: | high | Milestone: | 2.2.5 |
Component: | mindi | Version: | 2.2.3 |
Severity: | normal | Keywords: | |
Cc: |
Description
REMINDER FOR VERY OLD BUGS AND VERY EASY TO FIX
http://copilotconsulting.com/mail-archives/mondo.2006/msg00559.html
Hi, dear developers,
Just want to report a bug that I've found with the new bash script for Mindi with 3ware driver.
It turns out that the Mindi has problem locating the 3ware driver because the script it uses:
find /lib/....$kernel |grep ...$module|tail -n1 ....
The problem occurs when the module name isn't the file name for the driver.
In this case, the module name is 3w_xxxx, and the file name is 3w-xxxx.ko . For the new 3ware hardware, you'll have 3x_9xxx instead of 3w-9xxx.
The quick and dirty fix is to add the file name for the driver in the EXTRA_MODS section. This will force Mindi to load the driver during the boot image creation.
For example:
The original line:
EXTRA_MODS="$CDROM_MODS vfat fat loop linear raid0 raid1 raid5 lvm-mod dm-mod jfs xfs xfs_support pagebuf reiserfs ext2 ext3 minix nfs nfs_acl nfsd lockd sunrpc jbd"
The quick fix:
EXTRA_MODS="$CDROM_MODS vfat fat loop linear raid0 raid1 raid5 lvm-mod dm-mod jfs xfs xfs_support pagebuf reiserfs ext2 ext3 minix nfs nfs_acl nfsd lockd sunrpc jbd 3w-xxxx"
Best regards,
Poe
Change History (3)
comment:1 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 17 years ago
Milestone: | → 2.2.5 |
---|
Thanks for the reminder. That's why I like bug reports, as it much more easy for me to not forget one. Of course that doesn't mean I have plenty of time to treat it :-)
Fixed in rev [1417]