You are not logged in.
Hi, I've installed both of these network managers and neither one, after the laptop going to sleep\suspend\hibernate is able to reconnect to my wifi network. I'm using simple WEP encryption. I have to restart the machine in order for them to reconnect again, does anyone have an idea why this is happening?
Thank you
Offline
netcfg works with suspend/hibernate for me. Did you make any changes involving /usr/lib/pm-utils/sleep/11netcfg?
Offline
netcfg works with suspend/hibernate for me. Did you make any changes involving /usr/lib/pm-utils/sleep/11netcfg?
No, I didn't make any changes. I made a basic setup of netcfg and tested the sleep>reconnect and it didn't work so I reinstalled wicd-bzr which I really like the GUI and features of.
Offline
Could you post the output of
$ lspci | grep Network
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
What happens after suspending, does it appear to attempt connection? In particular, what is the output of:
iwconfig
Does manually brining the connection down / up with netcfg give any interesting errors?
Offline
Could you post the output of
$ lspci | grep Network 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
What happens after suspending, does it appear to attempt connection? In particular, what is the output of:
iwconfig
Does manually brining the connection down / up with netcfg give any interesting errors?
I get:
lspci | grep Network
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11abg ESSID:"60O00"
Mode:Managed Frequency:2.412 GHz Access Point: 00:15:05:ED:19:F7
Bit Rate=54 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=59/70 Signal level=-51 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Weird thing is that when I shutdown or restart the system isn't able to stop the daemon and gives a FAILED mark next to it because of python or something, is that normal?
Offline
That seems fine. I have the same wireless device which connects without issue after resuming.
Weird thing is that when I shutdown or restart the system isn't able to stop the daemon and gives a FAILED mark next to it because of python or something, is that normal?
It doesn't sound normal, though I'm afraid I'm not familiar with wicd (I imagine that's the daemon you're referring to).
Could you post the output of:
ip addr show wlan0
does the output appear correct for your network?
Offline
I don't seem to have the "ip" command in my system.
Wicd, upon resume, tries to reconnect and then says it wasn't able to receive an ip address. When it scans for networks, the networks become grayed out.
Offline
I don't seem to have the "ip" command in my system.
Wicd, upon resume, tries to reconnect and then says it wasn't able to receive an ip address. When it scans for networks, the networks become grayed out.
The 'ip' command is part of 'iproute2'. An alternative is 'ifconfig wlan0', which should already be available. (I intentionally avoided this before as it is deprecated, though it still works perfectly well ).
Are you able to establish a connection if you assign a static IP?
Offline
I'm able to have wireless working after sleep only after I reload the interface and driver via these commands:
sudo ifconfig wlan0 down
sudo modprobe -r iwl3945
sudo modprobe iwl3945
sudo ifconfig wlan0 up
Isn't there a way to do this without having to run these commands every time? Why is the system not reconfiguring wireless on wake?
Offline
Not sure why the module must be reloaded after suspend. Is there anything in /var/log/messages?
It shouldn't be too difficult to work around this. I suggest adding a hook to pm-utils to bring the connection down and remove the module prior to suspend / hibernate, then on resume have it reload the module. Assuming you're using pm-utils to suspend, the example here should help.
Last edited by chpln (2010-01-03 22:53:29)
Offline
I have the same problem. It was introduced with kernel 2.6.32 and may be related to the b43 driver. Are you using these kernel and driver by any chance?
Offline
Mine is the intel iwl3945 driver but the funny thing is that the b43 driver also worked for me in xubuntu. You just need to modprobe The driver and remove it upon sleep. So, modprobe iwl3945 -r upon sleep/hibernate and modprobe iwl395 upon wake. Place the file in /etc/pm/sleep.d/ and sudo chmod +x the file and voilla it works correctly.
Offline
I get the same problem on my ath5k card. changing from wicd back to networkmanager makes no difference. This is a weird issue. A better fix than the above should really be found - although I'll do that. I had assumed it was a wicd issue....
Offline
I was having a similar problem after the 2.6.32 update. It may be related to the IPv6 module. If you don't need that you could just stop it from loading and see if it works. Check the last couple posts in this thread for more info - http://bbs.archlinux.org/viewtopic.php?id=87802&p=2
Offline
I've completely give up on Wicd and have since installed wpa_supplicant. The software is still too buggy at this point. Wpa_supplicant with wpa_gui meanwhile works like a charm and does the job quite nicely with a script I've found online for rc.conf.
Last edited by leberyo (2010-01-13 05:09:11)
Offline