On 07/16/2014 03:49 AM, David C. Rankin wrote:
On 07/15/2014 05:28 AM, auxsvr@gmail.com wrote:
On Monday 14 of July 2014 20:52:39 David C. Rankin wrote:
Testing acpi_listen:
$ acpi_listen video/brightnessdown BRTDN 00000087 00000000 K video/brightnessdown BRTDN 00000087 00000000 K video/brightnessdown BRTDN 00000087 00000000 K video/brightnessup BRTUP 00000086 00000000 K video/brightnessup BRTUP 00000086 00000000 K video/brightnessup BRTUP 00000086 00000000 K video/brightnessup BRTUP 00000086 00000000 K ^\Quit
Hmm. So the keystrokes are seen with acpid running, but it has no effect on the brightness. So it looks like we need to create hooks or a config for the events. But where? /etc/acpi/events?
It depends on the desktop environment. On KDE 4.13.2, System Settings/Shortcuts and Gestures/Global Keyboard Shortcuts/KDE Daemon/Decrease or Increase Screen Brightness allows you to set the keys.
Guys,
The problem here seems to be 13.1 itself. I ran acpi to get a status:
# acpi -V Battery 0: Unknown, 100% Battery 0: design capacity 4000 mAh, last full capacity 4000 mAh = 100% Adapter 0: on-line Cooling 0: LCD 0 of 7 ^^^^^^^^^^^^^^^^^^^^^^ Cooling 1: Processor 0 of 3 Cooling 2: Processor 0 of 10
(which knocked network manager offline and my wireless??)
Here is the issue:
Cooling 0: LCD 0 of 7
WTF?? Cooling? then LCD 0 of 7??
It looks like the LCD brightness function is FUBAR in 13.1 for my Toshiba. Cooling??
I don't even know what to make of this?
I also think 13.1 is looking at the wrong brightness. The *current brightness* is 7, not zero. Recall, I show 2 brightness interfaces under /sys/class/backlight: # cat /sys/class/backlight/acpi_video0/brightness 7 # cat /sys/class/backlight/radeon_bl0/brightness 0 So it looks like acpi reports the wrong one, and who knows what it is attempting to set. The values never change in either when I use the function keys. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org