You are not logged in.
Hello,
I'm running Arch Linux on a system equipped with an AMD Radeon RX 6650 XT and AMD Ryzen 9 6900HS CPU, on an ASUS ROG Zephyrus G14 laptop. My issue is that the monitor resolution is incorrect and I've not been able to adjust it to its native resolution using the normal methods.
(kscreendoctor, xrandr or the kde GUI result in a black screen.)
Here's some information about my system:
OS & Kernel Version: Arch Linux, Kernel 6.4.3-arch1-2
CPU: AMD Ryzen 9 6900HS with Radeon Graphics (16 CPUs)
Architecture: x86_64
Graphics: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6650 XT / 6700S / 6800S] (Kernel driver in use: amdgpu)
Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (Kernel driver in use: amdgpu)EDID Information: EDID parsing shows an Identifier of "TL140ADXP01", VendorName "TMX", and no specific resolutions are listed in the parsed modelines. The VertRefresh rates are listed between 48-120 Hz and Horizsync is listed as 206-206.
Error messages: An error message in dmesg points to a potential issue with the amdgpu driver: dce110_edp_wait_for_hpd_ready+0x15a/0x190 [amdgpu]. However, it's unclear if this issue is directly related to the incorrect resolution.
I've tried updating the kernel, examining EDID data, but the issue persists. Parsing the EDID information did not provide any specific resolution details. I'm hesitant to make a custom EDID or use older kernel versions due to potential issues and long-term maintainability.
Recently, I ran a Fedora live session with the GNOME environment where the display was set to the wrong resolution originally just as well (2560x1600), but I could adjust it easily it within the gnome display settings, while on my kde arch session any changes to it result to only a black screen.
While testing this I realized that the erroneous resolution is listed in the bios as well.
The Fedora kernel version (6.2.9-300.fc38.x86_64), The Mesa versions: (23.0.1 on Fedora vs. 23.1.3 on Arch) - in case this helps.
The only other pointer I have is that I recently was trying to get a proton game running and installed amdvlk in addition to the recommended vulkan-radeon. Given that it did not resolve the issue at hand back then. I deinstalled it after a few minutes again.
Could anyone provide some guidance on how to further diagnose and resolve this issue? Any help would be greatly appreciated.
Last edited by Schopel (2023-07-18 21:12:13)
Offline
Please edit your post to use [ code ] [ / code ] tags for command outputs , see https://bbs.archlinux.org/help.php#bbcode .
Your system has 2 gpus, did you look at https://wiki.archlinux.org/title/PRIME ?
Are you running on X or on wayland ?
Please post full dmesg and/or journal from one boot.
Welcome to archlinux forums.
Last edited by Lone_Wolf (2023-07-17 11:39:29)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Please post full dmesg and/or journal from one boot.
Rather journal. And your xorg log.
sudo journalctl -b | curl -F 'f:1=<-' ix.ioOffline
Thank you, I will edit the post!
I have tried setting the mode through xrandr and kscreendoctor with prime (DRI_PRIME=1), but that sadly didn't change the situation.
I am running on wayland. This has been persisting for at least a week now, could be a bit more, given that I don't use the built in display too often.
cat /sys/class/drm/card1-eDP-2/modes only returns 2560x1600 (twice maybe 60hz + 120hz?)
Here is the journal:
This is a journal, from a later point, after having tried to change it within the system settings.
This is my xorg.log:
PS: I noticed that the resolution changes during booting or shut down when displaying the log to resemble a font size closer to how it should be originally.
uh: Maybe this helps too, when following the prime doc:
xrandr --listproviders
Providers: number : 0Last edited by Schopel (2023-07-17 16:45:58)
Offline
Jul 17 17:41:39 arch kwin_wayland[975]: No backend specified, automatically choosing drm
Jul 17 17:41:39 arch kwin_wayland[975]: OpenGL vendor string: AMDEvery X11 related information is moot, this is all xwayland.
The the behavior of plasma on X11
Offline
I tried my luck with creating a mode and setting the screen resolution manually with kscreen-doctor - same result. Wlr-randr does not support this setup. I am trying things blindly at this points, after a lot of fiddling, but I didn't mean to aggravate with this.
Offline
Try the behavior of plasma on X11
Offline
I have been on Wayland without a problem for months now. The last time I switched back was when fiddling with the bashrc and testing what variables to set in order to make as many applications run natively as possible.
Edit: It is not is not listing any other resolutions for that display on X11 then the erroneous one. Will try my luck with manual setting.
Last edited by Schopel (2023-07-18 20:18:08)
Offline
I created a mode under X11 for the original screen resolution and manually set the display to it. It went black again.
xorg.log after this:
http://ix.io/4AUx
journal after this:
http://ix.io/4AUz
Last edited by Schopel (2023-07-18 20:14:54)
Offline
Edit: didn't see your edit. Hang on.
edid-decode (hex):
00 ff ff ff ff ff ff 00 51 b8 81 14 00 00 00 00
1d 1f 01 04 a5 1e 13 78 07 0f 91 ae 52 43 b0 26
0f 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 c0 d8 00 a0 a0 40 64 60 2b 20
75 04 2d bc 10 00 00 18 60 6c 00 a0 a0 40 64 60
2b 20 75 04 2d bc 10 00 00 18 00 00 00 fd 00 30
78 ce ce 38 01 0a 20 20 20 20 20 20 00 00 00 fc
00 54 4c 31 34 30 41 44 58 50 30 31 0a 20 00 93
----------------
Block 0, Base EDID:
EDID Structure Version & Revision: 1.4
Vendor & Product Identification:
Manufacturer: TMX
Model: 5249
Made in: week 29 of 2021
Basic Display Parameters & Features:
Digital display
Bits per primary color channel: 8
DisplayPort interface
Maximum image size: 30 cm x 19 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4
Default (sRGB) color space is primary color space
First detailed timing includes the native pixel format and preferred refresh rate
Display is continuous frequency
Color Characteristics:
Red : 0.6796, 0.3203
Green: 0.2646, 0.6904
Blue : 0.1503, 0.0595
White: 0.3125, 0.3291
Established Timings I & II: none
Standard Timings: none
Detailed Timing Descriptors:
DTD 1: 2560x1600 120.000000 Hz 8:5 204.000 kHz 554.880000 MHz (301 mm x 188 mm)
Hfront 43 Hsync 32 Hback 85 Hpol N
Vfront 23 Vsync 5 Vback 72 Vpol N
DTD 2: 2560x1600 60.000000 Hz 8:5 102.000 kHz 277.440000 MHz (301 mm x 188 mm)
Hfront 43 Hsync 32 Hback 85 Hpol N
Vfront 23 Vsync 5 Vback 72 Vpol N
Display Range Limits:
Monitor ranges (Bare Limits): 48-120 Hz V, 206-206 kHz H, max dotclock 560 MHz
Display Product Name: 'TL140ADXP01'
Checksum: 0x93What modeline did you add/try?
Last edited by seth (2023-07-18 20:21:18)
Offline
I ran these:
ctv 1920 1200
xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync
xrandr --addmode eDP-1 1920x1200_60.00
xrandr --output eDP-1 --mode 1920x1200_60.00
Last edited by Schopel (2023-07-18 20:31:06)
Offline
The output doesn't advertise that resolution, https://bbs.archlinux.org/viewtopic.php … 8#p2109318
Offline
That sounds very similar ... given that it is a persistent annoyance at worst and I don't want to switch to the LTS kernel, I will wait till 6.5 then. It is reassuring to know that it is only a matter of time. Thank you for this, seth! You are doing the community an immeasurable service!
Offline