iwl3945 not able to associate kernel 2.6.27-7 ap channel 13

Bug #293607 reported by Daniel Dekovic
2
Affects Status Importance Assigned to Milestone
linux-backports-modules-2.6.27 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: linux-backports-modules-2.6.27-7-generic

I'm running ubuntu linux 8.10 on my msi ex700 laptop with 2.6.27-7 and 2.6.24-21 kernel. I'm using iwl3945 driver. I noticed that after upgrade my network didn't worked at all, but after I installed linux-backports-modules-2.6.27-7-generic package everything was fine again till I cahnged channel from 11 to 13 on my ap. When I did that I got following error:

Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0) starting connection 'Auto default'
Nov 3 21:32:17 heroina NetworkManager: <info> (wlan0): device state change: 3 -> 4
Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Nov 3 21:32:17 heroina NetworkManager: <info> (wlan0): device state change: 4 -> 5
Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto default' requires no security. No secrets needed.
Nov 3 21:32:17 heroina NetworkManager: <info> Config: added 'ssid' value 'default'
Nov 3 21:32:17 heroina NetworkManager: <info> Config: added 'scan_ssid' value '1'
Nov 3 21:32:17 heroina NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Nov 3 21:32:17 heroina NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 3 21:32:17 heroina NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
Nov 3 21:32:17 heroina NetworkManager: <info> Config: set interface ap_scan to 1
Nov 3 21:32:20 heroina NetworkManager: <info> (wlan0): supplicant connection state change: 0 > 2
Nov 3 21:32:32 heroina NetworkManager: <info> wlan0: link timed out.
Nov 3 21:32:42 heroina NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation.
Nov 3 21:32:42 heroina NetworkManager: <info> (wlan0): device state change: 5 -> 9
Nov 3 21:32:42 heroina NetworkManager: <info> Activation (wlan0) failed for access point (default)
Nov 3 21:32:42 heroina NetworkManager: <info> Marking connection 'Auto default' invalid.
Nov 3 21:32:42 heroina NetworkManager: <info> Activation (wlan0) failed.
Nov 3 21:32:42 heroina NetworkManager: <info> (wlan0): device state change: 9 -> 3
Nov 3 21:32:42 heroina NetworkManager: <info> (wlan0): deactivating device (reason: 0).

As I try manually to bring my network up I noticed that I don't receive any dhcp offers from my ap although I should. This is only happening when I switch my ap channel from 11 to 13 on 2.6.27-7 kernel. On 2.6.24-21 everything is working fine. Wireless is working on 2.6.27-7 kernel but only if I'm not using channel 13.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Daniel,

This actually looks to be a duplicate of bug 288401 which the kernel team is already aware of. The workaround mentioned in bug 288401 is to add the following to /etc/modprobe.d/options:

options cfg80211 ieee80211_regdom=EU

I'll go ahead and mark this a duplicate of that report. Please continue to track this issue there. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.