no DMPS shutoff after re-installing ATI fglrx drivers
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
no DMPS shutoff after re-installing ATI fglrx drivers
I'm running Debian Squeeze on a Gigabyte GA-MA790GP-UD4H (HD3300 graphics) mainboard with a quad-core Phenom II processor. This was an upgrade as the system had been running on an Asus board with a Phenom processor. I just swapped the board out, move the memory over and plugged everything in.
Everything worked except the video was a little slow. I decided to try the open source drivers but I could only get vesa to work so I reinstalled the fglrx drivers. This time the video is very fast and KDE has even decided to turn on some desktop effects that weren't used before. Everything is great except my monitor isn't suspending or shutting down after x minutes of inactivity. All that happens is the screen saver (blank screen) kicks in and requires a password.
My xorg.conf Monitor section contains the line
I've also tried Option "DMPS" "true" but that didn't work either. KDE System Settings | Display | Power Control shows power management turned on, so it's not that. Rebooting hasn't helped.
Sorry, I didn't notice the transposition when I typed in the Options line.
As I mentioned, the Systems Settings | Display | Power Control has display power management active. I've turned it on and off several times in case it had lost the setting, but even after multiple attempts and several reboots, I still don't have DPMS working.
Thanks Glen. The service program is a Redhat thing. However the KDE system monitor shows acpid running.
I'm pretty sure that the BIOS has power saving enabled, but the Kernel should be ignoring/overriding the BIOS settings anyway.
I've got the latest Debian kernel (2.6.26-2-amd64) but I don't think I changed it anytime between when DPMS was working and when it stopped.
I'm running a few things on my computer right now. I'll check adding the Option "DPMS" to the other areas, although I've never seen it anywhere but in the monitor section before.
I've been reading some interesting stuff about xorg not doing much with the xorg.conf file anymore. It may be ignoring the Option "DPMS" line entirely. I've just tried running xset +dpms so I'll see if that does anything... Apparently it doesn't survive a reboot, but for now it will be good enough - if it works.
Interesting. "xset +dpms" didn't work, so I tried "xset dpms force off" to see if it would turn the monitor off. It blanked the screen but that was all. The monitor didn't shut down.
I know the monitor does shutdown because I'm using a kvm and it turns off when I have it pointed to a different computer.
I'm contemplating a fresh install of Linux at this point. My system is running good except for this one point, but this is big one. Without the monitor shutting down, I'm generating too much heat and using too much power.
Debian and rpm based distros are slightly different, but mostly similar.
Filesystem differences being the most changed.
But with locate and find you can generally find the file required.
Do you have lm_sensors, smartd (smartmontools) or hddtemp installed?
More information on package lm_sensors3-3.0.3-2mdv2009.1.x86_64
* To use this package, you'll have to launch "sensors-detect" as root, and answer a few questions.
There is no need to modify startup files as shown at the end, all will be done for you.
* A special note for via686a and i2c-viapro: if you don t see the values, you probably have a PCI conflict.
It will be corrected in next kernel. Change the /etc/sysconfig/lm_sensors to use i2c-isa + via686a
(or i2c-viapro + another sensor)
If so, you may need to run sensors-detect and/or re-run sensors -s (as root) to configure it for the new mobo chipset.
lm_sensors - Utilities for lm_sensors
This package contains a collection of user space tools for general SMBus access and hardware monitoring. SMBus, also known as System Management Bus, is a protocol for communicating through a I2C ('I squared C') bus. Many modern mainboards have a System Management Bus. There are a lot of devices which can be connected to a SMBus; the most notable are modern memory chips with EEPROM memories and chips for hardware monitoring.
Most modern mainboards incorporate some form of hardware monitoring chips. These chips read things like chip temperatures, fan rotation speeds and voltage levels. There are quite a few different chips which can be used by mainboard builders for approximately the same results.
Nice to know it got resolved. I was going to mention that on occassion when you make big changes to ATI's setup, you sometimes have to remove /etc/ati/amdpcsnd (but NOT amdpcsnd.default). In order to make the ATI drivers do as you expect. Otherwise running amdcccle might help setup advanced (or not) features.