I just did a fresh install of 11.2 on my Thinkpad (previously running 11.1) and am having trouble with getting wifi to work properly.
My wireless will not connect reliably. Sometimes it connects after reboot but then drops and will not reconnect. Below in line 4 of the status query you can see that it says DHCP4 client NOT running.
ifstatus wlan0
wlan0 device: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
DHCP4 client NOT running
wlan0 is up
5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:13:02:4e:66:38 brd ff:ff:ff:ff:ff:ff
Configured IPv4 routes for interface wlan0:
default 192.168.1.1 - -
0 of 1 configured IPv4 routes for interface wlan0 up
wlan0 IEEE 802.11abg ESSID:“###########”
Mode:Managed Frequency:2.452 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key: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
Why is the dhcp client not running and how do I start it?
I set networking to use traditional method in Yast network setting and removed networkmanager. I am using wicd instead. I was experiencing the problem without wicd too.
In 11.1 wifi just worked for me and it’s the last thing I expected to have trouble with in 11.2. I’m wasting so much time over this.
When I did the install I had the wifi radio turned off. Do you think that could have affected the correct drivers being installed?
Mine worked really well under 11.1 which is why I’m puzzled as to why I’m having trouble now. Do you think that me having the wireless radio off at the time of installation may have upset something? It does appear that the drivers and modules are loaded though.
Any idea why the dhcp client might stop working?
What command did you run to get your output? I’ll run the same to see how mine compares.
If your eth0 is working OK with the current DHCP settings, I can’t imagine wlan will be different.
But some users have had DNS issues and had to set up their ISP info there.
wlan off at install matters NOT.
I’m no expert in this area, so hang about for the guru’s.
On 12/23/2009 11:26 AM, caf4926 wrote:
>
> su terminal
>
>
> Code:
> --------------------
> lspci -v
> --------------------
>
>
> If your eth0 is working OK with the current DHCP settings, I can’t
> imagine wlan will be different.
> But some users have had DNS issues and had to set up their ISP info
> there.
>
> wlan off at install matters NOT.
>
> I’m no expert in this area, so hang about for the guru’s.
The DHCP problem is a bug in the code on the 11.2 installation media. It has
been fixed with updates. Once you get the updates, you will be OK. If you have
updated within the last day, then deleting /etc/resolv.conf and remaking the
connection should be sufficient.
You may also have a problem with routing. That you can check by the command
/sbin/route -n
If you do not have a line with the UG flags set, then you have that problem.
That is corrected bu the command
sudo /sbin/route add default gw XXX.XXX.XXX.XXX
where the XXX are replaced by the IP address of your router/AP. Mine is
192.168.1.1. This bug is also corrected by recent updates.
OK, an update. After doing an unconditional update, and removing the resolv.conf file I managed to hook up to the network with wifi. But if for some reason the wifi disconnects e.g. after connecting my ethernet cable or turning the radio off) the wifi doesn’t reconnect when required.
My route shows
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
I see from the above that the UG flag is set to use the eth0 interface. Should there be another UG line for wlan0 too? I tried adding the default GW as you suggested but it returns “SIOCADDRT: File exists”.
I’ve also tried deleting the wifi device in Yast’s network settings, deleting resolv.conf again and then re-configuring the wifi device but that only fixes it temporarily. As soon as the wifi is disconnected it doesn’t reconnect. Connecting via eth0 never has a problem.
On 12/24/2009 01:56 AM, suse tpx60s wrote:
>
> OK, an update. After doing an unconditional update, and removing the
> resolv.conf file I managed to hook up to the network with wifi. But if
> for some reason the wifi disconnects e.g. after connecting my ethernet
> cable or turning the radio off) the wifi doesn’t reconnect when
> required.
>
> My route shows
>> Kernel IP routing table
>> Destination Gateway Genmask Flags Metric Ref Use
>> Iface
>> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
>> eth0
>> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
>> wlan0
>> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
>> eth0
>> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
>> lo
>> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
>> eth0
>
> I see from the above that the UG flag is set to use the eth0 interface.
> Should there be another UG line for wlan0 too? I tried adding the
> default GW as you suggested but it returns “SIOCADDRT: File exists”.
>
> I’ve also tried deleting the wifi device in Yast’s network settings,
> deleting resolv.conf again and then re-configuring the wifi device but
> that only fixes it temporarily. As soon as the wifi is disconnected it
> doesn’t reconnect. Connecting via eth0 never has a problem.
It looks as if your wired connection is set to activate “on boot”. You should
change that to be active “On cable connection”. This can be changed with YaST =>
Network Devices => Network Settings, but you can also edit (as root)
/etc/sysconfig/network/ifcfg-eth0 and change STARTMODE to ‘ifplugd’. After you
do that, the wired connection will be active only when a cable is plugged in.
I tried as you suggested and using yast set eth0 to only start when cable is connected.
Unfortunately, it’s not helping. My wireless still doesn’t connect once connection has been lost. The entry for the default gateway is often removed requiring me to re-add it.
I really can’t understand this as my wireless worked so well in 11.1.
Are there any debug commands I can run which may help with diagnosing this.
On 12/26/2009 08:46 AM, suse tpx60s wrote:
>
> I tried as you suggested and using yast set eth0 to only start when
> cable is connected.
> Unfortunately, it’s not helping. My wireless still doesn’t connect once
> connection has been lost. The entry for the default gateway is often
> removed requiring me to re-add it.
>
> I really can’t understand this as my wireless worked so well in 11.1.
>
> Are there any debug commands I can run which may help with diagnosing
> this.
Try deleting the wireless connection and remaking it.
The diagnostic info is likely in /var/log/NetworkManager.
I’ve tried deleting and re-adding the wireless card without any luck. I’m not using NetworkManager so that log doesn’t exist. I’m using ifup with wicd as the network manager.
I think I’m going to have to try a re-install of 11.2 as I can’t see what else I can try.
Before I go through a reinstall of 11.2 I just want to check a couple of things. In my dmesg logs I have the following which may help with diagnosing my problem.
This is what appears in dmesg after I come out if s2ram. The messages are similar when switch from wifi to eth0 and then back to wifi.
[17427.708087] PM: Finishing wakeup.
[17427.708090] Restarting tasks … done.
[17673.217379] e1000e 0000:02:00.0: irq 29 for MSI/MSI-X
[17673.269128] e1000e 0000:02:00.0: irq 29 for MSI/MSI-X
[17674.868659] Registered led device: iwl-phy0::radio
[17674.869426] Registered led device: iwl-phy0::assoc
[17674.869520] Registered led device: iwl-phy0::RX
[17674.869764] Registered led device: iwl-phy0::TX
[17686.211343] wlan0: authenticate with AP 00:14:85:ce:98:1e
[17686.213127] wlan0: authenticated
[17686.213174] wlan0: associate with AP 00:14:85:ce:98:1e
[17686.215640] wlan0: RX AssocResp from 00:14:85:ce:98:1e (capab=0x431 status=0 aid=1)
[17686.215648] wlan0: associated
[17693.396397] wlan0: deauthenticated (Reason: 6)
[17694.396060] wlan0: direct probe to AP 00:14:85:ce:98:1e try 1
[17694.398582] wlan0 direct probe responded
[17694.398589] wlan0: authenticate with AP 00:14:85:ce:98:1e
[17694.400358] wlan0: authenticated
[17694.400365] wlan0: associate with AP 00:14:85:ce:98:1e
[17694.403094] wlan0: RX ReassocResp from 00:14:85:ce:98:1e (capab=0x431 status=0 aid=1)
[17694.403101] wlan0: associated
[17704.405384] wlan0: disassociating by local choice (reason=3)
[17709.608683] wlan0: authenticate with AP 00:14:85:ce:98:1e
[17709.610480] wlan0: authenticated
[17709.610486] wlan0: associate with AP 00:14:85:ce:98:1e
[17709.612930] wlan0: RX AssocResp from 00:14:85:ce:98:1e (capab=0x431 status=0 aid=1)
As you can see the wlan0 seems to associate and authenticate fine with the router but then immediately disassociates itself with the router. This seems to repeat until I restart the network service after which it connects fine and stays connected.
On 12/30/2009 09:26 AM, suse tpx60s wrote:
>
> Any clues as to what’s going on here?
The reason codes for deauthentication are as follows:
Code…Description…Meaning
0…noReasonCode…Normal operation.
1…unspecifiedReason…Client associated but no longer authorized.
2…previousAuthNotValid…Client associated but not authorized.
3…deauthenticationLeaving…The access point went offline, deauthenticating
the client.
4…disassociationDueToInactivity…Client session timeout exceeded.
5…disassociationAPBusy…The access point is busy, performing load balancing,
for example.
6…class2FrameFromNonAuthStation…Client attempted to transfer data before it
was authenticated.
7…class2FrameFromNonAssStation…Client attempted to transfer data before it
was associated.
8…disassociationStaHasLeft…Operating System moved the client to another
access point using non-aggressive load balancing.
9…staReqAssociationWithoutAuth…Client not authorized yet, still attempting
to associate with an access point.
99…missingReasonCode…Client momentarily in an unknown state.
Reply With Quote
You appear to have driver problems, and reinstallation is unlikely to help. I do
not follow the Intel driver situation and do not know if compat-wireless would help.