[Kubuntu 11.10] Screen brightness control does not work on Samsung RV511 laptop

[Ivan Stetsenko]

The Fn keys does show the brightness indicator, but the brightness itself is not changed. The brightness regulator in the power applet in the notification area does not work either.

lspci

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
02:00.0 VGA compatible controller: nVidia Corporation Device 0a7a (rev a2)
02:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1)
03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

lspci -n

00:00.0 0600: 8086:0044 (rev 02)
00:01.0 0604: 8086:0045 (rev 02)
00:16.0 0780: 8086:3b64 (rev 06)
00:1a.0 0c03: 8086:3b3c (rev 05)
00:1b.0 0403: 8086:3b56 (rev 05)
00:1c.0 0604: 8086:3b42 (rev 05)
00:1c.3 0604: 8086:3b48 (rev 05)
00:1d.0 0c03: 8086:3b34 (rev 05)
00:1e.0 0604: 8086:2448 (rev a5)
00:1f.0 0601: 8086:3b09 (rev 05)
00:1f.2 0106: 8086:3b29 (rev 05)
00:1f.3 0c05: 8086:3b30 (rev 05)
00:1f.6 1180: 8086:3b32 (rev 05)
02:00.0 0300: 10de:0a7a (rev a2)
02:00.1 0403: 10de:0be3 (rev a1)
03:00.0 0280: 14e4:4727 (rev 01)
05:00.0 0200: 10ec:8168 (rev 06)
3f:00.0 0600: 8086:2c62 (rev 02)
3f:00.1 0600: 8086:2d01 (rev 02)
3f:02.0 0600: 8086:2d10 (rev 02)
3f:02.1 0600: 8086:2d11 (rev 02)
3f:02.2 0600: 8086:2d12 (rev 02)
3f:02.3 0600: 8086:2d13 (rev 02)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: stetzen 1930 F.... pulseaudio
 /dev/snd/controlC0: stetzen 1930 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc800000 irq 43'
   Mixer name : 'Realtek ALC269VB'
   Components : 'HDA:10ec0269,144dc581,00100100'
   Controls : 15
   Simple ctrls : 10
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xddefc000 irq 17'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100200'
   Controls : 16
   Simple ctrls : 4
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=36180a3f-7e23-0aef-edb8-a90176900ecd
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: SAMSUNG ELECTRONICS CO., LTD. RV411/RV511/E3511/S3511
NonfreeKernelModules: nvidia wl
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae root=UUID=ad954864-2a64-4185-9262-b45aa1ef5427 ro quiet acpi_backlight=vendor acpi_osi=Linux acpi_brightness=vendor splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.21~ppa4~loms~oneiric-generic-pae 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic-pae N/A
 linux-backports-modules-3.0.0-12-generic-pae N/A
 linux-firmware 1.60
StagingDrivers: brcmutil mei brcmsmac
Tags: oneiric staging
Uname: Linux 3.0.0-12-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/07/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02PA.M003.20110107.XW
dmi.board.asset.tag: Tag 12345
dmi.board.name: RV411/RV511/E3511/S3511
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr02PA.M003.20110107.XW:bd01/07/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnRV411/RV511/E3511/S3511:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRV411/RV511/E3511/S3511:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: RV411/RV511/E3511/S3511
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 886820

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Ivan Stetsenko (stetzen)]

apport information

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Andrea Gottardo (gozzi)]

I can confirm this bug is also present using Ubuntu and Kubuntu 11.10 with a Samsung RV520 laptop. It seems like the brightness of the LCD panel is changed using the graphic card, an Nvidia card in this case.

This driver allowed me to solve the problem:

https://github.com/guillaumezin/nvidiabl

It would be great if it could be integrated inside Ubuntu, without having to install it apart.

Thanks,
Andrea

[carasin (carasin-redhat-bugs)]

Description of problem:

There is a laptop Samsung RV520 with installed Fedora 16. Some hotkeys (Fn + <key>) don't work, e.g. [Fn + Up/Down] (backlight brightness control), [Fn + F5] (display backlight off/on), [Fn + F9] (wireless devices on/off). At the same time, hotkeys [Fn + Esc] (suspend), [Fn + Right/Left] (volume level up/down) and [Fn + F6] (volume off/on) work fine.
<lsmod> shows that <samsung-laptop> module isn't loaded. Attempt to load this module fails with error "No such device".
When I press [Fn + Up/Down], the contents of the files (<actual_brightness>, <brightness>) at the path </sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/backlight/acpi_video0/> change. But actually brightness level doesn't change.
___________________________________

Version-Release number of selected component (if applicable):

kernel-3.1.0-7.fc16.i686 / kernel-3.2.6-3.fc16.i686, udev-173-3.fc16.i686
___________________________________

How reproducible:
always
___________________________________

Steps to Reproduce:
1. Press [Fn + Up/Down/F9] (Samsung RV520, Fedora 16)
2. Backlight level doesn't change, wireless devices don't switch
___________________________________

Actual results:
Some [Fn + <key>] hotkeys don't work.
___________________________________

Expected results:
All [Fn + <key>] hotkeys (e.g. brightness control and wireless devices on/off) work fine.

Additional info:
<dmidecode -s system-product-name> command returns <RV420/RV520/RV720/E3530/S3530/E3420/E3520>.
The passing the <acpi_backlight=vendor> argument to the kernel doesn't help.
This trouble appears also in the Live-CD mode.

[carasin (carasin-redhat-bugs)]

I've tried to change the display brightness level with the <setpci> command, but this attempt has failed:

$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Device 1050 (rev a1)
$ sudo setpci -s 01:00.0 F4.B
00
$ sudo setpci -s 01:00.0 F4.B=50
$ sudo setpci -s 01:00.0 F4.B
00

[Josh (josh-redhat-bugs)]

Theoretically, the patches for this are here:

http://thread.gmane.org/gmane.linux.drivers.platform.x86.devel/2700/focus=2701

and queued up in the platform maintainer's git tree somewhere. The don't seem to have made the 3.3 kernel though.

[carasin (carasin-redhat-bugs)]

As far as I'm concerned, the necessary changes at the <samsung-laptop> driver will be in the kernel 3.4 or, if lucky, in 3.3. Right?

[carasin (carasin-redhat-bugs)]

I've took a workaround, which made brightness control to work:
I've put this code to the <samsung-laptop.c>
___________________________________
{
 .ident = "RV420/RV520/RV720/E3530/S3530/E3420/E3520",
 .matches = {
  DMI_MATCH(DMI_SYS_VENDOR,
    "SAMSUNG ELECTRONICS CO., LTD."),
  DMI_MATCH(DMI_PRODUCT_NAME, "RV420/RV520/RV720/E3530/S3530/E3420/E3520"),
  DMI_MATCH(DMI_BOARD_NAME, "RV420/RV520/RV720/E3530/S3530/E3420/E3520"),
 },
 .callback = dmi_check_cb,
},
___________________________________
and compiled the module with this Makefile:
___________________________________
obj-m := samsung-laptop.o

KERNELDIR ?= /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)

all:
 $(MAKE) -C $(KERNELDIR) M=$(PWD)

clean:
 rm -f *.o *~ core .depend .*.cmd *.ko *.mod.c
 rm -f Module.markers Module.symvers modules.order
 rm -rf .tmp_versions Modules.symvers
___________________________________
Then I've put <samsung-laptop.ko> to the </lib/modules/$(uname -r)/kernel/drivers/platform/x86/> directory and run <# depmod -a>.

Now the brightness level is adjustable.

[muzzol (muzzol)]

my toshiba satellite l735 is also affected by this bug.

i can't modify brightness and having always full brigth affects battery life.

[Dave (dave-redhat-bugs)]

[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

[Swâmi Petaramesh (swami-petaramesh)]

Cannot modify screen brightness on Toshiba Satellite L735-101 either. [Fn]-[Brightness] keys have absolutely no action.

Bug present in Ubuntu Precise Beta, Ubuntu Oneiric, Mint 12, Bodhi 1.3.

[carasin (carasin-redhat-bugs)]

When the new kernel-3.3.0-4 had appeared at the Fedora repository, the first thing I've done was testing the samsung-laptop kernel module on my Samsung RV-520.
The result is the same. This module isn't automaticaly loadable.
The work around is a rebuilding this module with the same instruction as before.

[carasin (carasin-redhat-bugs)]

* This module isn't loadable at all.

[Andrea Gottardo (gozzi)]

The bug is also present in Fedora 16.

I think we should change the name of this bug, as it doesn't seem to exist only on Samsung laptops...

[penalvch (penalvch)]

Ivan Stetsenko, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please attach the results following https://wiki.ubuntu.com/Kernel/Debugging/Backlight ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[Josh (josh-redhat-bugs)]

The patches I mentioned in comment #2 should go into the 3.4 kernel. That won't be immediately available in F17.

[carasin (carasin-redhat-bugs)]

I've exactly understood this.
Thanks.

[carasin (carasin-redhat-bugs)]

Well! Kernel 3.4 has been built for Fedora 17 here: http://koji.fedoraproject.org/koji/buildinfo?buildID=321678
I've installed it and now the <samsung-laptop> kernel module is loadable.

But the new trouble has appeared: when I try to change the brightness level, the maximum brightness limit becomes very low (~30%). Then, when I press <Fn + Up> (brightness up) further, a backlight is blinking for a short time, but the brightness level doesn't change. <Fn + Down> (brightness down) works well.

If I unplug the supply cable and then plug it back, the brightness level becomes maximum (100%). But after decreasing the brightness level the problem with <Fn + Up> repeats again.

[carasin (carasin-redhat-bugs)]

Addition:
now I use F17.

[carasin (carasin-redhat-bugs)]

# cat /sys/devices/platform/samsung/backlight/samsung/max_brightness
8

# echo 8 > /sys/devices/platform/samsung/backlight/samsung/actual_brightness
-bash: /sys/devices/platform/samsung/backlight/samsung/actual_brightness: Permission denied

But the backlight is blinking for a short time, if I execute this:
# echo 8 > /sys/devices/platform/samsung/backlight/samsung/brightness

[carasin (carasin-redhat-bugs)]

Created attachment 589037
the working <samsung-laptop> source

If I build the <samsung-laptop> (with the attached <samsung-laptop.c> and <Makefile>),
put the <samsung-laptop.ko> into </usr/lib/modules/3.4.0-1.fc17.i686.PAE/updates/>,
type <# modprobe -r samsung_laptop> / <# depmod -a> / <# modprobe samsung-laptop>

the brightness level becomes fully adjustable.

[carasin (carasin-redhat-bugs)]

Created attachment 589038
<Makefile> for building the working <samsung-laptop> kernel module

See a previous comment (attachment).

[carasin (carasin-redhat-bugs)]

I've updated kernel up to 3.4.1 from here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=321994

The situation is the same: after the brightness level decreasing it's not possible to increase it back higher some limited level. That's some console output (after <Fn + Down> to min and <Fn + Up> to max):

> $ cat /sys/devices/platform/samsung/backlight/samsung/actual_brightness
> 2
> $ cat /sys/devices/platform/samsung/backlight/samsung/brightness
> 8
> $ cat /sys/devices/platform/samsung/backlight/samsung/max_brightness
> 8

[carasin (carasin-redhat-bugs)]

<kernel-3.5.0-1.fc17.i686.PAE>: the situation is the same.

I've additionally reported this bug to upstream.
https://bugzilla.kernel.org/show_bug.cgi?id=45311

[Olivier LAPORTE (olivier-laporte1)]

Bug present on a toshiba satellite l655 under kubuntu 12.04 using kernel 3.2.0-25.

Same problem but I can change the screen brigthness using "xrandr --output LVDS --brightness" command.

[penalvch (penalvch)]

Olivier LAPORTE, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Josh (josh-redhat-bugs)]

(In reply to comment #15)
> Created attachment 589037 [details]
> the working <samsung-laptop> source
>

I'm confused as to what this is exactly. Where did it come from? Instead of attaching a full .c file, can you create a unified diff and send that to the driver maintainer for review with <email address hidden> on CC?

[Dave (dave-redhat-bugs)]

# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem.
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

[carasin (carasin-redhat-bugs)]

(In reply to comment #19)
> (In reply to comment #15)
> > Created attachment 589037 [details]
> > the working <samsung-laptop> source
> >
>
> I'm confused as to what this is exactly. Where did it come from?

When the <kernel> version was 3.3 it had no support for my laptop. And I has followed this instruction: http://linuxtweaking.blogspot.com/2011/11/enabling-samsung-laptop-backlight.html
So I had a working <samsung-laptop> module. I don't know what is this module version.

> Instead of attaching a full .c file, can you create a unified diff and send
> that to the driver maintainer for review with <email address hidden> on CC?

Then the <samsung-laptop> module has been modified enough at the 3.4 <kernel> version, in particular, the mechanism for determining the hardware. Now there is no need to modify the <samsung-laptop.c> with DMI output for each notebook model. So diff is useless.

The bug is in that it's impossible to increase the brightness level with native kernel <samsung-laptop> driver. I can not fix it myself, because I don't know programming languages and can not find a suitable manual for fixing it in the <samsung-laptop> module from kernel >= 3.4.

[carasin (carasin-redhat-bugs)]

UPD: Now I already use F18.

[Fedora (fedora-redhat-bugs)]

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Fedora (fedora-redhat-bugs)]

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

[penalvch (penalvch)]

OR using EOL release, and no response for years.