Ubuntu :: Power Saving Mode (monitor Off) Complete System Freeze?
Nov 21, 2010
when my monitor turns off after 30 minutes, I cannot do anything after. We're talking complete lock down of Ubuntu 10.04 64-bit. Not even alt+printscreen+REISUB reboots the machine; I have to do a hard reboot (which sucks and is hard on hardware).
All of a sudden today there was no display on my Ubuntu PC. It seems to be powering on - I get the LG screen when the monitor is switched on - but it goes into "Power Saving Mode". How do I diagnose this? I already unplugged and plugged. Monitor is connected to a graphics card - no change when I switched to VGA.
I've recently changed to Debian from Windows, it's a really great adventure so far, but I have one problem. So as I see you can set your monitor into "Blank Page" after 10 or any minutes to save power, like in Windows. 10 minutes passes, without any movement my monitor's led turns into orange and the monitor turns off, that's great, that's what i want.
But after a few seconds the led turns green (like when it's on), and it brings up a little box : "Power Saving Mode" (just like it did after 10 minutes), and it turns off, and then stars again from the beginning . And this goes on repeatedly until a move my mouse to get back from "Blank page" state. (It's like the monitor tries going into power saving mode, but it gets always a little bit of power, to show that text box, and start all over.) So what can I do? I use debian 8.0 "jessie", and my monitor is a LG L1750S(with Nvidia GeForce 9600 GT).
I have an Acer aspire notebook.graded from lucid and now I have a really big problem:every time i disconnect the ac-adapter from the pc, the system freeze completely, became unresponsive to commands and to sysrq. i need to phisically turn off the machine and then back on.
I work on Ubuntu 9.04 and our application requirement is not to go to power saving mode when application is running. I added ServerFlags section to /etc/X11/xorg.conf Section "ServerFlags" Option "blank time" "0" Option "standby time" "0" Option "suspend time" "0" Option "off time" "0" EndSection
This didn't help. Then I tried following commands gconftool-2 -s /apps/gnome-power-manager/ac_sleep_display --type=int 0 gconftool-2 -s /apps/gnome-screensaver/idle_activation_enabled --type=bool false I see that it works fine only if I change settings via Settings>ScreenSaver>Power Management in gnome. I wan to do this via script. Can I do this? Which file gets updated when I change display settings via Settings>ScreenSaver>Power Management.
When I try to shut my PC down (press the shutdown button in KDE 4.3.4), the desktop quits, but the console screen does not appear (the CTRL+ALT+F1 screen). Well, technically speaking it appears but only a still (not blinking) cursor is shown, otherwise the whole screen is blank. This means that not only the X freezes but whole system, because the keyboard is unresponsive too. It happend multiple times now, and every time I reboot after such event, some kde rc files (amarokrc, kmailrc, etc...) get deleted due to the automated filesystem check (unclean umount), which means that I have to reconfigure these apps again.
My home partition is on a separate EXT2 partition (this way I have full r/w access from winxp) and every time this is the only one which gets corrupted. The system partition (which is EXT3) is always intact (no fsck starts on boot). I'm using Debian Squeeze by the way.
How to configure Linux text console to automatically turn of the monitor after some time? And by "text console" I mean that thing that you get on ctrl+alt+F[1-6], which is what you get whenever X11 is not running. And, no, I'm not using any framebuffer console (it's a plain, good and old 80x25 text-mode). Many years ago, I was using Slackware Linux, and it used to boot up in text-mode. Then you would manually run startx after the login. Anyway, the main login "screen" was the plain text-mode console, and I remember that the monitor used to turn off (energy saving mode, indicated by a blinking LED) after some time. Now I'm using Gentoo, and I have a similar setup.
The machine boots up in text-mode, and only rarely I need to run startx. I say this because this is mostly my personal Linux server, and there is no need to keep X11 running all the time. (which means: I don't want to use GDM/KDM or any other graphical login screen). But now, in this Gentoo text-mode console, the screen goes black after a while, but the monitor does not enter any energy-saving mode (the LED is always lit). Yes, I've waited long enough to verify this. Thus, my question is: how can I configure my current system to behave like the old one? In other words, how to make the text console trigger energy-saving mode of the monitor?
All of these freezes happen either while I'm in Nautilus or I'm opening Nautilus. The usual Ctrl+Alt+Fx (x being one to six) to get into the backstage does not work. If I have some music open then it would start looping the last couple of seconds.Now generally I would go check the logs, but I see no nautilus logs so what should I check?This is all pretty recent. I think that this started to happen when one day exim4 (and some packages all marked exim) got updated but I cannot be certain. Major playing-around after that would be some Wine issues but the system froze once before all that Wine fun.So step one, what should I check?
I have a Dell Precision T3400 workstation (Nvidia Quadro NVS 290) with the kmod Nvidia driver installed. Everything works fantastic for power saving, the screen saver comes on , then the monitor blanks after a while. The only problem is that the monitor itself (Dell E228WFP) never goes into standby. The power LED stays green instead of orange. Worked fine under FC8, only noticed it recently under FC10.
I have been having a freaky experience where Firefox appears to freeze up and brings down the terminal and any process viewer with it. For example, I can open a gnome-terminal or xterm window, but the moment I press a key, that window freezes up as well and must be force-quitted with the Force Quit panel applet. In addition, the System Monitor applet I have on my top panel freezes. It's really weird.
I began having this problem around a month or two ago. I thought it was something to do with something I installed, so a week or so ago I did a clean install, backing up my documents, Firefox profile, and GNOME settings from the old installation but wiping everything else (I'd already ruled out the Firefox profile by renaming the folder and creating a new one from the profile manager). Yet the problem persists.
I'd be happy to post any output, but as bash (including Ctrl+Alt+F1 command line) freezes as well, it's a little hard to treat the problem when it happens. One more thing: I am on a university campus which uses 802.1x encryption on both wired and wireless connections; is it possible that that is causing the crashes?
Out of nowhere my computer will not boot up. I get the message like this NMI received for unknown reason 29 on CPU 0. Dazed and confused, but trying to continue Do you have a strange power saving mode enabled? NMI received for unknown reason 39 on CPU 0. Dazed and confused, but trying to continue Do you have a strange power saving mode enabled? I read something about it being the video card, so I took my old one out which it being an ati, an replaced it with an nvidia.
I have a very simple bash script that just runs a series of backups using tar; for example, one of the lines reads:tar -czvpf /srv/backups/backup_home.tar.gz /homeThis script is scheduled to run every Friday, but occasionally I will schedule it to run before using 'at'. The script is located on the same disk as the backups are saved, I then transfer them off the machine manually (I've yet to automate this). I am only compressing files that are located on the server's disk, no files are being transferred over the network at all.
The problem is, occasionally it appears to be causing the 'server' I have running all the time to completely freeze. When this happens the machine does not power down and there are no entries in the log that indicate a problem. Everything simply stops until I press the reset button. Note that this issue also happens when you run the script manually and not just when it is run via cron or at.I *think* this might be happening when a large file is being compressed, but I'm not certain.
I recently installed the first non-virtual Ubuntu server in our office (to put it in perspective, it's outnumbered several to one by Windows servers). It had an inexplicable array failure, and now it's been retasked to run VMware Server for testing purposes since we don't trust it at the moment. For the sake of ease of use, on this server I decided to install Xubuntu desktop x64, rather than Ubuntu server as I've done with a couple others.
This server is on an old school 8-port Linksys PS/2 KVM. It's got a CRT monitor in the middle of a rack of somewhat aging equipment. The problem I'm having is somewhere between the KVM, this old monitor, and some power saving... when Xubuntu tries to put the monitor in standby, instead it gets this vertically scrolling garbage. The Windows servers in this rack don't have any problem putting it to sleep, but I figured I might as well just turn off DPMS on this particular server.
So I logged in via SSH, stopped GDM, generated a /etc/X11/xorg.conf, and changed Option "DPMS" to Option "NoDPMS" which according to the manpage should take care of it. I also changed the GDM video mode with this xorg.conf so it's definitely being used. Following some other suggestions I found in my search, I issued "xset s off" and "xset -dpms" but this hasn't disabled monitor power saving either. I've been restarting GDM each time I change something. 5-10 minutes later it's scrolling garbage again. What's it going to take to turn off monitor power saving at the GDM logon screen?
I am planning to make a home made NAS running ubuntu server 10.04 LTS. Nothing fancy, simple samba with open access for all and openssh for admin access over the network. The NAS will not have heavy traffic, two home computers with occasional access, just to serve as central location. I am in doubt which CPU to use and I am after both budget and power saving solution.
1. I have an old Athlon Clawhammer I can use but the TDP of 90W is putting me off. I can also use existing 2x512MB DDR-400 memory with it. The board would be new. 2. I would rather invest in new mini-ITX board with built-in dual-core Atom D525 (TDP 13W), VGA and Gb ethernet. I would add 2GB DDR3-1333 memory.
Since I would need a new board for the Clawhammer too (current one doesn't have SATA), I am more attracted to option 2. Would the dual-core Atom be enough running this simple home NAS? I think it should but my experience with ubuntu server is limited.
I'm experiencing complete system freezes when dowloading torrents with more than 800kb/sec (I think this is the limit, I've capped it at 750, and it seems to be running ok now). I had this same problem in Ubuntu aswell. But not in Win 7. The problem also appeared in ubuntu when streaming video through VLC with more than 800kbps.
As my connection gives me quite alot higher download speeds this kind of annoys me, and me being quite new to this whole Linux thing, don't really know what to do. I had a dialogue with someone at Ubuntuforums regarding this, but we pretty much got nowhere.
running PCLinuxOS 2009.1 on my main machine : AMD Phenom II 545, 3GB DDR2, ATI Radeon HD 4870 512 GDDR3, 1 x 250GB IDE, 1 x 1x 250 GB SATA, 1 x 160GB SATA, 1 x 500GB SATA.What I want to disable are the HDD's powering down after a while because when I come back to work at my machine, it is painful to wait for the HDD's to spin up again. I also want to disable the screen from turning off. I have removed DPMS from myxconfig, but it as made no difference.
I intend to buy a UPS for personal use. I have a slackware 13.1 machine on a quite old pc, and what I would like is just the PC to being turned off after 5minutes every time there is a blackout. I have found the APC Power-Saving Back-UPS Pro 550. However I don't know if there are drivers for slackware.
I am using Xubuntu 9.10 on a nettop as a X11 terminal.In order to do that, I created a custom session script that runs some commands instead of starting xfce4-session and the likes from GDM. When I boot this nettop, GDM automatically logs a dummy user in (called "test"), and runs a script that does "xhost +", and opens a small X Terminal to keep the X session alive, while some other computer sets the DISPLAY environment variable to point to <nettop>:0 and runs gnome-session.
My trouble is that after 10 minutes of idle, the screen is blanked(power saving I presume). I tried to add "xset -dpms" and "setterm -blank 0 -powersave off" to my startup script, in vain. I want my power saving options to be configured on the remote computer, not the nettop. How could I prevent X/GDM/Whoever from blanking the screen ?
I am running openSUSE 11.2 x86_64. I am processing work units from Folding@home on this pc. Strange thing is, when I actually leave the pc alone and working on folding@home, my performance actually drops instead of going up as I would expect. I believe there is some kind of powersaving feature I cant find or something else that's hurting quite a bit on the PC. I am talking about maybe 20-30% performance loss. PC in question is: Athlon II 630.
Already deactivated Cool'n'Quiet from the BIOS. Got no fresh ideas on what could cause this weird behaviour.
Update: Code: [22:05:52] Completed 260000 out of 500000 steps (52%) [22:18:28] Completed 265000 out of 500000 steps (53%) [22:30:41] Completed 270000 out of 500000 steps (54%) [22:40:20] Completed 275000 out of 500000 steps (55%) [22:48:16] Completed 280000 out of 500000 steps (56%)
PC was "idle" working on folding and I came back at 54%, see the huge difference? Frames were taking about 13 minutes each when "idle". When I am using the computer, frames are done within 8 minutes.
I run Ubuntu Netbook 10.04 on my EeePC 1005HA. I'm going to get a SSD for it eventually, but I can't afford one right now so it's running from a 200GB hard disk I scavenged off a dead laptop.
I went in power management and set the option that says "spin down hard drives whenever possible", but this accomplished a whole lot of nothing - whenever the computer is on, the drive's spinning. I ran hdparm -y and the drive clicked off, and then promptly spun back up after a few seconds. Iotop shows occasional tiny bursts of activity from "jdb2/sda1-8", which I don't really know how to interpret, but I don't have anything weird installed so I'm assuming this is normal system operation.
Now, what I need is some sort of application, utility, command - anything - that forces the computer to keep all filesystem changes in RAM with the drive shut down; every five/ten minutes or so (this would hopefully be configurable) it spins up the drive, dumps the filesystem changes to it, and spins it down again.
I realize this presents data loss risks related to crashing and poweroffs when the cache hasn't been dumped to disk, but I'm willing to risk it as Linux never really crashes at all, and since it's a netbook power failures won't cause unexpected shutdowns.
I've covered a little of the exploration of this in another thread here. Unfortunately no replies.I've now installed as many power-saving features as I can get to work including laptop-mode scripts and my Asus Eee PC 900 has the battery lifespan of a gnat (2 hours 39 mins of extremely light usage including a long period of inactivity although with wireless turned on, from fully charged to battery cutting out, annoyingly this time ignoring my script that registers a critical battery APCI event and shut it down safely).
So, basically is my new Asus Eee PC 900 the worst designed netbook ever, or is linux just not supporting it's power-saving features? It is actually the version that comes with Asus's own linux distribution on it, but I've installed Arch.
[Code]...
What then are the power-saving options left available to me? How can I extend my battery life to long enough to check an email? What out of what I've said ins't working that really should?
I am trying to figure out why, i need to restart/reboot ubuntu in order to reconnect wirelessly after being in power save mode. It works fine before the power-save mode and fine after the restart. Is it an IP issue?
When I first installed ubuntu 10.10, the display was for some reason tinted green and shifted a few inches to the right. After experimenting with the resolution preferences, I eventually got it to a large resolution (1280x720 ... or something like that) yet is was quite blurry. I found out that the problem was with my monitor after I switched it to TV mode, then back to PC mode. It became perfectly clear! All I had to do then was adjust the screen positioning by shifting it left a bit.
Even though I have made the resolution I figured out to be default, whenever I turn the PC on after shutting down, it goes back to the "green-and-to-the-side" mode. :/ Ain't really a big problem, until I tried to fiddle with the resolution preferences s'more.
Somehow, I have set it to be twice as wide of the maximum my monitor can display, went back to being green tinted for some reason, and is completely shifted left (yet the right side is still visible) This means that I cannot see what is going on the left side, and cannot adjust the resolution preferences, nor can I click blindly cuz the border is only around my visible side of the screen. Now it is stuck like this.
I've researched many hours and eventually found the terminal command for the resolution preferences. it popped up on the visible side. Although it was to no avail cuz I HAVE TRIED EVERY SETTING AND OPTION and absolutely nothing changed. I assume a system restore would simply revert it back to the previous satisfactory settings, but the thing is I want to FIX it. I am new to this terminal stuff, so I want to learn it and all that. To put it simply, here's what I want:
Learn how to manually adjust resolution without depending on a simple dialog box. Make the satisfactory resolution default and consistent through turning it on and off. Link that could teach me the essential commands, all this googling is stressful. D:
A 2sec service interruption was enough to cold-crash my PC and its given me a few issues, most I have solved but Synaptic is freezing up. I can get into Synaptic if I go to the terminal and become root with sudo -i If I do it through Gnome it show a frozen-screen version of synaptic like the image I posted with this. Right after the outage (it cold-crashed my PC) I used to get a message box that would pop up when I tried to shut off the PC (I have enclosed images to illustrate) but I have since overcame that problem.
So I've come across several tips to optimize battery life on Linux. [URLs]. In addition to undervolting, I would like to underclock. Is there a way to control CPU speed outside of the BIOS via some software control in Linux... or some sort of boot manager? I would like to boot to linux using underclocked speeds and have Windows running full blast. Is there a way to run Linux completely in RAM? I have read that saves on power consumption from the hard drive.
I have a triple monitor setup, that works fine in Windows (either using Eyefinity, or just extended desktops) I HAVE been able to get all three monitors working as extended desktops in Ubuntu, but when I set it up, I usually get "Not enough allocated memory to enable this monitor".....OR by some weirdness, all three will work. but when I reboot or shut down and then come back, only two monitors are working, and I get a message saying that 'the configuration couldnt be saved, or there was a white line in line 1' or something to that effect.
Either get extended desktop working, or Eyefinity.
System info: Mother board Asus M4a78T-e 6 gig RAM AMD Phenom II x4 965 Black ATI Radeon HD 5770 Graphics CArd
I am having problems with the refresh rate if the screen. In the refresh mode of the monitor in the monitor options have only one option 60Hz. I have LG 24 + ATI Radon 3870, and have already installed the ATI driver via Ubuntu download center.
I am wondering if there is a basic tool out there that will work with graphics card powered by FOSS drivers that allows to adjust resolution (and configure secondary monitors) and then save that configuration so it can automatically be restored next time the system starts up.