I have a several problems with my work notebook ACER E1-572 Acer | Aspire E | Aspire E1-572P-6403 | Datasheet without windows 8 and installed OpenSUSE 13.1 KDE. I’m a newbie in openSUSE, but not in system administration on win. You may have to restart your laptop to see the results. Repeat the same steps with Increase Screen Brightness Click on Decrease Screen Brightnessīutton and assign the keyboard combo(s) that your laptop can use to decrease the light level. , click on the drop-down arrow and select KDE daemon. To get started, navigate to the Start button–>Configure Desktop–>System Settings–>Shortcuts and Gestures–>Global Keyboard Shortcuts.KDE4 has added a new KDE daemon to handle brightness. Read CURRENT /sys/class/backlight/intel_backlight/brightnessĮcho $BRIGHTNESS_MAX > /sys/class/backlight/intel_backlight/brightness # To be called from dedicated hardware buttons, etc. # Script to toggle brightness to either "low" or "high". …anyone know in which universe “4882” is a reasonable “max” level, by the way? It’s not half of some ^2 number, so… ?) #! /bin/sh Max, min and “current” values can be read from the directory with the backlight “device” you’re using, and so on. And thought it was too much work to make a few different functions for reading up/down, etc. I… just didn’t want to make it read in a bunch of values every time I hit the key. Please don’t use it without modifying the paths and values first. Associated this script under here to a keyboard combination gnome recognizes (see keyboard->shortcuts).Gave /sys/class/backlight/intel_backlight/brightness write permission as user.(I kind of solved it for me with a toggle-script like this, though… But maybe the key-event is overriden by some other module? The event is stolen by the nvidia driver, something like that …I don’t know enough to figure out what’s going on here. ![]() But this key (unlike the volume, keyboard backlight, etc) generates an “unknown event” in the system log. Either with xinput->keyboard or the wmi-device.Īnother strange thing - there’s a hardware button on my n56 that actually generates a key-event on the wmi-device. But the brightness up/down keys (fn+f4/f5) don’t register at all. And this has events for a lot of different keys (keyboard light, volume, etc. So on my asus, I have this asus-wmi device registered with xinput. But… not completely convinced this is a “bumblebee” problem, or specifically an nvidia proprietary driver problem.) (Honestly curious about what is actually going on here. Passing a different… acpi_backlight=vendor or something like that in the boot changes the devices in sys/class/ (get an asus-nb-wmi device instead of other “video0” devices), but won’t change anything else, or catch the key-events. Not really sure what actually happens, but in my case I can still set the brightness controls in intel_backlight. Or, I guess, the key event isn’t associated with the right class, or an nvidia type of event is expected, perhaps. OSD turns up.Īfter installing the proprietary display driver (and disabling it with bbswitch and so on), apparently the increase and decrease script is associated with some other, presumably non-existent device in sys/class/backlight, so none of those devices are changed with the brightness tilt, and the OSD doesn’t show up. They set a device in sys/class/backlight/, and so on, no problem. When using only the default intel driver, brightness controls work as you would expect. ![]() With bumblebee/nvidia driver installed from overman’s repo. On a intel/nvidia (optimus) setup (asus n56 with the entire asus-wmi keyboard thing).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |