Ubuntu Networking :: Wicd Won't Connect After Suspend / Resume?
Apr 10, 2010
i just installed ubuntu 9.10 netbook remix on my acer aspireone ao532h netbook, and so far, it's been working beautifully. much better than the windows 7 starter edition that came with the machine. the only problem i've experienced so far had to do with the wireless connection. initially, the connection would drop during certain types of activities (e.g. downloading updates or programs, or even streaming videos videos) and the network manager would freeze so completely that i'd have to hard reboot. that seems to have been fixed by installing wicd (following a suggestion here: http://ubuntuforums.org/showthread.php?t=1135723&page=2), meaning that it hasn't disconnected in the several hours since i've been using it. however, wicd has a different problem: it disconnects after a suspend / resume cycle. this requires a reboot to fix also, as not only does it disconnect, but it looses awareness of the network altogether. obviously, this could be a real headache on a netbook that gets closed and opened frequently.
I'm running Gnome with the bluetooth applet and I have to explicitly use the applet, select the mouse and tell it to connect. It automatically connects just fine when I boot into windows.
I have the same problem with both a Microsoft bluetooth mouse 5000 and a "BLUETOOTH HID v1.02 Mouse [Interlink Bluetooth Mouse]".
I'm actually running Debian Lenny and using WICD. Sometimes when I wake the system up from standby it reconnects me to my wireless connection, but sometimes it wont. (Same thing for hibernate). On the times that it wont work it just hangs at obtaining IP address.
After I resume from hibernate with my cpu frequency manually set to the highest settings (2ghz) the network manager shows not wifi APs. "wlan0" shows under both ifconfig and iwconfig but "iwlist wlan0 scan" says no results. "sudo iwlist wlan0 scan" also says no results. I've tried rmmod then modprobe with no luck. Rebooting is the only way I can get WiFi working.
I can get wifi working again by: - rebooting - changing the cpu scaling to a lower setting then hibernate/resume - changing the cpu scaling to a lower setting then 'sudo rmmod ath9k; sudo modprobe ath9k;'
I am using Ubuntu 10.04 with Atheros ar5008 (AR5BXB72) using ath9k drives Code: $ lspci |grep Atheros 0e:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) Code: $ uname -r 2.6.32-24-generic
I'v just installed wicd. I can't get it to sart, I get errors saying that wicd couldn't connect to it's dbus interface and the wicd deamon has shut down. Then there's a report from SELinux saying that it's preventing /usr/bin/python "write" access on /etc/dhcp/manager-settings.conf and that access is denied to wicd. I can get wicd to start if I su to root, but I'd like to not have to do that every time I boot. Is there a fix?
I am running Natty on a Lenovo T410. I can connect to wireless with no problem using the panel applet but not using wicd. syslog shows it trying to get a DHCP address and finally timing out with no lease offers. I think a big clue is that if I monitor wlan0 using wireshark I get no traffic at all when it tries to connect, whereas with the applet I see the dhcp traffic. It seems as though wicd is connecting to the wrong wlan0. Running "dhclient wlan0" directly gives the same behavior as wicd. I need to use wicd because I typically run enlightenment so can't use the ubuntu applet.
I've installed ubuntu 9.10 using a minimal install and started from there installing the rest of the things I needed. I'm running KDE4.4 and Wicd 1.6.1.
Problem is, wicd worked fine, but I don't know what happened before I got this annoying problem.
After logging into KDE, wicd asks me for my password in order to connect to the network-device. After filling that in, I get the message code...
As you can see in the logging, internet is working fine. I manually have to start wicd-client and I get an extra wicd-icon in the taskbar showing me the signal strength as it should do.
I've been searching a lot, but can't find anything about this, except a lot of people having the same errormessage, but they have some errors in the wicd.log too.
I'm trying to use wicd instead of network manager because I want a "no fuss" way to use wireless on wmii. However, wicd will not find any networks unless network-manager has been run and has connected to a network since startup. If it hasn't connected to a wireless network, the wicd will find no networks, and iwlist won't provide a list of networks either.
This seems to mean that network-manager is doing something to the interface when it connects that needs to be done to make it usable, but I'm not sure what it is or how exactly to find out. I do know that the interface (eth2) will not appear in ifconfig if network manager hasn't connected, which I assume means that it hasn't been brought up. ifconfig eth2 up makes it show up, but I still can't connect with wicd. What can I do?
I'm running Ubuntu 10.04, generic 2.6.32-22 kernel, MacBook 5,5 using the Broadcom STA driver. (more details below)
I'm at a family member's house for the holiday and was trying to use their wifi. Its a WEP connection (I tried to tell them to change but they won't listen). In the wicd connection manager, I see their network, set the encryption to WEP (passphrase), enter the password, and hit connect. It says bringing up the card, checking authentication, then gets to Acquiring IP address, sits there for a minute, then times out saying unable to connect.
I know I used the right password because it passed the Authenticating part (tested with a wrong password that hangs at this point). I know that my wifi card works because I used a store's unsecured wifi connection through wicd. I know the wifi network works because my brother's windows netbook can get on just fine. I'm running through the same router right now with a wire instead. Why I can't connect wirelessly?
My laptop won't resume after it suspends. It works fine under win 7 so it's not the hardware. The light says it's on and it's pretty much a blank screen. I'm not sure whether it's operational but the screen is off. It has exactly the same resault a waiting for the blank screen except it won't go back on.
I've just upgraded from 9.10 to 10.04 via the upgrade manager. Prior to the upgrade I was able to suspend and hibernate without any problems. Now that I have upgraded to 10.04, I can suspend however when I resume I am back at the gdm login prompt, logging in again with a new session.Having just done another test whilst writing this, it actually appears that if I select suspend from the top right I am suspended and can resume my session. If I close the lid on my laptop (which is supposed to suspend) I am logged out and suspended.Also, Hibernate doesn't work as well - sometimes it never actually hibernates (just sits on a black screen) and sometimes it doesn't resume (it's never hibernated and resumed correctly since the upgrade)
Whatever way I suspend my laptop (menu, keyboard shortcut, close lid), it seems to suspend just find (no panic lights, suspend LED indicator flashing as expected). However, when i try to resume, the laptop seems to begin the proper wakeup process (for example, the DVD-drive is tested), there's a lot of HDD activity for about 5 seconds, screen does not power on, and then the laptop just shuts off.
System setup: lucid beta 2, fully updated (just check now) LG E-500 laptop /w nvidia gforce mobile 8400G bios version 1.17 from June 2007 (not sure this is important)
Things I tried: * Completely remove anything to do with gpu drivers and installed nvidia-current driver. * Suspend stress test described here. this didn't work at all. The first test failed (with ac adapter attached) and the second test suspended but didn't automatically resume (see "the behavior" above). Also, when I booted up again, no apport bug report is created. I tried both with rtc set to utc=yes and utc=no. with utc=yes, the second test did automatically resume, but the same problem happened (laptop shutdown while resuming). * The debugging steps described here, but I couldn't get the "no_console_suspend" option to work. I tried adding both "no_console_suspend" and "no_console_suspend=1" (without quotes) to the boot script in the grub menu, but when I did pm-suspend in tty1, the laptop really did suspend. I would like to try to do this again if someone could explain how to add this option.
Notes: * Not sure this is relevant, but when I boot up after a failed resume attempt, wireless network is disabled (this only happens after a failed resume!!!). * I found a package called nvram-wakeup in synaptic that seems to be related to this. This package is not installed. Should I install it? In case this is relevant, forgot to mention I'm running ubuntu in dual-boot along side windows7.
I don't have any problems with 9.04 at all with suspend & resume just shutdown (wont power off usb saitek keyboard & razer mouse) but i don't care for that I prefer suspend & resume. However trying 9.10 suspend works while resume gets a black screen & locks up. Now on 10.04 it will suspend very fast but will not power up from resume keyboard & usb power is turned off thats what I can't figure out I have checked bios & changes settings after settings & nothing happens. I know in windows everything works but i do not want windows at all I prefer linux (ubuntu). In my asus eee pc 1001p suspend & resume works with both 9.10 & 10.04.
When I close my laptop lid (it goes into suspend mode). When I open it again, I can't see anything but a black screen. I have to reset the computer manually to accessUbuntu again.On a related note probably.. for 'some' screensavers, when I click to re-access my desktop, the screensaver freezes, but I can't see the unlock dialogue. I can however still type my password and it will unlock, I just can't see what I'm doing
in kubuntu how can i resume from suspend without password? it annoys the crap out of me i have been looking all over and cant find anything in settings to do this
Karmic 2.6.31-22-generic, Asus M3N78-EM, MCE remote with USB/IR dongle, latest Bios, Bios PM enable and set for suspend S3. IT will suspend but I need to depress case power button for it to resume. I want to use my remote control, I also can not get it to resume from Keyboard/mouse (See Note Below). Only suspend and power button work.
$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
When I suspend my computer and then resume later in the day my USB keyboard locks up. The only way I have found to reset the keyboard is to disconnect the USB cable from the USB port and then reconnect it.
I just got a Dell Inspiron 1764 and am dual booting it with Win7 and Ubuntu 9.10.Whenever I hibernate or suspend, it goes through everything fine, but then when I resume it just boots to a black screen and I have to do a hard shutdown. Is there a fix for this? I know it's a fairly common issue.
I've got a Thinkpad X31 with ATI M6 Ly card. Since Karmic, and Lucid, I get no suspend/hibernate/resume. If/when I select resume or close the lid, Lucid goes through the suspend cycle, and for approximately half a second it actually seems to go into suspend, then the screen comes back on, black, but definitely on, and absolutely no response to any keyboard input - have to hard-shutdown by holding down the power button. I've read that the problem is with the Ubuntu kernel, and that installing/compiling 2.6.33 fixes the issue, but causes other ones.
I have an issue with my Sony vaio fw31e not resuming from suspend. Reported this as a bug: [URL] The usual ways of suspending, from the kde 4 menu, from the power/battery widget or by lid closing always result in no resume. However, running pm-suspend from a root terminal suspends and resumes just fine. My question is, how does one delve into the way that the usual methods initiate suspend? Maybe if I could find out what each of these methods actually does, I may be able to see what is going wrong? I had been running squeeze on this lappy since July 2009 with no suspend issues until an update broke it sometime in January. The install is being fully upgraded every day at the moment.
If I suspend my notebook it starts the usual slow orange blinking indicating the suspend mode got reached. There is also evidence in the various log files that this works. If I try to resume it hangs a for 3 seconds and then I get the hdd-password screen from my bios and the notebook boots from zero. I couldn't find anything in /var/log/messages nor dmesg. If I first boot to windows (grub 2nd partition) and then restart and boot to linux, all the suspend works fine
how do i disable the screen lock after i wake my computer from suspend? i would prefer to be able to just wake the computer up and have it go right to the desktop, without having to enter a password. i used to use ubuntu until today, and i remember having to run "gconf-editor" and then switching off on "lock_on_suspend" under apps/gnome-power-management from the menu that popped up. i tried to run "gconf-editor" in fedora 15, but that doesn't appear to exist. i've searched around and haven't been able to find an answer, so i'm wondering if anybody knows what to do?
I've upgraded 4 boxes (32- and 64-bit) from Suse 11.1 to 11.2 with no unresolvable issues. Now I'm stuck with my 5th box, a Dell Dimension 8400 desktop box (yes, an old brick, 32-bit). I can suspend to RAM ("suspend") and to disk ("hibernate") fine, but resume seems to fail. In Suse 11.1 I used kpowersave (GUI in the sys tray) to suspend to RAM. For some reason, it couldn't suspend to disk but that didn't bother me. kpowersave relies on the powersaved running.
Note I had upgraded my 11.1 installation to all shiny and new KDE 4.3 stuff, and while KDE 4.3 seems not to use powersaved (and thus kpowersave) all worked fine. Upgrading to 11.2 has removed kpowersave and powersaved. I don't mind switching to another way if only I could find documentation what's being used on KDE 4.3 (and/or Suse 11.2). All I find by googling is that the daemon used is powerdevil, and that I should use a GUI for suspending (this battery monitoring plasma app).
Well, if I do that on this box it simply does -- nothing. So I tried s2ram and a2disk directly:Running s2ram with the --force option works, but the box doesn't resume. Goes on, screen stays blank, mouse and keyboard don't work. s2disk complains about not being able to "stat the resume device file". I gave it the --resume_device /dev/sda6 option, and it hibernated fine. But it doesn't resume. Pressing the power on button just starts Suse anew (and recovers the file system journals, so I assume it thinks it has crashed before).
So I think I have 2 questions: What the heck does Suse 11.2 use for suspend/hibernate and resume? Is there any how-to available to learn what I need to configure? Why can't I resume from successful s2ram or s2disk operations? /var/log/pm-suspend-log or pm-powersave-log don't provide any clues.
Laptop 1 is an acer aspire 5570. closing and opening the lid works a few times, after editing acpi_handler.sh, and battery life reporting is ok during this time. then, for no apparent reason, the laptop no longer responds to the lid closing, and no longer seems to be able to read the battery charge state. once this has occurred, the computer will also no longer restart, it tries a few times, with lights flashing and the hd making ugly noises. the only way to extricate the computer from this state is to pull and reinsert the battery.
Laptop 2 is a gateway nv18. suspend/resume with the lid are ok, mostly. the issure here is no display at all in x. but the computer does respond to ctrl-alt-backspace to kill x, with the command prompt returning. still not good. I'm trying a fresh install on the gateway, to see if this was just an installation glitch. Both laptops performed flawlessly in 13 otherwise.
I've been trying to find an answer to the following problem : whenever my PC is put in Suspend/Hibernate mode, it fails to recover when pushing the power button. This happens both with automatic suspend or manual suspend. I've been reading this problem, and mine is quite similar, but no solution is given.
uname -rmi 2.6.18-194.11.4.el5 x86_64 x86_64 PS: this computer is not connected to Internet, no update possible.
I just upgraded to 9.10 (Karmic Koala) on a Dell laptop. Now when I close the laptop lid to suspend and then open it to resume, the audio disappears; have to reboot to get the audio back. I remember having this problem a while ago back on Hardy Heron and finding a kludge to fix it - a line inserted in a shell script that gets invoked on resume
Title says it all. I close my laptop lid. It goes into suspend mode. I open it up again, the computer powers up... and I see a black blank screen. No key combinations seems to bring anything back.
I have recently updated my Ubuntu 9.10 install to Ubuntu 10.04 and the default kernel to 2.6.32-23 on my Acer Aspire 5738z laptop with 3 GB RAM and Intel GMA 4500m graphics card.
My problem is sometimes the laptop fails to resume after being Suspended to RAM. The problem is not consistent. Most of the time the system resumes properly but then some times it doesn't . It even doesn't respond to the Magic Keys. I am left with no other alternative but to keep the power button pressed till the laptop shuts down.
