I'm using a laptop as a mini server, but I haven't figured out how to sleep the display. I am not using the gnome desktop - I shut the lid but the display stays on.
ps - I should note - this is Debian 5.0.3 PPC version running on a PowerBook G4
i have the following problem which i couldnt solve in the past weeks. We have two Server with an onboard "Atheros AR8161 Gigabit Ethernet (rev 10)" and a quad "Realtek RTL8111/8168B" network adapter connected via PCIe. One of the servers is running Debian Wheezy with a custom 3.2.53Kernel (compiled from linus repository) and the second one runs Debian Jessie with stock kernel. Both are running XFCE4.
Each of the computers are connected to a local network (192.168.0.1 respectively .2) and to the intranet of our institute (10.20.0.81 respectively .82). After a random time they are not accessible via the intranet (ping doesnt work, ssh gives no route to host). However, i can still ping them over the local network. Also, at the moment i try to establish a ssh connection over the local network, the computer is again acessible via the intranet.
I already tried the boot options acpi=off and pcie_aspm=off without success. Additionally we switched from the onboard Atheros NIC to the Realtek, but everything stays the same. Therefore i don't believe that it is driver related.
For me it looks like that the NIC goes to an energy saving mode which is not handled correctly by our intranet. However, how can i avoid that the NIC goes to energy saving state? Is there a way to disable the D-states?
I have Debian Jessie 8 installed on a Acer 5733 Laptop. After I closed the screen, it goes sleeping, and when I open it, aleatory, it freezes. I don't have graphical interface, and the tty are not accessible. Sometimes, I get access to the computer 10 seconds, and then freeze.I have to shutdown the computer...and lose my work I was doing.I thought it was a X-problem, but the tty don't work too, so it's not ? When I restart the computer, it shows Code: Select allclearing orphaned inode <some inode number.
View 0 Replies View RelatedI have a strange problem in my new debian 8.3 LXDE install. Every time I boot my laptop it goes in to sleep mode automatically after a min. It is a default install and I have not configured any power management options. How do I find out the reason for the automatic sleep and how can I rectify it?
View 4 Replies View RelatedHow can I stop my display going to sleep?
I've got the Power Management settings for mains power as:
Actions - put computer to sleep when inactive - never
Display - put display to sleep when inactive - never
Screensaver settings are:
Regard computer as idle set to 2 hours
Unticked Activate screensaver when computer is idle
Yet the screen still goes blank after a few minutes when I'm not using it.
I dual boot and it doesn't do it in Windows. It didn't do it in 8.10 or 7.10 either.
My display is set to sleep after 30 minutes of inactivity. When I go to sleep at night I don't want to wait 30 minutes for the monitor to shutdown, is there any way I can use the keyboard (like a hotkey) for :
1. Start my screensaver (when I go for 5-10 minutes afk for example).
2. Make the monitor go to sleep mode.
I just recently changed one of my OSs to Ubuntu 10.04. I have run into a somewhat annoying problem. The problem: My monitor is going to sleep after 10 min. of inactivity no matter how I have the system set. I do not wish for this to occur, I mean why bother having a screensaver? lol I am using a desktop PC. The Power Management daemon is enabled. I have power management set to - Put computer to sleep when inactive for: Never Put display to sleep when inactive for: Never When power button is pressed: Shutdown When suspend button is pressed: Suspend
I have screensaver set to- Activate screensaver when computer is idle: unchecked Lock screen when screensaver is active: unchecked The duration slider is maxed out to 2 hours. The sleep function of my monitor is turned off. It's a Compaq WF 1907. I know it's Ubuntu because my monitor OSD is showing a "No Signal" message when it happens and it never happens when I am using Linux Mint 9. Since LM9 is built on top of Ubuntu, this leads me to believe a setting is simply not taking. Ubuntu is fully updated. I have a wonderful desktop set up and I would really hate to scrap it and go back to LM on this partition but this is really irritating. Is there some way to make it work the way it's supposed to?
I am wondering if it is possible turn off my display with a key of my laptop's keyboard. I mean if I press ctrl + o then my display turn off and then if I press ctrl + o my display turn on.
I applied Power Management settings to put my computer to sleep in the hope that it would only sleep when it wasn't downloading something in Deluge. Unfortunately it would seem that it puts the computer to sleep despite Deluge being active. No biggie I thought, I'll just disable the sleep settings my setting them both back to NEVER. However, it ignores my new settings and still puts the display / computer to sleep, at the exact times I set originally!
View 7 Replies View RelatedHow do I change amount of display Hertz in VC? I have a conjecture that it's not the same as in GUI (on my computer). Ubuntu 10.04, Gnome. if not Debian, but at least it's close.
View 2 Replies View Relatedhow do we control the display color quality in Debian, similar to setting 16 bit or 32 bit in Windows? I have Lenny on a notebook and Squeeze on a netbook, but cannot find a menu to set it. They both have the default vesa driver.
View 4 Replies View Relatedinstalled 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.
Linux downloaded new updates and worked perfectly. Next time I started mint, just before the login screen appears display says No Signal and goes in sleep mode. I think that mint downloaded somekind of display driver update wich is not compatible with my driver card. I can't see desktop, I just hear the login sound and that's all. What should I do? I'm new with linux.
View 6 Replies View RelatedI'm trying to get a framebuffer console with acceptable scrolling speed on Dell XPS M1530. It has GeForce 8600M GT card with maximum resolution supported by bios 1920x1200
# cat /sys/class/graphics/fb0/modes | sort
U:1024x768p-60
U:1280x1024p-59
U:1280x800p-60
U:1600x1200p-60
U:1920x1200p-60
[Code]...
I installed new ati radeon drivers in the morning because i was getting display/screen deformation when using some programs (like vertical lines and so on). Now everything is just fine but i can't get 3d accelerator to work and due to this some games are running very slow. I am a new linux user. I have done everything i know and searched this from the internet but i can't get 3d acc. to work again. i have installed new drivers over the old ones (or i don't know; mesa?)
[code]...
Despite having the Gnome Power Manager set to put the display to seep after 30 minutes, it always happens after 5 minutes. The display will go blank but still lit, and then it powers off after the 30 minutes. Surely, if I set it to 30 minutes, the display should power off then, and not just blank after 5? I have no screensaver packages installed so it's nothing to do with that.
View 2 Replies View RelatedUsing squeeze with a GeForce4 MX 440 video card (NVIDIA) I have a monitor (4/3 aspect ratio, 1024x768 usually), and a TV connected via S-video After installing the NVIDIA driver using the NVIDIA binaries I managed to have a cloned twin screen configuration working.
However, the monitor is (wrongly) detected as having size 1824x768 (aspect ratio is widescreen) Using system monitor, I can set the correct size, but only for one session; besides, the login screen too is messed up the xorg.conf file seems right: proper resolution modes are set; xorg.0.log too
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.
View 14 Replies View RelatedWith Debian 8 (keeped up to date), after a sleep my DE (kde) will not start again. If I look to dmesg, the only strange things i see are:
[ 1.495366] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[ 1.495375] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[ 1.495431] systemd[1]: Found ordering cycle on basic.target/start
[Code] ...
My display manager is KDM.
I have installed Debian 8.1 with KDE desktop on Lenovo t431s with intel HD4000 graphics.
When using it with dual monitor configuration, I experience the problem when I put system to sleep (by closing the lid), then remove the external monitor cable (from miniDP port) and then try to wake system from sleep. The login screen freezes and I am unable to move the mouse or type in credentials. In case I had music player running I can hear the music after system wake , but it shutters while playing.
This does not happen on some other distributions, but the problem is that I very much like my current setup and I would like to fix this problem and keep it.
I do not know if this problem is due to KDE or KDM or it's Debian base.
I wonder if it's possible to configure Debian so that it keeps network connection live while in sleep mode
View 3 Replies View RelatedI can't get debian 5.0.4 i386 to load I can get as far as root for crash repair during boot-up but much further than that and my monitor turns off. Ubuntu 8.04.4 live cd (kernel is 2.6.24 i believe) works but says I have to enter noapic in the boot string. APIC is on and greyed out i.e. not accessible in BIOS --- might be non-compliant Only thing I can think of is to add acpi=off in GRUB entry but the change doesn't seem to work or take effect. I added it to the relevant entries in menu.lst in grub and it still didn't take effect. Grub must be getting its config info somewhere else...
View 1 Replies View RelatedJust recently I notice this behavior. When the machine sleeps either on timeout or after closing the lid, it doesn't come back on opening or hitting esc etc..
The machine seems to come back to life, but the screen stays black. I even tried Ctl-Alt-F1 with no response.
uname -a yields
Linux xxxxxxxxx 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux
and lsmod for video yieldsvideo
17683 2 i915,nouveau
I am using a old laptop as a server now and its running great! I would like to disable sleep/hibernation when I close the lid (i would prefer the screen still shut off if possible) ...
This has to be done via command line because I don't use a gui ...
After a sleep resume cycle, my background image is corrupt. It's replace by a weird image.
Before [URL] ...
After [URL] .....
I'm using Debian Jessie, Gnome 3.14.1, Nividia-drvier 340.65-2
The problem was highlight previously [URL] ....
I am reporting two problems that could be related to each other. They have something to do with USB devices upon passing through the ACPI S3 sleep-resume cycle. The hardware is Thinkpad T450s, with Debian 8 64-bit edition. Kernel is provided by either the stock linux-image-3.16.0-4-amd64 or Liquorix's linux-image-4.1-3.dmz.1-liquorix-amd64 . For this case, it does not matter; the problem exists in both versions.
I have an external USB hub which has a USB keyboard receiver (for Microsoft wireless keyboard/mouse combo) attached to the hub. I then usually attach this hub to the laptop.
FIRST: The main problem is that the USB hub was not going to be re-detected upon resumption from sleep. Here is the sequence of events, in brief:
* Laptop was resumed from S3 sleep
* USB hub was attached to the laptop (has external keyboard receiver attached to the hub)--both were detected & working properly
* Laptop was put to S3 sleep
* Laptop was resumed from S3 sleep, both hub and external keyboard were not detected, the syslog says "USB disconnect" to that particular device.
Note that during all the actions above, the laptop is running by external AC power.
SECOND: I also found that the USB hub, if inserted while the laptop was asleep (before resumed), it would not get detected. `lsusb` turns nothing for that device, as if nothing was inserted in the laptop's USB port.
THIRD: I did an experiment this way: instead of putting keyboard receiver on the hub, I attached it to the laptop directly. Hub is still attached elsewhere on the laptop as well. In this way, the keyboard receiver is not malfunctioning after resume. But I found out that the keyboard receiver is behaving funny after resumption. It went to a kind of "very low power" state a lot when idling (not receiving keystroke/mouse movement) for more than about 3 seconds. This causes the external keyboard response to be sluggish, since the receiver has to be turned on back to "active" state before able to responsively receive keystrokes properly again. And this causes a lot of lost keystrokes.
In the second case, the sequence of events are like this:
* Laptop was resumed from S3 sleep
* USB hub was attached to the laptop; it is working
* External keyboard receiver was attached to the laptop; it is working
* Laptop was put to S3 sleep
* Laptop was resumed from S3 sleep, the hub was not detected anymore; the syslog says "USB disconnect" to that particular device. The external keyboard was re-detected, but now is running in a funny power state described above.
These issues did not exist when I use a different laptop running Debian 7/oldstable (wheezy).
Here's the lsusb output before sleep (after the USB hub was attached the laptop):
Code: Select all ~ $ lsusb
Bus 003 Device 002: ID 8087:8001 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:0366 Acer, Inc
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 008: ID 045e:071d Microsoft Corp.
Bus 001 Device 007: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Now to back to sleep, then resume. This is what comes up:
Code: Select all $ lsusb
Bus 003 Device 002: ID 8087:8001 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:0366 Acer, Inc
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Devices (045e:071d and 1a40:0101) were not detected again!
I included below excerpts of syslog to show the effect of sleep/resume to the USB devices. I munged it from the full syslog using this command:
Code: Select all grep -i -e usb -e "systemd.*(suspend|sleep|resum)" -e "pm:" syslog| killutf8 > syslog.usb-only
Syslog events (for FIRST case above):
Code: Select all # [SLEEP1]
Aug 4 11:57:28 wirawan2 kernel: PM: Syncing filesystems ... done.
Aug 4 11:57:28 wirawan2 kernel: PM: suspend of devices complete after 701.491 msecs
Aug 4 11:57:28 wirawan2 kernel: PM: late suspend of devices complete after 11.036 msecs
Aug 4 11:57:28 wirawan2 kernel: PM: noirq suspend of devices complete after 14.231 msecs
Aug 4 11:57:28 wirawan2 kernel: PM: Saving platform NVS memory
# [RESUME1]
[Code] ....
I found several postings on the web similar to this, e.g. [URL] .... and see the references therein. But I don't think the problem is the same as mine. In particular, only external USB hub gives me problem like this (as well as the keyboard receiver, to a lesser extent)..
Note: I use debian testing.GUI very frequently completely breaks for me, it looks like this:URL....It usually happens after a short freeze or after going back to GUI from TTY (which doesn't display because of a known Nvidia proprietary driver issue).And sometimes my laptop goes into sleep state by itself while it's being used. This is lenovo ideapad z510 laptop, with intel+nvidia GPU (nvidia Optimus). To use nvidia GPU I use bumblebee.
View 2 Replies View RelatedI recently came to Debian. As I have an ati card, I tried the proprietary drivers first, but then came back to radeon (open-source). In the process, I think I may have broke my xorg.conf . Sometimes, when the monitor goes into sleep mode, when I came back, the screen remains black (sometimes I see just the cursor).
Here is my xorg.conf
# NOXORGCONFEXISTED: No X.org configuration file existed when this backup was created.
Also, I have lots of backups in my X11 folder, like xorg.conf.fglrx-3, xorg.conf.original-1, or backup.xorg.conf. Is it safe to remove them? What should I do about the main xorg.conf?
I have set up a hdparm configuration file ( /etc/udev/rules.d/50-hdparm.rules ) with :
Code: Select allACTION=="add", SUBSYSTEM=="block", KERNEL=="sda", RUN+="/usr/bin/hdparm -B 255 -S 0 /dev/sda" .
This works correct when I power on my system, however after waking my computer from sleep mode , /dev/sda appears to operate with APM .
Is there a way I can make this setting to be persistent ,i.e. APM disabled when waking up from sleep mode?
I am running Debian Jessie x64.
I have a Powerbook G4 1.67Ghz. My problem is that if I sleep my laptop by choosing sleep from the desktop menu in kde then it sleeps and wakes fine but when it wakes the pointer is locked to the x axis and tends to snap back to the same point when I'm not actively manipulating it. This is also the case if my laptop sleeps after 10mins inactivity. If I sleep the laptop by closing the lid this problem does not occur. When it wakes all is working well.
View 5 Replies View Related