Just replaced Ubuntu with Fedora, as 10.04 went berserk with my old tpad t42. f13 seems nice.I want to enable the Dynamicclocks feature (graphics chips frequency scaling). I know how to do it with x.org.conf, but now i is gone, and i am not sure. How to make use of Graphics Chips Power Management features
View 2 Replies[A word of explanation: initially the post below followed a post by Adam Williamson in another thread devoted to inability to load GNOME 3 in VM; this is why I address Adam in the opening.]
Adam, the situation with the GNOME 3 support for Intel integrated graphics seems to be a little confusing. You are probably among the most competent to clarify it.
Let me tell my own story first.
I was installing earlier today Fedora 15 on an HP dm4-1160US laptop with i5 and Intel graphics, and the anaconda installer hung right after "Waiting for hardware to initialize..." flashed on the screen, before even Media Check screen was reached. I tried a few times, always with the sae result: anaconda hung. Then I decided to add nomodeset to the boot parameters and the anaconda installer went on and I was able to complete the installation without a slightest problem.
I rebooted and without a problem reached the GDM login screen. When logging into GNOME, a pop-up window informed me that the system was unable to load GNOME and that instead I would be logged into the fall back mode. By the way, I haven't experienced the problems that plagued "Classic GNOME" on another laptop of mine where instead of clean install I preupgraded from Fedora 14 (strictly following the guidelines for preupgrading).
Wireless card was recognized and wlan initialized, nearby wireless networks seen, yet I wasn't able to connect to my own wireless network (I tried to do this already in the process of installation, equally unsuccessfully).
I was able to connect via Ethernet cable, and then I proceeded to perform yum update.
The update brought a new kernel. I went into grub.conf and noticed that nomodeset has been automatically added to the boot parameters for each of the two kernels. I decided to perform an experiment: I removed nomodeset from the boot options for the new kernel, and left it in place for the anaconda installed kernel.
I rebooted into the new kernel. Right after the grub menu disappeared, the screen turned pitch black and stayed this way for good 10 seconds. I thought that the former situation repeats itself making impossible to boot without the nomodeset option. Suddenly, the screen lit up and the GDM login screen appeared.
I logged into a shiny GNOME 3 where I am writing these words right now. Ah, and I was also able to connect to the wireless (I made yet another attempt using the network manager applet -- this time it worked).
What does that seem to indicate? That GNOME 3 support is already available for Intel graphics chips? But one may need to play with the nomodeset cheatcode, as I described this above?
Maybe I don't pay enough attention. I just know that whenever I've wanted to resize an image or email it, I've been able to do it pretty quickly. It was usually a two step process of resizing with an editor and then sending from a menu. Today, though, I went into the shiny new Shotwell and there appears to be no way to resize; or email.
OK. Went back into F-Spot. Surely there's an easy way to resize and/or email from there. Nope. Are we missing an easy way to do this or am I missing something? I love Gimp but do I have to use that to resize an image? Seems like overkill. Ostensibly, there should be a one stop process - either from an app or from Nautilus - send image and a quick dialog to ask what size and GO!
it doesn't do anything critically wrong.it shuts down, starts up, suspends, restarts, etc, rather well.only thing is that, altho' I set the settings to never hibernate and to never put the display to sleep, it does. I't's annoying, since I can't whatch a movie in peace, for instance.
View 1 Replies View RelatedWhen I change the "Put display to sleep when in active for" it seems to make no difference. The screen goes to sleep when it wants. Some times in the middle of watching a dvd (after about 10 mins when it is set to 1 hour).Could this be done by terminal, perhaps there is a problem between entering in the GUI and actually telling the machine.
View 1 Replies View RelatedI installed Fedora 13 (KDE) version: Linux version 2.6.33.5-124.fc13.i686.PAE latptop: toshiba satellite C650 - intel core i3 I have few problem, one of them is the power management it seems the power management can't see the battery therefore not battery status. power profile isn;t working. after shutting down the system, the computer stays on (screen, hdd ..etc) until I press the "turn on button". also I cant change the screen brightness using power management..its fixed.I dont know whats the problem and i dont know how to fix it.
View 2 Replies View RelatedI just did an upgrade from F13 to F14.[*] Now, power management (in Gnome) does not work any more. For example, when pressing the power button, there is just a 'Cancel' button (no button for shut down, suspend, hibernate), in Gnome menu there is no possibility to shut down, and in 'gnome-power-preferences' most options do not work at all. For example, there is no other option than 'Blank screen' for 'When laptop lid is closed' action. When starting 'gnome-power-preferences' with '--verbose' parameter, I get following error messages:
Code:
Cannot add option, as cannot suspend.
...
[code]....
How to disable the power management in fedora 12, so that lcd/monitor should not go to sleep/off when system is idle?
View 3 Replies View RelatedI've just [up?]graded from F14 (Fedora 14) to F15 - actually a fresh install, - but now I don't know how to set Power Management in F15.
Are there any F15 users out there that use Power Management?
I'd like my laptop to run when the lid is closed instead of going to sleep and stop the hard drive from spinning down, because it's got hardware encryption on it and it doesn't like to sleep and then be woken up. In fact, I'd like to completely avoid any kind of sleep.
It looks like Fedora 15 is quite fancy but missing a lot of basic features that even Fedora 14 and earlier had (unless I'm somehow unable to find these features in an obvious place). If I can't figure out how to do power management I'll have to upgrade back to F14.
I just upgraded from FC10 to FC11 (32-bit) on an old Dell laptop. I set my power management settings (in Gnome) to turn the monitor off after some idle period but always leave the computer running and the hard drives powered. I also set my screen saver to a blank screen. I noticed that the screen saver does come on (turning the screen black), but the monitor back lighting never goes off. I tried different idle times for the power management settings (I usually set it to 1 min, but some other posts implied that 11 mins might work). I should also mention that this is after I've logged into a user account, not sitting at the login screen.
I didn't have this problem in FC10 (the monitor would actually turn off) so I figured it was a bug in FC11, but I can't seem to find a thread addressing this issue. I've found some what similar threads, but none mentioning this particular problem.
I have searched for a solution to this issue (it's difficult to come up with a minimum number of search terms) and have found at least one person reporting it, but the solution is "check the xorg logfile" - which is entirely too vague, since I don't know what I'm looking for in the file. Here's the issue: The screensaver and/or power management appears to initiate a logout when I try to awaken the computer, whether the screensaver is still functioning or the screen has been turned off. Wither way, I jiggle the mouse, and it appears there is a crash (black screen with spinning mouse circle) resulting in a new login screen, which is entirely disruptive if I have software running, such as recording an audio stream with Audacity.
I'm using KDE with an OpenGL screensaver (antinspect) set to engage after 10 minutes. As for power settings, I am "letting powerdevil manage screen power saving." On the screen tab I have checked "Dim display when idle for more than [10] minutes." I have enabled display power management - standby after 20 minutes and power off after 30 minutes. (There are way too many options under KDE now, and I don't find an explanation of what the various "Profile Management" options do and what the tabs for "Actions" and "CPU and System" do differently from the "Screen" tab. I have an ATI 4650 video adapter. I'm not using a proprietary driver, since I've not been able to determine that there is one that will work with Fedora 14 (or any other Fedora, for that matter). The machine is a recent AMD (dual core 6000+) with 4Gb of memory.
I'm trying to enable power management on my ATI Radeon HD 3650 video card (GPU: ATI RV635; see my Smolt profile). I'm using the open-source radeon driver (xorg-x11-drv-ati-6.14.1-1.20110504gita6d2dba6.fc15).I've followed the instructions found on the Arch Linux Wiki.In order to verify if power management really works, I've tried to enable the "low" power profile through these commands:
Code:
echo profile > /sys/class/drm/card0/device/power_method
echo low > /sys/class/drm/card0/device/power_profile
I've also added the above-mentioned commands to /etc/rc.local to have them executed at startup.Although this page on the X.Org Wiki says that power management on my video card is supported by the radeon driver, GPU clock frequency doesn't seem to decrease: cat /sys/kernel/debug/dri/0/radeon_pm_info reports
Code:
$ cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 725000 kHz
current engine clock: 722250 kHz
default memory clock: 500000 kHz
[code]....
Also, enabling dynamic frequency switching through
Code:
echo dynpm > /sys/class/drm/card0/device/power_method
seems to have no effect. how to actually enable power management on my GPU?
I can't find any proper power management options on Fedora 15, only really basic simple options under the Advanced tab of the Screensaver.Where can I change the Power Management settings in F15?I'd like to set it so that
- screen powers down on closing the lid only, else never powers down / or after a certain time.
- the machine never powers down, either on AC or on battery.
- screen dims on battery after some time, but no on AC.
- hard drive never powers down.
I previously used Fedora 14 and earlier version on my laptops, and could easily set these power management either through the Screensaver, or directly from another menu.Also, I enabled the "Blank Screen Only" mode in the Screensaver, and disabled the "Lock Screen After", but it still asks for a password after some time. How can I stop that?
I just upgraded to f15 x86_64. I use a VPCCEB3Z1E vaio laptop and I noticed that my laptop can't last more than half past an hour running from battery in wireless productivity (just surfing the net and make some word processing, so nothing so heavy...) I use kde 4, installed cpupowerutils (replacement for cpufrequtils), put the modules acpi_cpufreq, cpufreq-ondemand -powersave and the other governors in /etc/rc.d/rc.local for loading them at boot. Edited profiles in powerdevil (every profile has cpupowerutils freq-set -g and the name of a governor) but i still notice no changes. How I can get a better power management on this laptop? Fan still runs at high speed.
View 3 Replies View RelatedI have Fedora 15 gnome 3 installed on my new laptop. When my system runs on battery my power management keeps changing my screen brightness. It keeps dimming my backlight. In the GUI of Power Management I cant find any option to change this setting. How can I do that through Command Line
View 4 Replies View RelatedOn the last release, I had this app installed where I could pick my power profile. I could use power conservatively, and performance would suffer a bit, but longer batt life,or I could have it automatically detect, or I could have the apps use all the power they want and then some. I'm looking to reinstall that app. What was the name of it?I can't remember, and so far, can't find.
View 2 Replies View RelatedI 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.
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 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'm used to write simple programs on codeblock which run on consle. i.e.console applications. When I try to compile programs which need graphic features, I get stuck as many libraries 9especially header files) are not in MINGW/include folder so I have to search on the net and add those files into include. My question is, by default, to enable graphics features on code block which "folder" should I download and incorporate it into codeblock? I tried to follow examples on glut, opengl, that is you have to download glut and add it somewhere on codeblock. Now I just want to have graphics functionality especially which need graphics.h file, searched on the net and find that sometime you have to download BGI, sometimes you have to download SDL, etc.
I hope you get the picture of what I'm trying to understand, it seems that by default codeblock doesn't come with graphic functionality e.g.graphics.h file, now what shall I download, and where do I add it so that I can draw graphs etc on codeblock. [codeblock has /include folder in C: Program FilesCodeBlocksMinGWinclude], now whenever I download new feature e.g. glut has its own version of include, lib folders etc. Is it necessary to add those include, lib on inlude, lib of C:Program FilesCodeBlocksMinGW? or it should work on its own original path? suppose I download glut on C:Program FilesCodeBlocksGlut. Now, what folder should I download to have graphics on codeblock?...
I have selected to power down the monitor after 30 minutes, and suspend the computer after an hour. It does not work. With Beagle not running (more below), the monitor powers down after 30 minutes as expected. But then later (probably after an hour?) it powers up again and stays that way. Not exactly what I envisioned.I have removed Beagle from the set of running processes. The process list ("ps ax") shows Beagle as a serious consumer of CPU time, far more than any other process. (At termination it was at 500:00; the next most hungry process was /usr/bin/Xorg at 10:00. Most barely get over 0:01.) It introduces these problems:
1. after some amount of system idle time (it is about 5 - 10 minutes) Beagle starts consuming vast wodges of CPU time. I have dual core AMD 5200; both CPUs run up to about 70% usage until I do anything, like move the mouse. Then the usage drops back to the usual 5 - 10%.
2. When Beagle is thrashing the CPUs, the power management monitor thinks the system is busy. And powers down nothing.
I've attached a UPS to my server through USB. and sure enough up came a tab in Power Management Preferences for the UPS -- great.
There are power low options as follows:
"When UPS power is low"
"When UPS power is critically low"
The UPS sends a message to the computer when a threshold you set in the UPS is reached, in my case 25% of battery left.
The obvious guess is that this warning from the UPS is the "When UPS power is low" however, I don't know. It's just a guess.
Looking further at the data I can get from the UPS the battery data is as follows:
battery.charge: 100
battery.charge.low: 25
battery.charge.warning: 50
battery.runtime: 760
[Code]....
However, again, that's just a guess from what would make sense.
So my first question is, is there a way to know this information, and is there a place were these critical points are set, or are they all from the UPS. I'm guess there are some settings somewhere because not all UPSs are going to be able to supply this information. Some may only supply a battery level or some just a warning message so there must be some configuration for this somewhere.
My 2nd question is a probably a little harder to know the answer to. After getting this to work I wanted the added functionality of nut so I installed it and got it working and it uses the On UPS Power panel as far as I can tell.
Through all the nut documentation it talks about powering down on once the battery level reaches the critical point (I assume that is "When UPS power is critically low"). I don't see anywhere however where it mentions handling "When UPS power is low" so now the question comes up, will it have any effect at all with nut installed, i.e. what will happen?
Of course I can just "pull the plug" and start finding this stuff out but Linux is all about having the information and "knowing" (assuming all works as it should) I am asking to find out where this information would be -- and become smarter for it
Alright this is not a huge issue but a rather annoying one. I hook my laptop up to my lcd to watch movies all of the time. The problem is though I have selected and reselected many times for the screen to not power off after so many minutes of inactivity. But for some reason it doesnt work. If i set it to an 1 it still like every 5 minutes turns off my screen. Im running 9.10 on a toshiba satellite with an intel graphics card.
View 2 Replies View RelatedI have a laptop with 10.04 installed. When it is plugged in with AC Power, the screen fades black after a few minutes and locks up after about 10 minutes (shows a dialog for passwd when back).This gets really annoying when listening a movie or just reading text.System->Preferences->Power Management is set to "never" for everything.gconf-editor->apps->gnome-power-management is set to "0" for everything finishing with *_ac.
View 1 Replies View RelatedI am wanting to completely disable Power Management, can I do it through the GUI? I am a former OpenSuSE user & am use to YaST. So it is a little hard finding ways to edit some settings.
View 2 Replies View RelatedI just did a fresh installation of Kubuntu 10.10 on a laptop last night, which has a 1.6GHz Intel Core Duo CPU.
I was very disappointed to find that there appears to be no way to configure CPU frequency scaling in the System Settings. There were options for this in 10.04.
I prefer to have the CPU running at maximum speed when running on A/C. In Maverick, however, I have had to resort to installing cpufreq-utils, and setting the CPU cores to 'performance' from the command line.
I like this laptop a lot, but even many simple games run sluggishly if the CPU cores are not set to run at max GHz. (As a matter of fact, this machine is much more sluggish even with CPU cores running at maximum in 10.10 than was the case in 10.04.)
I wonder why such an important option would have been removed from the power management settings?
when i get the Graphics device driver on, then the power management not work. it can not change the CPU frequencies, and it can not change the LCD backlight and save the change. I try a lot, install laptop-mode-tools,and change thd setting, it still not work...
ubuntu 10.04.1
linux 2.6.32-27-generic
i5 460m CPU
ATI HD5470
Ok, I am running a file server that can be accessed throughout the house. I was able to successfully wake from suspend and it works beautifully. Now what I need the computer to do is go to sleep after lets say 30 minutes of inactivity so that I never have to touch the computer and it will use minimal power until I need it.
Anyhow, I tried to set the settings in Power management and the only thing that happens is the display turns off. the suspend on the desktop works fine, I can type in sudo pm-suspend and that works fine. but the computer just wont go to suspend automatically by way of the power manager.
I have tried changing the /etc/pm/config.d/00sleep_module to say SLEEP_MODULE="uswsusp", but that only made the computer go into some crazy linux mode that I had to reboot from. I had to change SLEEP_MODULE="kernel" (actually, I left it blank as it is the default).
I also turned off my screensaver so there wouldn't be any confusion from that.
I also ran cat /var/log/pm-powersave.log and I got a long list with the following being one of the main texts that kept repeating. "/usr/lib/pm-utils/power.d/sched-powersave false:**sched policy powersave OFF"
I'm fairly used to working with Fluxbox.There,if I want to let myself suspend the computer, all I have to do is add something like Code:[exec] (suspend) {sudo /usr/sbin/pm-suspend}to my .fluxbox/menu and it works like a charm, after having added me to the sudoers. I nstalled openbox earlier today because I was having some font rendering issues in flux and I've been trying to find a way to add something similar to my menu without success. I added this to .config/openbox/menu.xml:
Code:
<item label="suspend">
<action name="Execute">
[code]....
I've got a new netbook - Dell Inspiron mini 1011. I have installed slackware 13 on it. According to dell's website its battery should last up to 9 hours:Quote:Mini 10 offers up to 9.5 hours of battery life1 to keep you on the go.I understand that it depends on a variety of factors and these are just testing estimations that will probably never be achieved IRL.For 95% of the time I don't run X on it. Just emacs (gnus), nethack, elinks. If I do run X, it's fluxbox. The average battery time is 2hrs - 2.5hrs. I understand that Slackware 13 is not designed specifically for netbooks, but 2hrs is way off the 9-hour estimation. Either the battery is faulty, or it's the power management issue. Before I deal with the battery, I'd like to ask you for some suggestions on improving the power management. The acpi and acpid are installed on the system. Are there any packages that would improve the battery performance? Or perhaps some config options?I believe that recompiling the kernel would improve it, wouldn't it? What options I'd have to set/unset?P.S.Unfortunately, once I checked the netbook is ok, I removed WinXP that came with it, so can't compare with it.
View 14 Replies View Related