FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 08-17-2008, 05:50 PM
Sjoerd Hardeman
 
Default Bug#492852: Wireless connects, but not to N networks

Hi,

I have problems connecting to my home network with the 2.6.25 kernel, to
which I can connect flawlessly with the 2.6.24 kernel. On my system, it
does bind to the network, but the following dhcp request fails due to a
time-out.
Connecting under the 2.6.25 kernel on my work network (which does not
support the N-mode wifi) does work fine.
I really have no idea about what kind of additional information I should
send. In /var/log/syslog nothing more than the dhcp-time-outs appears.
Please give me some clues on what to send, so that I can help sorting
out the problem.
Thanks in advance!

Sjoerd Hardeman

From lspci
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or
AGN Network Connection (rev 61)

From /var/log/syslog:
Aug 16 20:39:42 laptop NetworkManager: <info> Activation
(wlan0/wireless): access point 'sjoerd' is encrypted, and a key exists.
No new key
needed.
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was 'OK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'AP_SCAN 1'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was 'OK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'ADD_NETWORK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was '0'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 ssid 736a6f657264'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was 'OK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 proto WPA'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was 'OK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 key_mgmt WPA-PSK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was 'OK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 psk <key>'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was 'OK'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
Aug 16 20:39:43 laptop NetworkManager: <info> SUP: response was 'OK'
Aug 16 20:39:43 laptop NetworkManager: <info> Activation (wlan0) Stage
2 of 5 (Device Configure) complete.
Aug 16 20:39:46 laptop kernel: [ 273.524505] wlan0: Initial auth_alg=0
Aug 16 20:39:46 laptop kernel: [ 273.524514] wlan0: authenticate with
AP 00:1d:7e:ab:ac:66
Aug 16 20:39:46 laptop kernel: [ 273.526254] wlan0: RX authentication
from 00:1d:7e:ab:ac:66 (alg=0 transaction=2 status=0)
Aug 16 20:39:46 laptop kernel: [ 273.526260] wlan0: authenticated
Aug 16 20:39:46 laptop kernel: [ 273.526264] wlan0: associate with AP
00:1d:7e:ab:ac:66
Aug 16 20:39:46 laptop kernel: [ 273.530031] wlan0: RX AssocResp from
00:1d:7e:ab:ac:66 (capab=0x431 status=0 aid=1)
Aug 16 20:39:46 laptop kernel: [ 273.530037] wlan0: associated
Aug 16 20:39:46 laptop kernel: [ 273.530042] wlan0: switched to short
barker preamble (BSSID=00:1d:7e:ab:ac:66)
Aug 16 20:39:46 laptop kernel: [ 273.530104] wlan0 (WE) : Wireless
Event too big (366)
Aug 16 20:39:46 laptop kernel: [ 273.530137] wlan0: WMM queue=2 aci=0
acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
Aug 16 20:39:46 laptop kernel: [ 273.530141] wlan0: WMM queue=3 aci=1
acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
Aug 16 20:39:46 laptop kernel: [ 273.530145] wlan0: WMM queue=1 aci=2
acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
Aug 16 20:39:46 laptop kernel: [ 273.530149] wlan0: WMM queue=0 aci=3
acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
Aug 16 20:39:46 laptop kernel: [ 273.530718] ADDRCONF(NETDEV_CHANGE):
wlan0: link becomes ready
Aug 16 20:39:46 laptop NetworkManager: <info> Supplicant state changed: 1
Aug 16 20:39:46 laptop NetworkManager: <info> Activation
(wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected
to access point 'sjoerd'.
Aug 16 20:39:46 laptop NetworkManager: <info> Activation (wlan0) Stage
3 of 5 (IP Configure Start) scheduled.
Aug 16 20:39:46 laptop NetworkManager: <info> Activation (wlan0) Stage
3 of 5 (IP Configure Start) started...
Aug 16 20:39:47 laptop NetworkManager: <info> Activation (wlan0)
Beginning DHCP transaction.
Aug 16 20:39:47 laptop NetworkManager: <info> Activation (wlan0) Stage
3 of 5 (IP Configure Start) complete.
Aug 16 20:39:47 laptop NetworkManager: <info> DHCP daemon state is now
12 (successfully started) for interface wlan0
Aug 16 20:39:47 laptop dhclient: wmaster0: unknown hardware address type 801
Aug 16 20:39:47 laptop avahi-daemon[6982]: Joining mDNS multicast group
on interface wlan0.IPv6 with address fe80::21f:3bff:fe89:529b.
Aug 16 20:39:47 laptop avahi-daemon[6982]: New relevant interface
wlan0.IPv6 for mDNS.
Aug 16 20:39:47 laptop avahi-daemon[6982]: Registering new address
record for fe80::21f:3bff:fe89:529b on wlan0.*.
Aug 16 20:39:48 laptop NetworkManager: <info> DHCP daemon state is now
1 (starting) for interface wlan0
Aug 16 20:39:48 laptop dhclient: wmaster0: unknown hardware address type 801
Aug 16 20:39:51 laptop dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 6
Aug 16 20:39:51 laptop NetworkManager: <info> Old device 'wlan0'
activating, won't change.
Aug 16 20:39:53 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 7
Aug 16 20:39:56 laptop kernel: [ 284.257290] wlan0: no IPv6 routers present
Aug 16 20:39:57 laptop dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 15
Aug 16 20:40:00 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 7
Aug 16 20:40:07 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 19
Aug 16 20:40:12 laptop dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 19
Aug 16 20:40:26 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 20
Aug 16 20:40:31 laptop dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255 port 67 interval 19
Aug 16 20:40:32 laptop NetworkManager: <info> Device 'wlan0' DHCP
transaction took too long (>45s), stopping it.
Aug 16 20:40:32 laptop dhclient: There is already a pid file
/var/run/dhclient.wlan0.pid with pid 9026
Aug 16 20:40:32 laptop dhclient: killed old client process, removed PID file
Aug 16 20:40:32 laptop dhclient: wmaster0: unknown hardware address type 801
Aug 16 20:40:32 laptop dhclient: wmaster0: unknown hardware address type 801
Aug 16 20:40:32 laptop dhclient: DHCPRELEASE on wlan0 to 192.168.1.1 port 67
Aug 16 20:40:33 laptop NetworkManager: <info> Activation (wlan0) Stage
4 of 5 (IP Configure Timeout) scheduled...
Aug 16 20:40:33 laptop NetworkManager: <info> DHCP daemon state is now
14 (normal exit) for interface wlan0
Aug 16 20:40:33 laptop NetworkManager: <info> DHCP daemon state is now
11 (unknown) for interface wlan0
Aug 16 20:40:33 laptop NetworkManager: <info> DHCP daemon state is now
14 (normal exit) for interface wlan0
Aug 16 20:40:33 laptop NetworkManager: <info> Activation (wlan0) Stage
4 of 5 (IP Configure Timeout) started...
Aug 16 20:40:33 laptop NetworkManager: <info> Activation (wlan0)
failure scheduled...
Aug 16 20:40:33 laptop NetworkManager: <info> Activation (wlan0) Stage
4 of 5 (IP Configure Timeout) complete.
Aug 16 20:40:33 laptop NetworkManager: <info> Activation (wlan0) failed
for access point (sjoerd)
Aug 16 20:40:33 laptop NetworkManager: <info> Activation (wlan0) failed.
Aug 16 20:40:33 laptop NetworkManager: <info> Deactivating device wlan0.
Aug 16 20:40:33 laptop kernel: [ 319.856854] wlan0:
deauthenticate(reason=3)
 
Old 11-13-2008, 09:46 PM
Moritz Muehlenhoff
 
Default Bug#492852: Wireless connects, but not to N networks

On Sun, Aug 17, 2008 at 07:50:42PM +0200, Sjoerd Hardeman wrote:
> Hi,
>
> I have problems connecting to my home network with the 2.6.25 kernel, to
> which I can connect flawlessly with the 2.6.24 kernel. On my system, it
> does bind to the network, but the following dhcp request fails due to a
> time-out.
> Connecting under the 2.6.25 kernel on my work network (which does not
> support the N-mode wifi) does work fine.
> I really have no idea about what kind of additional information I should
> send. In /var/log/syslog nothing more than the dhcp-time-outs appears.
> Please give me some clues on what to send, so that I can help sorting
> out the problem.
> Thanks in advance!

There have been plenty of lwlwifi fixes in 2.6.26. Does updating to
the current Lenny kernels fix the problem for you?

Cheers,
Moritz



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 05:30 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org