Launchpad has imported 33 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=66501.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-12-04T15:49:28+00:00 gmillet3 wrote: Created attachment 117421 dmesg The screen brightness control has apparently never worked off-the-shelf on this laptop released in 2009, Asus UL80VT-A1, which is an NVIDIA Optimus laptop (2 graphic cards). The use of the discrete Nvidia card is managed by Bumblebee (https://wiki.ubuntu.com/Bumblebee). It used to work with the workaround suggested at http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Screen_Brightness which modifies asus-brn-down.sh to use the "setpci" method. When the hotkeys are triggered, there is no brightness change but the KDE popup notification appears. $ ls /sys/class/backlight/ acpi_video0 acpi_video1 intel_backlight $ cat /sys/class/backlight/intel_backlight/max_brightness 2583660 $ cat /sys/class/backlight/intel_backlight/brightness 121584 The intel_backlight interface works, by echoing a value between 0 and 2583660. $ cat /sys/class/backlight/acpi_video0/brightness 6 $ cat /sys/class/backlight/acpi_video0/max_brightness 15 $ cat /sys/class/backlight/acpi_video0/device/device 0x2a42 $ cat /sys/class/backlight/acpi_video1/brightness 15 $ cat /sys/class/backlight/acpi_video1/max_brightness 15 $ cat /sys/class/backlight/acpi_video1/device/device 0x0a74 By echoing a value between 0 and 15, the two acpi_video interfaces do not change the screen brightness. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/71 ------------------------------------------------------------------------ On 2013-12-04T15:50:14+00:00 gmillet3 wrote: Created attachment 117431 acpidump Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/72 ------------------------------------------------------------------------ On 2013-12-04T15:51:35+00:00 gmillet3 wrote: Created attachment 117441 dmidecode Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/73 ------------------------------------------------------------------------ On 2013-12-04T15:53:04+00:00 gmillet3 wrote: Created attachment 117451 Xorg.0.log $ cat /etc/X11/xorg.conf Section "Screen" Identifier "Default Screen" DefaultDepth 24 EndSection Section "Device" Identifier "Default Device" EndSection Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/74 ------------------------------------------------------------------------ On 2013-12-04T15:55:31+00:00 gmillet3 wrote: Previous thread on linux-acpi http://marc.info/?t=138600362800003&r=1&w=2 Launchpad downstream bug report on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/75 ------------------------------------------------------------------------ On 2013-12-05T02:34:42+00:00 aaron.lu wrote: I saw the kernel you used is a distro kernel v3.11, is it the same case with v3.12? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/76 ------------------------------------------------------------------------ On 2013-12-07T11:43:33+00:00 gmillet3 wrote: Same problem with 3.12.0-031200-generic from http://kernel.ubuntu.com /~kernel-ppa/mainline/v3.12-saucy/. I can attach dmesg and Xorg.0.log, they seem similar. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/77 ------------------------------------------------------------------------ On 2013-12-09T08:57:42+00:00 aaron.lu wrote: Does adding acpi_osi="Linux" to kernel cmdline make any difference? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/78 ------------------------------------------------------------------------ On 2013-12-13T15:06:43+00:00 gmillet3 wrote: No difference. The hotkeys change the value in /sys/class/backlight/acpi_video0/brightness but the brightness doesn't change. I attach dmesg and Xorg.0.log with 3.12.0-031200-generic and acpi_osi="Linux" in case it would be useful. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/79 ------------------------------------------------------------------------ On 2013-12-13T15:07:51+00:00 gmillet3 wrote: Created attachment 118291 dmesg with acpi_osi=Linux and kernel 3.12 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/80 ------------------------------------------------------------------------ On 2013-12-13T15:08:16+00:00 gmillet3 wrote: Created attachment 118301 Xorg.0.log with acpi_osi=Linux and kernel 3.12 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/81 ------------------------------------------------------------------------ On 2013-12-16T02:19:39+00:00 aaron.lu wrote: I've no idea why ACPI brightness control method doesn't work. Please add acpi_backlight=vendor to kernel cmdline, see if there is only one interface(intel_backlight) left under /sys/class/backlight. If so, I can add your system into a blacklist table. BTW, is there a firmware update for your laptop from ASUS? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/82 ------------------------------------------------------------------------ On 2013-12-16T13:24:25+00:00 gmillet3 wrote: With acpi_backlight=vendor, there are two interfaces: asus_laptop and intel_backlight. asus_laptop reacts like acpi_video0 did when a brightness hotkey is pressed: the value of /sys/class/backlight/asus_laptop/brightness chnages but the brightness doesn't. The BIOS is already at the last version released by ASUS on https://www.asus.com/Notebooks_Ultrabooks/UL80Vt/#support, version 214. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/83 ------------------------------------------------------------------------ On 2014-01-02T01:43:40+00:00 aaron.lu wrote: Created attachment 120561 Debug patch to use native backlight for a Win7 system Sorry for replying late. Can you please test this patch on top of a v3.13 kernel? Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/85 ------------------------------------------------------------------------ On 2014-01-13T15:41:10+00:00 gmillet3 wrote: Thanks. Patch tested on kernel 3.13.0-rc8 for Saucy: $ modinfo video filename: /lib/modules/3.13.0-031300rc8-generic/kernel/drivers/acpi/video.ko license: GPL description: ACPI Video Driver author: Bruno Ducrot srcversion: 7F3F9A0CC7554649507A11E alias: acpi*:LNXVIDEO:* depends: vermagic: 3.13.0-031300rc8-generic SMP mod_unload modversions parm: brightness_switch_enabled:bool parm: allow_duplicates:bool parm: use_native_backlight:bool It doesn't seem to work and there is still a ACPI_video0 interface. $ dmesg | grep video [ 0.253443] pci 0000:00:02.0: Boot video device [ 1.380146] Modules linked in: ahci(+) libahci atl1c i915(+) i2c_algo_bit drm_kms_helper video drm [ 16.952911] asus_laptop: Backlight controlled by ACPI video driver What other debug information can I provide? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/86 ------------------------------------------------------------------------ On 2014-01-14T03:11:09+00:00 aaron.lu wrote: Oh, that probably because I didn't fill in the DMI entry correctly. Can you please check the value of use_native_backlight? It's located at: /sys/module/video/parameters/use_native_backlight And if it is N, please add video.use_native_backlight=1 to the patched kernel's cmdline and test again. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/87 ------------------------------------------------------------------------ On 2014-01-15T10:39:36+00:00 gmillet3 wrote: It was N. With the additional parameter, the acpi interface is still created: $ dmesg | grep -i backlight [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.13.0-031300rc8-generic root=UUID=d92f3a31-9e9c-4c19-98be-6fbc82629a36 ro quiet splash video.use_native_backlight=1 vt.handoff=7 [ 18.806833] asus_laptop: Backlight controlled by ACPI video driver $ cat /sys/module/video/parameters/use_native_backlight Y Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/88 ------------------------------------------------------------------------ On 2014-01-20T08:46:31+00:00 aaron.lu wrote: Created attachment 122671 Debug patch to use native backlight for a Win7 system, v2 Please test this patch on top of a v3.13 kernel, attach the dmesg after boot up, thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/89 ------------------------------------------------------------------------ On 2014-01-24T10:00:43+00:00 gmillet3 wrote: Created attachment 123271 dmesg with patch v2 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/90 ------------------------------------------------------------------------ On 2014-01-24T10:05:40+00:00 gmillet3 wrote: With the kernel option, dmesg is similar and it doesn't work. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/91 ------------------------------------------------------------------------ On 2014-01-26T01:15:54+00:00 aaron.lu wrote: Did you apply the patch? I saw your kernel cmdline has: BOOT_IMAGE=/boot/vmlinuz-3.13.0-031300-generic, is the image the patched one? I've added a print in the video module's init function and it has to be printed but I didn't see it in the attached dmesg, so I'm confused. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/92 ------------------------------------------------------------------------ On 2014-02-03T22:01:03+00:00 gmillet3 wrote: Sorry for the late reply, I was trying to understand why the modifications did not change anything whereas I changed video.ko. Could it be about the built-in property of the module, that is, can't I compile only video.ko as described in http://www.cyberciti.biz/tips /build-linux-kernel-module-against-installed-kernel-source-tree.html ? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/93 ------------------------------------------------------------------------ On 2014-02-07T06:21:07+00:00 aaron.lu wrote: If video.ko is built in, then I don't think you can rmmod video and then modprobe it... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/94 ------------------------------------------------------------------------ On 2014-02-12T01:06:26+00:00 gmillet3 wrote: Well, I'm lost. After adding some printk without any change, I deleted the module video.ko just to check if it is used... no change, the system works the same. On the other end, the kernel package installed video.ko and CONFIG_ACPI_VIDEO=m is present in /boot/config-3.13.0-031300-generic, doesn't it mean that video is a loadable module? Moreover, lsmod displays an entry video: video 19859 1 i915 whereas $ modprobe video FATAL: Module video not found. Where does that video module listed by lsmod comes from? Could the problem be related to the bug in drm module which logs a trace in dmesg, starting with [drm:intel_pipe_config_compare] *ERROR* mismatch in gmch_pfit.lvds_border_bits (expected 32768, found 0)? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/95 ------------------------------------------------------------------------ On 2014-02-12T02:13:33+00:00 aaron.lu wrote: (In reply to Guillaume Millet from comment #23) > Well, I'm lost. After adding some printk without any change, I deleted the > module video.ko just to check if it is used... no change, the system works > the same. On the other end, the kernel package installed video.ko and > CONFIG_ACPI_VIDEO=m is present in /boot/config-3.13.0-031300-generic, > doesn't it mean that video is a loadable module? > > Moreover, lsmod displays an entry video: > video 19859 1 i915 > whereas $ modprobe video > FATAL: Module video not found. > > Where does that video module listed by lsmod comes from? Maybe from initrd. > > Could the problem be related to the bug in drm module which logs a trace in > dmesg, starting with [drm:intel_pipe_config_compare] *ERROR* mismatch in > gmch_pfit.lvds_border_bits (expected 32768, found 0)? Not sure about the drm driver. Could you just build the entire kernel tree instead of only the video module? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/96 ------------------------------------------------------------------------ On 2014-02-16T10:38:25+00:00 gmillet3 wrote: Created attachment 126321 dmesg with patch v2 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/97 ------------------------------------------------------------------------ On 2014-02-16T10:48:13+00:00 gmillet3 wrote: It took me some time as I didn't have 11 GB free to build the entire kernel tree... Anyway, the patch works and the dmesg is attached. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/98 ------------------------------------------------------------------------ On 2014-02-17T03:16:24+00:00 aaron.lu wrote: OK, thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/99 ------------------------------------------------------------------------ On 2014-02-17T05:40:38+00:00 aaron.lu wrote: I think this should be solved the same way we did for Win8 systems though this laptop's firmware doesn't claim Win8 support but Matthew doesn't agree. The ACPI video control interface is broken and the reason is beyond me, so I'll re-assign this bug to Drivers/Platform-x86 for more analysis. Guillaume, You can continue to use the xorg.conf to select intel_backlight for your laptop. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/100 ------------------------------------------------------------------------ On 2017-04-14T13:55:28+00:00 gmillet3 wrote: Hi Aaron, I continue to use the xorg.conf as suggested. I wondered whether the issue could have been solved without update of this thread, so I have tried kernel 4.10.10-041010-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline without the xorg.conf, but the issue is still present as initially described. I suppose that this thread or the bug status will change is something happened. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/101 ------------------------------------------------------------------------ On 2017-05-27T02:12:26+00:00 aaron.lu wrote: There is a new quick mechanism in kernel now. Can you try adding acpi_backlight=native to kernel cmdline? With this cmdline option, you should have only one interface under /sys/class/backlight that is intel_backlight and xorg.conf modification isn't necessary. If everything works, I can add your machine to a quirk table for this to happen automatically so that you do not need to add that cmdline option. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/102 ------------------------------------------------------------------------ On 2017-08-27T15:13:04+00:00 gmillet3 wrote: Hi Aaron, I have just tried the native module option on 4.4.0-92 generic Ubuntu kernel (10-Aug-2017), after removing the xorg.conf modification, and it works. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/103 ------------------------------------------------------------------------ On 2019-08-03T19:23:57+00:00 gmillet3 wrote: Hi Aaron, I have just installed Debian Buster, kernel 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u1. Without the cmdline option, the backlight control does not work. Has UL80VT been added to the quirk table you mentioned? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178796/comments/104 ** Changed in: linux Status: Unknown => Incomplete ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1178796 Title: 8086:2a42 [Asus UL80VT] Backlight control does not work with Intel integrated card, but there are entries in /sys/class/backlight Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Bug description: It used to work with the workaround suggested at http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Screen_Brightness which modifies asus-brn-down.sh to use the "setpci" method. But I had forgotten that workaround and I suspect that upgrading to Raring removed my modified scripts. So, in the original description of the bug, I thought it was a regression. But it's probably not a regression as the brightness control has apparently never worked off- the-shelf. Not working neither with linux- image-3.9.1-030901-generic_3.9.1-030901.201305080210 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9.1-saucy/ Hotkeys are detected, showkey -s: Fn+F5: 0xe0 0x4c 0xe0 0xcc Fn+F6: 0xe0 0x54 0xe0 0xd4 I also attach the results from tests described on https://wiki.ubuntu.com/Kernel/Debugging/Backlight. Test with acpi_backlight=vendor: - on 3.8.0-20.31-generic, no change. But echo 8 > /sys/class/backlight/intel_backlight/brightness makes the screen dark, moreover /sys/class/backlight/intel_backlight/max_brightness = 2583660 - on 3.9.1, no brightness change but the KDE notification pops up with only 3 levels (0, 53, 100%) Test with video.use_bios_initial_backlight=0: - on 3.8.0-20.31-generic, no change. WORKAROUND: specify the backlight option in xorg.conf. Section "Device" Identifier "Default Device" Option "Backlight" "intel_backlight" Driver "intel" BusID "PCI:0:2:0" EndSection WORKAROUND: On KDE Raring Ubuntu 3.8.0-30.44-generic, bumblebee removed, BIOS SATA mode set to Compatible (this disables the Intel graphics card which does not appear anymore in lspci, http://wiki.daviddarts.com/Ubuntu_Maverick_on_the_Asus_UL30VT#Nvidia_Accelerated_Graphics_Driver), only default kernel parameters, and using either nouveau or nvidia drivers: The plasma widget for screen brightness (inside battery monitor widget) is able to change the brightness. And automatic brightness change from KDE system (when the power adaptor is unplugged) works also. In Raring, the hotkeys do not trigger any change (see bug #1225067) but this is fixed in Saucy. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-20-generic 3.8.0-20.31 ProcVersionSignature: Ubuntu 3.8.0-20.31-generic 3.8.11 Uname: Linux 3.8.0-20-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: guillaume 2490 F.... pulseaudio /dev/snd/controlC0: guillaume 2490 F.... pulseaudio Date: Fri May 10 12:14:58 2013 HibernationDevice: RESUME=/dev/sda6 InstallationDate: Installed on 2010-01-19 (1207 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: ASUSTeK Computer Inc. UL80VT MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-20-generic root=UUID=d92f3a31-9e9c-4c19-98be-6fbc82629a36 ro video.use_bios_initial_backlight=0 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-20-generic N/A linux-backports-modules-3.8.0-20-generic N/A linux-firmware 1.106 SourcePackage: linux UpgradeStatus: Upgraded to raring on 2013-04-27 (12 days ago) dmi.bios.date: 01/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL80VT dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr214:bd01/17/2011:svnASUSTeKComputerInc.:pnUL80VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL80VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL80VT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2788 F.... pulseaudio /dev/snd/controlC0: ubuntu 2788 F.... pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130813) MachineType: ASUSTeK Computer Inc. UL80VT MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash acpi_backlight=vendor -- ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 RelatedPackageVersions: linux-restricted-modules-3.11.0-1-generic N/A linux-backports-modules-3.11.0-1-generic N/A linux-firmware 1.113 Tags: saucy Uname: Linux 3.11.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UL80VT dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr214:bd01/17/2011:svnASUSTeKComputerInc.:pnUL80VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL80VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UL80VT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1178796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
