You are not logged in.

#26 2012-01-25 14:57:08

vwyodajl
Member
Registered: 2012-01-21
Posts: 183

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

orschiro wrote:

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

Mine has changed to /sys/class/backlight/toshiba/
and echoing no longer lowers it, so my acpi script fails on that part, but the fn keys work still? I have tried sending variables to all the files in there relating to brightness and one (actual_brightness) is not writable even tried changing permission to writable and still did not work. At least the fn keys still work for me.

I have an x505-887 toshiba just for reference.

Offline

#27 2012-01-25 21:20:58

LordChaos73
Member
From: .nl
Registered: 2008-11-11
Posts: 183

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

udev 179-1 fixed this problem for me.

Offline

#28 2012-01-25 21:37:22

Lexworth
Member
Registered: 2012-01-19
Posts: 36

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

Yeah, udev 179-1 did it for me too.

Offline

#29 2012-01-26 17:29:37

jwhendy
Member
Registered: 2010-04-01
Posts: 621

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

udev update to 179-1 that just came through fixed this for me.

Offline

#30 2012-01-27 15:17:30

martini
Member
Registered: 2010-11-30
Posts: 8

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

Can't check it now: turn my laptop to openSUSE smile

Last edited by martini (2012-01-27 18:05:23)

Offline

Board footer

Powered by FluxBB