On my Sid laptop with iwlagn as the wireless driver, I use gnome with network manager. I lost all wireless capability when laptop failed to come out of suspend.
I have the power manager set up to suspend when the lid is closed. This morning when I opened the lid I got a blank screen with a blinking cursor. Without thinking, I forced shutdown with the power button. I know, don't say it. When I booted up I had no wireless at all. lspci doesn't recognize wlan0 lsmod shows iwlagn is still there I performed the following:
# modprobe -r iwlagn
# modprobe iwlagn
Now I have two drives on this laptop and Squeeze is on the other drive. When I boot into squeeze I have wireless activated.
My ThinkPad X32 doesn't shut off the backlight when I suspend it. It also doesn't resume properly. Shutdown works normally. I'm using OpenSuse 11.3 Gnome. Had the same issue with an install of Linux Mint Debian Edition (201101). It is a well-known Debian issue that has evidently trickled down through Ubuntu to Mint. It also exists in Fedora. In search of a distro that would handle suspend/resume without problems, I first tried Scientific Linux. Suspend/resume worked flawlessly, but I was not happy with the package manager in SL, which leaves it to the user to resolve dependency issues that are automatically handled by Synaptic in Mint/Ubuntu/Debian and by the Package Manager in OpenSuse.
OpenSuse 11.3 Gnome had the same problem - the backlight remained on upon suspend, and resume didn't work at all. I solved this issue by making a simple change in a start-up file in OpenSuse. I'm hoping the solution will work in Mint as well, as it is my favorite distro which I have used for three years. The solution:
1. With OpenSuse: open a terminal and type gnomesu gedit /etc/grub/menu.lst. When prompted, type your root password and click OK.
2. Gedit opens with the menu.lst file displayed. Down the page a bit, you'll see several sections that begin with "###Don't change this comment"
3. The first section gives details for the default boot operating system. Somewhere in this long spec, you'll find "vga=0x314" or vga=(something different for your system).
4. Just before or after this part, type "nomodeset" separated from the vga spec by a space.
5. Save the file and reboot. In OpenSuse, suspend/resume now works normally.
someone could let future readers know where the menu.lst file is located under Linux Mint. In the past, I've found it frustrating to try to edit the menu spec with Mint 10 versions, which use Grub2.
i'm running debian lenny - latest stable i have recently installed smartcam (mobile phone as webcam over bluetooth) from .deb package , get errors of unmet dependency , but application works like a charm, unfortunately broken dependences block my aptitude , i cant fix them either as latest stable use older versions of dependences even in backports... how do i mark smartcam package as not broken and release my apt?
I use KnetworkManager for wireless. Works great except that if laptopgoes into suspend the wireless does not work after resume anymore.NetworkManager log
Apr 27 20:24:42 linux-nfii NetworkManager[1433]: <info> (wlan0): device state change: 7 -> 8 (reason 0) Apr 27 20:24:42 linux-nfii NetworkManager[1433]: <info> Policy set 'Morran' (wlan0) as
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.
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 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 the Dell Latitude D400 with the B4306 PCI card. I followed the instructions in the stickies on this forum and downloaded and installed the firmware. Still could not get the wifi card to work. Here is the read-out:
[Code]....
I am just beginning with Linux - please take pity on me.
I have three problems with my new Acer Aspire one 721 (Amd, ATI) [url]
1) Pymouth doesn't work when booting. I have to use the parameter "nodeset". Desktop effects are working. I have installed Mesa based DRI drivers (experimental).
2) I have to manually "enable wireles" to acess the wlan. It should connect automatically.
3) the laptop doesn't wake up from suspend/hibernate. I have to use brute force to restart. pm-suspend.log
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.
If I suspend this toshiba satellite, and the battery is or gets low it will wake from suspend to tell me that it will need to suspend due to a critical low battery. Which is pretty dumb. I've experimented with this by plugging and unplugging the ac adapter.
1. is it possible to schedule this command in the same manner as shutdown ? eg sudo shutdown -h 60
2. is it possible to schedule the laptop to come out of suspend ?
3. i have a usb sound card (xfi go). when waking from suspend, the internal sound card is selected. i have to manually select the external sound card & for whatever reason, also unmute it too
My wireless was working perfectly until I accidentally let the battery run flat with the machine prevented from hibernating. Upon recovery, there was no wireless available. Checking the Hardware Drivers, I can see the Broadcomm driver as "Activated but not currently in use". Following the copious advice elsewhere I have disabled the driver, rebooted the machine, enabled it again - many times. Still the same message. What is stopping me from activating it? Bit of a noob so........
I recently upgraded Ubuntu 9.10 to 10.04 and my wireless stopped working. It can detect that there are networks around, what their signal strength is, and then try to connect to one, but it just keeps connecting. After around 5 minutes, this stops and nm-applet says no network connection.
After I try to connect, dmesg is spammed with hundreds of the same message. I can not post these here, as I am writing from a different computer and I have no internet access from my main computer.Also, there is nothing in interfaces.conf other than lo. For some reason, my card is referred to as both wlan0 and wmaster0, with this changing depending upon where I look.Most interesting of all is that, even after I reinstalled 9.10, wireless is still broken, even though it wasn't before. It also used to work under liveCD.
When booting from the netbook USB, there are two wireless connection stages:
the first appears at the "TRY/INSTALL" selection screen, and after supplying the keyring password, the connection appears to succeed.
the second appears on the desktop, after selecting "TRY"; the keyring dialogue appears & seems to work, but then the network login dialogue pops up, and refuses to connect.
Both my Acer machines connect to the same AP under Maverick and the EEE PC works in Lucid.
I recently installed ndiswrapper and decided to remove it after some kernel panics. The problem is that it overwrote something because I have the compat-wireless-backport driver installed but 'wlan0' doesn't show up anymore. I can see my wireless card when I type 'lsusb'. Any ideas on how to fix?
After upgrading my laptop from 10.10 to 11.04 I can no longer connect to my home wi-fi. It was working flawlessly for months before the upgrade. The network manager just keeps spinning and nothing happens.dmesg output just keeps showing this over & over again:
I just rebooted my netbook after updates this last week and notices the wireless is broken now. The updates updated my kernel and wl modules. I'm using a broadcom 43224 driver.If i reboot to the older kernel the wireless works.
I'm not sure if I have two seperate issues or one inter-related issue. The Network Manager applet wasn't appearing in the tray, found out it wasn't installed. Installed, still didn't appear. Tried installing WiCd, WiCd did appear but couldn't find any networks. I had installed restricted drivers previous, decided it was worth another look. Found that Broadcom STA Wireless Driver wasn't installed. Tried to install, it said it couldn't and said I should review the var/log/jockey which is....excessively long.
I just upgraded the kernel on my Ubuntu laptop from 2.6.32-24-generic to 2.6.32-25-generic (using the update manager under gnome). After the update, the wireless network controller shows up as UNCLAIMED when I do lshw -C network.When I try to install the driver with the commands sudo modprobe lib80211 sudo insmod wl.ko
i get this error message: insmod: error inserting 'wl.ko': -1 Invalid module format
I have compiled the driver using the 2.6.32-24 kernel. Do I have to re-compile with the new kernel?I'm a unix user, but not a kernel hacker, so I'm wondering if I will run into problems every time I get a kernel update? Or is this problem an exception?
for over at week i have been trying to get my wireless card to work now. If i open Additional drivers, the non proprietary driver seems to be working and active. If i deactivate that and use the STA driver instead, it says active, but currently not in use. When i use the non proprietary driver, i can check mark on 'activate wireless', but nothing happens. When i use the STA driver there are no wireless options. I'm not sure if its important, but when i do "sudo lshw -C network" when the STA driver is active but not in use, the network status changes from 'disabled' to 'unclaimed'. When i came here, i tried to install "firmware-b43-lpphy-installer" as the sticky said i should, but the installation fails. It says my card is not supported: "Not supported card here (PCI id 14e4:4727)!"
I'm running stock Debian 8.2 with GNOME DE on an Acer ES1-512 series laptop. Whenever I attempt to go into suspend, either by closing the laptop lid or holding ALT when clicking the power button in the top-left system menu on the desktop, my laptop briefly flashes the default GNOME lock screen, fades to black, and then hangs there. Usually, when my laptop would actually suspend, the power indicator light would change from blue to orange and slowly fade in and out. However, now it just sits on blue. There is no way to re-awaken the laptop from this state, and I have to force shutdown by holding the power button.
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.
There should be the suspend and hibernate buttons in th System Menu, but there is only two options, Shut down and Log off.Also, in the Power Manager Preferences window, it has no option for suspend and hibernate.
