Stuck in 640x480 4:3 after hardware change/new computer

4xx Client Error 412 Precondition Failed
,
1

Hey, so I just built a new full AMD build, but I am having some issues with getting it to use the right resolution, and I am stuck with 640x480 (4:3) It’s like I don’t have the graphics driver or something similar like that.
EDIT: I am using the storage from the old computer in the new one with no reinstallation of the OS

Old Rig:
I7-8700K
GTX1080
32GB Ram
New Rig:
RX6900XT
R95900XT
64GB Ram

New rig is a completely new computer with new everything.

EDIT: I forgot to add.
Even my live USB boot drive is stuck in the same resolution, so I can’t even install a fresh Garuda installation on my new 4TB NVMe, because I can’t see the buttons at the bottom of the installation wizard window at all.

System:
Kernel: 6.12.8-zen1-1-zen arch: x86_64 bits: 64
compiler: gcc v: 14.2.1 clocksource: tsc
avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=843c3d8d-d041-4212-9b0f-69374b90a5ea rw
rootflags=subvol=@ quiet
rd.luks.uuid=1202f921-100f-4662-81fb-e8218244f935
rd.luks.uuid=6d993abc-8936-4ba6-beaa-315aed26ee40
resume=/dev/mapper/luks-6d993abc-8936-4ba6-beaa-315aed26ee40
loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A
info: frameworks v: 6.9.0 wm: kwin_x11 vt: 2 dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING
PLUS (MS-7C56) v: 4.0 serial: <superuser required>
uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.H0 date: 03/11/2024
CPU:
Info: model: AMD Ryzen 9 5900XT bits: 64 type: MT MCP
arch: Zen 3+ gen: 3 level: v3 note: check built: 2022
process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120E
Topology: cpus: 1x dies: 1 clusters: 1 cores: 16
threads: 32 tpc: 2 smt: enabled cache: L1: 1024 KiB
desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB
desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 1737 min/max: 550/4980
boost: enabled scaling: driver: amd-pstate-epp
governor: powersave cores: 1: 1737 2: 1737 3: 1737
4: 1737 5: 1737 6: 1737 7: 1737 8: 1737 9: 1737
10: 1737 11: 1737 12: 1737 13: 1737 14: 1737
15: 1737 16: 1737 17: 1737 18: 1737 19: 1737
20: 1737 21: 1737 22: 1737 23: 1737 24: 1737
25: 1737 26: 1737 27: 1737 28: 1737 29: 1737
30: 1737 31: 1737 32: 1737 bogomips: 211202
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1
sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21
[Radeon RX 6800/6800 XT / 6900 XT] vendor: ASUSTeK
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: DP-3
empty: DP-1, DP-2, HDMI-A-1, Writeback-1
bus-ID: 2d:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 21.1.15 with: Xwayland
v: 24.1.4 compositor: kwin_x11 driver: X:
loaded: amdgpu
unloaded: fbdev,modesetting,radeon,vesa
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 640x480 s-dpi: 96
s-size: 169x127mm (6.65x5.00") s-diag: 211mm (8.32")
Monitor-1: DP-3 mapped: DisplayPort-2 res: 640x480
hz: 60 size: N/A modes: 640x480
API: EGL v: 1.5 hw: drv: amd radeonsi platforms:
device: 0 drv: radeonsi device: 1 drv: swrast gbm:
drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa
v: 24.3.3-arch1.1 glx-v: 1.4 direct-render: yes
renderer: AMD Radeon RX 6900 XT (radeonsi navi21
LLVM 18.1.8 DRM 3.59 6.12.8-zen1-1-zen)
device-ID: 1002:73bf memory: 15.62 GiB unified: no
API: Vulkan v: 1.4.303 layers: 5 device: 0
type: discrete-gpu name: AMD Radeon RX 6900 XT (RADV
NAVI21) driver: N/A device-ID: 1002:73bf
surfaces: xcb,xlib
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23
HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2d:00.1
chip-ID: 1002:ab28 class-ID: 0403
Device-2: Advanced Micro Devices [AMD]
Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 2f:00.4
chip-ID: 1022:1487 class-ID: 0403
Device-3: SteelSeries ApS Arctis 7
driver: hid-generic,snd-usb-audio,usbhid type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1
bus-ID: 1-9:5 chip-ID: 1038:12ad class-ID: 0300
API: ALSA v: k6.12.8-zen1-1-zen status: kernel-api
with: aoss type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.7 status: active with:
1: pipewire-pulse status: active 2: wireplumber
status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: MEDIATEK vendor: AzureWave driver: mt7925e
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: N/A bus-ID: 05:00.0 chip-ID: 14c3:7925
class-ID: 0280
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI
Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 2a:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp42s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd,
wpa_supplicant
Bluetooth:
Device-1: IMC Networks Wireless_Device driver: btusb
v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 1-2.3:4 chip-ID: 13d3:3602
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no
software: yes address: <filter> bt-v: 5.4 lmp-v: 13
status: discoverable: no pairing: no
Drives:
Local Storage: total: 10.01 TiB used: 1.39 TiB (13.9%)
SMART Message: Unable to run smartctl. Root
privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Kingston
model: SFYRS1000G size: 931.51 GiB block-size:
physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.6
temp: 18.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Kingston
model: SFYRDK4000G size: 3.64 TiB block-size:
physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.7
temp: 18.9 C
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD2003FZEX-00SRLA0 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01
scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD2003FZEX-00SRLA0 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01
scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD2003FZEX-00SRLA0 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01
scheme: GPT
Partition:
ID-1: / raw-size: 896.8 GiB size: 896.8 GiB (100.00%)
used: 680.72 GiB (75.9%) fs: btrfs dev: /dev/dm-0
maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
ID-2: /boot/efi raw-size: 300 MiB
size: 299.4 MiB (99.80%) used: 728 KiB (0.2%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:2
ID-3: /home raw-size: 896.8 GiB
size: 896.8 GiB (100.00%) used: 680.72 GiB (75.9%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
ID-4: /var/log raw-size: 896.8 GiB
size: 896.8 GiB (100.00%) used: 680.72 GiB (75.9%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
ID-5: /var/tmp raw-size: 896.8 GiB
size: 896.8 GiB (100.00%) used: 680.72 GiB (75.9%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
Swap:
Kernel: swappiness: 133 (default 60)
cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 34.42 GiB
used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-1
maj-min: 254:1
mapped: luks-6d993abc-8936-4ba6-beaa-315aed26ee40
ID-2: swap-2 type: zram size: 62.71 GiB
used: 0 KiB (0.0%) priority: 100 comp: zstd
avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 37.2 C mobo: 21.0 C
gpu: amdgpu temp: 31.0 C mem: 28.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 64 GiB note: est. available: 62.71 GiB
used: 7.74 GiB (12.3%)
Processes: 591 Power: uptime: 28m
states: freeze,mem,disk suspend: deep avail: s2idle
wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 25.03 GiB
services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257
default: graphical tool: systemctl
Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 1948
libs: 496 tools: octopi,pamac,paru pm: flatpak pkgs: 0
Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 13
Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1.1):
System install date:     2024-02-17
Last full system update: 2025-01-11
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:
1 Like
2

Remove all nVidia stuff including drivers → reboot and check again.

3 Likes
3

It is now removed, and I have rebooted the system, here is the new garuda-inxi

System:
Kernel: 6.12.8-zen1-1-zen arch: x86_64 bits: 64
compiler: gcc v: 14.2.1 clocksource: tsc
avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=843c3d8d-d041-4212-9b0f-69374b90a5ea rw
rootflags=subvol=@ quiet
rd.luks.uuid=1202f921-100f-4662-81fb-e8218244f935
rd.luks.uuid=6d993abc-8936-4ba6-beaa-315aed26ee40
resume=/dev/mapper/luks-6d993abc-8936-4ba6-beaa-315aed26ee40
loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.5 tk: Qt v: N/A
info: frameworks v: 6.9.0 wm: kwin_x11 vt: 2 dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING
PLUS (MS-7C56) v: 4.0 serial: <superuser required>
uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.H0 date: 03/11/2024
CPU:
Info: model: AMD Ryzen 9 5900XT bits: 64 type: MT MCP
arch: Zen 3+ gen: 3 level: v3 note: check built: 2022
process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120E
Topology: cpus: 1x dies: 1 clusters: 1 cores: 16
threads: 32 tpc: 2 smt: enabled cache: L1: 1024 KiB
desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB
desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 1737 min/max: 550/4980
boost: enabled scaling: driver: amd-pstate-epp
governor: powersave cores: 1: 1737 2: 1737 3: 1737
4: 1737 5: 1737 6: 1737 7: 1737 8: 1737 9: 1737
10: 1737 11: 1737 12: 1737 13: 1737 14: 1737
15: 1737 16: 1737 17: 1737 18: 1737 19: 1737
20: 1737 21: 1737 22: 1737 23: 1737 24: 1737
25: 1737 26: 1737 27: 1737 28: 1737 29: 1737
30: 1737 31: 1737 32: 1737 bogomips: 211203
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1
sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21
[Radeon RX 6800/6800 XT / 6900 XT] vendor: ASUSTeK
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: DP-3
empty: DP-1, DP-2, HDMI-A-1, Writeback-1
bus-ID: 2d:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 21.1.15 with: Xwayland
v: 24.1.4 compositor: kwin_x11 driver: X:
loaded: amdgpu
unloaded: fbdev,modesetting,radeon,vesa
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 640x480 s-dpi: 96
s-size: 169x127mm (6.65x5.00") s-diag: 211mm (8.32")
Monitor-1: DP-3 mapped: DisplayPort-2 res: 640x480
hz: 60 size: N/A modes: 640x480
API: EGL v: 1.5 hw: drv: amd radeonsi platforms:
device: 0 drv: radeonsi device: 1 drv: swrast gbm:
drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa
v: 24.3.3-arch1.1 glx-v: 1.4 direct-render: yes
renderer: AMD Radeon RX 6900 XT (radeonsi navi21
LLVM 18.1.8 DRM 3.59 6.12.8-zen1-1-zen)
device-ID: 1002:73bf memory: 15.62 GiB unified: no
API: Vulkan v: 1.4.303 layers: 4 device: 0
type: discrete-gpu name: AMD Radeon RX 6900 XT (RADV
NAVI21) driver: N/A device-ID: 1002:73bf
surfaces: xcb,xlib
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23
HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2d:00.1
chip-ID: 1002:ab28 class-ID: 0403
Device-2: Advanced Micro Devices [AMD]
Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 2f:00.4
chip-ID: 1022:1487 class-ID: 0403
Device-3: SteelSeries ApS Arctis 7
driver: hid-generic,snd-usb-audio,usbhid type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1
bus-ID: 1-9:5 chip-ID: 1038:12ad class-ID: 0300
API: ALSA v: k6.12.8-zen1-1-zen status: kernel-api
with: aoss type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.7 status: active with:
1: pipewire-pulse status: active 2: wireplumber
status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: MEDIATEK vendor: AzureWave driver: mt7925e
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
port: N/A bus-ID: 05:00.0 chip-ID: 14c3:7925
class-ID: 0280
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI
Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 2a:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp42s0 state: down mac: <filter>
IF-ID-1: proton0 state: unknown speed: 10000 Mbps
duplex: full mac: N/A
Info: services: NetworkManager, systemd-timesyncd,
wpa_supplicant
Bluetooth:
Device-1: IMC Networks Wireless_Device driver: btusb
v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s lanes: 1
mode: 2.0 bus-ID: 1-2.3:4 chip-ID: 13d3:3602
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no
software: yes address: <filter> bt-v: 5.4 lmp-v: 13
status: discoverable: no pairing: no
Drives:
Local Storage: total: 10.01 TiB used: 1.39 TiB (13.9%)
SMART Message: Unable to run smartctl. Root
privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston
model: SFYRS1000G size: 931.51 GiB block-size:
physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.6
temp: 21.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Kingston
model: SFYRDK4000G size: 3.64 TiB block-size:
physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: EIFK31.7
temp: 20.9 C
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD2003FZEX-00SRLA0 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01
scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD2003FZEX-00SRLA0 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01
scheme: GPT
ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
model: WD2003FZEX-00SRLA0 size: 1.82 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 1A01
scheme: GPT
Partition:
ID-1: / raw-size: 896.8 GiB size: 896.8 GiB (100.00%)
used: 681.75 GiB (76.0%) fs: btrfs dev: /dev/dm-0
maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
ID-2: /boot/efi raw-size: 300 MiB
size: 299.4 MiB (99.80%) used: 728 KiB (0.2%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:2
ID-3: /home raw-size: 896.8 GiB
size: 896.8 GiB (100.00%) used: 681.75 GiB (76.0%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
ID-4: /var/log raw-size: 896.8 GiB
size: 896.8 GiB (100.00%) used: 681.75 GiB (76.0%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
ID-5: /var/tmp raw-size: 896.8 GiB
size: 896.8 GiB (100.00%) used: 681.75 GiB (76.0%)
fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-1202f921-100f-4662-81fb-e8218244f935
Swap:
Kernel: swappiness: 133 (default 60)
cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 34.42 GiB
used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-1
maj-min: 254:1
mapped: luks-6d993abc-8936-4ba6-beaa-315aed26ee40
ID-2: swap-2 type: zram size: 62.71 GiB
used: 0 KiB (0.0%) priority: 100 comp: zstd
avail: lzo-rle,lzo,lz4,lz4hc,deflate,842
max-streams: 32 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 40.5 C mobo: 23.0 C
gpu: amdgpu temp: 36.0 C mem: 32.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 64 GiB note: est. available: 62.71 GiB
used: 7.56 GiB (12.1%)
Processes: 624 Power: uptime: 2m
states: freeze,mem,disk suspend: deep avail: s2idle
wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 25.07 GiB
services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257
default: graphical tool: systemctl
Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 1884
libs: 475 tools: octopi,pamac,paru pm: flatpak pkgs: 0
Compilers: clang: 18.1.8 gcc: 14.2.1
Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1.1):
System install date:     2024-02-17
Last full system update: 2025-01-11
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:
4

The drivers are correct.

Have you tried a wayland session? Have you tried a different kernel, e.g. linux-lts?

Have you tried a different HDMI/DP port?

:thinking:
Unfortunately, the Ryzen 9 5900XT doesn’t have an iGPU - can you install the GTX1080 in the new rig to test it?

@TimRambo Please do not move threads back to the wrong category after mods have already moved your thread to the right spot. You have no problem with FireDragon!
Thanks.

2 Likes
5

Wayland is the same as X11, and I was thinking it could be maybe X11 config files that haven’t been reset maybe? I will try that kernel now.

I will try this if the kernel change does not work.

6

My apologies, won’t happen again.

7

I did try to change them but no luck, but plugging in my brand-new monitor worked right away.

I tried the LTS kernel and no luck + it didn’t even detect my wifi7 network card. I am currently on -mainline kernel. Furthermore, I used this thread Troubleshooting System Stutter, Lags, Freezes, and Hangs to install and try different kernels.

–
So I connected my new Asus monitor in, and it works fine with what it can give via HDMI, I used Xrandr to force my old acer monitor into 1080P, and it black screened. If anyone got any ideas, let me know, because I am very lost now, haha. My old monitor is an ACER XB270H.

8

which live iso you use ?
perhaps for testing
https://iso.builds.garudalinux.org/iso/community/dr460nized-lts/

3 Likes
9

The one from the garudalinux website, but I only used it to remove and install graphics drivers with chroot. I would assume that the issue is with the monitor and not the os itself.

10

That’s my suspicion too (or the DP port on the RX6900XT is faulty).

It’s an old G-Sync monitor, try resetting it to the factory settings. Unfortunately it only has one connection (DP) - can you test whether the new Asus monitor (which obviously works flawlessly with HDMI) works flawlessly with the RX6900XT via DP?

1 Like
11

All the DP and HDMI slots on my RX6900XT works flawlessly. I have tried the reset button in the monitor menu, but no luck there either. I am pretty sure it is already reset since I have already clicked the reset button that is in the OSD menu.

12

The most likely thing is that it has something to do with the old settings in KDE (or with nvidia remnants) in the new rig:

but you have the same issue with a live.iso (only default settings are set there). In both cases, the old g-sync monitor (based on its age, it should still have a built-in nvidia g-sync chip, newer models don’t have that anymore) is not recognized correctly.

Have you tried this:

Is the old monitor currently running on the old rig without issues (I7-8700K/GTX1080)?
Can you test the old monitor on another machine with an AMD GPU (for example at a friend’s)?
Another thing you can try a fresh installation with the new asus monitor and then test whether the old monitor is working correctly.

3 Likes
13

I am not able to get the card out once it is in because of its massive size. I will ask my brother if he can help me try out the different monitors only thing he does not have an AMD Gpu tough.

I was thinking of making my SSD to a bootable drive so I can see if the issues I got persist on that drive if it does not it has to be something with KDE and its configuration wanting Nvidia over AMD.

Thank you for the suggestions, I really appreciate it.

EDIT:

Forgot to add when I installed the bird of prey update freshly on my usb there was only options of nvidia in the menu before u are in the live usb OS. What is the cause there?

14

The nvidia driver is a proprietary driver and the garuda devs have this driver implemented in the live iso to install.
Reason (my mind)
Garuda Linux is designed for Gamers (not only of course) and many users are owners from a nvidia gpu. (myself also)
Without use a live iso the open-source driver nouveau (free driver) or fbdev implemented inside kernel.

15

Leave that alone for now.

:thinking:

We’ll start again from the beginning:
Download the garuda.iso again and flash it onto a USB stick using ventoy or balena.
Turn off the computer and connect the old monitor to your computer.
Boot the garuda live environment from this USB stick and select “Boot with open source drivers”:

live_boot
live_boot1393×835 82.6 KB

Can you select that? If so, will the old monitor then correctly recognized in the live environment?

If that works (as expected), then we’re back here:

Boot your installed garuda and post the output of:

pacman -Qs nvidia

Then go to kde settings → Display and Monitor, and set everything to the standard values ​​(somewhere you should also be able to disable VRR).

1 Like
16

Ventoy failed :sleepy: since some weeks, balena is a monster app.
Just use dd in terminal :slight_smile:
cdto the dir of the ISO, use lsblk -f for USB-Stick path,

lsblk -f | grep 'sd|NAME'
NAME        FSTYPE FSVER LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                      
└─sda1      ext4   1.0               94987c18-4166-4131-8c02-2d4e789613bd    6,9G     3% /run/media/sgs/94987c18-4166-4131-8c02-2d4e789613bd

change X= here to a, also use the correct Garuda ISO name :smiley:

sudo dd bs=4M if=garuda.iso of=/dev/sdX  oflag=sync status=progress
1 Like
17

Yeah, I know. A slim and simple alternative to balena is KDE isoimagewriter.

Still or already again? I’m glad I have my 2 year old Ventoy stick, the thing has never seen an update, it runs and runs and runs like a Duracell :grin:

1 Like
18

My test failed last week, and some month before.

New must not always be better.

19

Will do. Sorry about late reply, but after I removed the GPU earlier I had no video signal.:joy: I was just able to fix this by reaseating the GPU. :laughing:

I will reset the OS I am on now, and only plug in my older monitor to see if that does anything, otherwise I just got to get a new monitor.

I will update you on this here shortly. Update, so the 640 is not gone on my old monitor at all, here is the output of

pacman -Qs nvidia

> pacman -Qs nvidia
╰─λ pacman -Qs nvidia
local/libvdpau 1.5-3
Nvidia VDPAU library
local/mhwd-nvidia 565.77.3-1
NVIDIA pci id list for MHWD
local/mhwd-nvidia-390xx 390.143-1
mhwd-nvidia-390xx PCI ID database
local/mhwd-nvidia-470xx 470.94-1
mhwd-nvidia-470xx PCI ID database
local/xf86-video-nouveau 1.0.18-1 (xorg-drivers)
Open Source 3D acceleration driver for nVidia cards
20

You can leave it like that, i.e. don’t remove it. vdpau is required by ffmpeg and xf86-video-nouveau is just the nvidia open source driver (required by garuda-video-linux-config). None of this is relevant to the issue with your old monitor.

Post the output from:

ls /etc/X11/xorg.conf.d/

and:

ls /usr/share/X11/xorg.conf.d/

Have you installed the Nvidia card and tested whether the old monitor works with it?

You should first test whether the old monitor works in general, so try this first:

1 Like