OpenSUSE Network :: No Internet After Resume From Hibernate Or Suspend?
Mar 13, 2011
The good news: 11.4 seems to have much better support for my radeon graphics driver which makes many of my workarounds for 11.3 unnecessary
The bad news: whereas previously for 11.2, 11.3 using traditional ifup meant that I could easily restore internet (either wlan0 or eth0) with ifdown/ifup now this seems to have no effect. I haven't investigated further yet since without internet on hibernate or suspend 11.4 is not my grub of choice at the moment
There seem to be quite a few glitches with the 'stable' release of 11.4 but this seems to be the main problem for me. (Minimizing the beta 4 Firefox windows closing them is another...)
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.
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 dont know why my system dosnt resume from suspend sstate.i it goes in suspend state.it doesnt resume .i have to poweroff then restart it again.and when i get logged in it gives me Following Error: Resume problem: Your system did not appear to resume correctly from Suspend/Hibernate. This may be a driver problem or a hardware problem. Check the GNOME Power Manager Manual for common problems.
do you think it is because of batterry.i have a problem in my By Battery .IN DOS operating system.when i check my battery icon . A red Cross constantly blink on lower right side of the battery and it says (your Battery consider Replacing).i have notice one thing .And My battery timing hias become Decreased. Do you think this Resume problm is cause of battery problm.Or there is some problm in my Os software.
I am running Squeeze on an older Compaq EVO laptop with radeon graphics.
A few months ago, after an upgrade, suspend and hibernate stopped working. The suspend or hibernate worked fine, but the resume just hung with a black screen. I finally got around to looking into it and found a workaround.
The workaround is to disable Kernel Mode Setting for the radeon. This can be done by adding the boot parameter "radeon.modeset=0" or by editing /etc/modprobe.d/radeon-kms.conf so that it includes the line "options radeon modeset=0".
If you are interested in the details, you can search for problem reports related to radeon kernel mode setting.
To workaround the kio_smb madness, I set up shares to be mounted via /etc/fstab. It works flawlessly until I suspend my laptop. Coming back from suspend, samba mounts are not being re-mounted automatically. Since I'm new to opensuse, I wish to ask you: Is there a polished way to make this happen, in opensuse approach? Or shall I just go and toy with scripts in the init.d (or what is it in suse)? As much as I could figure, I checked in yast, and smbfs service is signed as "Yes".
Just got Ubuntu 9.10 and I'm liking it a lot, but my computer refuses to go into hibernate or suspend. I have a Dell M1530 but I don't really think it's a dell hardware issue because it's not just when I close the screen, it's also when I click suspend or hibernate from the menu.
Lately I upraded my Debian using aptitude update/aptitude upgrade - including installing a new kernel (3.0). Since this upgrade I have strange problem with networking. When I suspend my computer and resume it, I do not have connectivity with network:
$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.1.1 icmp_seq=1 Destination Host Unreachable
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.
There is an intermittent problem with resuming from s2ram. Occasionally, the power button is pressed to resume, the screensaver comes on but the animation is frozen along with the mouse and KB. Sometimes the desktop will show although with the same frozen condition. My swap parition is 2GB. I read in the forums that a small swap partition may cause a somewhat similar condition. I also read a recommendation to disable powersaving and screensaver, again not for my exact symptoms. I would like to find the root cause even if it takes some doing. Otherwise, the system rocks (except Amarok never worked but Kaffeine works for sound). Here are the system specs:
openSUSE 11.3 x86_64 KDE 4.4.4. rel 3 HP xw9400 Workstation AMD 64 Opteron OCZ Vertex 60GB (dedicated system drive-single boot)
I've set up a media box for mythtv based on OpenSUSE 11.3 and LXDE. By default, the screen gets locked prior to a suspend. On resume, therefore, the screen is locked and requires a password to unlock. I need to disable this action. In KDE4, I can do that by going to the power management settings and un-selecting the appropriate check box. In LXDE, however, I can find no such settings. There must be a config file somewhere that I can tweak to turn off the screen lock prior to suspend, but I have no idea what it is.
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.
When I resume my system after choosing the "Suspend to RAM" option, the login prompt appears but the keyboard doesn't work at all. (Caps/Num/Scroll don't light up either) The mouse, however, works fine and I'm able to click on the on-screen elements. Since I'm not able to login, I'm forced to reboot and abort the session. Note that this does NOT happen with the "Suspend to Disk" feature. (ie, it works fine).
openSUSE 11.2 KDE4.3 x86_64 (updated) Sony VAIO VGN-CS17G
I've just started using OpenSuse 11.2 KDE. I have KDE4.4 installed. I had this issue with KDE 3.4 as well. My HP Multimedia DV3065 laptop is encountering an issue with suspend/restore. After restoring, the mouse is frozen. I have already tried a few things.
1. Dropping to init 1 and then back up to init 5 did not provide a temporary fix. So this is probably hardware related in some sense (kernel?) 2. I tried a grub option (cant remember what it is now). i8500-reset something like that. It made no difference. 3. I tried modifying my 99ZGrub file per another posts suggested solution. That actually locked up my laptop and I could not reboot (even after a cold boot). I pulled the battery and let it sit for a bit and it booted again
So I have several issues.. 1. I would like suspend to restore my mouse. 2. I have not figured out how to program my Sleep button to Sleep. My menu bar icon has Log Out / Restart / Turn Off. The ALT+F1 menu tab Leave has those plus Sleep and Hibernate.
The PC is a Toshiba laptop model# x205-s9359 running 11.2, KDE 4.3.5. Its video card is an nVidia 8700 GT. For two years now I've been plagued by random flashes, flickers and even missing scan lines on my screen when I use the nVidia drivers (up to and including 195.36.15), so lately I've been using the nv drivers. I miss the effects, etc. but I can live with that. At least I can get my work done, even if the display isn't as fancy as I'd like.
- When I run the nv drivers I can't suspend the PC to RAM or Disk. This means a lot of wasted time waiting for the machine to shut down and reboot every time I leave my desk for any length of time. If I try to suspend to RAM the only thing that happens is that the network connection disconnects then reconnects immediately. Here's the log file.... - If I try to suspend to Disk the PC appears to suspend as expected, but when it resumes it hangs before restarting X, and there's no keyboard or power button response. I have to use alt-prtsc-reisub to reboot. When the reboot is complete the screen shows all the windows, etc that were present before the suspend. Here's that log file.... -When I run the nVidia drivers the suspend/resume functions work perfectly, but I have to put up with all the problems described above. Here's the log file for Suspend to RAM with nVidia, and here's the one for Suspend to Disk.
I've spent hours searching for clues in these forums, on the openSUSE.org site in general, at KDE.org and with Google and I'm sorry to say that most of I've found is horribly out of date, and/or it's way over my head. or (worst of all) not even dated, so I've no idea whether it's current info relevant to my situation or so out of date that I might do real harm if I were to trust it. (RANT: Is it too hard to put a date on an article?... end of RANT) I'd be quite content to use the nv drivers if I could solve the power management issues, but I'd be equally happy to solve the flickering etc. with nVidia drivers.
My system cannot resume after hibernation. I have done all as described here [URL] ...
My have set up swap file "/swap_debian".
I have 3 partitions: sda1: windows boot partition. sda2: windows 8.1. sda3 : debian
I have the only linux distro installed: debian.
I have read lots of web pages. I have managed to set up suspend 2 disk. After dancing 2 days at the computer the system still cannot resume. I am getting "clearing orphaned inode" msgs while booting, and when booted to ram was not recovered.
Swap file is 4000 MB, RAM is 3860 something MB
My current grub is:
Code: Select all# If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration'
And yes, I did update-grub.
My current /etc/uswsusp.conf is:
Code: Select all# /etc/uswsusp.conf(5) -- Configuration file for s2disk/s2both resume device = /dev/sda3 compress = y early writeout = y image size = 1855258869 RSA key file = /etc/uswsusp.key shutdown method = platform resume offset = 31606784
My current /etc/fstab is:
Code: Select all# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5).
I found this line in dmseg when I was checking out another problem. "[0.104467] ACPI Warning: Incorrect checksum in table [OEMB] - 03, should be FA 20090521 tbutils-246" Could this be why I have never been able to resume from hibernate on this machine?
I have ubuntu 10.04 installed on a 50 gb partition on my hard drive I have given a 3.5 gb partition for swap which is > 3gb ram i have. Druing the installation of ubuntu I had specified the swap partition and its hibernate was working fine sometimes before. But I had to delete the swap partition and recreate it because of some reasons so I did that and again created a 3.5 gb partition for swap space usig ubuntu live cd.
But after restart ubuntu no longer detected the swap partition it was ok as its uuid had changed so I specified the swap partition to be mounted automatically by adding an entry in /etc/fstab and then also added the same UUID in /etc/initramfs-tools/conf.d/resume so that it could resume. After restarting ubuntu after adding the entrly in /etc/fstab i got the option of hibernate but after hibernate everything goes well but after hibernate when i start laptop again ubuntu first tries to resume but it does not and without giving any message it shows the login screen.
I'm using stock 32 bit current on a AAO D250 netbook. I'm running into a video issue after upgrade to the recent 220.127.116.11 kernel that doesn't exist after resume from suspend. The condition shows as a broken display that shows a black screen on the left with the KDE desktop partial exposed on the right side. Weird! My only fix so far is to blindly ctrl-alt-f6, login as root and reboot. The screen does not show the console screen during this reboot process
The pm-suspend logs show a clean hibernate and a clean thaw so that's no help. I've checked modprobe.d and don't have any alterations to any of the modules. The video module loaded is the intel_agp which sound right. I'm stumped at the moment.
So I'm having this weird problem where my computer wants to continuously resume a session from hibernate no matter how I shut it down. I think it started when I tried to hibernate my computer with the battery really low. Somehow it messed it up. In any case, it can't resume properly, but gets stuck somewhere in the middle (I think when it's trying to sort out the resume image). Each time I power it on I have to boot it, restart in the middle of the boot so the boot menu comes up as it starts up again, edit commands before boot and add the "noresume" option so it will boot up normally.
I have an Asus EeePc 1001PX and on resume I have "Network Management disabled", neither wired nor wireless interface can be configured, the NM icon is greyed out. running ifconfig shows eth0 and wlan0 have disappeared completely.
I found 2 options: 1. https://bugs.launchpad.net/ubuntu/+bug/555571 2. Network management disabled after start on 11.2 - openSUSE Forums
but I don't have the /var/lib/NetworkManager folder at all
I am pretty new to Linux, but this can't be the way the system is supposed to operate.
Fedora 12 KDE 4.4 kernel 18.104.22.168-70.fc12.i686 Toshiba satellite L305D
As of updating KDE to 4.4 and a kernel update from two weekends ago hibernate/resume works perfectly. The problem is I feel that all terminals should be locked/logged out automatically upon suspend/hibernate. Through bug reporting at KDE found that an additional setting is required in KDE to lock the desktop before suspend/hibernate. But any of my other terminals that are logged in remain logged in upon resume. Is there an additional setting that I have to flip to secure the terminals? Would this be considered a security hole? Is there anything short of me manually logging out that I can do to automate locking/logging my terminals?
I have problem with resuming after hibernate, it is about 50% chance that computer restart when I want resume, then it starts boot normally and all my work is lost. Acer aspire 3820tg Ubuntu 11.04 Builtin hibernate on partition I try uswsusp s2disk ... on resume it always stops in half of process. I used mainly hibernate, but I'm lost now.
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)