On Friday 23 November 2007 11:54:56 Holger Schurig wrote: > > Don't be fooled by the PCI ID - we already know that these > > are not reliable to identify the chipset used on a > > Atheros-based card. See also http://madwifi.org/ticket/1192. Hmm, I also notices that in ticket 1192, neither the output of "lspci" nor "lshw" doesn't even output the subsystem ID. The MODULE_ALIAS() syntax doesn't seem to have a way to specify subsystem IDs. I have two Atheros based cards here, one is a D-Link DWL-G650, one a Proxim 8470-WD. Both have the PCI ID 168C:0013. The D-Link has the subsystem ID 1186:3a12, the Proxim has 14b7:0a40. The driver for the Proxim card contains an INF file, which has this section: [Vendor] ; DisplayName Section DeviceID ; ----------- ------- -------- %LEX.DeviceDesc.CB22ag_G% = LEX_CB22ag_01, PCI\VEN_168C&DEV_0013&SUBSYS_0A1014B7 %LEX.DeviceDesc.CB22ag_S% = LEX_CB22ag_02, PCI\VEN_168C&DEV_0013&SUBSYS_AA1014B7 %LEX.DeviceDesc.CB22ab_G% = LEX_CB22ab_01, PCI\VEN_168C&DEV_0012&SUBSYS_0A001B47 %LEX.DeviceDesc.CB22ab_S% = LEX_CB22ab_02, PCI\VEN_168C&DEV_0012&SUBSYS_AA001B47 %LEX.DeviceDesc.CB22ab_A% = LEX_CB22ab_03, PCI\VEN_168C&DEV_0012&SUBSYS_1A001B47 %LEX.DeviceDesc.CB22g_G% = LEX_CB22g_01, PCI\VEN_168C&DEV_0013&SUBSYS_0A4014B7 %LEX.DeviceDesc.CB22g_S% = LEX_CB22g_02, PCI\VEN_168C&DEV_0013&SUBSYS_AA4014B7 %LEX.DeviceDesc.MB22ag% = LEX_MB22ag_01, PCI\VEN_168C&DEV_0013&SUBSYS_0A6014B7 %LEX.DeviceDesc.ORiNOCO% = LEX_ORiNOCO, PCI\VEN_168C&DEV_0013&SUBSYS_04101467 And, as it turns out, the driver for the Proxim card doesn't recognize the D-Link card, because it looks not only at the PCI-ID, but also at the subsystem ID. It would be interesting to get a list of the subsystem IDs of misdetected atheros-based WLAN cards. - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
