Hi Garudalinux users,
I am still new to garudalinux and discourse forums, and am very grateful, that out of a few distros that I have tried, garudalinux instantly booted a desktop, right from the installer AND after the first reboot.
Now I need some help:
I ran into some problems, one screen didn’t get seen in xrandr at first at all, it is in standby modus and stays there. When I manually turned it on from standby it became visible in xrandr output, but stayed black, even when I tried to give it a secondary role.
I have found the Display Manager multi-monitor configuration tutorial and a follow up on it here:
Multi-monitor Xsetup script not working after sleep
I am trying to connect two screens to my newly installed garuda system.
One screen stays black, at first I did not even get an output from xrandr.
╰─λ garuda-inxi
System:
Kernel: 6.9.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=e7cb1af2-f296-4590-a4ed-6dc38ab8187b rw rootflags=subvol=@
nvidia-drm.modeset=1 quiet
resume=UUID=7aa0d346-898d-4481-b614-c00ddc0a0872 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.3 tk: Qt v: N/A info: frameworks v: 6.4.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7E26 v: 1.0
serial: <superuser required>
Mobo: Micro-Star model: B650 GAMING PLUS WIFI (MS-7E26) v: 1.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.F1 date: 07/08/2024
Battery:
Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 5 7500F bits: 64 type: MT MCP arch: Zen 4 gen: 5
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 6 MiB desc: 6x1024 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 545 min/max: 545/5074 scaling: driver: amd-pstate-epp
governor: powersave cores: 1: 545 2: 545 3: 545 4: 545 5: 545 6: 545 7: 545
8: 545 9: 545 10: 545 11: 545 12: 545 bogomips: 88799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA AD106 [GeForce RTX 4060 Ti] vendor: Micro-Star MSI
driver: nvidia v: 555.58.02 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-06) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 8
ports: active: none off: DP-1,DP-3 empty: DP-2,HDMI-A-1 bus-ID: 01:00.0
chip-ID: 10de:2803 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.1
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia d-rect: 3840x1080
display-ID: 0
Monitor-1: DP-1 pos: primary,left res: 1920x1080 size: N/A modes: N/A
Monitor-2: DP-3 pos: right res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: zink inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
memory: 15.62 GiB display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 1 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 4060 Ti driver: nvidia v: 555.58.02 device-ID: 10de:2803
surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA AD106M High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
bus-ID: 01:00.1 chip-ID: 10de:22bd class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 10:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.9.10-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.2.1 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: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 0c:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp12s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 0d:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp13s0 state: down mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:4 chip-ID: 0e8d:0616
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 931.51 GiB used: 30.58 GiB (3.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD Blue SN580 1TB 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: 281010WD temp: 41.9 C scheme: GPT
Partition:
ID-1: / raw-size: 897.17 GiB size: 897.17 GiB (100.00%)
used: 30.58 GiB (3.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 897.17 GiB size: 897.17 GiB (100.00%)
used: 30.58 GiB (3.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 897.17 GiB size: 897.17 GiB (100.00%)
used: 30.58 GiB (3.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 897.17 GiB size: 897.17 GiB (100.00%)
used: 30.58 GiB (3.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.95 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.05 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 40.9 C mobo: 34.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.95 GiB used: 4.32 GiB (14.0%)
Processes: 366 Power: uptime: 32m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.34 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1603 libs: 429 tools: octopi,pamac,paru
Compilers: clang: 18.1.8 gcc: 14.1.1 Shell: garuda-inxi default: fish
v: 3.7.1 running-in: konsole inxi: 3.3.35
Garuda (2.6.26-1):
System install date: 2024-07-14
Last full system update: 2024-07-21 ↻
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
Failed units:
xrandr output now with second screen in standby mode
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
DP-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
When I now turn on the other screen both screens go black and no more KDE visible, just plain black, I am not sure where I am, so when I enter CTRL+ALT+F1 nothing happens (no tty) CTRL+ALT+F2 opens a black screen but with mousepointer, which I can control, but can do nothing else, I have to hit CTRL+ALT+F3 twice to go back to tty3.
The same happens when I log in as user and type startx
or do garuda-inxi from tty3 (remaining screen going black and even in standby)
the second screen is not waking up at all.
I had the situation that I could detect the second screen and with manage-displays (Anzeige-einrichtung) could asign it the role to extend into some direction or mirror the main display, however it always stayed black and didn’t go into active-mode.
two identical screens both connected to DP on the GPU. The two Ports on the main board do not seem to react at all, (the CPU doesn’t have internal graphics)
https://www.amd.com/en/products/processors/desktops/ryzen/7000-series/amd-ryzen-5-7500f.html
Now, when I do
startx
out of that state above, I find following errors in Xorg.0.log:
https://paste.debian.net/1323972/
Probably the relevant output in that paste above being:
9.135] (II) LoadModule: "nouveau"
[ 9.136] (WW) Warning, couldn't open module nouveau
[ 9.136] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 9.136] (II) LoadModule: "nv"
[ 9.136] (WW) Warning, couldn't open module nv
[ 9.136] (EE) Failed to load module "nv" (module does not exist, 0)
[ 9.138] (II) LoadModule: "fbdev"
[ 9.138] (WW) Warning, couldn't open module fbdev
[ 9.138] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 9.138] (II) LoadModule: "vesa"
[ 9.138] (WW) Warning, couldn't open module vesa
[ 9.138] (EE) Failed to load module "vesa" (module does not exist, 0)
I am a little hesitant modifying my config files, since that messed up the system completely before with debian… So that I did not even get a tty running afterwards, and had to re-install…
I thought that I do not need nouveau, as I am using the proprietary nvidia drivers, and I have no idea what to do next…
.