Changing screen brightness fails

Bug #1874716 reported by Lisa Nelson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Lenovo Legion with Nvidia card:

FN+F5/F6 shows brightness changes, but the screen actually doesn't change at all.

01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)

nvidia 20430848 538 nvidia_uvm,nvidia_modeset
nvidia_drm 45056 8
nvidia_modeset 1114112 12 nvidia_drm
nvidia_uvm 966656 0
nvme 49152 2
nvme_core 102400 4 nvme

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020
 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 06:23:22 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3ffb]
InstallationDate: Installed on 2020-03-12 (42 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306)
MachineType: LENOVO 81T2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: BHCN35WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Y545 PG0
dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:
dmi.product.family: Legion Y545 PG0
dmi.product.name: 81T2
dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
dmi.product.version: Legion Y545 PG0
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Lisa Nelson (lisa50469) wrote :
Revision history for this message
Lisa Nelson (lisa50469) wrote :

Also: the slider in settings does not change the brightness either.

affects: ubuntu → xorg (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Could you add your 'journalctl -b 0' log after getting the issue? Could also try if disabling the nvidia driver and using nouveau makes a difference?

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Lisa Nelson (lisa50469) wrote :

Attaching Journalctl log

Revision history for this message
Lisa Nelson (lisa50469) wrote :
Download full text (5.4 KiB)

Monitoring syslog I see the following when I try to change screen brightness:

root@lisa-Legion-Y545-PG0:~# tail -f /var/log/syslog
Apr 27 10:46:55 lisa-Legion-Y545-PG0 kernel: [ 142.184842] nvme 0000:06:00.0: AER: device [15b7:5006] error status/mask=00000001/0000e000
Apr 27 10:46:55 lisa-Legion-Y545-PG0 kernel: [ 142.184846] nvme 0000:06:00.0: AER: [ 0] RxErr
Apr 27 10:47:00 lisa-Legion-Y545-PG0 kernel: [ 147.048707] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:06:00.0
Apr 27 10:47:00 lisa-Legion-Y545-PG0 kernel: [ 147.048718] nvme 0000:06:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 27 10:47:00 lisa-Legion-Y545-PG0 kernel: [ 147.048725] nvme 0000:06:00.0: AER: device [15b7:5006] error status/mask=00000001/0000e000
Apr 27 10:47:00 lisa-Legion-Y545-PG0 kernel: [ 147.048731] nvme 0000:06:00.0: AER: [ 0] RxErr
Apr 27 10:47:20 lisa-Legion-Y545-PG0 kernel: [ 167.054672] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:06:00.0
Apr 27 10:47:20 lisa-Legion-Y545-PG0 kernel: [ 167.054687] nvme 0000:06:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 27 10:47:20 lisa-Legion-Y545-PG0 kernel: [ 167.054696] nvme 0000:06:00.0: AER: device [15b7:5006] error status/mask=00000001/0000e000
Apr 27 10:47:20 lisa-Legion-Y545-PG0 kernel: [ 167.054701] nvme 0000:06:00.0: AER: [ 0] RxErr
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Apr 27 10:47:28 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

Apr 27 10:48:01 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Apr 27 10:48:01 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Apr 27 10:48:01 lisa-Legion-Y545-PG0 gnome-shell[2043]: Window manager warning: Ov...

Read more...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I think this is close enough to bug 1861532 that we should use that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.