After resuming from suspend (press power button), display is correct except cursor is not displayed. Mouse responds and I am able to highlight widgets etc. on display and X responds to mouse-clicks correctly.Confirmed it was definitely Xorg-related (radeonhd):Logged out of GNOME then logged back in using 'xterm' desktop.ran pm-suspend(8).pressed power button and cursor was not displayed.Currently using the setting where I use the ctrl key to show the cursor position.
I recently upgraded from Karmic to Lucid via the Update Manager. I would like to upgrade further by switching from 32 Bit to 64 Bit. I downloaded the Lucid 64 Bit ISO and wrote an install disk. When I reboot the computer with the install disk nothing happens.
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?
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)
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.
This issue happens on both my Dell D630 and my homebuilt desktop, so I'm pretty sure that its not a hardware issue. Both installs are clean new installs with encrypted home directories. Computers go to sleep just fine but when I wake them, karmic is unresponsive and stuck in IO wait for the majority of the time. How can I gather enough information to submit a useful bug report?
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.
I'm experiencing very slow resume from hibernation. Last one was nearly 3 minutes. Sure, there is 2GB of RAM to read from disk (no SSD) to memory but that long?What could I check/do?
I've read many threads here on wireless problems in 10.04. I've got it updated as of this morning.
Symptom: wireless works perfectly - doesn't drop out and starts right up at boot. But if computer (Dell Latitude D505) goes to sleep, wireless won't resume. Network Manager shows wireless networking greyed out after waking.
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
I am using uswsusp / s2disk and it hibernates fine. Then, on resume, it apparently completes the resume (reaches 100%) but it never progresses to the actual resumed system and gets stuck on this screen: Before upgrading from 9.04 to 10.04 it worked fine. It does not anymore.
Like the subject says, I was at my server and logged in directly and started screen. I then started a command and detached the screen.I then logged in remotely through ssh thinking I could resume the screen but when I try "screen -r", it says not screens to resume. I see the screen process still running and when I do go back to the server directly (no ssh) I can resume the screen and things are running just fine.Anyone know how to resume a screen remotely that wasn't started remotely?
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
I'm having trouble resuming from hibernation. The splash screen loads up with "Resuming from /dev/sda6" (this is the correct partition) and the HDD light shows it's reading the drive. It then stops reading and the loading animation starts up (I'm running Lucid). Then nothing, just the animation. I recently updated initramfs-tools to 0.98ubuntu2~lucid as hibernation wouldn't work at all with the old version (see [URL]). I've also installed this script because of errors on hibernation.
I have a Dell Latitude D630 with Nvidia graphics, Dual-Core, 4GB of RAM. I am using Ubuntu 10.10 64bit . The Nvida driver version is 260.19.06.Whenever I walk away from the computer and it prompts for a password to log back in, it is SLOW. It continues to run slowly until I reboot. The fans are running and system monitor shows that Compiz is eating up a LOT of processor time. After a reboot, all is normal. I need a solution that involves as much automation as possible, I want to try to deploy several identical machines in an environment and I can't with this issue still presenting.
I'm setting up an HTPC (Zotac IONITX-F in a Silverstone ML02-MXR case with remote) running XBMC on top of a minimal karmic install. So far I've managed to get everything running including the tricky stuff: wireless, lcdpro and lirc. I did have the same samba/dhcp conflict described in this thread, so I opted for a static IP solution instead of the usual dhcp connection with the router (D-link DIR-615) reserving an IP for the MAC-address. This is my /etc/network/interfaces file:
Code: auto lo iface lo inet loopback # The primary network interface #auto eth0 #iface eth0 inet dhcp
I'm having trouble getting conky to start automatically after resume from sleep. I've tried putting a copy of my conky startup script into /etc/pm/sleep.d but nothing happened.
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'm currently using putty on my laptop to control my headless server (both Ubuntu 8.04.) I'm running an rsync job that ran all night long and still going all day today so far. I need to restart my laptop, but if I do, I'll break the SSH connection. If I SSH back in, I won't see the same thing (rsync is showing me each file it's copying) that I'm seeing now. (At least I think that's true. Please correct me if I'm wrong.)
So I guess my questions are..Is there some way to restore my SSH session when reconnecting? (So I can resume seeing which file is being copied and - more importantly - when the rsync job (finally) finishes?If not, how else can I know when the rsync job finishes?
I'm sure this doesn't need a new thread but after searching for a bit I didn't find much about this. The problem is this;My system sleeps quite well, I can resume from sleep and get back to the desktop. However. the one thing that doesn't resume is > networking.I can disable> re-enable networking from the NM-applet and it tries again to connect but won't.I can sudo /etc/init.d/ networking restart, which essentially is the same as above. No connectionI've run ifconfig, and the connection is there but no address. Has this bug not been solved? Is it just a driver issue with my particular network card?It's the realtek 8201, part of the VT8237 chipset.Does anyone know what to do about this? I've been avoiding sleep mode on this computer for a very long time because of this bug.
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.
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.