4k at 60Hz resolution present and working in Wayland but missing from X11

Questions about the experimental Wayland support on Linux Mint Cinnamon
Forum rules
Include your system information for help with troubleshooting. Report reproducible issues related to Wayland, whether for Cinnamon, an XApp, a Mint tool or any Linux Mint maintained software on the dedicated issue tracker. Topics in this forum are automatically closed after 6 months.
Post Reply
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

Hello all and thanks in advance for any help. If this topic would be better in a different sub-forum please feel free to move it obviously.

New install of 21.3 Cinnamon EDGE (first LM install in years). AMD 7735 APU. 50" 4k Sceptre brand "dumb" TV for my monitor which Mint recognizes as a 32" Sceptre.

So, as the title states, when I log into a Wayland session the correct 4k 60hz resolution is present and can be chosen. When I log into a standard X11(?, xorg?) session, the Mint display settings app only gives me a 4k at 30Hz option. I know my monitor is capable of 4k at 60Hz, I have selected HDMI 2.0 in the TVs settings and I know I have the correct HDMI cables.

I would prefer not to use Wayland for now as not everything I need works during a Wayland session. Following what I assume are outdated instructions, I have tried (and so far failed) to properly add the 4k 60Hz option to xrandr.

If possible, I guess I am asking for proper instructions to add the missing 4k 60Hz option using the terminal and xrandr. And/or some insight as to why this particular problem is occurring for me.

Thanks for your time.
Last edited by SMG on Fri Feb 02, 2024 5:38 pm, edited 1 time in total.
Reason: Moved from Other Topics to Graphics Cards & Monitors because the issue is getting monitor refresh rate working.
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Fri Feb 02, 2024 5:27 pmNew install of 21.3 Cinnamon EDGE (first LM install in years). AMD 7735 APU. 50" 4k Sceptre brand "dumb" TV for my monitor which Mint recognizes as a 32" Sceptre.
Welcome to the forum, driver8.

Mint recognizes what the EDID of the monitor sends through the cable to the computer. Many devices are not coded correctly in the EDID and show up with different names/dimensions than what you might expect.

Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click the Copy button in the lower right and paste the results into a reply window here so we can see how Linux Mint views your hardware.

I also recommend updating the amdgpu linux-firmware to see if that helps with this issue.

Here are instructions to update your system with the latest AMD driver linux-firmware.
  • Take a Timeshift snapshot. If this change causes problems, a snapshot will be the best way to reverse the change.
  • Please go to this page and download the linux-firmware-main.tar.gz firmware package into your Downloads directory. Make sure there is still a red rectangle with HEAD in it and a green rectangle with main in it. If not, stop and I will get you updated information.
  • Right-click the downloaded file and select "Extract here". That will create a directory named linux-firmware-main.
  • Navigate to the amdgpu folder in the linux-firmware-main directory just created and open a terminal in that amdgpu directory and run the following lines one at a time.

    Code: Select all

    sudo cp -u * /lib/firmware/amdgpu/
    sudo update-initramfs -u -k all
  • Reboot the computer.
If you have any questions on the instructions, just ask.
driver8 wrote: Fri Feb 02, 2024 5:27 pmSo, as the title states, when I log into a Wayland session the correct 4k 60hz resolution is present and can be chosen. When I log into a standard X11(?, xorg?) session, the Mint display settings app only gives me a 4k at 30Hz option.
Are you rebooting in between those sessions?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

Thanks for the response.

With regard to System info - I currently have the display set at 1920x1080 60hz just to make it easier for now with the sizing of windows and apps. If you want me to set the resolution to 4k 30hz in X or 4k 60hz in Wayland and then access and copy the System Info, just let me know. I just thought I would explain why the below output is currently showing 1080p 60hz.

I will try updating the AMD driver linux firmware immediately after posting this.

Lastly as to the question of whether or not I was rebooting between sessions - I tried it both ways. Simply logging in to Wayland, setting the 4k 60hz, logging out of Wayland and back into X. Also, at different times I tried rebooting in between. Neither made a difference. I did read (somewhere) that starting the Wayland session, setting the proper 4k 60hz, logging out and logging into X would supposedly solve the issue for that session but would not persist when the computer was rebooted. I did not find that to be true in my case.

Here is the current System Info snapshot:

Code: Select all

System:
  Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33
    wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Micro (HK) Tech product: Venus series v: Version 1.0
    serial: <superuser required>
  Mobo: Shenzhen Meigao Equipment model: F7BFD v: Version 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: 1.15 date: 11/30/2023
CPU:
  Info: 8-core model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP smt: enabled
    arch: Zen 3 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 1797 high: 4772 min/max: 400/4829 cores: 1: 2105 2: 2097 3: 2100 4: 2105
    5: 400 6: 400 7: 2110 8: 400 9: 2106 10: 2107 11: 400 12: 400 13: 400 14: 2107 15: 4772 16: 4749
    bogomips: 102207
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Rembrandt driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, HDMI-A-2 bus-ID: 34:00.0
    chip-ID: 1002:1681 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23")
  Monitor-1: HDMI-A-0 mapped: HDMI-A-1 model: Sceptre W50 res: 1920x1080 hz: 60 dpi: 69
    size: 708x398mm (27.9x15.7") modes: max: 3840x2160 min: 720x400
  OpenGL: renderer: REMBRANDT (rembrandt LLVM 15.0.7 DRM 3.54 6.5.0-15-generic)
    v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: AMD driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 34:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor driver: snd_pci_acp6x v: kernel
    pcie: speed: 16 GT/s lanes: 16 bus-ID: 34:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h HD Audio vendor: Realtek driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 34:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound Server-1: ALSA v: k6.5.0-15-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel driver: igc v: kernel pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0
    chip-ID: 8086:125c class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter driver: mt7921e
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14c3:7961 class-ID: 0280
  IF: wlp2s0 state: down mac: <filter>
  IF-ID-1: wg-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-3:2
    chip-ID: 0e8d:7961 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2202 hci-v: 5.2 rev: 915
Drives:
  Local Storage: total: 931.51 GiB used: 402.25 GiB (43.2%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN770 1TB size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 731100WD temp: 38.9 C scheme: GPT
Partition:
  ID-1: / size: 912.73 GiB used: 401.93 GiB (44.0%) fs: ext4 dev: /dev/dm-1 mapped: vgmint-root
  ID-2: /boot size: 1.61 GiB used: 321.9 MiB (19.6%) fs: ext4 dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-2
    mapped: vgmint-swap_1
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-4:2 info: Razer USA DeathAdder V2 X HyperSpeed type: Mouse,Keyboard
    driver: hid-generic,usbhid interfaces: 5 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 1532:009c
    class-ID: 0300 serial: <filter>
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 3 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-3:2 info: MediaTek Wireless_Device type: Bluetooth driver: btusb interfaces: 3
    rev: 2.1 speed: 480 Mb/s power: 100mA chip-ID: 0e8d:7961 class-ID: e001 serial: <filter>
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 5-1:2 info: Microsoft 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900
    type: Keyboard,Mouse,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 100mA chip-ID: 045e:07b2 class-ID: 0300
  Hub-6: 6-0:1 info: Linux Foundation 3.0 root hub ports: N/A rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-7: 7-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-8: 8-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 9-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-10: 10-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 40.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2227 apt: 2226 flatpak: 1
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //mirror.steadfastnet.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //mirror.steadfastnet.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //mirror.steadfastnet.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 410 Uptime: 6h 0m wakeups: 9 Memory: 27.14 GiB used: 2.41 GiB (8.9%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
  inxi: 3.3.13
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Fri Feb 02, 2024 10:26 pmLastly as to the question of whether or not I was rebooting between sessions - I tried it both ways. Simply logging in to Wayland, setting the 4k 60hz, logging out of Wayland and back into X. Also, at different times I tried rebooting in between. Neither made a difference. I did read (somewhere) that starting the Wayland session, setting the proper 4k 60hz, logging out and logging into X would supposedly solve the issue for that session but would not persist when the computer was rebooted. I did not find that to be true in my case.
That is likely because the information you read was not for using Wayland on Cinnamon. There are different ways to implement Wayland and what works on one desktop environment does not necessarily work on a different desktop environment. Right now, Wayland is experimental for Cinnamon and it requires rebooting to switch sessions or else you will have problems in X11. Please see WAYLAND - read this first! in the Cinnamon on Wayland forum.
driver8 wrote: Fri Feb 02, 2024 10:26 pmWith regard to System info - I currently have the display set at 1920x1080 60hz just to make it easier for now with the sizing of windows and apps. If you want me to set the resolution to 4k 30hz in X or 4k 60hz in Wayland and then access and copy the System Info, just let me know. I just thought I would explain why the below output is currently showing 1080p 60hz.
What is the output of xrandr?

I did a quick check of the AMD bug reports and don't see anything for that CPU/GPU that might relate to this issue.

You are connecting the monitor directly to the motherboard, correct (no dock of any type)?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

I updated the AMD driver linux-firmware as instructed. No joy.

Edit: Yes I am connecting directly to the TV from the motherboard via HDMI. No dock in between.

xrandr:

Code: Select all

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
HDMI-A-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 708mm x 398mm
   3840x2160     30.00 +  25.00    24.00    29.97    23.98  
   1920x1200     30.00  
   1920x1080     60.00*   50.00    59.94    24.00    23.98  
   1600x1200     30.00  
   1680x1050     59.88  
   1280x1024     60.02  
   1440x900      30.00  
   1280x960      60.00  
   1360x768      60.02  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       60.00    59.94  
   720x400       70.08  
HDMI-A-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
After updating the AMD driver linux-firmware and rebooting I logged in to Wayland again just to look again and I paid more attention this time. It defaults to 4k 60hz and in the display settings app recognizes the TV as "Sceptre Tech Inc." The X11 session continues to list the 50" TV as "Sceptre Tech Inc. 32". I don't know if that info is helpful in any way but it seems to me that the X11 session simply doesn't recognize the monitor correctly and the DPI and screen size are simply wrong as a result.

Edit2: Yes you already said the above..lol
Many devices are not coded correctly in the EDID and show up with different names/dimensions than what you might expect.
I continue to wonder if forcing a new modeline to xrandr wouldn't somehow solve the issue. I also wonder if the DPI and actual screen size in millimeters needs to be set somehow. I have just been reading so many different "fixes" from so many varied sources that it is all running together in my brain atm.

I will await to be further instructed. Thanks again for your help.
Last edited by SMG on Fri Feb 02, 2024 11:07 pm, edited 1 time in total.
Reason: Added code tags to the xrandr output so it retains its formatting.
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Fri Feb 02, 2024 11:04 pm

Code: Select all

HDMI-A-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 708mm x 398mm
   3840x2160     30.00 +  25.00    24.00    29.97    23.98  
   1920x1080     60.00*   50.00    59.94    24.00    23.98 
When reading xrandr output, *= current resolution and += preferred resolution.

When the 7900XT/XTXs first came out, there was an issue with the cursor disappearing. I found mention on a bug report the problem only happened in X11 (not Wayland) and that if one changed the cursor to software rendering it would show. I still have the info in the Graphics Tips topic on how to enable the software cursor, but that doesn't seem to be happening any more so apparently AMD changed their driver so that problem was fixed. I mention that because this may be another one of those issues where there is a difference because of how AMD coded the driver.

Usually, if xrandr does not show a preferred resolution, then we often can get it to work on the monitor's preferred resolution. However, this output is showing an preferred resolution which does not usually bode well for being able to successfully add another one. The fact it is a TV also does not help as those tend to be more finicky.

What is the output of

Code: Select all

xrandr --verbose
Please enclose the results in code tags as described in this tutorial How to use code display tags on forums.linuxmint.com. I'd like to see what the EDID indicates before we attempt to make xrandr changes.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

xrandr --verbos

Code: Select all

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
HDMI-A-0 connected primary 1920x1080+0+0 (0x60) normal (normal left inverted right x axis y axis) 708mm x 398mm
	Identifier: 0x52
	Timestamp:  287887
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       0
	CRTCs:      0 1 2 3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	_MUTTER_PRESENTATION_OUTPUT: 0 
	EDID: 
		00ffffffffffff004e14c51300000000
		2c210103800000000ad7a5a2594a9624
		145054a30800d1c0b300810081808140
		81c00101010104740030f2705a80b058
		8a00c48e2100001e662150b051001b30
		407036003f432100001e000000fd001e
		4c1e501e000a202020202020000000fc
		0053636570747265205735300a2001e0
		020344735590050403070206011f1413
		121611155f5e5d61602026097f071507
		506d030c001000003c20006001020367
		d85dc401788000e3050301e40f00000c
		83010000011d007251d01e206e285500
		c48e2100001e011d8018711c1620582c
		2500c48e2100009e8c0ad08a20e02d10
		103e9600138e210000180000000000f4
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
		0 1 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
	max bpc: 16 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 83 
		supported: 83
	non-desktop: 0 
		range: (0, 1)
  3840x2160 (0x5a) 297.000MHz +HSync +VSync +preferred
        h: width  3840 start 4016 end 4104 total 4400 skew    0 clock  67.50KHz
        v: height 2160 start 2168 end 2178 total 2250           clock  30.00Hz
  3840x2160 (0x5b) 297.000MHz +HSync +VSync
        h: width  3840 start 4896 end 4984 total 5280 skew    0 clock  56.25KHz
        v: height 2160 start 2168 end 2178 total 2250           clock  25.00Hz
  3840x2160 (0x5c) 297.000MHz +HSync +VSync
        h: width  3840 start 5116 end 5204 total 5500 skew    0 clock  54.00KHz
        v: height 2160 start 2168 end 2178 total 2250           clock  24.00Hz
  3840x2160 (0x5d) 296.703MHz +HSync +VSync
        h: width  3840 start 4016 end 4104 total 4400 skew    0 clock  67.43KHz
        v: height 2160 start 2168 end 2178 total 2250           clock  29.97Hz
  3840x2160 (0x5e) 296.703MHz +HSync +VSync
        h: width  3840 start 5116 end 5204 total 5500 skew    0 clock  53.95KHz
        v: height 2160 start 2168 end 2178 total 2250           clock  23.98Hz
  1920x1200 (0x5f) 297.000MHz +HSync +VSync
        h: width  1920 start 4016 end 4104 total 4400 skew    0 clock  67.50KHz
        v: height 1200 start 2168 end 2178 total 2250           clock  30.00Hz
  1920x1080 (0x60) 148.500MHz +HSync +VSync *current
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
  1920x1080 (0x61) 148.500MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  56.25KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  50.00Hz
  1920x1080 (0x62) 148.352MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.43KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  59.94Hz
  1920x1080 (0x63) 74.250MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  27.00KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  24.00Hz
  1920x1080 (0x64) 74.176MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  26.97KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  23.98Hz
  1600x1200 (0x65) 297.000MHz +HSync +VSync
        h: width  1600 start 4016 end 4104 total 4400 skew    0 clock  67.50KHz
        v: height 1200 start 2168 end 2178 total 2250           clock  30.00Hz
  1680x1050 (0x66) 119.000MHz +HSync -VSync
        h: width  1680 start 1728 end 1760 total 1840 skew    0 clock  64.67KHz
        v: height 1050 start 1053 end 1059 total 1080           clock  59.88Hz
  1280x1024 (0x67) 108.000MHz +HSync +VSync
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1440x900 (0x68) 297.000MHz +HSync +VSync
        h: width  1440 start 4016 end 4104 total 4400 skew    0 clock  67.50KHz
        v: height  900 start 2168 end 2178 total 2250           clock  30.00Hz
  1280x960 (0x69) 108.000MHz +HSync +VSync
        h: width  1280 start 1376 end 1488 total 1800 skew    0 clock  60.00KHz
        v: height  960 start  961 end  964 total 1000           clock  60.00Hz
  1360x768 (0x6a) 85.500MHz +HSync +VSync
        h: width  1360 start 1424 end 1536 total 1792 skew    0 clock  47.71KHz
        v: height  768 start  771 end  777 total  795           clock  60.02Hz
  1280x800 (0x6b) 71.000MHz +HSync -VSync
        h: width  1280 start 1328 end 1360 total 1440 skew    0 clock  49.31KHz
        v: height  800 start  803 end  809 total  823           clock  59.91Hz
  1280x720 (0x6c) 74.250MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  45.00KHz
        v: height  720 start  725 end  730 total  750           clock  60.00Hz
  1280x720 (0x6d) 74.250MHz +HSync +VSync
        h: width  1280 start 1720 end 1760 total 1980 skew    0 clock  37.50KHz
        v: height  720 start  725 end  730 total  750           clock  50.00Hz
  1280x720 (0x6e) 74.176MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  44.96KHz
        v: height  720 start  725 end  730 total  750           clock  59.94Hz
  1024x768 (0x6f) 65.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  800x600 (0x70) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  800x600 (0x71) 36.000MHz +HSync +VSync
        h: width   800 start  824 end  896 total 1024 skew    0 clock  35.16KHz
        v: height  600 start  601 end  603 total  625           clock  56.25Hz
  720x576 (0x72) 27.000MHz -HSync -VSync
        h: width   720 start  732 end  796 total  864 skew    0 clock  31.25KHz
        v: height  576 start  581 end  586 total  625           clock  50.00Hz
  720x480 (0x73) 27.027MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.50KHz
        v: height  480 start  489 end  495 total  525           clock  60.00Hz
  720x480 (0x74) 27.000MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.47KHz
        v: height  480 start  489 end  495 total  525           clock  59.94Hz
  640x480 (0x75) 25.200MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.50KHz
        v: height  480 start  490 end  492 total  525           clock  60.00Hz
  640x480 (0x76) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
  720x400 (0x77) 28.320MHz -HSync +VSync
        h: width   720 start  738 end  846 total  900 skew    0 clock  31.47KHz
        v: height  400 start  412 end  414 total  449           clock  70.08Hz
HDMI-A-1 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x53
	Timestamp:  287887
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1 2 3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
	max bpc: 16 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 91 
		supported: 91
	non-desktop: 0 
		range: (0, 1)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x54
	Timestamp:  287887
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1 2 3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
	max bpc: 16 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 96 
		supported: 96
	non-desktop: 0 
		range: (0, 1)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x55
	Timestamp:  287887
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1 2 3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
	max bpc: 16 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 102 
		supported: 102
	non-desktop: 0 
		range: (0, 1)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x56
	Timestamp:  287887
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1 2 3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
	max bpc: 16 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 107 
		supported: 107
	non-desktop: 0 
		range: (0, 1)
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x57
	Timestamp:  287887
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1 2 3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
	max bpc: 16 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 112 
		supported: 112
	non-desktop: 0 
		range: (0, 1)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x58
	Timestamp:  287887
	Subpixel:   unknown
	Clones:    
	CRTCs:      0 1 2 3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	GAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	DEGAMMA_LUT_SIZE: 4096 
		range: (0, -1)
	GAMMA_LUT: 0 
		range: (0, 65535)
	CTM: 0 
	DEGAMMA_LUT: 0 
		range: (0, 65535)
	TearFree: auto 
		supported: off, on, auto
	subconnector: Unknown 
		supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
	HDCP Content Type: HDCP Type0 
		supported: HDCP Type0, HDCP Type1
	Content Protection: Undesired 
		supported: Undesired, Desired, Enabled
	vrr_capable: 0 
		range: (0, 1)
	Colorspace: Default 
		supported: Default, BT709_YCC, opRGB, BT2020_RGB, BT2020_YCC
	max bpc: 16 
		range: (8, 16)
	underscan vborder: 0 
		range: (0, 128)
	underscan hborder: 0 
		range: (0, 128)
	underscan: off 
		supported: off, on, auto
	scaling mode: None 
		supported: None, Full, Center, Full aspect
	link-status: Good 
		supported: Good, Bad
	CONNECTOR_ID: 117 
		supported: 117
	non-desktop: 0 
		range: (0, 1)
Last edited by driver8 on Sat Feb 03, 2024 12:20 am, edited 1 time in total.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

I thought I would switch to Wayland and get the System Info from there and post it (below). Mostly because I was just curious and trying to learn about what I am looking at.

Code: Select all

System:
  Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33
    wm: muffin vt: 8 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Micro (HK) Tech product: Venus series v: Version 1.0
    serial: <superuser required>
  Mobo: Shenzhen Meigao Equipment model: F7BFD v: Version 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: 1.15 date: 11/30/2023
CPU:
  Info: 8-core model: AMD Ryzen 7 7735HS with Radeon Graphics bits: 64 type: MT MCP smt: enabled
    arch: Zen 3 rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 1513 high: 4779 min/max: 400/4829 cores: 1: 400 2: 400 3: 2310 4: 2400
    5: 400 6: 400 7: 4767 8: 4779 9: 400 10: 2117 11: 400 12: 400 13: 400 14: 2117 15: 400 16: 2119
    bogomips: 102206
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Rembrandt driver: amdgpu v: kernel pcie: speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, HDMI-A-2 bus-ID: 34:00.0
    chip-ID: 1002:1681 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1 driver: X:
    loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-A-1 model: Sceptre W50 res: 3840x2160 dpi: 138 size: 708x398mm (27.9x15.7")
    diag: 812mm (32") modes: max: 3840x2160 min: 720x400
  OpenGL: renderer: REMBRANDT (rembrandt LLVM 15.0.7 DRM 3.54 6.5.0-15-generic)
    v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes
Audio:
  Device-1: AMD driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 34:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor driver: snd_pci_acp6x v: kernel
    pcie: speed: 16 GT/s lanes: 16 bus-ID: 34:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h HD Audio vendor: Realtek driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 34:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound Server-1: ALSA v: k6.5.0-15-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel driver: igc v: kernel pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0
    chip-ID: 8086:125c class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter driver: mt7921e
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14c3:7961 class-ID: 0280
  IF: wlp2s0 state: down mac: <filter>
  IF-ID-1: wg-mullvad state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 3-3:2
    chip-ID: 0e8d:7961 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 2202 hci-v: 5.2 rev: 915
Drives:
  Local Storage: total: 1.02 TiB used: 414.44 GiB (39.5%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN770 1TB size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: 731100WD temp: 33.9 C scheme: GPT
  ID-2: /dev/sda type: USB vendor: Patriot model: N/A size: 118 GiB type: N/A serial: <filter>
    rev: PMAP scheme: MBR
Partition:
  ID-1: / size: 912.73 GiB used: 403.51 GiB (44.2%) fs: ext4 dev: /dev/dm-1 mapped: vgmint-root
  ID-2: /boot size: 1.61 GiB used: 324.1 MiB (19.7%) fs: ext4 dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-2
    mapped: vgmint-swap_1
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-4:2 info: Razer USA DeathAdder V2 X HyperSpeed type: Mouse,Keyboard
    driver: hid-generic,usbhid interfaces: 5 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 1532:009c
    class-ID: 0300 serial: <filter>
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 3 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-3:2 info: MediaTek Wireless_Device type: Bluetooth driver: btusb interfaces: 3
    rev: 2.1 speed: 480 Mb/s power: 100mA chip-ID: 0e8d:7961 class-ID: e001 serial: <filter>
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 4-2:2 info: Kingston Patriot Memory type: Mass Storage driver: usb-storage
    interfaces: 1 rev: 3.2 speed: 5 Gb/s power: 896mA chip-ID: 13fe:6000 class-ID: 0806
    serial: <filter>
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 5-1:2 info: Microsoft 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900
    type: Keyboard,Mouse,HID driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 100mA chip-ID: 045e:07b2 class-ID: 0300
  Hub-6: 6-0:1 info: Linux Foundation 3.0 root hub ports: N/A rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-7: 7-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-8: 8-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-9: 9-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-10: 10-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 37.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2229 apt: 2228 flatpak: 1
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //mirror.steadfastnet.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //mirror.steadfastnet.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //mirror.steadfastnet.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 438 Uptime: 1h 25m wakeups: 3 Memory: 27.14 GiB used: 1.9 GiB (7.0%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
  inxi: 3.3.13
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Sat Feb 03, 2024 12:15 am I thought I would switch to Wayland and get the System Info from there and post it (below). Mostly because I was just curious and trying to learn about what I am looking at.
I'm going to move this topic to the Cinnamon on Wayland forum so we have this comparison information in one place.

I ran the information through the EDID decode and what is coming up for X11 is showing in the EDID. The preferred timing is 30Hz.

Code: Select all

 edid-decode edid.bin
edid-decode (hex):

00 ff ff ff ff ff ff 00 4e 14 c5 13 00 00 00 00 
2c 21 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24 
14 50 54 a3 08 00 d1 c0 b3 00 81 00 81 80 81 40 
81 c0 01 01 01 01 04 74 00 30 f2 70 5a 80 b0 58 
8a 00 c4 8e 21 00 00 1e 66 21 50 b0 51 00 1b 30 
40 70 36 00 3f 43 21 00 00 1e 00 00 00 fd 00 1e 
4c 1e 50 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 
00 53 63 65 70 74 72 65 20 57 35 30 0a 20 01 e0 

02 03 44 73 55 90 05 04 03 07 02 06 01 1f 14 13 
12 16 11 15 5f 5e 5d 61 60 20 26 09 7f 07 15 07 
50 6d 03 0c 00 10 00 00 3c 20 00 60 01 02 03 67 
d8 5d c4 01 78 80 00 e3 05 03 01 e4 0f 00 00 0c 
83 01 00 00 01 1d 00 72 51 d0 1e 20 6e 28 55 00 
c4 8e 21 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 
25 00 c4 8e 21 00 00 9e 8c 0a d0 8a 20 e0 2d 10 
10 3e 96 00 13 8e 21 00 00 18 00 00 00 00 00 f4 

----------------

EDID version: 1.3
Manufacturer: SPT Model 5061 Serial Number 0
Made in week 44 of 2023
Digital display
Image size is variable
Gamma: 1.00
RGB color display
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6357, 0.3486
  Green: 0.2900, 0.5888
  Blue:  0.1425, 0.0800
  White: 0.3134, 0.3291
Established Timings I & II
    720x400    70.082 Hz   9:5    31.467 kHz  28.320 MHz (IBM)
    640x480    59.940 Hz   4:3    31.469 kHz  25.175 MHz (DMT)
    800x600    56.250 Hz   4:3    35.156 kHz  36.000 MHz (DMT)
    800x600    60.317 Hz   4:3    37.879 kHz  40.000 MHz (DMT)
   1024x768    60.004 Hz   4:3    48.363 kHz  65.000 MHz (DMT)
Standard Timings
   1920x1080   60.000 Hz  16:9    67.500 kHz 148.500 MHz (DMT)
   1680x1050   59.954 Hz  16:10   65.290 kHz 146.250 MHz (DMT)
   1280x800    59.810 Hz  16:10   49.702 kHz  83.500 MHz (DMT)
   1280x1024   60.020 Hz   5:4    63.981 kHz 108.000 MHz (DMT)
   1280x960    60.000 Hz   4:3    60.000 kHz 108.000 MHz (DMT)
   1280x720    60.000 Hz  16:9    45.000 kHz  74.250 MHz (DMT)
Detailed mode: Clock 297.000 MHz, 708 mm x 398 mm
               3840 4016 4104 4400 (176  88 296)
               2160 2168 2178 2250 (  8  10  72)
               +hsync +vsync
               VertFreq: 30.000 Hz, HorFreq: 67.500 kHz
Detailed mode: Clock 85.500 MHz, 575 mm x 323 mm
               1360 1424 1536 1792 ( 64 112 256)
                768  771  777  795 (  3   6  18)
               +hsync +vsync
               VertFreq: 60.015 Hz, HorFreq: 47.712 kHz
Display Range Limits
  Monitor ranges (GTF): 30-76 Hz V, 30-80 kHz H, max dotclock 300 MHz
Display Product Name: Sceptre W50
Has 1 extension block
Checksum: 0xe0

----------------

CTA-861 Extension Block Revision 3
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
3 native detailed modes
64 bytes of CTA data blocks
  Video Data Block
     1920x1080   60.000 Hz  16:9    67.500 kHz 148.500 MHz (VIC  16, native)
     1920x1080i  60.000 Hz  16:9    33.750 kHz  74.250 MHz (VIC   5)
     1280x720    60.000 Hz  16:9    45.000 kHz  74.250 MHz (VIC   4)
      720x480    59.940 Hz  16:9    31.469 kHz  27.000 MHz (VIC   3)
     1440x480i   59.940 Hz  16:9    15.734 kHz  27.000 MHz (VIC   7)
      720x480    59.940 Hz   4:3    31.469 kHz  27.000 MHz (VIC   2)
     1440x480i   59.940 Hz   4:3    15.734 kHz  27.000 MHz (VIC   6)
      640x480    59.940 Hz   4:3    31.469 kHz  25.175 MHz (VIC   1)
     1920x1080   50.000 Hz  16:9    56.250 kHz 148.500 MHz (VIC  31)
     1920x1080i  50.000 Hz  16:9    28.125 kHz  74.250 MHz (VIC  20)
     1280x720    50.000 Hz  16:9    37.500 kHz  74.250 MHz (VIC  19)
      720x576    50.000 Hz  16:9    31.250 kHz  27.000 MHz (VIC  18)
     1440x576i   50.000 Hz  16:9    15.625 kHz  27.000 MHz (VIC  22)
      720x576    50.000 Hz   4:3    31.250 kHz  27.000 MHz (VIC  17)
     1440x576i   50.000 Hz   4:3    15.625 kHz  27.000 MHz (VIC  21)
     3840x2160   30.000 Hz  16:9    67.500 kHz 297.000 MHz (VIC  95)
     3840x2160   25.000 Hz  16:9    56.250 kHz 297.000 MHz (VIC  94)
     3840x2160   24.000 Hz  16:9    54.000 kHz 297.000 MHz (VIC  93)
     3840x2160   60.000 Hz  16:9   135.000 kHz 594.000 MHz (VIC  97)
     3840x2160   50.000 Hz  16:9   112.500 kHz 594.000 MHz (VIC  96)
     1920x1080   24.000 Hz  16:9    27.000 kHz  74.250 MHz (VIC  32)
  Audio Data Block
    Linear PCM, max channels 2
      Supported sample rates (kHz): 192 176.4 96 88.2 48 44.1 32
      Supported sample sizes (bits): 24 20 16
    AC-3, max channels 6
      Supported sample rates (kHz): 48 44.1 32
      Maximum bit rate: 640 kb/s
  Vendor-Specific Data Block, OUI 0x000c03 (HDMI)
    Source physical address 1.0.0.0
    Maximum TMDS clock: 300 MHz
    Extended HDMI video details:
      HDMI VICs:
         3840x2160   30.000 Hz  16:9    67.500 kHz 297.000 MHz (HDMI VIC 1)
         3840x2160   25.000 Hz  16:9    56.250 kHz 297.000 MHz (HDMI VIC 2)
         3840x2160   24.000 Hz  16:9    54.000 kHz 297.000 MHz (HDMI VIC 3)
  Vendor-Specific Data Block, OUI 0xc45dd8 (HDMI Forum)
    Version: 1
    Maximum TMDS Character Rate: 600 MHz
    SCDC Present
  Extended tag: Colorimetry Data Block
    xvYCC601
    xvYCC709
  Extended tag: YCbCr 4:2:0 Capability Map Data Block
     3840x2160   60.000 Hz  16:9   135.000 kHz 594.000 MHz (VIC  97)
     3840x2160   50.000 Hz  16:9   112.500 kHz 594.000 MHz (VIC  96)
  Speaker Allocation Data Block
    Speaker map:
      FL/FR - Front Left/Right
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
               1280 1390 1430 1650 (110  40 220)
                720  725  730  750 (  5   5  20)
               +hsync +vsync
               VertFreq: 60.000 Hz, HorFreq: 45.000 kHz
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
               1920 2008 2052 2200 ( 88  44 148)
                540  542  547  562 (  2   5  15)
               +hsync +vsync
               VertFreq: 60.000i Hz, HorFreq: 33.750 kHz
Detailed mode: Clock 27.000 MHz, 531 mm x 398 mm
                720  736  798  858 ( 16  62  60)
                480  489  495  525 (  9   6  30)
               -hsync -vsync
               VertFreq: 59.940 Hz, HorFreq: 31.469 kHz
Checksum: 0xf4
It's getting late for me. I will check through this data again tomorrow to see if there is anything else we can try. The difference may be an issue related to the color options.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

It's getting late for me. I will check through this data again tomorrow to see if there is anything else we can try.
Hey, I completely understand. There really is no urgency to this at all but I do think it is an interesting problem that I would like to learn more about and have a fix for if possible. Respond if/when you have time. Thanks again.
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Sat Feb 03, 2024 12:54 am...I do think it is an interesting problem that I would like to learn more about and have a fix for if possible. Respond if/when you have time. Thanks again.
All I was able to find were indications there was a hardware component causing the possible issue. However, the fact you are using the exact same hardware in both cases negates that theory.

Information I found indicated AMD uses YCbCr by default (which is where that one line with 60 Hz is located in the video data block in the CTA-861 Extension Block Revision 3 section).

Code: Select all

     3840x2160   60.000 Hz  16:9   135.000 kHz 594.000 MHz (VIC  97)
However, neither detail mode has that available. (First detailed timing is preferred timing.)

Code: Select all

Detailed mode: Clock 297.000 MHz, 708 mm x 398 mm
               3840 4016 4104 4400 (176  88 296)
               2160 2168 2178 2250 (  8  10  72)
               +hsync +vsync
               VertFreq: 30.000 Hz, HorFreq: 67.500 kHz
Detailed mode: Clock 85.500 MHz, 575 mm x 323 mm
               1360 1424 1536 1792 ( 64 112 256)
                768  771  777  795 (  3   6  18)
               +hsync +vsync
               VertFreq: 60.015 Hz, HorFreq: 47.712 kHz
The EDID is showing Display Product Name: Sceptre W50. That is what your X11 output indicates on the last line of the below.

Code: Select all

  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23")
  Monitor-1: HDMI-A-0 mapped: HDMI-A-1 model: Sceptre W50 res: 1920x1080 hz: 60 dpi: 69
I've searched this as many ways of which I could think and I don't know why you are seeing something different for Wayland, especially considering the information in the EDID decode indicates 30Hz.

Do you have the option in Wayland to switch to 30Hz in the Display app drop-down? Maybe it's not really 60Hz but there's a bug which is doubling that number somehow?
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

Do you have the option in Wayland to switch to 30Hz in the Display app drop-down? Maybe it's not really 60Hz but there's a bug which is doubling that number somehow?
Not sure. I will check and edit this post when I know.

Ok, yes 30hz is an option. At 4k all of the following refresh rates are options in a Wayland session: 60.00, 59.98, 59.94, 50.00, 30.00, 29.97, 25.00, 24.00, 23.98. And, it defaults to 4k at 60hz (as it should).

I attempted to run wlr-randr and wdisplay and both returned the following error: "compositor doesn't support wlr-output-management-unstable-v1"

After checking those options I have scaled the display to 200% just to make life easier for the time being and am going to piddle around in Wayland for a bit. Is there a terminal command for accessing this "EDID" information in Wayland? Would it be helpful to diagnosing anything?
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Sun Feb 04, 2024 11:27 amI attempted to run wlr-randr and wdisplay and both returned the following error: "compositor doesn't support wlr-output-management-unstable-v1"
I will again tell you:
SMG wrote: Fri Feb 02, 2024 10:54 pm..the information you read was not for using Wayland on Cinnamon. There are different ways to implement Wayland and what works on one desktop environment does not necessarily work on a different desktop environment.
Wayland is a protocol. It is not code. That means how it works will be different on each desktop environment using it. At this time, Cinnamon is not using wlroots so neither wlr-randr (which requires wlroots) will work nor will wdisplay (which requires a compositor that implements the wlr-output-management-unstable-v1 protocol such as wlroots).

It's like you owning a Audi car, but you are trying to use Ford and Chevy car parts to fix it. Yes, Ford and Chevy are cars, but their parts will not work on an Audi. Stop trying to use Chevy parts on your Audi.
driver8 wrote: Sun Feb 04, 2024 11:27 am
Do you have the option in Wayland to switch to 30Hz in the Display app drop-down? Maybe it's not really 60Hz but there's a bug which is doubling that number somehow?
Ok, yes 30hz is an option. At 4k all of the following refresh rates are options in a Wayland session: 60.00, 59.98, 59.94, 50.00, 30.00, 29.97, 25.00, 24.00, 23.98. And, it defaults to 4k at 60hz (as it should).
Considering the data from the EDID, I don't know from where it might be generating the ones above 30 unless somehow the EDID decoder is wrong.
driver8 wrote: Sun Feb 04, 2024 11:27 amIs there a terminal command for accessing this "EDID" information in Wayland? Would it be helpful to diagnosing anything?
Wayland is a display protocol and can be implemented many different ways. You keep asking questions as if Wayland is defined code that only works one way when that is not the case.

The commands for accessing EDID are the ones I ran to produce the output I posted earlier and I got them from this post.

Cinnamon on Wayland has been out with EXPERIMENTAL support for a month. There is a great deal of it which does not yet work at all. It's possible you are seeing different resolutions when in Wayland because that part of it is not working properly.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

driver8 wrote: Sun Feb 04, 2024 11:27 amI attempted to run wlr-randr and wdisplay and both returned the following error: "compositor doesn't support wlr-output-management-unstable-v1"
I will again tell you:
SMG wrote: Fri Feb 02, 2024 10:54 pm..the information you read was not for using Wayland on Cinnamon. There are different ways to implement Wayland and what works on one desktop environment does not necessarily work on a different desktop environment.
I understood that the first time but also assumed that, presumably, there probably should be commands that would be implemented in Wayland on Cinnamon that served the same or a similar function as xrandr on X. Which is why I tried those. It's simply ignorance on my part. Not an accusation or a critique of Wayland on Cinnamon. My including the error message is just me trying to be complete in case "wlroots" (as it turns out) should be functioning and I was doing something wrong.
Wayland is a protocol. It is not code. That means how it works will be different on each desktop environment using it. At this time, Cinnamon is not using wlroots so neither wlr-randr (which requires wlroots) will work nor will wdisplay (which requires a compositor that implements the wlr-output-management-unstable-v1 protocol such as wlroots).
Sure, again you are dealing with ignorance here (me). It's probably not worth your time to explain it more than to say "yeah, Wayland on Cinnamon hasn't yet decided on and/or implemented those commands (or functions or features or whatever the proper term for them is).
It's like you owning a Audi car, but you are trying to use Ford and Chevy car parts to fix it. Yes, Ford and Chevy are cars, but their parts will not work on an Audi. Stop trying to use Chevy parts on your Audi.
Actually what it's like is an owner of an Audi assuming that there are parts that worked on his Chevy that probably have equivalent, yet newer, parts that serve the same function(s) on his Audi. What you are telling me is that there are not. Or rather, not yet anyway in Wayland/Cinnamon. Ok. Understandable. It's just that I don't know what is implemented and what isn't. I don't know enough to know what I don't know.
Cinnamon on Wayland has been out with EXPERIMENTAL support for a month. There is a great deal of it which does not yet work at all. It's possible you are seeing different resolutions when in Wayland because that part of it is not working properly.
Considering the data from the EDID, I don't know from where it might be generating the ones above 30 unless somehow the EDID decoder is wrong.
If I am reading you correctly, you are basically saying that you believe it is likely that the resolutions in Wayland are the lie. Ok, I accept that. I just assumed that since Wayland/Cinnamon was ostensibly showing and defaulting to the correct setting that it was some problem with X and the correct setting could ultimately be achieved in X.

Either way it seems you're becoming frustrated. Let's leave it.

As I said previously, this issue certainly isn't urgent (for me). I have been dealing with scaling issues for at least a week now and at this point I regret even buying this 4k TV. I haven't found a distro yet that deals with large format 4k well at all, let alone gets the resolution correct "out of the box" so it's certainly no black mark on Mint.

Be well.
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Sun Feb 04, 2024 11:58 pmI understood that the first time but also assumed that, presumably, there probably should be commands that would be implemented in Wayland on Cinnamon that served the same or a similar function as xrandr on X.
Wayland protocol only covers some of what X Server does. And Wayland is not a one-for-one replacement of X in those parts is does cover. It is a start-completely-over type of situation with a lot of code re-writing necessary. That's one reason it has taken so long to be accepted and implemented.
driver8 wrote: Sun Feb 04, 2024 11:58 pm My including the error message is just me trying to be complete in case "wlroots" (as it turns out) should be functioning and I was doing something wrong.
Only some of the DEs are using wlroots. Others are not using it at all. wlroots is not required code to run Wayland. It's one of multiple options.
driver8 wrote: Sun Feb 04, 2024 11:58 pmf I am reading that last bit correctly, you believe it is the resolutions in Wayland that are the lie. I assume you came to that conclusion based on the info you've seen.
I don't know. When I went searching, I found people for whom their resolutions options disappeared when they changed kernel versions. The graphics driver was now only giving them the preferred resolution in Wayland and they could no longer get the other options. Apparently, that was a deliberate change because the desktop environment (DE) was giving options in Wayland that should not have been available for the AMD driver because those resolutions could damage the display (the computers were laptops). Something in how the DE was handling either the EDID or the resolution (I wasn't sure) was giving options that should not have been made available. X was not giving the options, but Wayland was. That was actually a bug that the newer graphics driver (in the newer kernel) made sure did not happen. [DE was GNOME if I'm recalling correctly. It was not Cinnamon.]

In your case, the monitor is advertised to be able to do 60Hz so I wouldn't think damage would be a problem, but I don't understand the lower levels of how all this is working in Wayland to have any guesses as to what is happening that you are seeing options in Wayland that are not showing as options in X11. There are A LOT of pieces and parts to making the graphics you see on the screen and I only understand some parts of them.

Additionally, the code that has been written is experimental which means it is not complete and it should be expected to be buggy. It's alpha stage. We're all learning how it works.
driver8 wrote: Sun Feb 04, 2024 11:58 pmI have been dealing with scaling issues for at least a week now and at this point I regret even buying this 4k TV. I haven't found a distro yet that deals with large format 4k well at all, let alone gets the resolution correct "out of the box" so it's certainly no black mark on Mint.
You could try adding the resolution in xrandr, but I don't have high hopes it would work. The general process to follow is in this post. In your case, you would want to add a third parameter because you are seeking a specific frequency.

Code: Select all

cvt 3840 2160 60
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

SMG wrote: Mon Feb 05, 2024 12:53 amYou could try adding the resolution in xrandr, but I don't have high hopes it would work. The general process to follow is in this post. In your case, you would want to add a third parameter because you are seeking a specific frequency.

Code: Select all

cvt 3840 2160 60
Ok, some interesting developments. To me anyway. I tried forcing 4k at 60hz following those instructions and it returned "xrandr: Configure crtc 0 failed" as I think you were expecting. So, out of curiosity I tried the process with 50hz since that was one of the rez listed in the Wayland session. After the --output command the screen went black momentarily and then came up violently tearing/shaking and, after about 4 seconds, settled.

xrandr while running at 50hz:

Code: Select all

Screen 0: minimum 320 x 200, current 3640 x 2160, maximum 16384 x 16384
HDMI-A-0 connected primary 3640x2160+0+0 (normal left inverted right x axis y axis) 708mm x 398mm
   3840x2160     30.00 +  25.00    24.00    29.97    23.98  
   1920x1200     30.00  
   1920x1080     60.00    50.00    59.94    24.00    23.98  
   1600x1200     30.00  
   1680x1050     59.88  
   1280x1024     60.02  
   1440x900      30.00  
   1280x960      60.00  
   1360x768      60.02  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       60.00    59.94  
   720x400       70.08  
   3840x2160_60.00  59.98  
   3640x2160_50.00  49.98* 
HDMI-A-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
Not sure if that provides any clues or not. I am going to set the resolution back to 1080p 60hz and just live with it for the time being regardless.

Edit: Also I am curious about the following if you have any insight. Especially the "pclk: 712.75 MHz" number. When I tried to force the resolution (before posting asking for help here on the Mint forums) the instructions were very similar to the thread you linked me too but there was a final step regarding putting the added resolution in a /.config file of some sort (can't recall specifically) and after all was said and done and it didn't work, that 712 number was referenced in an error. Anyway, no worries obviously, I am just trying to learn what these numbers signify.

Code: Select all

# 3840x2160 59.98 Hz (CVT 8.29M9) hsync: 134.18 kHz; pclk: 712.75 MHz
Modeline "3840x2160_60.00"  712.75  3840 4160 4576 5312  2160 2163 2168 2237 -hsync +vsync
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

Wait! Holy crap I just realized I typed in cvt 3640 2160 50! Now I am tempted to try the 50hz with the correct 3840 and see if that horrible tearing still happens. Can I remove these added resolutions from the list of possible with a command and/or do they not persist after a reboot? Going to reboot to find out.
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Mon Feb 05, 2024 11:32 amSo, out of curiosity I tried the process with 50hz since that was one of the rez listed in the Wayland session. After the --output command the screen went black momentarily and then came up violently tearing/shaking and, after about 4 seconds, settled.
:shock:
driver8 wrote: Mon Feb 05, 2024 11:32 amEdit: Also I am curious about the following if you have any insight. Especially the "pclk: 712.75 MHz" number. When I tried to force the resolution (before posting asking for help here on the Mint forums) the instructions were very similar to the thread you linked me too but there was a final step regarding putting the added resolution in a /.config file of some sort (can't recall specifically) and after all was said and done and it didn't work, that 712 number was referenced in an error.
One would only add the information to a config file if the resolution works during one's initial test. I don't endorse making changes like that without testing them first.

The clk part of pclk likely means clock. I found this for calculating pclk which is probably not something you should be doing. These clock speeds are something the graphics driver engineers handle and are not meant to be something users mess with, unless you want to chance zapping your brand new monitor.
driver8 wrote: Mon Feb 05, 2024 11:54 amCan I remove these added resolutions from the list of possible with a command and/or do they not persist after a reboot? Going to reboot to find out.
I think rebooting will clear the added resolutions.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
driver8
Level 1
Level 1
Posts: 14
Joined: Fri Feb 02, 2024 4:34 pm

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by driver8 »

SMG wrote: Mon Feb 05, 2024 12:51 pm
driver8 wrote: Mon Feb 05, 2024 11:32 amSo, out of curiosity I tried the process with 50hz since that was one of the rez listed in the Wayland session. After the --output command the screen went black momentarily and then came up violently tearing/shaking and, after about 4 seconds, settled.
:shock:
Yeah haha.
SMG wrote: Mon Feb 05, 2024 12:51 pmOne would only add the information to a config file if the resolution works during one's initial test. I don't endorse making changes like that without testing them first.
I figured that was why you said something to the effect of "try that and get back to me" in that other thread you linked to. Wise of course.
SMG wrote: Mon Feb 05, 2024 12:51 pmThe clk part of pclk likely means clock ... These clock speeds are something the graphics driver engineers handle and are not meant to be something users mess with.
Thanks, yeah I wasn't going to try to mess with that. I was just trying to get a handle on why it was that particular number that threw the error message.
SMG wrote: Mon Feb 05, 2024 12:51 pmI think rebooting will clear the added resolutions.
Rebooting did indeed clear them. They weren't added to whatever config file they needed to be to become persistent.

I am giving up for the time being and going to live in Wayland for a bit and see how it goes. I really do think the cake isn't a lie in this case. At 4k 30hz in X I was getting all kinds of screen tearing in video playback. Doesn't happen in the Wayland session which reports 4k 60hz. Now if Mint only had a way to resize window title bars and icons. Seemingly everything else can be made sufficiently large without having to resort to "200% scaling".

Thanks for all your help.
User avatar
SMG
Level 25
Level 25
Posts: 32438
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 4k at 60Hz resolution present and working in Wayland but missing from X11

Post by SMG »

driver8 wrote: Tue Feb 06, 2024 11:55 pmAt 4k 30hz in X I was getting all kinds of screen tearing in video playback. Doesn't happen in the Wayland session which reports 4k 60hz.
I've seen comments to that effect (tearing in X11 and not in Wayland) for people for whom the resolution/frequency is the same in both X11 and Wayland. It's my understanding it has to do with the underlying execution of the different protocols the two have.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Post Reply

Return to “Cinnamon on Wayland”