Black screen on 6.5

[zomp]

Hello, the screen stays black under many resolutions on Ryzen on kernel 6.5. It worked well up until the update (from 6.2). It seems to be a known regression already fixed in upstream. Could you also apply the patch https://www.spinics.net/lists/stable/msg679132.html? Thank you.

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: KDE
Date: Tue Nov 14 22:48:59 2023
InstallationDate: Installed on 2023-08-07 (99 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
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 (12 days ago)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.35
dmi.bios.vendor: LENOVO
dmi.bios.version: R22ET65W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CNS17C00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.27
dmi.modalias: dmi:bvnLENOVO:bvrR22ET65W(1.35):bd08/08/2023:br1.35:efr1.27:svnLENOVO:pn21CNS17C00:pvrThinkPadX13Gen3:rvnLENOVO:rn21CNS17C00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CN_BU_Think_FM_ThinkPadX13Gen3:
dmi.product.family: ThinkPad X13 Gen 3
dmi.product.name: 21CNS17C00
dmi.product.sku: LENOVO_MT_21CN_BU_Think_FM_ThinkPad X13 Gen 3
dmi.product.version: ThinkPad X13 Gen 3
dmi.sys.vendor: LENOVO

[zomp (jan-molnar)]

Huh, I have just noticed bug 2042867 which might even raise the true fix for the issue. I am sorry for the churn.