All non-default resolutions result in garbled primary display output

OpenBagTwo · 2023-07-21 15:20:26

I have a GPD Win4 that I'm using to run Arch and get my hands dirty learning the nitty-gritty of how to create a portable gaming focused distro.

Some background on the device:

It's powered by the 6800U "Rembrandt" APU from AMD
Relevantly, the graphics package is the RDNA-2 680M iGPU
The display is an extremely bespoke 1080x1920 6" panel which tweaked in the hardware to function, for all intents and purposes, as a native landscape (1920x1080) screen

It also has a built-in keyboard, which makes it a neat alternative to the Steam Deck, ROG Ally, etc., as it is perfectly usable for non-gaming purposes (I'm using it right now to type out this post) without needing to be docked.

While the panel looks gorgeous at FHD, its tiny size means that in a lot of cases, I'd prefer to run it at a lower resolution, like 1280x720, and while all those modes show up in `xrandr`:

$ xrandr -q
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 132mm x 75mm
   1920x1080     60.00*+  44.99  
   1680x1050     59.95  
   1400x1050     74.87    59.98  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1440x900      74.98    59.89  
   1280x960      60.00  
   1366x768      59.79  
   1360x768      60.02  
   1280x800      74.93    59.81  
   1152x864      75.00  
   1280x768      74.89    59.87  
   1280x720      60.00  
   1024x768      75.03    70.07    60.00  
   800x600       72.19    75.00    60.32    56.25  
   848x480       60.00  
   640x480       75.00    72.81    59.94  
   256x160       58.79

selecting any of these modes results in a garbage output:
What the display looks like

I've reproduced this issue running booting to the Debian(?)/XFCE-based SystemRescue Live environment to rule out issues related to experimental mesa drivers or a bad xorg config (I've also confirmed that this is an issue under Wayland). However, a clean copy of Windows 11 (fresh ISO, from Microsoft, not using what came pre-loaded) can change the resolution fine, ruling out an inherent hardware / firmware issue.

I do not have this issue setting resolutions on external displays (which is why I'm posting this to the laptop forum). I'm hoping that other 6xxxU/H/HX laptop users have encountered something similar and might know of a boot setting, driver fix or kernel module patch that I need to roll out.

Here are some dumps for diagnostic purposes. Let me know if there are others I should provide.

$ cat /etc/default/grub
# GRUB boot loader configuration

GRUB_DEFAULT="0"
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="Holo Shed"
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 amd-pstate=passive fbcon=font:ter-v28b"
GRUB_CMDLINE_LINUX=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

$ sudo inxi -Gx
Graphics:
  Device-1: AMD Rembrandt [Radeon 680M] driver: amdgpu v: kernel arch: RDNA-2
    bus-ID: 73:00.0 temp: 34.0 C
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 23.1.2 driver: X:
    loaded: amdgpu unloaded: modesetting dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 23.1.3 renderer: AMD Radeon Graphics (rembrandt
    LLVM 15.0.7 DRM 3.52 6.4.3-arch1-2) direct-render: Yes

$ neofetch
             .......                       openbagtwo@lin4 
         .'';cokkkkox:..                   -------------- 
      .'loddkkkkkkkxxxdd:,.                OS: HoloShed x86_64 
    .cxxkkkkkkkOOxc....,:dl'               Host: GPD G1618-04 
   ckkkkkkkkkOKX:.';.,,:..xd;.             Kernel: 6.4.3-arch1-2 
  :KOkkkkkO0XWM, ,M    'N xkdo             Uptime: 1 hour, 15 mins 
  0WNKKKKXNWMMx  :N;..'lO 00kxl            Packages: 1000 (pacman), 19 (flatpak) 
  ',kkMMMMMMMk    .odx:, lWKOOk            Shell: bash 5.1.16 
      .'cll:k'.    'lllO0MNXKd.            Resolution: 1920x1080 
  .,.       ,,k  ,kMMMMMMMMWWo . .         DE: Pantheon 
  ,MXkk,      K OMMMMMMMMMMMN  .o0Oo       WM: Mutter(Gala) 
   ;0MMMdl''''cOMMMMMMMMMM0c. .:kXNW       Theme: io.elementary.stylesheet.mint [GTK3] 
     ,kNXMk dkWMMMMMMMMMM0   ..,lOWc       Icons: elementary [GTK3] 
       .'x0.,xMMMMMMMN0Ol.'; c.o:dx        Terminal: io.elementary.t 
          dxk,:kkkd,,.     ;dOxxkx,        CPU: AMD Ryzen 7 6800U with Radeon Graphics (16) @ 4.768GHz 
            'lxl;.         .kl:xX.         GPU: AMD ATI Radeon 680M 
              cMMW   .         k0 ,'       Memory: 4271MiB / 23816MiB 
               'dO. ,:,,..   ..c;.,c.   
                     .;',c::;cl,;;,,d                              
                         ',c:;O;::::l

seth · 2023-07-21 16:22:50

https://wiki.archlinux.org/title/Hidpi
xrandr --output eDP --scale 0.66
https://bbs.archlinux.org/misc.php?action=rules

OpenBagTwo · 2023-07-21 16:44:45

Brilliant! That works! Outside of gamescope do you have any suggestions for enforcing that with games and other applications that go fullscreen and set a resolution?

seth · 2023-07-21 19:47:07

Configure the game to not change the resolution?

You got the part where HoloShed isn't archlinux or supported here?

OpenBagTwo · 2023-07-21 23:06:33

seth wrote:

You got the part where HoloShed isn't archlinux or supported here?

Haha, sorry for the confusion, but I promise you my system is indeed just running plain, vanilla Arch (see the kernel entry). I don't even have any custom repos set up beyond the AUR, and I even went through the install process manually rather than relying on the guided script. "HoloShed" is just me futzing around with neofetch and a few other config files--it's not a real distro.

seth · 2023-07-22 06:23:08

There'd be an ongoing bug where the default modes are not added, https://bbs.archlinux.org/viewtopic.php?id=287054
So the panel would have to advertise those failing modes for you?

xrandr --verbose

Arch Linux

#1 2023-07-21 15:20:26

All non-default resolutions result in garbled primary display output

#2 2023-07-21 16:22:50

Re: All non-default resolutions result in garbled primary display output

#3 2023-07-21 16:44:45

Re: All non-default resolutions result in garbled primary display output

#4 2023-07-21 19:47:07

Re: All non-default resolutions result in garbled primary display output

#5 2023-07-21 23:06:33

Re: All non-default resolutions result in garbled primary display output

#6 2023-07-22 06:23:08

Re: All non-default resolutions result in garbled primary display output

Board footer