Monitors not being recognized after boot

The 2 latest days my two monitors have a hard time being recognized after either waking the computer up from sleep or from boot.

I've had this setup working without problems for about 2 months.
So I suspect that the problems comes from the Garuda update in Octopai.

Yesterday I got it working after a lot of trial and error but never figured out why.
Today I finally got it working after removing the the secondary monitor completely,
a Samsung U28E590D using DisplayPort. My main monitor is a 328E9FJAB/00 and are now using the DisplayPort for this monitor since none of the attempts with HDMI worked today.

But until today I used the DisplayPort for the Samsung monitor and a HDMI cable for my Philips main monitor without problems. I did try another HDMI cable with the problem persisting.

I don't know if this is related but another problem that is related to this (in my opinion), but that worked out in the end every time is that one of two or three open Firefox (not the Dragonized version) windows didn't show the taskbar at the top so I could not close it, minimize it or maximize it, no matter if it was maximized or not. I suspect this is a window manager problem though.

How I solved that problem was by pulling the display cable and reattaching it. Or closing my Firefox session. The latter solution I try to avoid since I sometimes lose the last session with open tabs.

System:
Kernel: 5.16.2-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=df24bdae-c083-4314-bce7-f49e58559361 rw rootflags=subvol=@
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1
resume=UUID=5d34b90d-33db-4d1a-bf97-eddb9e1e7da6 loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: B550 AORUS ELITE V2 v: x.x
serial: <superuser required> UEFI: American Megatrends v: F12
date: 01/18/2021
CPU:
Info: model: AMD Ryzen 7 PRO 4750G with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 family: 0x17 (23) model-id: 0x60 (96) stepping: 1
microcode: 0x8600106
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 8 MiB desc: 2x4 MiB
Speed (MHz): avg: 3169 high: 4147 min/max: 1400/3600 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4138 2: 3561
3: 3047 4: 2981 5: 2995 6: 2990 7: 2989 8: 2994 9: 4147 10: 2994 11: 2960
12: 2982 13: 2964 14: 2978 15: 2995 16: 2994 bogomips: 114985
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Renoir vendor: Gigabyte driver: amdgpu v: kernel
bus-ID: 0b:00.0 chip-ID: 1002:1636 class-ID: 0300
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0")
s-diag: 777mm (30.6")
Monitor-1: DisplayPort-0 res: 2560x1440 dpi: 93
size: 697x392mm (27.4x15.4") diag: 800mm (31.5")
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
v: kernel bus-ID: 0b:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel bus-ID: 0b:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k5.16.2-zen1-1-zen running: yes
Sound Server-2: PulseAudio v: 15.0 running: no
Sound Server-3: PipeWire v: 0.3.43 running: yes
Network:
Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k
v: kernel bus-ID: 05:00.0 chip-ID: 168c:002b class-ID: 0280
IF: wlp5s0 state: up mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
port: f000 bus-ID: 08:00.0 chip-ID: 10ec:8125 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152
bus-ID: 3-2.4:4 chip-ID: 0bda:8152 class-ID: 0000 serial: <filter>
IF: enp11s0f3u2u4 state: down mac: <filter>
IF-ID-1: anbox0 state: down mac: <filter>
IF-ID-2: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A
mac: <filter>
IF-ID-3: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:
Local Storage: total: 17.55 TiB used: 903.92 GiB (5.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:8 vendor: Corsair model: Force MP510
size: 894.25 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: ECFM22.7
temp: 28.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Corsair model: Force MP510
size: 894.25 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: ECFM22.7
temp: 28.9 C scheme: GPT
ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Corsair model: Force MP510
size: 894.25 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: ECFM22.6
temp: 32.9 C scheme: GPT
ID-4: /dev/nvme3n1 maj-min: 259:1 vendor: Corsair model: Force MP510
size: 894.25 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: ECFM22.7
temp: 31.9 C scheme: GPT
ID-5: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 850 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 2B6Q scheme: MBR
ID-6: /dev/sdb maj-min: 8:16 vendor: Kingston model: SA400S37960G
size: 894.25 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 1103 scheme: MBR
ID-7: /dev/sdc maj-min: 8:32 model: QNAP QDA-A2AR RAID1 size: 12.73 TiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: HDD
rpm: 7200 serial: <filter> rev: 0601 scheme: GPT
Partition:
ID-1: / raw-size: 825.54 GiB size: 825.54 GiB (100.00%)
used: 348.91 GiB (42.3%) fs: btrfs dev: /dev/nvme3n1p2 maj-min: 259:4
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme3n1p1 maj-min: 259:3
ID-3: /home raw-size: 825.54 GiB size: 825.54 GiB (100.00%)
used: 348.91 GiB (42.3%) fs: btrfs dev: /dev/nvme3n1p2 maj-min: 259:4
ID-4: /var/log raw-size: 825.54 GiB size: 825.54 GiB (100.00%)
used: 348.91 GiB (42.3%) fs: btrfs dev: /dev/nvme3n1p2 maj-min: 259:4
ID-5: /var/tmp raw-size: 825.54 GiB size: 825.54 GiB (100.00%)
used: 348.91 GiB (42.3%) fs: btrfs dev: /dev/nvme3n1p2 maj-min: 259:4
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 62.28 GiB used: 2.8 MiB (0.0%)
priority: 100 dev: /dev/zram0
ID-2: swap-2 type: partition size: 68.42 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme3n1p3 maj-min: 259:6
Sensors:
System Temperatures: cpu: 29.0 C mobo: 25.0 C gpu: amdgpu temp: 25.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 405 Uptime: 2h 21m wakeups: 0 Memory: 62.28 GiB
used: 8 GiB (12.8%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1588 lib: 368 Shell: fish
v: 3.3.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.12
Garuda:
System install date:     2021-11-18
Last full system update: 2022-01-25
Is partially upgraded:   No
Using TLP:               No
Windows dual boot:       No/Undetected

I can't exactly say what is causing your monitor issues (one monitor's manual did say to avoid adapters, but since you didn't mention that, I don't think that is the case). I know on some setups I have to be sure the monitor is on before I boot up the system.

However...
I couldn't help noticing there is a critical bios update for your motherboard from earlier this month. The site states "Major vulnerabilities updates, customers are strongly encouraged to update to this release at the earliest." https://www.gigabyte.com/Motherboard/B550-AORUS-ELITE-V2-rev-10/support#support-dl-bios

After trying out some of the commands in this thread:

I ran this in Konsole:
╭─thrillseeker@RYZEN7 in ~ took 1s
╰─λ xrandr | awk ’ /connected/ { print $1, $2 }’
HDMI-A-0 connected
DisplayPort-0 connected

I did notice that the command only recognizes if the computers outputs is connected, not if the other end of the cable is connected.

I suddenly got both monitors working again, but with the display cables switched between the monitors. So I still use the DisplayPort cable for my main monitor as of today and a HDMI cable for the Samsung monitor as of today. I also noted some flickering just after my new attempt, so I tried a third HDMI cable that is 10m long and also in another HDMI port on the Samsung monitor (note that I did try diffrent HDMI ports earlier when troubleshooting but still didn’t get it working at the time). So the problem with flickering seems to be gone.

I still need to check if the main problem is still there from waking the computer up from sleep or from boot.

1 Like

Oh I see, I will for sure look into that. I only had that motherboard for about two months as well so I didn't even consider to update it since many vendors says you shouldn't update BIOS if all works.

I see it was posted very recently, as of the 13th of January.

I just didn't think of it.

Thanks a lot!

1 Like

If you include terminal outputs in your post please
use the proper output format in your post.
Using "~" 3 times above and "~" 3 times below the text block
will provide a readable, raw look.

Please edit your posts.

and
:slight_smile:

3 Likes

Sorry, I'm not used to these commands or symbols. It's fixed now.

1 Like

I now looks like it works without problems.

I did update to the latest BIOS version but there were some hick ups I had to figure out before getting it to work without problems.

I had to change back the monitor cables so the Samsung monitor uses the DisplayPort cable and the Philips monitor uses the HDMI cable. But once again I had to change to another HDMI cable, so I suspect there was at least 2 or more problems causing these problems.

One of them being a faulty HDMI cable and another one of them being bad connectors on the Samsung monitor. Also probably some more problem that the BIOS update fixed.

It has only been like 20 minutes since I got it to work without problems so time will tell.

Can I, or do I myself need to check this thread as [Solved] or do a moderator do this?

Again, thanks a lot for your fast reply and help! :pray: :metal:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.