Ubuntu Networking :: Wireless Fails After Reboot / Suspend
Dec 30, 2010
I recently installed Ubuntu 10.04.1 LTS and have it set to dual-boot with windows 7 on my gateway tablet PC. Since installing, sometimes when I suspend or reboot, my wireless does not work. To be more clear - it is working fine, then I either suspend/reboot, then I come back and no wireless networks show up at all. I can still connect with ethernet cable though. I can solve it by rebooting multiple times (usually around 1-5 times) and then it (magically) seems to work again. I have also tried switching from network-manager to wicd, but the problem persists. With both network-manager and wicd, I've tried simulating a reboot for the wireless by using the command 'sudo modprobe -r iwl3945 && sudo modprobe iwl3945' (network-manager) and 'sudo /etc/init.d/wicd restart' (wicd), but these do not seem to work.
I have a bit of a silly question, as I should know better, but I have a Toshiba A200 laptop that wasn't working well with the default ath5k driver so I switched to madwifi. It works great, but after the laptop goes into suspend or reboots, the driver doesn't get loaded and wireless isn't available.
I've been working around this by going to proprietary drivers, which shows the madwifi driver. When I say activate, it comes back with a failed message but works.
I'd like to save myself from going through this several times a day, but I'm not 100% sure what to do. Do I add madwifi to modprobe or something like that?
reason my wireless is constantly failing. the only solution is a reboot but it will start to fail again. I use hp mini 210 ubuntu netbook remix.here is a log file
Mar 19 19:37:37 nicky-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 19 19:37:37 nicky-laptop NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (
I can get connected to the Internet when I reboot the system, but the connection usually fails after within 10 mins. However, even then the network manager says it's connected. Never reconnect, manually or automatically.
I am applying a virtual interface (eth0:0) which is failing after the system reboots. It actually cause the default interface (eth0) to fail as well, I must manually go in and remove the configuration for the eth:0:0 and restart the network to get it running again. How do I successfully add a Virtual interface to Fedora 11 that will stick when rebooted.
After upgrade from Hardy to Lucid, wireless card (Atheros Communications Inc. AR5212 ) was extremely slow and not really functional. I installed the madwifi driver following the instructions from Ubuntu Wiki and wireless works now. But, after suspend Network Manager nor Wicd could scan for any wirelss networks.
I found a workaround: in console, run "dhclient" and, magically, while the scan for Ip address is going on, suddenly also Network Manager starts connecting to my default access point!
I've got a Dell Latitude 131L with Broadcom B4311, running Ubuntu 10.04. Wireless networking generally works just fine, but I lose my connection when the computer is suspended, and I have to reconnect manually from the drop down menu.
I cannot see any wireless networks after waking the computer from suspend. Wireless works fine on boot. I've tried restarting the network service, but I still don't see any available wireless networks.
I have FC 12 install on a Compaq nx9600 that comes with a Broadcom BMC4306 wireless card. I'm not sure what my kernel is, but I have all of the updates for FC 12.Whenever my laptop resumes from Hibernation/Suspend my Enable Wireless check box in the Network Manager is greyed out and it will not come back till I reboot the computer. Is there any one out there that can help with this problem, as I do not want to disable my Hibernation/Suspend as I tend to forget to turn the laptop off for a few days on end, and this beast sucks a lot of power so it is a drain on my power bill.
A few months back, my Lenovo IdeaPad Y510 stopped connecting to my wireless network after coming out of Suspend (it had worked fine previously). Wireless networking is simply disabled, and I have to reboot in order to get it back. I tried upgrading my OS from Intrepid all the way to Lucid, but the problem persisted. I also tried changing my 00sleep_module as suggested in this thread, but to no avail.
I've had my wireless networking (on an Acer Aspire laptop) working perfectly well for at least six months.Now, quite suddenly, after a reboot I get the message from wicd, "No wireless networks found". I probably was running a week or so before that without needing a reboot. Windows wireless is fine (I'm using it to send this post).In addition, my sound stopped working and I see a fleeting message to the effect that the sound system is reverting from analog to digital.I'm running Kubuntu 9.10. My guess is that something in a recent round of updates knocked me out of the box. How can I proceed to set things aright?
I just upgraded to natty last night, and everything is working fine except for the network manager. I can enable and configure the wireless card via bash, but the network manager widget will not manage the wireless card.
When I first boot up, the "Enable wireless" check box is greyed out. After I enable the card via the terminal, the "Enable wireless" check box becomes ungreyed, but every time I click it, it instantly unchecks itself. I feel like Currly from the Three Stoogies. Check, uncheck, Check, uncheck.. "Slaps face repeatedly."
Maverick (64 bit) will suspend to RAM on my desktop computer immediately after I boot it up (before I start working). But after I have some programs open, it always fails to suspend. I get the typical blinking cursor in the upper right corner of a black screen. Then, after 20 seconds, the screen comes back on. The logs contain a message that "Freezing of tasks failed after 20.01 seconds." The problem task is usually listed as gnome-panel. Sometimes other tasks are listed too (such as Nautilus). Why will gnome-panel allow me to suspend soon after booting up, but not allow suspend after I start working with applications? I am not changing anything in the panel. And deleting the applets I have installed (system monitor and hardware monitor) doesn't make any difference - the problem continues. As I said, sometimes Nautilus is listed as the task that refuses to freeze.
If I switch users, I can suspend. I assume switching users just puts me in the "clean" state I have with my own user after booting up, so this doesn't really tell me anything new. I have searched all the other threads I can find. Most of the extensive suspend debugging threads are either from the 2007 era or they deal with laptops or resume issues. My issue is failure to suspend on a desktop. As you can see from the logs, I've been working on this for a month already!
Here's a typical error message:
Nov 7 01:52:59 MyComputer kernel: [ 1625.221296] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): Nov 7 01:52:59 MyComputer kernel: [ 1625.221374] gnome-panel D 000000010001fdc2 0 1925 1853 0x00800004
Here's an example log showing 2 tasks that fail to freeze:
Code:
Nov 9 01:25:09 MyComputer kernel: [16615.765114] PM: Syncing filesystems ... done. Nov 9 01:25:09 MyComputer rtkit-daemon[1738]: The canary thread is apparently starving. Taking action. Nov 9 01:25:09 MyComputer kernel: [16615.767512] PM: Preparing system for mem sleep
Ubuntu Maverick (64 bit) will suspend to RAM on my desktop computer immediately after I boot it up (before I start working). But after I have some programs open, it always fails to suspend.
I get the typical blinking cursor in the upper right corner of a black screen. Then, after 20 seconds, the screen comes back on. The logs contain a message that "Freezing of tasks failed after 20.01 seconds."
The problem task is usually listed as gnome-panel. Sometimes other tasks are listed too (such as Nautilus).
Why will gnome-panel allow me to suspend soon after booting up, but not allow suspend after I start working with applications? I am not changing anything in the panel. And deleting the applets I have installed (system monitor and hardware monitor) doesn't make any difference - the problem continues. As I said, sometimes Nautilus is listed as the task that refuses to freeze.
If I switch users, I can suspend. I assume switching users just puts me in the "clean" state I have with my own user after booting up, so this doesn't really tell me anything new.
I have searched all the other threads I can find. Most of the extensive suspend debugging threads are either from the 2007 era or they deal with laptops or resume issues. My issue is failure to suspend on a desktop.
As you can see from the logs, I've been working on this for a month already!
Here's a typical error message: Nov 7 01:52:59 MyComputer kernel: [ 1625.221296] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): Nov 7 01:52:59 MyComputer kernel: [ 1625.221374] gnome-panel D 000000010001fdc2 0 1925 1853 0x00800004
I've been searching forums like for 2 days, but couldn't find any similar problem. First of all im running Ubuntu 10.04 desktop version on my netbook Acer aspire one (AOD150) Every time i turn off my netbook and after turn it on, in "Hardware drivers" it says that driver for wifi is not in use, also button for switching on/off wifi is not working. So everytime i start up i have to go into "Hardware drivers", remove driver for wifi, and then activate it again. And everything is working gr8 after. Its just too annoying to do it everytime.
i installed linux on this laptop around 2 years ago (hp g6000 laptop) with internal wireless card and was unable to get the internal wireless card to work under ubuntu. so i purchased a linux supported usb wifi stick, which worked perfectly (connected automatically on boot) each time. however, i moved house recently and lost this usb wifi stick. i am currently using a ethernet connection to my hub and have updated ubuntu to the current version. all software is also up to date. since i lost my old wifi stick, i have used this connection, however, yesterday when i was on videos, all of a sudden (without me having done anything {intentionally anyway}) i see the wireless connection graphic at the top right of the screen! both green dots lit and the connection was live! so i disconnected the ethernet and used the wifi all night without a hitch.
i was extremely happy with what had happened and could not work out why it had decided to work (having not been aware to doing anything, except sit and watch a videos video). so i shut down, go to bed, go to work the next day and come home looking forward to browsing the web from my sofa, and guess what, no internet connection once i logged in! i just think 'if it worked last night, it can work now'. i have ndiswrapper and i have the .inf driver file for the internal card installed in ndiswrapper. i have opened that tonight and it looks okay - except it says 'hardware present: no'. i do not understand what has happened at all. (also there is a wifi 'on off' switch on the front of the laptop, with an orange led but neither position makes any difference to the card working or not and it hasnt changed positions since i moved house (to the best of my knowledge anyway).
I'm having a problem with my wireless connection. When it runs, it's perfect, but every once in a while (and increasingly more often) it randomly disconnects and doesn't reconnect when I click reconnect, even if I manually disconnect it. Every time this happens, I have to reboot the system, after which it works perfectly. Then it dies again.
I've checked around the forums, there are some similar threads but they seem to be specific to the wireless card. The reboot method works, but I'd really like to find a way to solve the problem without having to resolve to the Vulcan nerve pinch. I'm a real newbie to Linux and the more complex side of computers in general, and I hardly know what is what, so please excuse me if I seem a bit thick.
I was having an issue with my wireless connection last week, and sometimes even my hardwired connection. It had seemed like every time my PC went into standby, or any low-power mode, the WiFi would stop working. I used the "power off" command and got it back and running. When I boot up the computer in the morning, I am unable to connect until I reset the wireless router. Unfortunately, I did not have the presence of mind to get iwconfig first thing in the morning, but I did reboot the laptop and grabbed iwconfig before I connected and after I connected. Now, for some reason, the router worked when I rebooted, but I had to reset it this morning. Any ideas? iwconfig below:
****Before Connect**** jake@jake-laptop:~$ sudo iwconfig eth1 [sudo] password for jake:
When I put my computer running Ubuntu 9.10 into suspend or hibernate the screen goes black with a little flashing underscore in the corner and when I try to bring the computer out of suspend or hibernate nothing happens and I am forced to manually reboot.
Dell mini 10 with ubuntu 10.04/windows xp, connecting to linksys wrt54g. Connected when I was using 9.10, has worked for several months since 10.04 was installed. Still works if I boot XP, but, when booting Ubuntu, router won't accept the passkey which I obtained from my wired computer. I've glanced through a bunch of posts and see several which are close, but no solution. Only cause that I can think of might be a shut down while connected. I say that because it was working and I had no need to change settings.
I upgraded from 9.x to 10.10. Under 9.x my wireless usb dongle worked correctly. After upgrade it does not. I checked the dongle on another machine and it works correctly. I inserted a usb memory stick and the system found it as a drive correctly. I assume from this that both the dongle and usb port are ok. The wireless device is a D-Link G122 A2 which is on the supported list (it ran out of the box on 9.x). The link light did not even come on. So I installed ndiswrapper and the windows D-Link driver (note that this was not needed in 9.x). Now the link light comes on and the wireless router is found but the unit will still not connect.
The log file entries on dongle insertion are as follows:
It appears that the problem is with wlan0 not being ready. If this is the case how do I make it ready?
When connecting to any wireless network, DNS lookups completely fail to work. Over a wired connection, there's no trouble.
I can ping machines by IP address, and I can dig and nslookup domain names using the DNS servers assigned by Network Manager or by myself. When I try to ping by domain name, however, nothing happens. Similarly, I cannot ssh into machines by domain name or browse the web.
My wireless card (Intel 4965AGN) is managed by Network Manager. The issue is seen regardless of whether DNS servers are obtained automatically by DHCP or assigned by me through Network Manager. This started about a month or two ago while I was using Maverick and presents again with Natty. I dual-boot Natty and Windows 7, and everything works fine in Windows.
Somehow, this seems to be linked to Nautiluswhile connected to a wireless network, Nautilus won't open, my desktop icons won't show, all that jazz. If I'm connected to a wired connection at login time, Nautilus works fine.
I've managed to workaround the browsing issue by setting up an ssh tunnel through a machine at school and forwarding Firefox's DNS resolution through that tunnel. But I'm at a loss as to how to resolve the core problem.
Here's some diagnostic info. I've modified my IP and hardware addresses below.
I've tried all the basic steps killing and restarting Network Manager, renewing my DHCP lease using dhclient, restarting /etc/init.d/networking. I'm at the end of my rope, though, and ready to reinstall. I'd be much obliged if anyone can think of a less "Microsoft" solution.
School with linux running on students' laptops, connecting via wlan to a Debian NFS and LDAP server. Every student logs on his/her profile residing on the NFS server.The clients are set up with autofs. Earlier, I had set up the wireless network in /etc/network/interfaces, but this time I decided to configure network manager so as to bring up both wireless and wired network before logon. This setup has been working on for the last fire or five years with only minor changes. Also worked with Karmic Koala, but still with the interfaces file instead of networkmanager. The Vostro is also new here, we've previously used mostly Dell Latitude D505s.
So here is what works:
1: Clients can log on to LDAP and NFS servers both wired and wirelessly. Everything is smooth.
2: While on LAN, shutdown and restart works flawlessly (and quick as a breeze, I'm really impressed by startup/restart/shutdown times, under 25 secs!).
3: Shutdown and restart also works wirelessly when doing it either from a local account or from the GDM chooser.
What doesn't work, however, is shutting down or restarting directly from a networked account connected while only being connected over the wireless network. This is what's being displayed on the terminal after it has tried tho shut down for a while:
Code:
The system is going down for halt NOW!
acpid: exiting init: cron main process (1011) killed by TERM signal. init: tty1 main process (1365) killed by TERM signal.
[code]...
If I try ctrl-alt-del at this stage, it says:
"init: rc main process (3030) killed by TERM signal"
"Checking for running unattended-upgrades: "
And then it will hang again, until I hold the powerbutton for some seconds. The unattended-upgrades part is what seems to be the culprit. I suspect it is about the wireless network not being connected any longer or something like that, but I'm not sure about how to go about debugging shutdown scripts here. I'd be grateful for pointers. I will try and see how it goes with the old interfaces file setup, but I'd rather make nm work.
Suspend works about 50% of the time on my T400. The other 50% of the time, the screen goes blank (light stays on), there is a blinking cursor in the top left, and the "moon" light blinks forever.
I've got the latest ATI (3470?) video driver installed. I've seen a few posts about this but no clear solution. Anyone here have this problem and (more importantly) been able to fix it?
I've had this problem two times before and solved it once by following a guide, the other time by formatting. It always happens when it fails to wake up from suspend. Usually I am unable to even mount the drive or access the files. This one is different in that now I can actually access my files for the most part but this comes up on boot. I backed up most of my files (except it still says I don't have permission to access some of them) but I would like to get it back up and running without formatting. If I boot in recovery mode it stops at this. I took a picture but I rewrote some of it here.
Firewire_core: created device fw0: GUID 00016c000061b4b4. S4??? in/sh: cannot open ro Kernel panic - not syncing: attempted to kill init! Call Trace: [<c05c8283>] ? printk+0x2d/0x32 etc Image posted here: [URL]
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.
I had been manually starting my wireless network with "sudo iwconfig wlan0 essid "my wireless router id". The network would start and work flawlessly for weeks at a time. I can't ask my wife to find the essid in the terminal and then start wireless manually when I'm not here. She hates and fears the terminal. So I downloaded gnome network manager for a point and click interface on gnome panel.The network would start fine but shut down after anywhere from one to six hours. It would then refuse to restart manually or otherwise. I completely uninstalled network manager and tried wicd instead. The same basic problem is happening. The network will restart if I reboot the computer. My system:
Desktop computer acting as proxy server for the internet. Internet connection is by a dial up modem. This computer uses a wireless pci card connected to a dedicated hub. This is for file sharing via nfs. The OS is ubuntu 9.10. My wife's computer sharing the internet using a proxy to my computer. File sharing via nfs and a wireless card. Also running ubuntu 9.10. This same basic system worked flawlessly under Ubuntu Hardy.My desktop was updated recently with new hardware which created the need to move to Ubuntu Karmic. Some hardware was too new for hardy to deal with.
