Changing display resolution leads into black screen

Bug #2042867 reported by Aleix
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Unknown
linux (Ubuntu)
Confirmed
Undecided
Unassigned
linux-oem-6.5 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Since updating into 23.10, when I change my build-in display from 2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen black and unable to use.

The only resolution that works is the predefined one.

This bug wasn't present on the previous release, 23.04.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 6 19:37:48 2023
InstallationDate: Installed on 2023-05-05 (185 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-10-generic N/A
 linux-backports-modules-6.5.0-10-generic N/A
 linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago)
dmi.bios.date: 04/18/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UM5401QAB_UM5401QA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UM5401QAB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UM5401QAB_UM5401QA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Aleix (aleixduck) wrote :
Revision history for this message
Aleix (aleixduck) wrote :

Changing the resolution on the external screen works fine. The problem is with the build-in display.

Revision history for this message
Mario Limonciello (superm1) wrote (last edit ):

This issue is fixed in 6.6-rc3: 2de19022c5d7 ("drm/amd/display: fix the ability to use lower resolution modes on eDP")

It's backported to stable 6.5.6 as 79aec38ba852 ("drm/amd/display: fix the ability to use lower resolution modes on eDP").

Canonical needs to pull the fix into their kernel.

Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux-oem-6.5 (Ubuntu):
status: New → Confirmed
Changed in linux:
status: Unknown → Fix Released
Revision history for this message
Juerg Haefliger (juergh) wrote :

It will show up as part of one of our upcoming stable updates.

Revision history for this message
zomp (jan-molnar) wrote (last edit ):

Is the release expected soon please? (The bug does not affect only those who proactively modified resolution and so know what got wrong, but also those who had it modified and upgraded from Lunar to Mantic – these people have no clue what the issue is. I almost left Ubuntu because the blank screen was not something I could live with and I could not find a solution. Early release might help other people. Edit: No intent to push on you, just trying to bring some motivation. :-D Thanks for your hard work.)

Revision history for this message
Aleix (aleixduck) wrote :

I installed manually 6.5.7 and the issue has been resolved. The bug was so frustrating

Revision history for this message
AaronMa (mapengyu) wrote :
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.