Hi,
I just gave the new ath5k driver a go, but it fails for me with:
pccard: CardBus card inserted into slot 0
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 16
ath5k_pci 0000:02:00.0: can't get channels
I did a git fetch of wireless/everything branch:
$ git describe
v2.6.23-469-g4bcbd55
Modules were loaded automatically: mac80211 and ath5k.
I was hoping for a better result as [1] lists my PCI ID as "OK", but maybe
that is for the PCI version and not the PCMCIA one?
The card works well with the madwifi driver (see below).
The host system is a Toshiba Satellite A40 laptop (i386, Mobile Pentium 4)
running Debian unstable.
I can't help with coding, but am willing to test. Feel free ask for any
additional info you need. Please CC me as I'm not subscribed.
[1] http://linuxwireless.org/en/users/Drivers/ath5k
Cheers,
Frans Pop
>From lspci -nn:
01:0b.0 CardBus bridge [0607]: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support [1179:0617] (rev 33)
02:00.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5212 802.11abg NIC [168c:0013] (rev 01)
>From lspci -vv:
01:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 33)
Subsystem: Toshiba America Info Systems Unknown device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168
Interrupt: pin A routed to IRQ 16
Region 0: Memory at cff00000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=02, subordinate=02, sec-latency=0
Memory window 0: 28000000-2bfff000 (prefetchable)
Memory window 1: 30000000-33fff000
I/O window 0: 0000c000-0000c0ff
I/O window 1: 0000c400-0000c4ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite+
16-bit legacy interface ports at 0001
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
Subsystem: Global Sun Technology Inc Unknown device 7103
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 16
Region 0: Memory at 30000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Output of dmesg with 2.6.18 and madwifi driver:
pccard: CardBus card inserted into slot 0
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 169
wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: turboG rates: 6Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wifi0: H/W encryption support: WEP AES AES_CCM TKIP
wifi0: mac 5.9 phy 4.3 radio 4.6
wifi0: Use hw queue 1 for WME_AC_BE traffic
wifi0: Use hw queue 0 for WME_AC_BK traffic
wifi0: Use hw queue 2 for WME_AC_VI traffic
wifi0: Use hw queue 3 for WME_AC_VO traffic
wifi0: Use hw queue 8 for CAB traffic
wifi0: Use hw queue 9 for beacons
wifi0: Atheros 5212: mem=0x2e000000, irq=169
ath0: no IPv6 routers present
On Monday 22 October 2007, Luis R. Rodriguez wrote:
> > -==Device Information==-
> > MAC Version: 5212 (0x50)
> > MAC Revision: 5213A(0x59)
> > PHY Revision: 5110 (0x0)
> > PHY Revision: 5110 (0x0)
>
> This is the problem. ath5k currently assumes only AR5210s (which are
> 802.11a only capable) have an RF5110. This is also an 802.11bg card.
> Essentially support for this is on the TODO list. For now we'll have
> to just detect this and inform users the card is not supported yet.
OK. Thanks for the info.
I'd gotten the impression that the driver was a bit further along. No
problem though. I'll just stay alert for announcements.
Cheers,
FJP
2007/10/22, Frans Pop <[email protected]>:
> On Monday 22 October 2007, Luis R. Rodriguez wrote:
> > > -==Device Information==-
> > > MAC Version: 5212 (0x50)
> > > MAC Revision: 5213A(0x59)
> > > PHY Revision: 5110 (0x0)
> > > PHY Revision: 5110 (0x0)
> >
> > This is the problem. ath5k currently assumes only AR5210s (which are
> > 802.11a only capable) have an RF5110. This is also an 802.11bg card.
> > Essentially support for this is on the TODO list. For now we'll have
> > to just detect this and inform users the card is not supported yet.
>
> OK. Thanks for the info.
> I'd gotten the impression that the driver was a bit further along. No
> problem though. I'll just stay alert for announcements.
>
> Cheers,
> FJP
> -
Your card is a 5213 and doesn't have 5110 PHY (it's a bug in ath_info
i'm working on it -it reports phy version id = 0 sometimes and that
matches 5110's version id, ath5k doesn't hve that bug), problem is
that it is a b/g only card and we didn't have such cards to test. I'll
send some patches soon that might fix b/g only PHYs but i can't
guarantee anything ;-(
--
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
On 10/21/07, Frans Pop <[email protected]> wrote:
> Hi,
>
> I just gave the new ath5k driver a go, but it fails for me with:
> pccard: CardBus card inserted into slot 0
> PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 16
> ath5k_pci 0000:02:00.0: can't get channels
>
> I did a git fetch of wireless/everything branch:
> $ git describe
> v2.6.23-469-g4bcbd55
>
> Modules were loaded automatically: mac80211 and ath5k.
>
> I was hoping for a better result as [1] lists my PCI ID as "OK", but maybe
> that is for the PCI version and not the PCMCIA one?
> The card works well with the madwifi driver (see below).
>
> The host system is a Toshiba Satellite A40 laptop (i386, Mobile Pentium 4)
> running Debian unstable.
>
> I can't help with coding, but am willing to test. Feel free ask for any
> additional info you need. Please CC me as I'm not subscribed.
>
> [1] http://linuxwireless.org/en/users/Drivers/ath5k
>
> Cheers,
> Frans Pop
>
> From lspci -nn:
> 01:0b.0 CardBus bridge [0607]: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support [1179:0617] (rev 33)
> 02:00.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5212 802.11abg NIC [168c:0013] (rev 01)
>
> From lspci -vv:
> 01:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 33)
> Subsystem: Toshiba America Info Systems Unknown device 0001
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 168
> Interrupt: pin A routed to IRQ 16
> Region 0: Memory at cff00000 (32-bit, non-prefetchable) [size=4K]
> Bus: primary=01, secondary=02, subordinate=02, sec-latency=0
> Memory window 0: 28000000-2bfff000 (prefetchable)
> Memory window 1: 30000000-33fff000
> I/O window 0: 0000c000-0000c0ff
> I/O window 1: 0000c400-0000c4ff
> BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite+
> 16-bit legacy interface ports at 0001
>
> 02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
> Subsystem: Global Sun Technology Inc Unknown device 7103
> Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Interrupt: pin A routed to IRQ 16
> Region 0: Memory at 30000000 (32-bit, non-prefetchable) [size=64K]
Get this line again from lspci, and for example if its 30000000 again
run from madwifi:
./tools/ath_info 0x30000000
Note I'm prepending the "0x", otherwise use whatever address it gives you.
Luis
On Monday 22 October 2007, Luis R. Rodriguez wrote:
> Get this line again from lspci, and for example if its 30000000 again
> run from madwifi:
>
> ./tools/ath_info 0x30000000
That results in:
-==Device Information==-
MAC Version: 5212 (0x50)
MAC Revision: 5213A(0x59)
PHY Revision: 5110 (0x0)
PHY Revision: 5110 (0x0)
-==EEPROM Information==-
EEPROM Version: 4.6
EEPROM Size: 16K
Regulatory Domain: 0x30
-==== Capabilities ====-
| 802.11a Support: no |
| 802.11b Support: yes |
| 802.11g Support: yes |
| RFKill Support: no |
| 32KHz Crystal: yes |
========================
GPIO registers: CR 00000000 DO 00000000 DI 00000000
On Monday 22 October 2007, Nick Kossifidis wrote:
> 2007/10/22, Frans Pop <[email protected]>:
> > OK. Thanks for the info.
> > I'd gotten the impression that the driver was a bit further along. No
> > problem though. I'll just stay alert for announcements.
>
> Your card is a 5213 and doesn't have 5110 PHY (it's a bug in ath_info
> i'm working on it -it reports phy version id = 0 sometimes and that
> matches 5110's version id, ath5k doesn't hve that bug), problem is
> that it is a b/g only card and we didn't have such cards to test. I'll
> send some patches soon that might fix b/g only PHYs but i can't
> guarantee anything ;-(
That would be excellent.
I'll be happy to test any patches. I'm sure we'll get there in the end :-)
On 10/22/07, Frans Pop <[email protected]> wrote:
> On Monday 22 October 2007, Luis R. Rodriguez wrote:
> > Get this line again from lspci, and for example if its 30000000 again
> > run from madwifi:
> >
> > ./tools/ath_info 0x30000000
>
> That results in:
>
> -==Device Information==-
> MAC Version: 5212 (0x50)
> MAC Revision: 5213A(0x59)
> PHY Revision: 5110 (0x0)
> PHY Revision: 5110 (0x0)
This is the problem. ath5k currently assumes only AR5210s (which are
802.11a only capable) have an RF5110. This is also an 802.11bg card.
Essentially support for this is on the TODO list. For now we'll have
to just detect this and inform users the card is not supported yet.
Luis
On Monday 21 January 2008, Frans Pop wrote:
> As I don't have a wireless router at home (and no neighbors with open
> ones), I cannot try an actual connection.
Turns out I _do_ have a friendly neighbor at the back of the house :-)
I managed to associate with his AP and get an IP address using DHCP, but
could not get any real Internet traffic (tried website and ping). Could
possibly be a problem on his side though.
ath0: Initial auth_alg=0
ath0: authenticate with AP 00:18:39:d4:75:9e
ath0: RX authentication from 00:18:39:d4:75:9e (alg=0 transaction=2
status=0)
ath0: authenticated
ath0: associate with AP 00:18:39:d4:75:9e
ath0: RX AssocResp from 00:18:39:d4:75:9e (capab=0x401 status=0 aid=2)
ath0: associated
ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
ath0: no IPv6 routers present
On Monday 22 October 2007, Luis R. Rodriguez wrote:
> This is the problem. ath5k currently assumes only AR5210s (which are
> 802.11a only capable) have an RF5110. This is also an 802.11bg card.
> Essentially support for this is on the TODO list. For now we'll have
> to just detect this and inform users the card is not supported yet.
I've just given the ath5k driver from current wireless-everything.git
repository a try, and it looks like it now supports my Trust Speedshare
Turbo Pro PCMCIA card. At least, I can scan for networks.
As I don't have a wireless router at home (and no neighbors with open ones),
I cannot try an actual connection.
$ git describe
v2.6.24-rc8-689-g40dfd0a
I do get some probably bad messages in dmesg though:
<on insertion of the card>
pccard: CardBus card inserted into slot 0
PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 16
ath5k_pci 0000:02:00.0: registered as 'phy0'
phy0: Selected rate control algorithm 'pid'
ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
ath5k phy0: RF2112A 2GHz radio found (0x46)
udev: renamed network interface wlan0 to ath0
<on 'ifconfig ath0 up'>
ADDRCONF(NETDEV_UP): ath0: link is not ready
<on 'iwlist ath0 scan'>
ath5k phy1: noise floor calibration timeout (2412MHz)
ath5k phy1: noise floor calibration timeout (2412MHz)
ath5k phy1: noise floor calibration timeout (2422MHz)
ath5k phy1: ath5k_chan_set: unable to reset channel 3 (2422 Mhz)
ath0: failed to set channel 3 (2422 MHz) for scan
ath5k phy1: noise floor calibration timeout (2412MHz)
ath5k phy1: ath5k_chan_set: unable to reset channel 1 (2412 Mhz)
ath0: failed to restore operational channel after scan
The host system is a Toshiba Satellite A40 laptop (i386, Mobile Pentium 4)
running Debian unstable.
>From lspci:
01:0b.0 CardBus bridge [0607]: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 33)
01:0b.0 0607: 1179:0617 (rev 33)
02:00.0 Ethernet controller [0200]: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
02:00.0 0200: 168c:0013 (rev 01)
Still, definite progression over what we had in October :-) Thanks!
If you need any additional info, please ask.
Cheers,
FJP