Skip to contentSkip to conversation

ath5k and Atheros AR242x - No scan results

DISCUSSION Joel Roth 6 participants 19 messages Jun 30, 2009 – Jul 17, 2009

lore
Share & tools
lore

Joel Roth

author
#0 lore raw

Hello all,

I'd appreciate some help troubleshooting my wireless connection.

I have a Toshiba Satellite L305 series laptop running Debian sid with a recent, stock Debian kernel version 2.6.29-2-486.

$ lspci | grep Atheros

05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

I am seeking to connect to a D-Link 614+ wireless router. For initial testing, the AP is unencrypted, unsecured.

My wife's G3 i-Book with AfterTheMac USB wireless adapter connected just fine, on the first try.

I believe I have the modules I should have:

$ lsmod | grep 80211
mac80211              139680  1 ath5k
cfg80211               21576  2 ath5k,mac80211

My wireless network interface is present:

$ iwconfig wlan0

wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

$ ifconfig wlan0

wlan0 Link encap:Ethernet HWaddr 00:21:63:82:82:40
UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

However, I don't find the D-Link 614+:

$ iwlist wlan0 scan

wlan0 No scan results

And of course, dhclient fails to find a server.

Am I missing something? What could I try next?
I'd appreciate any pointers.

Thanks.

Signature · 1 line
Joel Roth
author
#2 lore raw
Quoted 3 lines · Luis R. Rodriguez

On Tue, Jun 30, 2009 at 10:09 AM, Joel Roth<[email protected]> wrote:

sudo ip link set dev wlan0 up

Hi Luis,

I've tried this, with no obvious change.

I've not used the 'ip' command before in my networking explorations, always relying on ifconfig to bring up devices.

Ifconfig reports that wlan0 is UP. Is there any other kind of UP that I need to understand?

Another question: From the point of view of setting up wireless, if the wlan0 device is UP, should 'iwlist scan' return a list of access points?

Or are there any other conditions to be met?

Thanks.

Quoted 8 lines
Quoted 4 lines
$ iwlist wlan0 scan

wlan0     No scan results

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 1 line
Joel Roth
#3 lore raw
Quoted 13 lines · Joel Roth
Quoted 3 lines · Luis R. Rodriguez

On Tue, Jun 30, 2009 at 10:09 AM, Joel Roth<[email protected]> wrote:

sudo ip link set dev wlan0 up

Hi Luis,

I've tried this, with no obvious change.

I've not used the 'ip' command before in my networking explorations, always relying on ifconfig to bring up devices.

Quoted 8 lines

Ifconfig reports that wlan0 is UP. Is there any other kind of UP that I need to understand?

Another question: From the point of view of setting up wireless, if the wlan0 device is UP, should 'iwlist scan' return a list of access points?

Or are there any other conditions to be met?

http://wireless.kernel.org/en/users/Documentation/Reporting_bugs#Identifying_the_bug

Luis

#4 lore raw
In reply to Joel Roth

2009/6/30 Joel Roth <[email protected]>:

Quoted 53 lines

Hello all,

I'd appreciate some help troubleshooting my wireless connection.

I have a Toshiba Satellite L305 series laptop running Debian sid with a recent, stock Debian kernel version 2.6.29-2-486.

$ lspci | grep Atheros

05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

I am seeking to connect to a D-Link 614+ wireless router. For initial testing, the AP is unencrypted, unsecured.

My wife's G3 i-Book with AfterTheMac USB wireless adapter connected just fine, on the first try.

I believe I have the modules I should have:

$ lsmod | grep 80211
mac80211              139680  1 ath5k
cfg80211               21576  2 ath5k,mac80211

My wireless network interface is present:

$ iwconfig wlan0

wlan0     IEEE 802.11  ESSID:""
         Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated Tx-Power=0 dBm
         Retry min limit:7   RTS thr:off   Fragment thr=2352 B Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:21:63:82:82:40 UP BROADCAST MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

However, I don't find the D-Link 614+:

$ iwlist wlan0 scan

wlan0     No scan results

And of course, dhclient fails to find a server.

Quoted 7 lines

Am I missing something? What could I try next?
I'd appreciate any pointers.

Thanks.

--
Joel Roth

Hello ;-)

Can you please sent the dmesg output when ath5k loads ? Also do you see any messages on dmesg while scaning ?

Signature · 3 lines
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
author
#5 lore raw
Quoted 59 lines · Nick Kossifidis

2009/6/30 Joel Roth <[email protected]>:

Quoted 58 lines

Hello all,

I'd appreciate some help troubleshooting my wireless connection.

I have a Toshiba Satellite L305 series laptop running Debian sid with a recent, stock Debian kernel version 2.6.29-2-486.

$ lspci | grep Atheros

05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

I am seeking to connect to a D-Link 614+ wireless router. For initial testing, the AP is unencrypted, unsecured.

My wife's G3 i-Book with AfterTheMac USB wireless adapter connected just fine, on the first try.

I believe I have the modules I should have:

$ lsmod | grep 80211
mac80211              139680  1 ath5k
cfg80211               21576  2 ath5k,mac80211

My wireless network interface is present:

$ iwconfig wlan0

wlan0     IEEE 802.11  ESSID:""
         Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated Tx-Power=0 dBm
         Retry min limit:7   RTS thr:off   Fragment thr=2352 B Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:21:63:82:82:40 UP BROADCAST MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

However, I don't find the D-Link 614+:

$ iwlist wlan0 scan

wlan0     No scan results

And of course, dhclient fails to find a server.

Am I missing something? What could I try next?
I'd appreciate any pointers.

Thanks.

Quoted 7 lines
Quoted 2 lines

--
Joel Roth

Hello ;-)

Can you please sent the dmesg output when ath5k loads ? Also do you see any messages on dmesg while scaning ?

Hi :-)

On loading the ath5k driver, dmesg reports:

[83838.020161] ath5k 0000:05:00.0: PCI INT A disabled
[83852.364249] cfg80211: Using static regulatory domain info
[83852.364253] cfg80211: Regulatory domain: US
[83852.364255]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[83852.364258]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[83852.364261]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364264]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364266]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364269]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364271]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[83852.364274] cfg80211: Calling CRDA for country: US
[83852.427844] ath5k 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[83852.427858] ath5k 0000:05:00.0: setting latency timer to 64
[83852.427916] ath5k 0000:05:00.0: registered as 'phy0'
[83852.620221] wmaster0 (ath5k): not using net_device_ops yet
[83852.620896] phy0: Selected rate control algorithm 'minstrel'
[83852.620913] wlan0 (ath5k): not using net_device_ops yet
[83852.621565] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)

On attempting to scan:

[84202.916169] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Thanks!

Signature · 1 line
Joel Roth
author
#6 lore raw
Quoted 91 lines · Joel Roth
Quoted 59 lines · Nick Kossifidis

2009/6/30 Joel Roth <[email protected]>:

Quoted 58 lines

Hello all,

I'd appreciate some help troubleshooting my wireless connection.

I have a Toshiba Satellite L305 series laptop running Debian sid with a recent, stock Debian kernel version 2.6.29-2-486.

$ lspci | grep Atheros

05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

I am seeking to connect to a D-Link 614+ wireless router. For initial testing, the AP is unencrypted, unsecured.

My wife's G3 i-Book with AfterTheMac USB wireless adapter connected just fine, on the first try.

I believe I have the modules I should have:

$ lsmod | grep 80211
mac80211              139680  1 ath5k
cfg80211               21576  2 ath5k,mac80211

My wireless network interface is present:

$ iwconfig wlan0

wlan0     IEEE 802.11  ESSID:""
         Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated Tx-Power=0 dBm
         Retry min limit:7   RTS thr:off   Fragment thr=2352 B Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:21:63:82:82:40 UP BROADCAST MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

However, I don't find the D-Link 614+:

$ iwlist wlan0 scan

wlan0     No scan results

And of course, dhclient fails to find a server.

Am I missing something? What could I try next?
I'd appreciate any pointers.

Thanks.

Quoted 7 lines
Quoted 2 lines

--
Joel Roth

Hello ;-)

Can you please sent the dmesg output when ath5k loads ? Also do you see any messages on dmesg while scaning ?

Hi :-)

On loading the ath5k driver, dmesg reports:

[83838.020161] ath5k 0000:05:00.0: PCI INT A disabled
[83852.364249] cfg80211: Using static regulatory domain info
[83852.364253] cfg80211: Regulatory domain: US
[83852.364255]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[83852.364258]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[83852.364261]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364264]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364266]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364269]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[83852.364271]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[83852.364274] cfg80211: Calling CRDA for country: US
[83852.427844] ath5k 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[83852.427858] ath5k 0000:05:00.0: setting latency timer to 64
[83852.427916] ath5k 0000:05:00.0: registered as 'phy0'
[83852.620221] wmaster0 (ath5k): not using net_device_ops yet
[83852.620896] phy0: Selected rate control algorithm 'minstrel'
[83852.620913] wlan0 (ath5k): not using net_device_ops yet
[83852.621565] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Quoted 5 lines

On attempting to scan:

[84202.916169] ADDRCONF(NETDEV_UP): wlan0: link is not ready

Thanks!

Is there anything I can glean from these diagnostics? I can certainly compile a more recent version of the driver.

Anything else I might try to get this hardware working for me?

Regards,

Signature · 1 line
Joel Roth
author
#7 lore raw
In reply to Joel Roth
Quoted 49 lines · Joel Roth

Hello all,

I'd appreciate some help troubleshooting my wireless connection.

I have a Toshiba Satellite L305 series laptop running Debian sid with a recent, stock Debian kernel version 2.6.29-2-486.

$ lspci | grep Atheros

05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

I am seeking to connect to a D-Link 614+ wireless router. For initial testing, the AP is unencrypted, unsecured.

My wife's G3 i-Book with AfterTheMac USB wireless adapter connected just fine, on the first try.

I believe I have the modules I should have:

$ lsmod | grep 80211
mac80211              139680  1 ath5k
cfg80211               21576  2 ath5k,mac80211

My wireless network interface is present:

$ iwconfig wlan0

wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

$ ifconfig wlan0

wlan0 Link encap:Ethernet HWaddr 00:21:63:82:82:40
UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

However, I don't find the D-Link 614+:

$ iwlist wlan0 scan
Quoted 8 lines

wlan0 No scan results

And of course, dhclient fails to find a server.

Am I missing something? What could I try next?
I'd appreciate any pointers.

Thanks.

Okay, I'm back with a new kernel 2.6.30.1 and the latest ath5k. Here are my basic diagnostics data.

$ iwlist wlan0 scan

wlan0 No scan results

$ iwlist wlan0 ap

wlan0 Interface doesn't have a list of Peers/Access-Points

$ iwconfig wlan0

wlan0 IEEE 802.11bg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

$ ifconfig wlan0

wlan0 Link encap:Ethernet HWaddr 00:21:63:82:82:40
UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

dmesg highlights

[    4.884157] ath5k 0000:05:00.0: enabling device (0000 -> 0002)
[    4.884223] ath5k 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    4.884283] ath5k 0000:05:00.0: setting latency timer to 64
[    4.884326] ath5k 0000:05:00.0: registered as 'phy0'
[    6.411392] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[  337.543014] ADDRCONF(NETDEV_UP): wlan0: link is not ready

I compiled the kernel with debugfs support for wireless. Can someone point me to helpful docs in setting this up.

Also, is there a chance that another driver would serve me better?

Regards,

Signature · 1 line
Joel Roth
#8 lore raw

2009/7/12 Joel Roth <[email protected]>:

Quoted 102 lines · Joel Roth
Quoted 49 lines

Hello all,

I'd appreciate some help troubleshooting my wireless connection.

I have a Toshiba Satellite L305 series laptop running Debian sid with a recent, stock Debian kernel version 2.6.29-2-486.

$ lspci | grep Atheros

05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

I am seeking to connect to a D-Link 614+ wireless router. For initial testing, the AP is unencrypted, unsecured.

My wife's G3 i-Book with AfterTheMac USB wireless adapter connected just fine, on the first try.

I believe I have the modules I should have:

$ lsmod | grep 80211
mac80211              139680  1 ath5k
cfg80211               21576  2 ath5k,mac80211

My wireless network interface is present:

$ iwconfig wlan0

wlan0     IEEE 802.11  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated Tx-Power=0 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:21:63:82:82:40 UP BROADCAST MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

However, I don't find the D-Link 614+:

$ iwlist wlan0 scan
Quoted 8 lines

wlan0     No scan results

And of course, dhclient fails to find a server.

Am I missing something? What could I try next?
I'd appreciate any pointers.

Thanks.

Okay, I'm back with a new kernel 2.6.30.1 and the latest ath5k. Here are my basic diagnostics data.

$ iwlist wlan0 scan

wlan0     No scan results

$ iwlist wlan0 ap

wlan0     Interface doesn't have a list of Peers/Access-Points

$ iwconfig wlan0

wlan0     IEEE 802.11bg  ESSID:""
         Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated Tx-Power=27 dBm
         Retry min limit:7   RTS thr:off   Fragment thr:off Power Management:off
         Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:21:63:82:82:40 UP BROADCAST MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

dmesg highlights

[    4.884157] ath5k 0000:05:00.0: enabling device (0000 -> 0002) [    4.884223] ath5k 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [    4.884283] ath5k 0000:05:00.0: setting latency timer to 64
[    4.884326] ath5k 0000:05:00.0: registered as 'phy0'
[    6.411392] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [  337.543014] ADDRCONF(NETDEV_UP): wlan0: link is not ready

I compiled the kernel with debugfs support for wireless. Can someone point me to helpful docs in setting this up.

Quoted 6 lines

Also, is there a chance that another driver would serve me better?

Regards,

--
Joel Roth

O.K. can you try madwifi so that we can eliminate the possibility of a hw failure ?

Signature · 3 lines
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick
author
#9 lore raw
Quoted 105 lines · Nick Kossifidis

2009/7/12 Joel Roth <[email protected]>:

Quoted 104 lines · Joel Roth
Quoted 49 lines

Hello all,

I'd appreciate some help troubleshooting my wireless connection.

I have a Toshiba Satellite L305 series laptop running Debian sid with a recent, stock Debian kernel version 2.6.29-2-486.

$ lspci | grep Atheros

05:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

I am seeking to connect to a D-Link 614+ wireless router. For initial testing, the AP is unencrypted, unsecured.

My wife's G3 i-Book with AfterTheMac USB wireless adapter connected just fine, on the first try.

I believe I have the modules I should have:

$ lsmod | grep 80211
mac80211              139680  1 ath5k
cfg80211               21576  2 ath5k,mac80211

My wireless network interface is present:

$ iwconfig wlan0

wlan0     IEEE 802.11  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated Tx-Power=0 dBm
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:21:63:82:82:40 UP BROADCAST MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

However, I don't find the D-Link 614+:

$ iwlist wlan0 scan
Quoted 8 lines

wlan0     No scan results

And of course, dhclient fails to find a server.

Am I missing something? What could I try next?
I'd appreciate any pointers.

Thanks.

Okay, I'm back with a new kernel 2.6.30.1 and the latest ath5k. Here are my basic diagnostics data.

$ iwlist wlan0 scan

wlan0     No scan results

$ iwlist wlan0 ap

wlan0     Interface doesn't have a list of Peers/Access-Points

$ iwconfig wlan0

wlan0     IEEE 802.11bg  ESSID:""
         Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated Tx-Power=27 dBm
         Retry min limit:7   RTS thr:off   Fragment thr:off Power Management:off
         Link Quality:0  Signal level:0  Noise level:0
         Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0 Tx excessive retries:0  Invalid misc:0   Missed beacon:0

$ ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:21:63:82:82:40 UP BROADCAST MULTICAST  MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

dmesg highlights

[    4.884157] ath5k 0000:05:00.0: enabling device (0000 -> 0002) [    4.884223] ath5k 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [    4.884283] ath5k 0000:05:00.0: setting latency timer to 64
[    4.884326] ath5k 0000:05:00.0: registered as 'phy0'
[    6.411392] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70) [  337.543014] ADDRCONF(NETDEV_UP): wlan0: link is not ready

I compiled the kernel with debugfs support for wireless. Can someone point me to helpful docs in setting this up.

Also, is there a chance that another driver would serve me better?

Quoted 7 lines
Quoted 4 lines

Regards,

--
Joel Roth

O.K. can you try madwifi so that we can eliminate the possibility of a hw failure ?

My naive compile of madwifi failed; however, I was able to boot up the factory Windows Vista.

Vista advised me to:

1) turn on the hardware wifi switch <blush>

2) use the hotkey combination to enable wifi

Then I was able to see the AP in Vista's Connect-To pane.

Rebooting under 2.6.30.1 for amd64, the driver still doesn't find access points.

None of my hotkeys work under Linux (the toshiba_acpi driver doesn't load), so I can't press the Fn-F8 key combination to enable wifi.

It may be that the wireless driver is fine, but that I simply can't (yet) enable the hardware.

Thanks for your suggestions.

Joel

Signature · 1 line
Joel Roth
#10 lore raw
Quoted 5 lines · Joel Roth

Vista advised me to:

1) turn on the hardware wifi switch <blush>

2) use the hotkey combination to enable wifi

It might be worth trying compat-wireless or 2.6.31-rcX. Support for reading the card's internal rfkill state was added in the post-2.6.30 time-frame.

Signature · 1 line
Bob Copeland %% www.bobcopeland.com
author
#11 lore raw
Quoted 10 lines · Bob Copeland
Quoted 5 lines · Joel Roth

Vista advised me to:

1) turn on the hardware wifi switch <blush>

2) use the hotkey combination to enable wifi

It might be worth trying compat-wireless or 2.6.31-rcX. Support for reading the card's internal rfkill state was added in the post-2.6.30 time-frame.

Okay, I'll give this a go and report back. Thanks.

Quoted 1 line

Bob Copeland %% www.bobcopeland.com

Signature · 1 line
Joel Roth
author
#12 lore raw
Quoted 10 lines · Bob Copeland
Quoted 5 lines · Joel Roth

Vista advised me to:

1) turn on the hardware wifi switch <blush>

2) use the hotkey combination to enable wifi

It might be worth trying compat-wireless or 2.6.31-rcX. Support for reading the card's internal rfkill state was added in the post-2.6.30 time-frame.

I installed compat-wireless against my 2.6.30.1 kernel, and also the iw command.

I've read some docs, however I'm not sure what the next step should be.

My general idea is that I should be able to see a list of access points, however iwlist doesn't tell me anything new.

# iwlist wlan0 ap

wlan0 Interface doesn't have a list of Peers/Access-Points

I'm appending some diagnostics.

Here's what dmesg tells me after 'modprobe ath5k'

[256888.841092] cfg80211: Using static regulatory domain info
[256888.841098] cfg80211: Regulatory domain: US
[256888.841101] 	(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[256888.841105] 	(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[256888.841109] 	(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[256888.841112] 	(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[256888.841116] 	(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[256888.841119] 	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[256888.841123] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[256888.841134] cfg80211: Calling CRDA for country: US
[256888.870476] ath5k 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[256888.870492] ath5k 0000:05:00.0: setting latency timer to 64
[256888.870563] ath5k 0000:05:00.0: registered as 'phy0'
[256888.943464] ath: EEPROM regdomain: 0x65
[256888.943466] ath: EEPROM indicates we should expect a direct regpair map
[256888.943471] ath: Country alpha2 being used: 00
[256888.943474] ath: Regpair used: 0x65
[256888.947007] phy0: Selected rate control algorithm 'minstrel'
[256888.947904] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
# iw list

Wiphy phy0
Band 1:
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (passive scanning)
* 2472 MHz [13] (20.0 dBm) (passive scanning)
* 2484 MHz [14] (disabled)
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point

# iw wlan0 scan

BSS 00:40:05:c5:4f:19 (on wlan0)

        TSF: 5703065889 usec (0d, 01:35:03)
        freq: 2412
        beacon interval: 100
        capability: ESS PBCC (0x0041)
        signal: -92.00 dBm
        SSID: default
        Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0 
        DS Paramater set: channel 1
BSS 00:16:b6:db:fd:78 (on wlan0)
        TSF: 625899182784 usec (7d, 05:51:39)
        freq: 2437
        beacon interval: 100
        capability: ESS ShortSlotTime (0x0401)
        signal: -101.00 dBm
        SSID: linksys
        Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0

54.0
DS Paramater set: channel 6
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 9.0 12.0 48.0

# iw wlan0 info
Interface wlan0
        ifindex 6
        type managed
Signature · 1 line
Joel Roth
author
#13 lore raw
Quoted 15 lines · Joel Roth
Quoted 10 lines · Bob Copeland
Quoted 5 lines · Joel Roth

Vista advised me to:

1) turn on the hardware wifi switch <blush>

2) use the hotkey combination to enable wifi

It might be worth trying compat-wireless or 2.6.31-rcX. Support for reading the card's internal rfkill state was added in the post-2.6.30 time-frame.

I installed compat-wireless against my 2.6.30.1 kernel, and also the iw command.

Quoted 8 lines

I've read some docs, however I'm not sure what the next step should be.

My general idea is that I should be able to see a list of access points, however iwlist doesn't tell me anything new.

# iwlist wlan0 ap

wlan0 Interface doesn't have a list of Peers/Access-Points

After some RTFM'ing,

# iw wlan0 scan

BSS 00:40:05:c5:4f:19 (on wlan0) -- associated

	TSF: 9251942689 usec (0d, 02:34:11)
	freq: 2412
	beacon interval: 100
	capability: ESS PBCC (0x0041)
	signal: -40.00 dBm
	SSID: default
	Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0 
	DS Paramater set: channel 1
BSS 00:16:b6:db:fd:78 (on wlan0)
	TSF: 629448825249 usec (7d, 06:50:48)
	freq: 2437
	beacon interval: 100
	capability: ESS ShortSlotTime (0x0401)
	signal: -105.00 dBm
	SSID: linksys
	Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
	DS Paramater set: channel 6
	ERP: Barker_Preamble_Mode
	Extended supported rates: 6.0 9.0 12.0 48.0 
# iw wlan0 connect default 
# dhclient wlan0

And voila! I have an IP address on wlan0.
I can't think of anything more that I need. :-)

Oh, maybe a pointer for others.

Perhaps I was just missing the iw 'connect' incantation? 'iwlist' was a complete red herring; didn't help me find my AP.

http://linuxwireless.org/en/users/Documentation was the only site of several I visited mentioning 'iw' at all!

And at linuxwireless, I find no example of using 'iw' to set up a connection. I'd be glad to contribute one.

Thanks Bob, Nick and others for your tips.

Signature · 1 line
Joel Roth
#14 lore raw
In reply to Joel Roth
Quoted 3 lines · Joel Roth
# iwlist wlan0 ap

wlan0 Interface doesn't have a list of Peers/Access-Points

# iwlist wlan0 scan

should have worked, but I'm glad you're making good use of iw :)

johannes

author
#15 lore raw
Quoted 9 lines · Johannes Berg
Quoted 3 lines · Joel Roth
# iwlist wlan0 ap

wlan0 Interface doesn't have a list of Peers/Access-Points

# iwlist wlan0 scan

should have worked, but I'm glad you're making good use of iw :)

Hmm. It does work _now_, provided the interface is UP.

That may be thanks to having a recent kernel with the latest compat-wireless drivers.

I was also misled by assuming iwlist's 'ap' option would provide useful information.

To summarize what I now know, the steps to follow for basic wireless connectivity to an unencrypted network would be:

1. kernel and driver setup - use compat-wireless

2. set wireless interface to UP

ifconfig <interface> up

3. find available networks using

iw dev <interface> scan
or
iwlist <interface> scan

4. connect to a network using

iw dev <interface> connect <SSID>

5. acquire IP address, typically by

dhclient <interface>

Regards,

Joel

Quoted 1 line

johannes

Signature · 1 line
Joel Roth
#16 lore raw
Quoted 1 line · Joel Roth

Hmm. It does work _now_, provided the interface is UP.

Yes, it has to be UP.

Quoted 5 lines

That may be thanks to having a recent kernel with the latest compat-wireless drivers.

I was also misled by assuming iwlist's 'ap' option would provide useful information.

It hasn't for many years, really. Oh well, not much we can do about it.

Quoted 7 lines

To summarize what I now know, the steps to follow for basic wireless connectivity to an unencrypted network would be:

1. kernel and driver setup - use compat-wireless

2. set wireless interface to UP

Quoted 7 lines

ifconfig <interface> up

3. find available networks using

iw dev <interface> scan
or
iwlist <interface> scan

This isn't strictly necessary if you know the SSID already.

Quoted 3 lines

4. connect to a network using

iw dev <interface> connect <SSID>

The old way of doing this would be
iwconfig wlan0 essid <SSID>

But as long as you don't need ancient hardware, you're probably better off using iw. You can also use
iw dev <interface> connect -w <SSID>
if you run a current git snapshot, and it will wait for the connection to be established or fail and print the status.

Oh and if you're just doing this on the command line you can do
iw <interface> connect <SSID>

(i.e. leave out the "dev"), but please don't script it that way :)

johannes

#17 lore raw
In reply to Joel Roth
Quoted 11 lines

1. kernel and driver setup - use compat-wireless

2. set wireless interface to UP

ifconfig <interface> up

3. find available networks using

iw dev <interface> scan
or
iwlist <interface> scan

And maybe here the tools could emit "interface <interface> isn't up" as a more specfic error message ?!?

Signature · 1 line
http://www.holgerschurig.de
#18 lore raw
Quoted 6 lines · Holger Schurig
Quoted 6 lines

1. kernel and driver setup - use compat-wireless

2. set wireless interface to UP

ifconfig <interface> up

Quoted 8 lines
Quoted 5 lines

3. find available networks using

iw dev <interface> scan
or
iwlist <interface> scan

And maybe here the tools could emit "interface <interface> isn't up" as a more specfic error message ?!?

They do.

johannes