Can't connect wirelessly! • KDE Community Forums

This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Board index

Can't connect wirelessly!

Page 2 of 2 (22 posts)

Previous • 1, 2

Tags:

Alec Registered Member Posts 565 Karma 1 OS	RE: Can't connect wirelessly! Tue Mar 31, 2009 4:40 am I'm thinking this has to be a driver issue... Could you please post the output of the following two commands after trying to connect? Code: Select all `dmesg \| grep -e ath9k -e wlan0 grep -e ath9k -e wlan0 /var/log/dmesg` (The second one might need to be run as root) Last edited by Alec on Tue Mar 31, 2009 4:41 am, edited 1 time in total. Get problems solved faster - get reply notifications through Jabber!
6tr6tr Registered Member Posts 20 Karma 0	RE: Can't connect wirelessly! Tue Mar 31, 2009 2:56 pm A quick note about the output here: this is after installing the new fixes for ath9k, so that may have altered the messages from earlier. But it's still not working, so... Code: Select all ath9k: disagrees about version of symbol struct_module ath9k: 0.1 ath9k 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 ath9k 0000:01:00.0: setting latency timer to 64 phy0: Selected rate control algorithm 'ath9k_rate_control' wlan0: authenticate with AP 00:14:3a:c1:61:0d wlan0: authenticate with AP 00:14:3a:c1:61:0d wlan0: authenticated wlan0: associate with AP 00:14:3a:c1:61:0d wlan0: RX AssocResp from 00:14:3a:c1:61:0d (capab=0x421 status=0 aid=2) wlan0: associated wlan0 (WE) : Wireless Event too big (344) wlan0: disassociating by local choice (reason=3) wlan0: direct probe to AP 00:14:3a:c1:61:0d try 1 wlan0: direct probe to AP 00:14:3a:c1:61:0d try 2 wlan0: direct probe to AP 00:14:3a:c1:61:0d try 3 wlan0: direct probe to AP 00:14:3a:c1:61:0d timed out wlan0 direct probe responded wlan0: authenticate with AP 00:14:3a:c1:61:0d wlan0: authenticate with AP 00:14:3a:c1:61:0d wlan0: authenticate with AP 00:14:3a:c1:61:0d wlan0: authentication with AP 00:14:3a:c1:61:0d timed out NOTE: Your second command resulted in the message: "grep: /var/log/dmesg: No such file or directory" So instead I ran the command on "/var/log/NetworkManager" Code: Select all Mar 31 10:42:26 mycomputer NetworkManager: wlan0: driver is 'ath9k'. Mar 31 10:42:26 mycomputer NetworkManager: wlan0: driver supports SSID scans (scan_capa 0x01). Mar 31 10:42:26 mycomputer NetworkManager: Found new 802.11 WiFi device 'wlan0'. Mar 31 10:42:26 mycomputer NetworkManager: (wlan0): exported as /org/freedesktop/Hal/devices/net_00_22_43_53_21_ff_0 Mar 31 10:42:30 mycomputer NetworkManager: (wlan0): device state change: 1 -> 2 Mar 31 10:42:30 mycomputer NetworkManager: (wlan0): bringing up device. Mar 31 10:42:30 mycomputer NetworkManager: (wlan0): preparing device. Mar 31 10:42:30 mycomputer NetworkManager: (wlan0): deactivating device (reason: 2). Mar 31 10:42:30 mycomputer NetworkManager: (wlan0): device state change: 2 -> 3 Mar 31 10:42:30 mycomputer NetworkManager: (wlan0): supplicant interface state: starting -> ready Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0) starting connection 'MyNetwork' Mar 31 10:44:10 mycomputer NetworkManager: (wlan0): device state change: 3 -> 4 Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 31 10:44:10 mycomputer NetworkManager: (wlan0): device state change: 4 -> 5 Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0/wireless): access point 'MyNetwork' has security, but secrets are required. Mar 31 10:44:10 mycomputer NetworkManager: (wlan0): device state change: 5 -> 6 Mar 31 10:44:10 mycomputer NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 31 10:44:11 mycomputer NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 10:44:11 mycomputer NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Mar 31 10:44:11 mycomputer NetworkManager: (wlan0): device state change: 6 -> 4 Mar 31 10:44:11 mycomputer NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 31 10:44:11 mycomputer NetworkManager: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Mar 31 10:44:11 mycomputer NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 31 10:44:11 mycomputer NetworkManager: (wlan0): device state change: 4 -> 5 Mar 31 10:44:11 mycomputer NetworkManager: Activation (wlan0/wireless): connection 'MyNetwork' has security, and secrets exist. No new secrets needed. Mar 31 10:44:11 mycomputer NetworkManager: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 31 10:44:11 mycomputer NetworkManager: (wlan0): supplicant connection state: inactive -> scanning Mar 31 10:44:36 mycomputer NetworkManager: Activation (wlan0/wireless): association took too long. Mar 31 10:44:36 mycomputer NetworkManager: (wlan0): device state change: 5 -> 6 Mar 31 10:44:36 mycomputer NetworkManager: Activation (wlan0/wireless): asking for new secrets Mar 31 10:44:36 mycomputer NetworkManager: (wlan0): supplicant connection state: scanning -> disconnected Mar 31 10:44:36 mycomputer NetworkManager: (wlan0): device state change: 6 -> 9 Mar 31 10:44:36 mycomputer NetworkManager: Activation (wlan0) failed for access point (MyNetwork) Mar 31 10:44:36 mycomputer NetworkManager: Activation (wlan0) failed. Mar 31 10:44:36 mycomputer NetworkManager: (wlan0): device state change: 9 -> 3 Mar 31 10:44:36 mycomputer NetworkManager: (wlan0): deactivating device (reason: 0).
bcooksley Administrator Posts 19765 Karma 87 OS	RE: Can't connect wirelessly! Wed Apr 01, 2009 3:12 am What is the output of this command? Code: Select all `cat /var/log/messages \| grep ath9k` KDE Sysadmin [img]content/bcooksley_sig.png[/img]
6tr6tr Registered Member Posts 20 Karma 0	RE: Can't connect wirelessly! Wed Apr 01, 2009 4:42 pm bcooksley wrote:What is the output of this command? Code: Select all `cat /var/log/messages \| grep ath9k` Mar 30 19:03:00 mycomputer kernel: ath9k 0000:01:00.0: PCI INT A disabled Mar 30 19:03:00 mycomputer kernel: ath9k: driver unloaded Mar 30 19:03:00 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:07:54 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:08:04 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:10:52 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:11:46 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:12:23 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:19:53 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:22:46 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:35:59 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 30 19:52:10 mycomputer kernel: ath9k: disagrees about version of symbol struct_module Mar 31 10:41:38 mycomputer sudo: MyLoginName : TTY=pts/1 ; PWD=/home/MyLoginName/downloads/computer/hardware/wireless/drivers/ath9k ; USER=root ; COMMAND=/bin/rpm -Uhv ath9k-kmp-pae-1_2.6.27.19_3.2-2.1.i586.rpm Mar 31 10:42:14 mycomputer sudo: MyLoginName : TTY=pts/1 ; PWD=/home/MyLoginName/downloads/computer/hardware/wireless/drivers/ath9k ; USER=root ; COMMAND=/sbin/rmmod ath9k Mar 31 10:42:25 mycomputer sudo: MyLoginName : TTY=pts/1 ; PWD=/home/MyLoginName/downloads/computer/hardware/wireless/drivers/ath9k ; USER=root ; COMMAND=/sbin/modprobe ath9k Mar 31 10:42:25 mycomputer kernel: ath9k: 0.1 Mar 31 10:42:25 mycomputer kernel: ath9k 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Mar 31 10:42:25 mycomputer kernel: ath9k 0000:01:00.0: setting latency timer to 64 Mar 31 10:42:25 mycomputer kernel: phy0: Selected rate control algorithm 'ath9k_rate_control' Mar 31 10:48:45 mycomputer sudo: MyLoginName : TTY=pts/1 ; PWD=/home/MyLoginName/downloads/computer/hardware/wireless/drivers/ath9k ; USER=root ; COMMAND=/usr/bin/grep -e ath9k -e wlan0 /var/log/dmesg Mar 31 10:49:05 mycomputer sudo: MyLoginName : TTY=pts/1 ; PWD=/home/MyLoginName/downloads/computer/hardware/wireless/drivers/ath9k ; USER=root ; COMMAND=/usr/bin/grep -e ath9k -e wlan0 dmesg Mar 31 10:50:18 mycomputer sudo: MyLoginName : TTY=pts/1 ; PWD=/home/MyLoginName/downloads/computer/hardware/wireless/drivers/ath9k ; USER=root ; COMMAND=/usr/bin/grep -e ath9k -e wlan0 /var/log/NetworkManager Mar 31 10:53:39 mycomputer sudo: MyLoginName : TTY=pts/1 ; PWD=/home/MyLoginName/downloads/computer/hardware/wireless/drivers/ath9k ; USER=root ; COMMAND=/usr/bin/grep -e ath9k -e wlan0 /var/log/dmesg
Alec Registered Member Posts 565 Karma 1 OS	RE: Can't connect wirelessly! Wed Apr 01, 2009 4:51 pm Code: Select all `ath9k: disagrees about version of symbol struct_module` It sounds as though your module and your kernel are not compatible... Did you get both of them from the same place? Is there perhaps an update to either that you did not apply? Get problems solved faster - get reply notifications through Jabber!
6tr6tr Registered Member Posts 20 Karma 0	RE: Can't connect wirelessly! Wed Apr 01, 2009 5:10 pm Alec wrote: Code: Select all `ath9k: disagrees about version of symbol struct_module` It sounds as though your module and your kernel are not compatible... Did you get both of them from the same place? Is there perhaps an update to either that you did not apply? This is due to attempts to fix things when I was unable to get on wirelessly. So, ath9k has not been working since I first put on opensuse 11.1/KDE 4.1.3. The update I put on recently: http://download.opensuse.org/repositori ... 1.i586.rpm There may be an issue with that but it's not the original reason for it not working. (The problem you've noticed may be keeping the update from working though) as it never worked even prior to the update. Any suggestions? Last edited by 6tr6tr on Wed Apr 01, 2009 6:11 pm, edited 1 time in total.
bcooksley Administrator Posts 19765 Karma 87 OS	RE: Can't connect wirelessly! Thu Apr 02, 2009 3:43 am The Ath9k driver is part of the base openSUSE distribution. On my system it is contained in the kernel-pae package, therefore an external package should not be needed. KDE Sysadmin [img]content/bcooksley_sig.png[/img]

Page 2 of 2 (22 posts)

Previous • 1, 2

Bookmarks

Who is online

Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]