Description of problem: This applies to FC2 as well as FC3 test2/rawhide (and made it so my driver disk wouldn't work). The current pcitable has the following 3ware entries: 0x13c1 0x1000 "3w-xxxx" 0x13c1 0x1001 "3w-xxxx" 0x13c1 0x1002 "3w-xxxx" The last entry is wrong (using wrong driver). The device id 0x1002 is for the 3ware 9000 series SATA RAID controller. I have one in a FC2 box. [root@mooru root]# lspci -n [snip] 01:03.0 Class 0104: 13c1:1002 [snip] The last line should be: 0x13c1 0x1002 "3w-9xxx" I have submitted a patch to the pci.ids maintainer as well. Software version: hwdata-0.130-1.noarch.rpm
Is this a change from the 2.4 kernel?
I don't understand the question. How does the kernel version relate? The card is brand new, I don't why the wrong entry was in there in the first place (maybe an assumption that all 3ware cards --including unreleased ones-- will use the 3w-xxxx driver??). The 9000 series cards were released this summer and the driver (3w-9xxx .. note the '9') was accepted by Linus around the 2.6.7 timeframe.
That was the question, whether there was a 2.4 3w-9xxx driver, or if it was driven by 3w-xxxx under 2.4. In any case, fixed, will be in future builds.
I checked the 3ware website and they have a 2.4 driver for it, and it has an identical name as the 2.6 driver '3w-9xxx'. Source code is here: http://www.3ware.com/download/Escalade9000Series/9.0.2/3w-9xxx2.4.tgz (I looked inside the tarball to completely verify) So it was never driven by the 3w-xxxx driver.
Thanks for handling this, I have been trying to get this updated for a while with little luck. Originally the mapping was entered wrong since it was added prior to the new product shipping which required a new driver hence the module name being different.