Lenovo Legion 7: Cannot Control Display Brightness

Bug #1995173 reported by Yosua Liu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The device is Lenovo Legion 7. This laptop has a mux switch to switch between dynamic/hybrid or discrete graphics mode. This laptop has a high resolution with high pixel density than the other displays out there, but I don't know the exact number. Additionally, this laptop can adjust the display refresh rate between 60 and 165 Hz.

---

There were 1 problem I encountered in dynamic/hybrid graphics mode:

- The widgets shown were too small.

Details:

The resolution was correct, at 2560x1600, but all widgets shown were too small. I suspected this was due to the laptop screen high pixel density and the widget size calculation didn't make use of physical dimension, but in terms of pixel.

I thought installing NVIDIA driver would fix this, but no; this worked in OpenSUSE Leap with KDE Plasma and I think it was because of the inclusion of NVIDIA OpenGL driver.

The current workaround was to scale by 200% in "Display Settings", although the login screen isn't affected by the scaling at all.

---

There were 3 problems I encountered in discrete graphics mode:

- The widgets were are too small, like the hybrid graphics mode issue.
- The DE seemed to use wrong screen refresh rate.

The refresh rate was fixed at 93 Hz in the "Display Settings".

Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't update the 93 Hz in the "Display Settings".

This didn't happen in the hybrid graphics mode.

OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I think it may be either GNOME DE or xorg misconfigurations.

- Screen brightness was fixed at 100%.

Details:

Screen brightness could be adjusted by the keyboard Fn keys, but the brightness was fixed at 100%.

This didn't happen in the hybrid graphics mode.

This is the most annoying problem and have forced me to use the hybrid graphics mode which I don't like.

My first thought was either a specific NVIDIA issue or xorg misconfigurations.

So I tried adding "acpi_backlight=vendor" and "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but didn't work at all.

---

In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed below:

Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading X.509 certificate -65
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above except that there was no:

Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.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 Open Kernel Module for x86_64 520.56.06 Release Build (dvs-builder@U16-T12-10-2) Thu Oct 6 21:33:54 UTC 2022
 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 29 18:50:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/520.56.06, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3aa6]
InstallationDate: Installed on 2022-10-29 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
MachineType: LENOVO 82N6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=755b225e-e7d8-439f-a685-8ab759683ed6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/16/2022
dmi.bios.release: 1.57
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN57WW
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 7 16ACHg6
dmi.ec.firmware.release: 1.57
dmi.modalias: dmi:bvnLENOVO:bvrGKCN57WW:bd06/16/2022:br1.57:efr1.57:svnLENOVO:pn82N6:pvrLegion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO
nvidia-settings: ERROR: A supplied argument is invalid
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
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:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Yosua Liu (jiazhang) wrote :
summary: - Display Issues : Cannot Control Display Brightness, High Pixel Density
- Issue, and Resolution Issue
+ Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High
+ Pixel Density Issue, and Resolution Issue
Yosua Liu (jiazhang)
description: updated
Yosua Liu (jiazhang)
description: updated
affects: xorg (Ubuntu) → nvidia-graphics-drivers-520 (Ubuntu)
Revision history for this message
Yosua Liu (jiazhang) wrote : Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

The latest Ubuntu update fully fixed the refresh rate and partially fixed the brightness issue in the discrete graphics mode. This is a critical improvement.

Now, I can choose the 60Hz and 165Hz screen refresh rate from the DE settings.

The brightness issue is partially fixed because when the brightness level indicator is at about 0%, 5%, and 10 %, the actual screen brightness is at about 50%, 75%, and 100%. So the brightness level indicator at 100-20% maps to the actual brightness 100-20%, but the brightness level indicator at 10-0% seems to map to the actual screen brightness of 100%, 75%, and 50%.

I believe the small widgets issue can just be resolved by the DE feature of 2x scaling.

So, the brightness issue is the last problem to be fixed in this bug issue.

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

Thanks for the bug report, but please ensure you only report one issue per bug in future.

summary: - Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High
- Pixel Density Issue, and Resolution Issue
+ Lenovo Legion 7 Display Issues : Cannot Control Display Brightness
affects: nvidia-graphics-drivers-520 (Ubuntu) → linux (Ubuntu)
summary: - Lenovo Legion 7 Display Issues : Cannot Control Display Brightness
+ Lenovo Legion 7: Cannot Control Display Brightness
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Yosua Liu (jiazhang) wrote :

Noted, I will report 1 issue per 1 bug report in the future.

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.