Page 1 of 6

Backlight doesn't work with latest Maverick kernel

Posted: 09 Dec 2010, 00:57
by DervishD
Hi :)

Latest Maverick kernel, namely 2.6.35-24, prevents backlight control to work in my N150+ Samsung netbook.
I've manually modprobe'd the modules with debug=1 but I haven't noticed anything weird :?

To date, I've been using the modules installed with voRia kernels with latest Ubuntu kernels without problems.

Should I wait for the next voRia kernel or is there anything I can do to fix the issue? Right now I'm just booting with the voRia kernel, ignoring the kernel update.

Thanks!

Raúl

Re: Backlight doesn't work with latest Maverick kernel

Posted: 17 Dec 2010, 22:40
by Lolo
I have exactly the same problem for over a week on my N210 and the screen is now bleak.
Voria thank you if you could do something for us

Re: Backlight doesn't work with latest Maverick kernel

Posted: 20 Dec 2010, 15:56
by Ain
Same problem for me.
No one of my attempts worked to solve so I just boot with the previous kernel.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 21 Dec 2010, 15:21
by Drake
Same problem on NF310. :(

Re: Backlight doesn't work with latest Maverick kernel

Posted: 21 Dec 2010, 16:40
by Steph
Same problem on N220 and N150 :(

Regards

Re: Backlight doesn't work with latest Maverick kernel

Posted: 21 Dec 2010, 17:40
by Drake
Just filed a bug report: https://bugs.launchpad.net/samsung-tools/+bug/693071
Did anybody discover source code for building samsung-backlight?

Re: Backlight doesn't work with latest Maverick kernel

Posted: 22 Dec 2010, 13:39
by Drake
Adding

Code: Select all

acpi_backlight=vendor
to the kernel's parameter list in your bootloader should do the trick.
For some reason, in 2.6.35-24 the ACPI driver starts feeling responsible for controlling the backlight.

In case of trouble when updating the kernel, backlight can also be controlled by manually writing numbers (0-7) to /sys/class/backlight/samsung/brightness (you may have to save several times to reach your target level of brightness).

Re: Backlight doesn't work with latest Maverick kernel

Posted: 22 Dec 2010, 13:47
by Lolo
Drake wrote:Adding

Code: Select all

acpi_backlight=vendor
to the kernel's parameter list in your bootloader should do the trick.
For some reason, in 2.6.35-24 the ACPI driver starts feeling responsible for controlling the backlight.

In case of trouble when updating the kernel, backlight can also be controlled by manually writing numbers (0-7) to /sys/class/backlight/samsung/brightness (you may have to save several times to reach your target level of brightness).
you know, for many peoples, it's more easy to install Windows ! ;D

Re: Backlight doesn't work with latest Maverick kernel

Posted: 22 Dec 2010, 22:26
by Drake
I'm slightly aware of this fact.
Nevertheless, it might help some fanatic open source lover and Windows hater (I was told that Linux users sometimes match this character). ;)

Re: Backlight doesn't work with latest Maverick kernel

Posted: 22 Dec 2010, 22:34
by Lolo
sometimes yes .... but they are fewer and fewer ;D

Re: Backlight doesn't work with latest Maverick kernel

Posted: 22 Dec 2010, 22:58
by eth1cal
Many many thanks Drake : ) works like a charm!

Here's how you change the kernel parameters. I am running Ubuntu 10.10 Netbook Edition on Samsung N210, so my bootloader is GRUB2.

Open the terminal...

1) Type "sudo nano /etc/default/grub" (replace nano with your favourite text editor, if needed)
2) Add "acpi_backlight=vendor" to the GRUB_CMDLINE_LINUX_DEFAULT parameters, so that...

GRUB_CMDLINE_LINUX_DEFAULT="quiet"

...or something similar becomes...

GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi_backlight=vendor"

3) Close nano (CTRL+X) and save changes (Y)
4) Type "sudo update-grub2"
5) Type "sudo reboot"

In case you still have GRUB bootloader (instead of GRUB2), I believe you have to add "acpi_backlight=vendor" to /boot/grub/menu.lst, but unfortunately I don't have any system running with GRUB anywhere near, so I am unable to give you the full how-to. Google knows, I'm sure.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 22 Dec 2010, 23:47
by Lolo
Thank you Drake and eth1cal for your "how to"...

but it doesn't work for me (N210 & classical ubuntu 10.10)
I will wait for again for few days and maybe make a downgrade toward ubuntu 10.04 LTS ;)

Re: Backlight doesn't work with latest Maverick kernel

Posted: 23 Dec 2010, 00:05
by Drake
Try setting it manually:
1) Type

Code: Select all

sudo nano /sys/class/backlight/samsung/brightness
=> The file should contain a single number (0-7).
2) Type a small number (replacing the old one), e.g. "1" and save several times (CTRL+O, ENTER).
=> Your screen should lower the brightness step by step.

Posting the output of the following command may also help to analyse your specific problem:

Code: Select all

ls /sys/class/backlight
Before wearing sun glasses, try adjusting the brightness at the GRUB screen.

Re: Backlight doesn't work with latest Maverick kernel

Posted: 23 Dec 2010, 00:55
by Lolo
At the same time, an update of Voria's deposits, has changed for the maximum luminosity (and it's better for me for now)

As you suggest, I can manually adjust the brightness lower step by step without any problems. ;)

And here is the result of the code required:
acpi_video0 samsung


EDIT : I tried the eth1cal's method again and after the reboot, it works perfectly now, so a big thank you both for your help and your patience !

Re: Backlight doesn't work with latest Maverick kernel

Posted: 23 Dec 2010, 01:49
by Drake
The presence of the "acpi_video0" directory is a strong indication of the ACPI driver problem solved by the fix mentioned above. After adding "acpi_backlight=vendor" to your kernel's paramter list it must not (well, it should not) exist.
You might want to check if applying the parameter was successful by running

Code: Select all

sudo dmesg | grep acpi_backlight
Output should look like

Code: Select all

[0.000000] Command Line: ... quiet splash acpi_backlight=vendor
[0.000000] Kernel command line: ... quiet splash acpi_backlight=vendor
If there is no output, the parameter was not applied successfully. You may want to check the GRUB_CMDLINE_LINUX_DEFAULT string, rerun update-grub2 and reboot first.
If there is an output... well, one step at a time. Feel free to post it. :D

EDIT: I am glad to read about your success. :)