Page 1 of 1

Low monitor resolution after transplanting MX SSD into new system

Posted: Mon Jan 02, 2023 7:39 am
by fossean
I successfully moved my MX SSD (and a couple of data hard drives) from a 10 year old system to a new machine with Windows 11 pre-installed on NVME. The old system had an Nvidia GTX 1060, the new has a Radeon RX 6700 XT. I purged the Nvidia drivers before the move.

Everything is working perfectly apart from the monitor resolution being limited to 1024 x 768. And in 'Display Configuration' the monitor is simply listed as 'default'.

This is happening with my default kernel, 5.10.0-20-amd64. If I switch to 6.0.0-13.3-liquorix-amd64, the issue is fixed. Is this simply because the hardware is not supported by the older kernel? The 6700 isn't newly released, it's been out for a couple of years. I'd rather run the default kernel as I found the temperatures to be noticeably lower.

EDIT: Probably unrelated, but the during boot with default kernel I get the error - KVM: disabled by BIOS

Code: Select all

System:    Kernel: 5.10.0-20-amd64 [5.10.158-2] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-20-amd64 
           root=UUID=<filter> ro gfxsave quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.2.1_KDE_x64 Wildflower October 5  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: Micro-Star model: B550M PRO-VDH WIFI (MS-7C95) v: 1.0 
           serial: <filter> UEFI: American Megatrends LLC. v: 2.C1 date: 07/15/2022 
CPU:       Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3 family: 19 (25) 
           model-id: 21 (33) stepping: 2 microcode: A20120A cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 88796 
           Speed: 3715 MHz min/max: 2200/4932 MHz boost: enabled Core speeds (MHz): 1: 3715 
           2: 3704 3: 4650 4: 3719 5: 3709 6: 4634 7: 4640 8: 3719 9: 3703 10: 3701 11: 3706 
           12: 4650 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, 
           RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] vendor: Gigabyte 
           driver: N/A bus-ID: 2d:00.0 chip-ID: 1002:73df class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: ati,vesa 
           unloaded: fbdev,modesetting,radeon display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm (10.7x8.0") 
           s-diag: 339mm (13.3") 
           Monitor-1: default res: 1024x768 hz: 76 
           OpenGL: renderer: llvmpipe (LLVM 14.0.5 256 bits) v: 4.5 Mesa 22.0.5 direct render: Yes 
Audio:     Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel bus-ID: 2d:00.1 
           chip-ID: 1002:ab28 class-ID: 0403 
           Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403 
           Device-3: C-Media USB-BH209A type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus-ID: 1-3:2 chip-ID: 0d8c:0012 class-ID: 0300 serial: <filter> 
           Sound Server-1: ALSA v: k5.10.0-20-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: MEDIATEK RZ608 Wi-Fi 6E 80MHz driver: N/A modules: wl bus-ID: 29:00.0 
           chip-ID: 14c3:0608 class-ID: 0280 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI 
           driver: r8169 v: kernel port: f000 bus-ID: 2a:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-4:3 
           chip-ID: 0bda:8771 class-ID: e001 serial: <filter> 
           Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1 
           sub-v: 8a6b hci-v: 5.1 rev: ca9 
           Info: acl-mtu: 1021:5 sco-mtu: 255:11 link-policy: rswitch hold sniff park 
           link-mode: slave accept service-classes: rendering, capturing, object transfer, audio 
           Device-2: MediaTek Wireless_Device type: USB driver: btusb v: 0.8 bus-ID: 1-9:8 
           chip-ID: 0e8d:0608 class-ID: e001 serial: <filter> 
           Report: ID: hci1 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no 
           software: no address: <filter> 
           Info: acl-mtu: 0:0 sco-mtu: 0:0 link-mode: slave accept 
Drives:    Local Storage: total: 3.33 TiB used: 1.29 TiB (38.7%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 model: SOLIDIGM SSDPFKNU010TZ size: 953.87 GiB 
           block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 001C temp: 24.9 C scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: CC45 scheme: MBR 
           ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD6400AAKS-22A7B2 
           size: 596.17 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A 
           serial: <filter> rev: 3B01 scheme: MBR 
           ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WDS100T2B0A-00SM50 
           size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD 
           serial: <filter> rev: 20WD scheme: MBR 
Partition: ID-1: / raw-size: 29.3 GiB size: 28.67 GiB (97.86%) used: 18.28 GiB (63.8%) fs: ext4 
           dev: /dev/sdc5 maj-min: 8:37 
           ID-2: /home raw-size: 901.22 GiB size: 886.01 GiB (98.31%) used: 570.83 GiB (64.4%) 
           fs: ext4 dev: /dev/sdc6 maj-min: 8:38 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 915 MiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sdc7 maj-min: 8:39 
Sensors:   System Temperatures: cpu: 52.2 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2973 lib: 1739 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ bullseye main non-free
           2: deb http://mxrepo.com/mx/repo/ bullseye ahs
           Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list 
           1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
           Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
           1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:      Processes: 312 Uptime: 0m wakeups: 1 Memory: 15.62 GiB used: 1.67 GiB (10.7%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

Re: Low monitor resolution after transplanting MX SSD into new system

Posted: Mon Jan 02, 2023 9:48 am
by Huckleberry Finn
fossean wrote: Mon Jan 02, 2023 7:39 am... resolution being limited to 1024 x 768. .
Normal because (for this or that reason) drivers are not loaded:

Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M] vendor: Gigabyte
driver: N/A bus-ID: 2d:00.0 chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: ati,vesa
unloaded: fbdev,modesetting,radeon display-ID: :0 screens: 1

Though it's ok with 6.0 kernel:

Code: Select all

sudo rm /etc/X11/xorg.conf
Reboot and try with 5.10

(it may say "no such file or directory", no harm)

Re: Low monitor resolution after transplanting MX SSD into new system

Posted: Mon Jan 02, 2023 10:08 am
by fossean
Thanks for the suggestion. I tried that and file didn't exist (pretty sure I checked that already after a search).

Re: Low monitor resolution after transplanting MX SSD into new system

Posted: Mon Jan 02, 2023 10:43 am
by Huckleberry Finn
Yes, it seems it needs most recent kernels. At least 5.11 +

Nevertheless it was still not working with 5.13 on Ubuntu (and Mint) and even with 5.19 on Fedora.


You know, you can also use the (Debian's) 6.x kernel from "MX Package Installer" ; it doesn't have to be Liquorix.

Re: Low monitor resolution after transplanting MX SSD into new system

Posted: Mon Jan 02, 2023 2:03 pm
by fossean
Thank you for the help! Saves me from obsessing about it for longer than I ought ;)

Re: Low monitor resolution after transplanting MX SSD into new system

Posted: Mon Jan 02, 2023 4:03 pm
by Stevo
Absolutely, the 6700XT requires the AHS release. Bullseye's Mesa is also too old for it, so a kernel upgrade is not enough.

Debian 11 users are up the creek with that hardware, since they don't have Mesa backports like AHS.