Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

martini · 2012-01-22 15:42:35

Before last kernel update and kmod introducing my brightness combinations (fn+F2, fn+F3) worked perfect with "acpi_backlight=vendor" added to /boot/grub/menu.lst.

But after it that keys do not work at all. No icon on screen, no brightness change.

How make them work agane?

martini · 2012-01-23 15:39:13

Solved by downgrade (https://aur.archlinux.org/packages.php?ID=37713). But it's not right way!

olsman037 · 2012-01-23 15:41:23

Same problem with a vaio laptop... I don't want to downgrade so I'll wait for a fix..

martini · 2012-01-23 15:59:50

Let me know if you get keys working please )

ajaxas · 2012-01-23 16:08:33

This *does* seem like my problem with Sony Vaio: https://bbs.archlinux.org/viewtopic.php?pid=1046260

There are cases when similar problems are solved by updating to udev-git: https://bugs.archlinux.org/task/28049 (something with udev naming). Not my case, though.

My bad, I recently flushed pacman cache so I don't have old udev, module-init-tools or mkinitcpio packages. How could I get those packages for x86_64 architecture?

Last edited by ajaxas (2012-01-23 16:12:22)

martini · 2012-01-23 16:21:44

ajaxas wrote:

My bad, I recently flushed pacman cache so I don't have old udev, module-init-tools or mkinitcpio packages. How could I get those packages for x86_64 architecture?

Want me email it to you?

ajaxas · 2012-01-23 16:23:53

martini wrote:

Want me email it to you?

Please, do so!
ajaxas аt gmail dоt cоm

martini · 2012-01-23 16:28:22

ajaxas wrote:

Please, do so!

Done.

ajaxas · 2012-01-23 16:38:48

Thanks, but that didn't help either.

Lexworth · 2012-01-23 18:33:54

I was having issues with brightness control as well. I had acpi_osi=Linux and acpi_backlight=vendor in my kernel line. Before the kmod update it worked perfectly, on screen pop up and everything. After the update I could still control the level but it was laggy and no on screen pop up (this is in KDE).

I removed the acpi_osi=Linux from the kernel line and kept the other and now it works almost perfectly except for the fact that if I press Fn+brightness_up_key it opens the Run Command dialog box but only if brightness is all the way up at the same time. Weird.

Maybe this could help you narrow something down.

snoxu · 2012-01-23 18:55:43

I have the same issue after a system update on a Vaio laptop.

Adding acpi_backlight=vendor to grub does not fix it and my screen defaults to max brightness, so I removed it.

I can only adjust brightness thorugh gnome brightness slider in settings. Fn+brightness keys are broken for the time being.

Last edited by snoxu (2012-01-23 18:57:27)

olsman037 · 2012-01-23 19:01:22

An easy way to change brightness : install gbacklight
Another issue for me : the fn key to switch screen does not work either...

jwhendy · 2012-01-23 20:12:41

This is occurring on an HP 8540w laptop as well. All was well until last upgrade today:

[2012-01-23 09:34] synchronizing package lists
[2012-01-23 09:34] starting full system upgrade
[2012-01-23 09:35] warning: /etc/modprobe.d/modprobe.conf saved as /etc/modprobe.d/modprobe.conf.pacsave
[2012-01-23 09:36] removed module-init-tools (3.16-3)
[2012-01-23 09:36] upgraded freeglut (2.6.0-1 -> 2.8.0-1)
[2012-01-23 09:36] upgraded gnutls (3.0.11-1 -> 3.0.12-1)
[2012-01-23 09:36] upgraded gstreamer0.10-python (0.10.21-1 -> 0.10.22-1)
[2012-01-23 09:36] installed kmod (4-1)
[2012-01-23 09:36] upgraded udev (175-1 -> 178-1)
[2012-01-23 09:36] warning: /etc/rc.conf installed as /etc/rc.conf.pacnew
[2012-01-23 09:36] upgraded initscripts (2012.01.2-1 -> 2012.01.3-1)
[2012-01-23 09:36] upgraded mdadm (3.2.2-4 -> 3.2.3-1)
[2012-01-23 09:36] upgraded mkinitcpio (0.8.0-3 -> 0.8.2-1)
[2012-01-23 09:36] upgraded pixman (0.24.0-1 -> 0.24.2-1)
[2012-01-23 09:36] upgraded poppler (0.18.2-1 -> 0.18.3-1)
[2012-01-23 09:36] upgraded poppler-glib (0.18.2-1 -> 0.18.3-1)
[2012-01-23 09:36] upgraded poppler-qt (0.18.2-1 -> 0.18.3-1)
[2012-01-23 09:36] upgraded rxvt-unicode (9.14-1 -> 9.15-1)
[2012-01-23 09:36] upgraded sdl (1.2.14-10 -> 1.2.15-1)
[2012-01-23 09:36] upgraded sdl_image (1.2.11-1 -> 1.2.12-1)
[2012-01-23 09:36] upgraded sg3_utils (1.30-1 -> 1.33-1)
[2012-01-23 09:36] upgraded sqlite3 (3.7.9-1 -> 3.7.10-1)
[2012-01-23 09:36] upgraded xkeyboard-config (2.4.1-3 -> 2.5-1)
[2012-01-23 09:36] upgraded xterm (276-1 -> 278-1)

Using xev, certain Fn+F# keys are recognized, others are not. My brightness keys (F9, F10, F11) are no longer recognized.

BrencelJ · 2012-01-24 09:28:37

I have the same problem on my Vaio.

Brightness, switch screen, sleep, zoom in, zoom out fn buttons don't work and they aren't recognized by xev.

ajaxas · 2012-01-24 10:08:32

@snoxu
@olsman037
@jwhendy
@BrencelJ
Have you tried installing udev-git from AUR and if yes, did it help you?

olsman037 · 2012-01-24 10:18:33

Function keys work again with udev-git... Now just have to wait for an update of the official package (I work with my laptop so I prefer to not use unstable packages..)

snoxu · 2012-01-24 11:03:53

udev-git fixed it. It will do for now.

BrencelJ · 2012-01-24 11:28:38

It does't fix it for me.

jwhendy · 2012-01-24 21:05:12

Is everyone running SELinux? My udev-git build fails to find libselinux. This is with the standard Arch kernel.

twelveeighty · 2012-01-25 02:23:21

Alright - I was all by my lonesome over in Apps & Desktop Environments (https://bbs.archlinux.org/viewtopic.php?id=134258), but this must be the same problem I am having on my Toshiba A500.

Add Toshiba to the list of broken brightness adjustment.

Edit: I just noticed that there is an update to both the kernel and udev out there - I'll have to try that first, I guess.

Last edited by twelveeighty (2012-01-25 02:41:23)

orschiro · 2012-01-25 06:37:41

Are you guys able to adjust the brightness by directly writing the brightness level into sys?

I used to do that with the command

 echo "15" > /sys/class/backlight/acpi_video0/brightness

However, regardless what value I choose, the brightness doesn't change at all.

In this case upgrading to udev-git doesn't solve my problem.

Regards

ajaxas · 2012-01-25 13:12:42

@orschiro
If you use Nvidia proprietary video driver, put

Option  "RegistryDwords" "EnableBrightnessControl=1"

into the "Device" section of your xorg.conf or whatever /etc/X11/xorg.conf.d/* rule you use.

At least it works for me.

orschiro · 2012-01-25 13:18:14

@ajaxas,

I use the xf86-video-intel driver for my Intel GMA 3000 onboard chip.

I tried adding acpi_osi=Linux and acpi_backlight=vendor to the kernel line but this doesn't help either.

It used to work all the time.

ajaxas · 2012-01-25 14:01:31

That's strange. Check if your video kernel module is loaded.

Me, I found the root of my problem: it was XFCE. With udev-179 from [testing] and under new user account everything works.

orschiro · 2012-01-25 14:18:20

I was able to solve it.

Instead of writing the values to acpi_video0 I chose to write my settings to /sys/class/backlight/asus_laptop which still works perfectly.

Regards

Arch Linux

#1 2012-01-22 15:42:35

Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#2 2012-01-23 15:39:13

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#3 2012-01-23 15:41:23

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#4 2012-01-23 15:59:50

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#5 2012-01-23 16:08:33

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#6 2012-01-23 16:21:44

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#7 2012-01-23 16:23:53

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#8 2012-01-23 16:28:22

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#9 2012-01-23 16:38:48

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#10 2012-01-23 18:33:54

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#11 2012-01-23 18:55:43

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#12 2012-01-23 19:01:22

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#13 2012-01-23 20:12:41

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#14 2012-01-24 09:28:37

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#15 2012-01-24 10:08:32

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#16 2012-01-24 10:18:33

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#17 2012-01-24 11:03:53

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#18 2012-01-24 11:28:38

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#19 2012-01-24 21:05:12

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#20 2012-01-25 02:23:21

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#21 2012-01-25 06:37:41

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#22 2012-01-25 13:12:42

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#23 2012-01-25 13:18:14

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#24 2012-01-25 14:01:31

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

#25 2012-01-25 14:18:20

Re: Last update to 3.2.1-1 & kmod broke backlite brightness keys @ Samsung

Board footer