Simon Geard wrote:
> Hi all...
> 
> On finding ath5k integrated into the new 2.6.25 kernel, I decided to
> give it a try, replacing the current madwifi release. Unfortunately,
> though the drivers appear to load and recognise the device correctly,
> any attempt to scan for APs finds nothing. Rebooting with madwifi, at
> least two are in range, such as the one I'm currently connected to.
> 
> Not sure might be needed for someone to help, but here's what I've got:
> 
> ### Related sections of dmesg output:
> 
> ath5k_pci 0000:03:06.0: registered as 'phy0'
> phy0: Selected rate control algorithm 'pid'
> ath5k phy0: Atheros AR5213A chip found (MAC: 0x79, PHY: 0x45)
> ath5k phy0: RF2112A 2GHz radio found (0x56)
> ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
> ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [AAZA] -> GSI 22 (level,
> low) -> IRQ 22
> PCI: Setting latency timer of device 0000:00:10.1 to 64
> udev: renamed network interface wlan0 to ath0
> 
> ### Relevant lspci output:
> 
> 03:06.0 Ethernet controller: Atheros Communications, Inc. AR5212
> 802.11abg NIC (rev 01)
>         Subsystem: D-Link System Inc D-Link AirPlus DWL-G520 Wireless
> PCI Adapter(rev.B)
>         Flags: bus master, medium devsel, latency 168, IRQ 16
>         Memory at fdfe0000 (32-bit, non-prefetchable) [size=64K]
>         Capabilities: [44] Power Management version 2
> 
> ### Output of 'ip link':
> 
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> qlen 1000
>     link/ether 00:1b:fc:c9:6b:35 brd ff:ff:ff:ff:ff:ff
> 3: wmaster0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> qlen 1000
>     link/ieee802.11 00:11:95:be:05:03 brd ff:ff:ff:ff:ff:ff
> 4: ath0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
> qlen 1000
>     link/ether 00:11:95:be:05:03 brd ff:ff:ff:ff:ff:ff
> 
> ### Output of 'iwlist ath0 scan':
> 
> ath0      No scan results
> 
> 
> Note - this last command takes about a second to run, before returning
> no results. Under the madwifi drivers, it returns results instantly. Not
> sure if this is significant, but seems worth mentioning...
> 
> 
> Any ideas?
> 
> Simon.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> ath5k-users mailing list
> [email protected]
> https://lists.ath5k.org/mailman/listinfo/ath5k-users

Hello,

Try with the latest compat wireless,

alban

_______________________________________________
ath5k-users mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-users

Reply via email to