|
Bugzilla – Full Text Bug Listing |
| Summary: | dimming the screen doesn't work | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Forgotten User d3bkfIx-vJ <forgotten_d3bkfIx-vJ> |
| Component: | Mobile Devices | Assignee: | E-mail List <mobile-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | awafaa, forgotten_0RO3Kla3Ru, forgotten_k_W9C-4F_b, gfarrell, martin |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Screenshot of absent brightness slider in power management Performance profile | ||
|
Description
Forgotten User d3bkfIx-vJ
2010-11-30 18:59:59 UTC
I don't know what to make out of this, because this most likely hardware specific. under 11.2 it is working fine, so it should work under 11.4 ... Maybe it's only missing keybindings. How can I check that? Use xev. I'm running latest factory on an HP NC6320 and an Asus eeePC 1000HE. I gety different results from both. The HP works perfectly, where as none of the Fn keys work on the eeePC. So it looks like something happened with the eeePC ACPI Just did a fresh install of Milestone 5, and everything seems to be working fine in GNOME. Screen brightness controls are not working with a Samsung NF310-A01AU on 11.4 M5, in KDE. These are the xev outputs for Brightness Up (Fn-Up Arrow) and Brightness Down (Fn-Down Arrow) events:
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0
KeyRelease event, serial 34, synthetic NO, window 0x5200001,
root 0xab, subw 0x0, time 2855941, (804,211), root:(807,234),
state 0x0, keycode 233 (keysym 0x1008ff02, XF86MonBrightnessUp), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 34, synthetic NO, window 0x5200001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 34, synthetic NO, window 0x5200001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0
KeyRelease event, serial 34, synthetic NO, window 0x5200001,
root 0xab, subw 0x0, time 2858201, (804,211), root:(807,234),
state 0x0, keycode 232 (keysym 0x1008ff03, XF86MonBrightnessDown), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
The graphical brightness indicator does not appear on the screen when the brightness buttons are activated. In contrast, the Audio indicator does appear when the Audio Up and Audio Down buttons are activated. For comparison purposes, these are the xev outputs for the audio events:
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 34, synthetic NO, window 0x5400001,
root 0xab, subw 0x0, time 3871715, (-137,231), root:(1048,254),
state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 34, synthetic NO, window 0x5400001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 34, synthetic NO, window 0x5400001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 34, synthetic NO, window 0x5400001,
root 0xab, subw 0x0, time 3873983, (-137,231), root:(1048,254),
state 0x0, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
FocusOut event, serial 34, synthetic NO, window 0x5400001,
mode NotifyNormal, detail NotifyNonlinear
The only time the brightness indicator appears is after a powersave event: either an event has occurred, or a mouse event triggers the system out of a powersave profile. For example in Aggressive Powersave profile (Level set at 50% brightness, Dim Display after 2 mins, with screen off after 3 mins), afer 1 minute, the Brightness indicator appears, showing about 25%, then after another 30 seconds, the Brightness indicator appears, showing fully dimmed (0%). (These times are half the set times, which is probably a separate bug). If the mouse is then moved, the Brightness indicator appears, showing 50% level. Of note though, is that the screen brightness does not actually change when these indicator events occur; it stays at the same level throughout. When triggered manually by explicitly activating these profiles through mouse, menu or power button action, the screen brightness settings are again not followed.
The screen brightness also does not change when different powersave profiles are selected. For example, with these settings:
Powersave 75%
Aggressive Powersave 50%
Performance ???
the screen brightness stays at the same level as when the machine first started, regardless of which profile is activated. Note that the Performance level can't be stated, as the slider is absent in the settings dialog (see attached screenshot).
Output of cat /proc/acpi/wakeup:
# cat /proc/acpi/wakeup
Device S-state Status Sysfs node
EXP1 S4 *disabled pci:0000:00:1c.0
EXP2 S4 *disabled pci:0000:00:1c.1
EXP3 S4 *disabled pci:0000:00:1c.2
EXP4 S4 *disabled pci:0000:00:1c.3
PCIB S3 *disabled pci:0000:00:1e.0
PWRB S4 *enabled
Created attachment 406704 [details]
Screenshot of absent brightness slider in power management Performance profile
On a Toshiba laptop with Intel 965 GM graphics and using 11.4 X64 KDE MS6 updated to RC1 the screen dims after some time of non use and then when work restarts the brightness does not increase to the old value. The machine runs with the mains charger on and the battery is fully charged. Is this linked to this bug? or should I file a new bug? My comment above is still applicable to RC2. (In reply to comment #6) > Screen brightness controls are not working with a Samsung NF310-A01AU on 11.4 > M5, in KDE. These are the xev outputs for Brightness Up (Fn-Up Arrow) and It works a bit with KDE4.6.0 on a Samsung NF310: The brightness can be dimmed, but only between very low (indicator at minimum) and very bright (indicator at maximum), not discreetly. And in /var/log/messages are these messages: kernel: [ 2981.991453] ACPI: Failed to switch the brightness Confirmed on 11.4 with samsung n220p (marvel plus) . Brightness scaling works, but starts to scale down to the lowest/highest brightness available. Looks like a keyboard event<->brightness scaling hooks issue. E.g. no key release sent. The workarounds (force_release hack in sysfs) doesn't solve this here. Mabye just a missing quirk in atkbd ? evtest /dev/input/event0 evtest report on "space" : Event: time 1306938324.616450, -------------- Report Sync ------------ Event: time 1306938329.104620, type 4 (Misc), code 4 (ScanCode), value 39 Event: time 1306938329.104650, type 1 (Key), code 57 (Space), value 1 Event: time 1306938329.104656, -------------- Report Sync ------------ Event: time 1306938329.234245, type 4 (Misc), code 4 (ScanCode), value 39 Event: time 1306938329.234276, type 1 (Key), code 57 (Space), value 0 evtest report on "brightness down" (which goes down to low through all 8 steps): Event: time 1306938329.234283, -------------- Report Sync ------------ Event: time 1306938336.078620, type 4 (Misc), code 4 (ScanCode), value 89 Event: time 1306938336.078653, type 1 (Key), code 224 (Brightness down), value 1 Event: time 1306938336.078662, -------------- Report Sync ------------ Event: time 1306938336.078686, type 1 (Key), code 224 (Brightness down), value 0 Event: time 1306938336.078693, -------------- Report Sync ------------ Note the missing type 4 report here before the key released event ! <------ Hmmm, trying xbacklight on cmdline: * I think it is because of the default fading * samsung platform/backlight driver has latencies built-in * early readback (while value still processed by driver) might trigger scaling down brightness Ideas ? The patches here solve it here: http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=commit;h=fb1c6d41f212db192c2355d75baca2d5299f2ed7 Should show up in the kernel soon. Candidate for next 11.4 update kernel ? The patches here solve it here: http://git.kernel.org/?p=linux/kernel/git/gregkh/patches.git;a=commit;h=fb1c6d41f212db192c2355d75baca2d5299f2ed7 Should show up in the kernel soon. Candidate for next 11.4 update kernel ? setting the status to resolved because the bug is very old and it's working under 12.3 dito |