I had this problem at first in Fedora 14 KDE. When I try to put it to sleep or hibernate it will go to black screen and then just turn back up. And now on my other computer which runs on Fedora 13. After KDE 4.5.2 update it does the same thing. I think it is same problem but I can't be sure.
i'm having this problem:when i put Fedora to sleep the system disconnect all my usb (or so i think)basically i can't wake up my computer becouse there is no where to do it.it gets back to normal after i power it off/on...how can i fix this?please since i'm new both to fedora and linux try to be detailed with the explanations, or there is a good chance i won't understand a thing
I'M using F14 x86_64 and my problem is suspending. When I closed my laptop lid its going black screen and my hdd led is lighting I think my hdd is working hard and I think my cpu is working hard too so fan is working fast and my notebok is going hot.Any key is working on black screen. I must shut down hard .y computer has i5 and ati 5650. WHen I was using Mint 10, it has going sleep well
I just recently updated to kernel 2.6.35.10-83, and after the usual hassle of updating my ATI driver, it worked perfectly. Or so I thought ..
When i pushed the sleep button on my laptop to suspend the system, it turned out that it doesn't do so very well any more - it sounds like it turns off the harddrive, and then the screen just goes blank except for a blinking, but unresponsive cursor. Also, pressing numlock/capslock doesn't switch those little lights on/off.
The only thing I can then do is to hold the power button for a while to shut down.
Is anyone else experiencing this, or does anyone have a solution?
I upgraded to fedora 11 from fedora 10 yesterday, I like it ok but when I put the machine in sleep mode and then go to turn it back on it comes up to the log in screen and thats it its frozen. I hate to completely shut down the machine every time I get off.
when I hit the shutdown option... I notice my Hibernate and Sleep button are gone... just the other 3 buttons are there.I wonder if it's certain apps I'm running (that can't be allowed to go into Hibernate) or if it just happens at random for no reason.Has anybody else had this problem? and what is causing this?
I've configured my F12 system to go to sleep when idle for a period of time and so far everything has been working out well except that it appears that the USB ports are completely dead with the system is put into sleep. I can't wake it using keyboard or mouse. only with the power button. Anyoen else experience this or know how to allow sleep from keyboard/mouse?
which log file should i look at to debug problem with system sleep or anything to do with the system won't return back after goes to sleep.
Basically i got my system running from the night before. No problem until this evening around 5pm. (i realised the problem at 5pm) my monitor goes to sleep. My system power still on. It won't respond to monitor/mouse movement. i can't ssh in.
After reboot, check /var/log/messages. The only message there before reboot was at 9am. I am pretty sure everything worked fine around 2pm.
So I have Fedora 14 installed on a laptop directly connected to my printer. I really never use the laptop except to send print jobs to it wirelessly. I was wondering if there was a way to make it suspend or sleep, or even idle everything down so it uses less power, but still listen for print jobs?
I'm not sure, but I think this is hardware. Anyway, I have two different boxen running FC14. One has a Nvidia 9800, the other a Nvidia NV96. The former I use as a desktop, the latter a server. I've let the server go with whatever the system autodetects for video, but the desktop I've played with a ton: nouveau, nvidia, etc.
Anyway, since I upgraded both to 2.6.35.9-64, both go to sleep at some point during rhgb. I can't find anything in boot.log, messages, or what have you to try. This happens even if I go to runlevel 3, so unless I'm misunderstanding the boot sequence, this is way before X starts.
Now, just upgraded to 2.6.35.10-72 tonight, and the behavior slightly changed. Before, it would show the rhgb loading screen for a few, but then the monitor would sleep before it completed. As of this kernel, it just goes to sleep right away.
The only quirky thing I can think is that I'm running DVI out into a KVM. I have been making sure to have the machine as the active video when it boots, so it should still be able to feed EDID info to the machine, but I did notice when trying to track down nouveau/nvidia problems on the desktop that X was having trouble reading my EDID all the sudden.
I'm assuming there's some automagic default now that's putting my monitor out of range. The only way I've been able to keep the desktop running is to not have the nvidia driver installed, but also not have a driver type specified in xorg.conf. If I do that *and* specify a modelines, I can boot with rhgb off at runlevel 3, then manually start X. From the Xorg.0.log, it appears to be falling back to vesa, which is the only thing that works.
How can I debug this? If the monitor sleeps but there are no messages in boot.log, messages, or Xorg.0.log, how can I even figure out what rhgb is doing?
I have been using fedora 14 .. I have set d sleep timer and lock the window timer to "Never"But when i watch movies on VLC player the screen locks automaticaly after a few minutes ..
I have a HP laptop with an internal tv-tuner card, which i use once in a while, because i don't have a tv. The problem is, that the kernel module i installed to make this piece of hardware work, for some reason makes my laptop unable to sleep. So if i want to suspend my pc, i have to first unload the module, using
finally got my wireless to connect before i log in, but now i see that when the computer boots, before i login, it will go to sleep if i wait too long. next question, how do i change pre-login sleep timers?
I have Fedora 10 x86_64 installed on my Think Pad T61p and when ever I put it to sleep and then try to wake it back up, it doesn't wake back up, all I get is a blank screen
I have been working on this problem for a few month. By messing with windows registry and local security policies I was able to remotely shut down windows from Linux by issuing:
Gnome would sleep after specified 10 min and put this machine into <1 Wt saving mode.KDE just invokes screensaver and turns off display. It won't even spin down HDDs.There are no profiles in KDE power settings and I can't create any - create button works, but 'new profile' dialogue does not actually create any profiles.This is a brand new default install of F14 on AMD 890 chipset.
installed Fedora 14 on my desktop a couple of days ago. For the most part, it seems to be fine, but I've got a problem with the 'put display to sleep when inactive for' setting. From the desktop, I've tried going to system/preferences/power management, where I've set the display to go to sleep when inactive for 30 minutes - however, it instead goes to sleep after five minutes. The same applies whether I set it to 10m, 30m, 1hr or never.
Having looked online, someone mentioned gconf-editor as a fix to another issue, so I decided to give that a try as well. Under /apps/gnome-power-manager/timeout, I tried setting sleep_display_ac, sleep_display_battery and sleep_display_ups each to 1800 ("The amount of time in seconds before the display goes to sleep" - 30mins, by my maths) on the off-chance that the OS had incorrectly detected the power source, but the display again went to sleep after five minutes.
If it makes any difference, I'm not using a screensaver, and I think the kernel I have installed is 2.6.35.13-92.fc14.i686 (that's what's given in System Monitor). I've also tried running yum update, again just on the off-chance it'd fix something, but everything is up to date.
I have a home server that I'd like to put into standby for a specified period of time (like from 1AM to 9AM) daily. How could I make this happen, so that it goes to sleep and wakes up automatically?
Running FC13 on Dell E6410. Everything was great until I ran the latest update about a week back. I started to see (or actually not see) that after resume from sleep the mouse cursor will disappear. It is there, just not work showing. If i click on left click on the desktop I get the menu, I can also "see" going over windows from time to time as I move it. I'm currently running 2.6.33.6-147.fc13.i686.PAE I think previously it was /vmlinuz-2.6.33.5-124.fc13.i686.PAE Nvidia driver is 195.36.31
I have an odd problem since preupgrading from Fedora 12 to Fedora 14.
My power management settings are set to never put the monitor to sleep, yet after a certain amount of time, lo and behold, the Fedora box has gone blank and I have to enter my user information and password to get back to my gnome session.
In the power management preferences I have "never" selected for both putting the computer or display to sleep.
In the screensaver preferences "Lock Screen After" is *not* checked. (And if I click "advanced" I also note that "Power Management Enabled" is also *not* checked).
I'd just as soon not have to "log on" to this machine every time I'm away from it for a while.
"Sleep" is not supposed to permanently kill off the network service. restarting the NetworkManager / network services DOES NOT WORK. Why this blatent and crippling bug is allowed tp persist? I dont want to "rasberry reboot" like windows, this has been the only forced reboot
Anyone noticing intermittent problems with the screensaver not kicking in or the display not sleeping? This is in gnome under F11.I have the Power Management Preferences set to put the display to sleep after 30 minutes of inactivity and gnome screensaver is configured for 5 minutes idle time.On a regular basis, I'll leave my computer come back anda) the screensaver hasn't kicked inorb) the screensaver kicked in, but the power management features didn't kick in to put the display to sleep.It seems to be an intermittent problem and usually it goes away after I restart X, but then at some point it comes back. In the past, I've gotten in the habit of being logged in for weeks/months at a time but I find that I can't go more than a few hours without logging out and back in or else the screen won't go to sleep.