Ubuntu Multimedia :: Monitor Backlight Comes Back On After DPMS Off?
Dec 23, 2010
After upgrading to Mythbuntu 10.10 from 9.10 (clean install) on my combined front/backend I cannot get monitor (Dell 3007) to switch off from remote, I have been using simple script to DPMS force off for years with no problems, it still works, but some random time later the backlight comes back on. I have tryed the more complex scripts that stop and start the frontend and all of the acpi_osi options. Disabling screensaver has no effect. what causes this, or how to fix? Sysem is Abit IP35e (I suspect this board is the problem)
[Code]...
I have 2 remote frontends both upgraded OK. I have tryed installing 10.10 on a 'scrap' P4 machine, DPMS off works fine on it. I would try another install and/or another MoBo but its the only TV system in the house now.
I have an embedded board with a small UPS. When AC power goes down, I need to turn off all power hungry devices in order to have a clean shutdown. First thing I do, is set DPMS to force powerdown, then go through the usual SIGTERM/SIGKILL/umount sequence. I have an Intel i915 Display adapter connected to an LVDS LCD panel.
Unfortunately, when Xorg dies, Xserver or the VT code turn the LCD panel back on.
I even tried working around it by directly poking the panel enable register in the Display chip, so that X doesn't know about it, but the panel goes back on when the VT comes back.
Is there any "legal" way of keeping the display off?
I'm using the stock nouveau driver that ships with Jessie, and loads by default. I installed this card during my botched attempt to upgrade from Wheezy. This is a fresh install, and DPMS isn't working right.
I can run "xset dpms force off", and the screens will blank. I even see the "HDMI signal lost" screen of both (identical) monitors. However, before the power LEDs of either monitor go orange (instead of blue) the screens come back on as if I had made mouse or keyboard input. If I've locked the screen with xscreensaver, the screens are blank (I use only the blank hack). I've forgone the use of xscreensaver for now, believing it to be contributing to the problem. If I run "xset dpms force off" now, the screens blank, but the "HDMI signal lost" screen doesn't show, and the screens immediately unblank.
Here's the output of "xset q":
Code: Select allxset q Keyboard Control: auto repeat: on key click percent: 0 LED mask: 00000000 XKB indicators: 00: Caps Lock: off 01: Num Lock: off 02: Scroll Lock: off 03: Compose: off 04: Kana: off 05: Sleep: off
[Code] ...
It's like something is preventing the screen from going blank, but I don't know what it could be.
I installed the proprietary nvidia driver. Sadly, it does the same thing, so that's one thing I can cross off as the likely culprit.
Ran this command:
Code: Select allxset dpms 0 0 0
So when "xset dpms force off" is called, it powers down the monitor immediately. I will be reverting back to nouveau, and will report whether the problem resurfaces.
Fn + brightness-rightness+ = shows notification about brightness status (50%), but does not control the intensity of backlight. it's just stuck on 50% and that's all.
unning 11.2 on laptop used as stationary desktop. Normally, the backlight turns off after several minutes of inactivity from keyboard/mouse. However, once video played using VLC, the screen simply blanks while backlight stays on, until system restart. Using Totem does not have this effect, but I like VLC.
The problem: backlight is in maximum state and I can not change it.
There are a tons of advices like this:
1 - Open terminal (as a superuser) and type: gksudo gedit /etc/default/grub 2 - In the text file that opens, find the line which says GRUB_CMDLINE_LINUX="" and, inbetween the "", insert the words "acpi_backlight=vendor" (the line will be as follows: GRUB_CMDLINE_LINUX="acpi_backlight=vendor"), save and close the file. 3 - Back again in the terminal session, type: sudo update-grub 4 - Reboot.
I just installed Ubuntu 10.04.1 32-bit on a Dell Optiplex GX280 with Intel P4 3.4GHz, 1GB ram, 40GB hard drive, it's connected to a 17" CRT monitor which was detected automatically. Anyways, I set screensaver to come on after 15 minutes, monitor to shut off after 30 minutes and computer to go to sleep after an hour idle. The screensaver came on and monitor shut off as desired but the computer wouldn't go to sleep. So I manually put it to sleep (clicked "Suspend") and it went down and came back up just fine.I then did a few other things like installed java, flash, vlc player and I noticed that the screensaver won't even come on now. What is going on???Running:
Code:sudo lshwshows under display: Intel 82915G/GV/910GL Integrated Graphics Controller. Again the screensaver and DPMS WERE working, but they aren't now. I don't understand why Ubuntu isn't doing what I asked it to do in Preferences. it's very frustrating
Currently I have two 1920x1080 screens running in Twinview on my Geforce 275 graphics card. Want I want to do is a quick simple way of disabling my secondary monitor when playing video games or using xbmc to watch movies, etc. I've tried a few applets but they require the xandr function which I think Nvidia doesn't support.
Is there a way to disable this quickly other than loading up nvidia-settings and disabling the monitor everytime. I don't really want to use two seperate x sessions and xinerama due to the fact you can't use compositing.
I like my monitor to turn off when I'm not at the computer for more than 10 or 20 minutes or so and it wasn't doing that. I haven't used Linux for years and was used to xorg.conf/x11.conf and xinitrc and such.
So I rediscovered xset is responsible for DPMS settings. xset -q revealed DPMS was off. So I used it and put it in ~/.xinitrc. It didn't work. After some canoodling around I found out about xfce's Session and Startup gui thing. I was using that to run ~/.xinitrc.
When I got to my desktop and did a check with xfce4-terminal by running xset -q it would show DPMS enabled but the values were wrong. 600, 0, 900 to be exact.
After some searching I came across the information that xscreensaver will override DPMS settings as it manages DPMS too. So after more canoodling I found out about xfce's Screensaver preferences dialogue and used that to set my values. The values would immediately be set but the problem is that they are not persistent. If I reboot or log out the values will revert to 600, 0, 900. They will only reset to what I want them to be by running xfce's Screensaver preferences dialogue manually.
man gdm3, info gdm3, grep -r DPMS in /etc/gdm3, grep -r dpms in /etc/gdm3 reveal nothing related to DPMS. I've done some searching and nothing useful.
there is an /etc/X11/app-defaults/XScreenSaver-nogl which has some DPMS settings but the times are too large (2 hours); the only thing that matches is the off setting which is specified there.
xscreensaver -no-splash is present in the output of ps so it is xscreensaver and not gnome-screensaver.
The weird thing is that I re-enabled my ~/.xinitrc in xfce's Session and Startup gui thing and it is being run, but the numbers are getting set wrong after it is run. (I put an echo command after xset dpms 900 1200 1500, and the file is appearing in ~)
Where does 600, 0, 900 come from? Mystified on how to proceed from here. I don't remember enough on how to see what's doing what. Is there some sys thing or proc thing I can monitor to find out what's setting these values?
Short version: my xset dpms values are getting reset to 600, 0, 900 every time I logout or reboot. They revert to 600, 0, 900 every time I get to my desktop. I use gdm3 and xfce. Where are these coming from?
I have this issue with two different computers. One is a dell optiplex gx60 and the other a hp pavilion a317x. The two monitors are a hp pavilion f70 and a nec mulitsync lcd.
The problem I have is the monitor will randomly turn off like it would if the signal is lost but the computer is still running. I cannot get the monitor back on unless I do a hard shutdown and reboot. Sometimes it will happen within minutes of turning on the computer and sometimes it will take hours or days. I have had this problem with ubuntu 10.04 which is currently installed, mint 9 xfce, and mint 9 fluxbox. The only distro that it did not do this on was peppermint ice and windows xp.
I don't know at this point if it is hardware or software related. I am new to linux so I don't know what else to look for.
i have a probelm once i leave my laptop there for a while the monitor turned off and there is no way for me to turn it back on, so i need to restart the machine.
I've been getting a message on my monitor where "Input not supported" is floating around. This only happens when I manually turn the monitor off and then later turn it back on. Leaving the monitor on and allowing it to go to the screen saver doesn't seem to cause the issue (but I prefer to turn the monitor off if I'm going to be away from the computer for any length of time).
Specs: Acer X203w monitor Radeon 9600 Pro Video card Linux Mint 8 (Helena) Resolution 1680 x 1050 (16:10 - Preferred native resolution for the monitor) Refresh Rate 60hz
[Code]...
I just had it happen again. I tried unplugging the DVI cable from the back of the computer and then plugging it back in. The monitor then displayed the desktop properly. I'm not sure if that makes a difference or not in what I may need to change settings-wise.
I am running on ubuntu 10.04 and using the latest nvidia driver. What I experience is a random black screen, my monitor goes dead and won't turn back on till I hardboot. I had this issue on windows and solved it by downloading rivatuner and telling it to force my 9700m into staying in 3d performance mode at all times. I know it has nothing to do with temps or anything like that. All I need to know is how I can duplicate what I did with rivatuner on windows
The following script should make screen blanking work without disabling gnome-power-manager code...
This script can also be called from a panel launcher (with ./<scriptname> if it is in $HOME). It will not disable the power manager even though the process disappears from the system monitor. The "if" condition is necessary because SIGHUP will return an error if the process doesn't exist.
If you want a bash command, add this to $HOME/.bashrc:
# The following cannot be implemented as an alias # and it cannot be called from a launcher, more's the pity dark () code...
I'm using Redhat 5 with a video card nvdia fx 1500 and a zalman zm-m220 monitor
Has anyone configured a 3D monitor with redhat?
I'm trying to set the resolution to 1680x1020. I edit /etc/X11/xorg.conf and try to manually enter the resolution but after a reboot it goes back to the default.
which is the file i need to edit to manually enter the resolution.
I cannot install Ubuntu 10.04, or even boot into the live CD. I'm not an expert, but I've used Ubuntu for several years, and I'm pretty sure I'm not doing anything stupid... Here's what happens when I boot with the Ubuntu 10.04 live CD: I get a purple screen with just an accessibility(?) symbol at the bottom (this lasts 15 seconds). The screen goes black, with a flashing cursor, then changes back to purple, this time with an Ubuntu logo, with 5 dots acting as a progress indicator (this lasts about 1 minute). The screen switches to standby. The CD drive continues to make noises for another minute or so, then stops.
I physically removed my graphics card (ATI Radeon HD 5770), and plugged the monitor straight into the VGA port on the motherboard. Now the CD boots up fine. I could try installing Ubuntu at this point, while my graphics card is unplugged, and then plug my graphics card back in, and see if it starts working then.
ive installed ubuntu 10.4 beta on a toshiba a505-s6015 intell i5 processor and intel integrated graphics.it worked fine then the backlight went off.well i restarted it a couple of times and it wouldnt come back on.how do i fix this problem?
The title pretty much describes the issue. The timespan is sometimes some minutes instead of some seconds. I've tried unplugging every peripherials and disabling the touchpad, killing every non-critical processes, disabling and enabling Compiz, but nothing has helped so far.
I'm running Karmic on an Acer Aspire 8935G-874G100BN laptop with a Radeon graphics chipset.
I am dual-booting Karmic/OS X. I have a MacBook Pro 5,1. When using the keyboard to change the backlight, the graphic in the top left does move to indicate a higher brightness (albeit, it moves extremely slowly).
I, of course, have all the necessary drivers installed.
I have all the packages I needed from the Mactel repository. This has been a problem within Karmic since I've put it on my MBP. There have been several updates from the Mactel repository concerning the Nvidia backlight package (I don't remember exactly what that package is called though). I hope each time that it will fix what is going on, but obviously, it hasn't.
Is there any program that I could use to otherwise change the backlight? When I'm sitting outside it's really difficult to see what's on my screen as it also doesn't automatically respond to the change in environmental brightness by making the screen brighter.
I have an Asus P50IJ-X2 and in lucid the backlight cannot be adjusted. The panel app doesnt work, when I click on it and try to adjust the slider it just disappears. When I reopen it the slider is at the top left corner of the screen.
The function keys seem to be detected alright, but when I press them I get the notification that the brightness is going down but nothing happens. Also after the first press the notification gets extremely laggy. If I press the brightness keys again it takes 30 seconds or more for the notification to show up. Also after the first press my volume function keys have the same behaviour in the notification area as the function keys.
Also messing with the controls in the power settings doesn't do anything. The strange thing is all of this worked perfectly in Karmic. The function keys, auto dimming, everything just worked out of the box. I have no idea where to start trouble shooting this so can anyone give me some direction?
Just upgraded to 10.04. Everything seems to still work on my Macbook, with a bonus being the buttons to modify the keyboard backlight brightness seem to work now.
However, the only caveat is that I can't seem to turn off the backlight. Pressing the dim button all the way to off just seems to reset to full brightness. Even if I set the brightness to 1 (almost off), the backlight seems to reset itself to full brightness at seemingly random times.
Running this command used to turn it off, but now doesn't work:
Code: echo 0 | sudo tee -a /sys/class/leds/smc::kbd_backlight/brightness
Is this a bug? How do I turn off the keyboard backlight?
I've finished integrating proper keyboard backlight support into gnome-power-manager (which in turn uses upower to actually control the keyboard backlight) which with any luck will be available in Natty out of the box. A similar patch should also land upstream too so Fedora etc should get it for free too in their next release too. In essence this allows us to provide the user with greater feedback and control than say just using pommed (ie. we can dim the keyboard on idle like the lcd display etc, and can display nice notifications of the keyboard backlight level too - see attached screenshot).
Debian Lenny on a Toshiba Portege 350000:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1 (rev 82)kernel version 2.6.26-2-686On my system, "xset dpms force off" blanks the screen, but does not turn off the backlight. This means that the automated screen off in X does not actually save any power when it blanks the screen.I can turn off the backlight manually using the BIOS tool "vbetool dpms off" (but then I have to turn it back on again manually too).Question 1: is this a problem with the graphics driver interface, or with X, or with the power management driver interface?Question 2: as a workaround, is there any way for me to hook into the dpms off/on that X is doing, and run a script to call vbetool? The best workaround hack I have come across so far is to have a screensaver that calls vbetool, but I was hoping to find something that doesn't require me to run a daemon all the time.
I have been given the task of installing CentOS 5.5 on some new Fujitsu Siemens S710 laptops and have the following problem. The OS seems to install without any issues but when it starts up you can see the login prompt just as the backlight is off on the laptop screen. If you were to plug in an external monitor it will work fine and the screen is perfect. The only thing I can think of is if the video drivers need to be updated but I can't seem to fine any Linux ones. It seems to use the Intel mobile HD graphics chipset.
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:
I just finished installing Fedora 11 and I'd love to love it but the issue is I can't see the screen without straining my eyes. So I bring to you almighty support forum a challenge: Need to enable the screen backlight. The laptop model is an Asus G50-X5