Thread: [Madwifi-users] Linksys WPC100 in a Thinkpad
Status: Beta
Brought to you by:
otaku
From: Geoff W. <wh...@ve...> - 2008-05-17 16:14:56
|
I'm inserting a WPC100 (802.11a/b/g/n) card in a ThinkPad A20M running Slack 12.0. The only kernel indication on doing that is 'CardBus card inserted in slot 0.' Lspci -vd 168c:0023 (the vendor:device of the card) yields: 02:00.0 Network controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI adapter (rev 01) Subsystem: Linksys Unknown device 0068 Flags: 66MHz, medium devsel, IRQ 11 ===> Memory at 34000000 (32-bit, non-prefetchable) [disabled] [size=64k] Capabilities: [40] #80 [0000] Capabilities: [80] #00 [0000] I was able to make the [disabled] go away with 'setpci,' but I was doing it with so many switches and values I've forgotten the magic incantation that made it enabled, so that's my first dilemma. Next is, even after enabling the memory and loading the madwifi modules, a device is not created for me to 'wlanconfig' and 'ath_info' returns 'Unable to read from Magic EEProm.' Can 'modprobe' be made to attach modules to specific hardware if the module doesn't see it? Thanks, Geoff. |
From: Pavel R. <pr...@gn...> - 2008-05-19 10:27:57
|
On Sat, 2008-05-17 at 12:11 -0400, Geoff Wheeler wrote: > I'm inserting a WPC100 (802.11a/b/g/n) card in a ThinkPad A20M running > Slack 12.0. The only kernel indication on doing that is 'CardBus card > inserted in slot 0.' Lspci -vd 168c:0023 (the vendor:device of the card) > yields: > > 02:00.0 Network controller: Atheros Communications, Inc. AR5416 > 802.11a/b/g/n Wireless PCI adapter (rev 01) > Subsystem: Linksys Unknown device 0068 > Flags: 66MHz, medium devsel, IRQ 11 > ===> Memory at 34000000 (32-bit, non-prefetchable) [disabled] [size=64k] > Capabilities: [40] #80 [0000] > Capabilities: [80] #00 [0000] > > I was able to make the [disabled] go away with 'setpci,' but I was doing > it with so many switches and values I've forgotten the magic incantation > that made it enabled, so that's my first dilemma. Next is, even after > enabling the memory and loading the madwifi modules, a device is not > created for me to 'wlanconfig' and 'ath_info' returns 'Unable to read > from Magic EEProm.' I think removing and inserting the card should undo the consequences of playing with setpci. No setpci commands should be needed for MadWifi to work. You didn't specify the version of MadWifi, but all recent versions would create a network device. Please check kernel messages using the dmesg command. > Can 'modprobe' be made to attach modules to specific hardware if the > module doesn't see it? There is a mechanism for binding and unbinding devices using sysfs. However, it's probably irrelevant here. Since you have a recent device, I suggest that you try the current version from Subversion: svn co https://svn.madwifi.org/madwifi/trunk madwifi-trunk -- Regards, Pavel Roskin |
From: Geoff W. <wh...@ve...> - 2008-05-19 20:17:37
|
Pavel Roskin wrote: > On Sat, 2008-05-17 at 12:11 -0400, Geoff Wheeler wrote: > >> I'm inserting a WPC100 (802.11a/b/g/n) card in a ThinkPad A20M running >> Slack 12.0. The only kernel indication on doing that is 'CardBus card >> inserted in slot 0.' Lspci -vd 168c:0023 (the vendor:device of the card) >> yields: >> >> 02:00.0 Network controller: Atheros Communications, Inc. AR5416 >> 802.11a/b/g/n Wireless PCI adapter (rev 01) >> Subsystem: Linksys Unknown device 0068 >> Flags: 66MHz, medium devsel, IRQ 11 >> ===> Memory at 34000000 (32-bit, non-prefetchable) [disabled] [size=64k] >> Capabilities: [40] #80 [0000] >> Capabilities: [80] #00 [0000] >> >> I was able to make the [disabled] go away with 'setpci,' but I was doing >> it with so many switches and values I've forgotten the magic incantation >> that made it enabled, so that's my first dilemma. Next is, even after >> enabling the memory and loading the madwifi modules, a device is not >> created for me to 'wlanconfig' and 'ath_info' returns 'Unable to read >> from Magic EEProm.' >> > > I think removing and inserting the card should undo the consequences of > playing with setpci. No setpci commands should be needed for MadWifi > to work. > > You didn't specify the version of MadWifi, but all recent versions would > create a network device. Please check kernel messages using the dmesg > command. > > >> Can 'modprobe' be made to attach modules to specific hardware if the >> module doesn't see it? >> > > There is a mechanism for binding and unbinding devices using sysfs. > However, it's probably irrelevant here. > > Since you have a recent device, I suggest that you try the current > version from Subversion: > > svn co https://svn.madwifi.org/madwifi/trunk madwifi-trunk > > I'll give the current version a shot, I'm currently using the 0.9.4 version. There are no kernel messages except for an acknowledgment that the modules are loaded and that the kernel is tainted via use of the binary. No device is created. As to the disabled memory, inserting and removing the card has no affect, it's always disabled. I thought that enabling it would allow for detection of the card. Perhaps that's not accurate, are you implying that the disabled memory is not important? Thanks, Geoff. |
From: Pavel R. <pr...@gn...> - 2008-05-20 03:00:44
|
On Mon, 2008-05-19 at 16:14 -0400, Geoff Wheeler wrote: > I'll give the current version a shot, I'm currently using the 0.9.4 > version. There are no kernel messages except for an acknowledgment that > the modules are loaded and that the kernel is tainted via use of the > binary. No device is created. I see it now. The ID for your device in not in the table of the supported devices for version 0.9.4. But it is in the trunk. > As to the disabled memory, inserting and removing the card has no > affect, it's always disabled. I thought that enabling it would allow for > detection of the card. Perhaps that's not accurate, are you implying > that the disabled memory is not important? The detection is done using vendor and device ID, which are located in the PCI configuration space. It is distinct from the onboard memory. Since lspci is showing the device, the driver should be able to find it. -- Regards, Pavel Roskin |
From: Geoff W. <wh...@ve...> - 2008-05-26 18:33:48
|
Pavel Roskin wrote: > On Thu, 2008-05-22 at 19:43 -0400, Geoff Wheeler wrote: > > >>>> I'll give the current version a shot, I'm currently using the 0.9.4 >>>> version. There are no kernel messages except for an acknowledgment that >>>> the modules are loaded and that the kernel is tainted via use of the >>>> binary. No device is created. >>>> >>>> >>> I see it now. The ID for your device in not in the table of the >>> supported devices for version 0.9.4. But it is in the trunk. >>> >>> >> The very thing. Thanks so much for your help in chasing this down. I've >> compiled the trunk version and it spots the card right off the bat. >> > > Please don't take the discussion private. Somebody with the same card > can find the archived thread, and it will end with you disappearing > after being told to use the current version. > > >>>> As to the disabled memory, inserting and removing the card has no >>>> affect, it's always disabled. I thought that enabling it would allow for >>>> detection of the card. Perhaps that's not accurate, are you implying >>>> that the disabled memory is not important? >>>> >>>> >>> The detection is done using vendor and device ID, which are located in >>> the PCI configuration space. It is distinct from the onboard memory. >>> Since lspci is showing the device, the driver should be able to find it. >>> >>> >>> >> It does indeed, and now spits out all sorts of wonderful info. Should I >> share what I find with this list, or elsewhere? >> > > If it short, it may be useful. If nothing else, it will contain the MAC > revision of your card, and there is an effort underway to make a > complete table of such revisions. > > Thanks Pavel, it slipped my mind that we'd taken this conversation private. So, the latest is that the driver package now works with the WPC100, containing the Atheros 5416 chip. I was even able to clamp it on to my wifi network at home. Now things are a bit murkier, having to do with wpa_supplicant and its awareness (lack, really) of madwifi. When I boot with the card installed, there are a string of 'directory not found' messages, so I decided to reinstall the wpa_supplicant package as Eric's slackware madwifi wiki page suggests. Now, the only way that '...supplicant' will work is using '-Dwext' as the driver. When I attempt to tell it to use madwifi, the message that 'madwifi is not supported in this version' pops up. So, it's back to the drawing board, but at least the driver works. I'll be posting some other info shortly, as there are some confusing messages kicked back even when everything _does_ work. Thanks for the help, I'll write soon, Geoff. |