NVidia - screen black after Standby and problems after screen off

Hi! I have some major problems with my graphic system.
When I put Manjaro into standby and wake it again, the screen stays black. I have to unplug the HDMI cable and plug it into another HDMI socket. Then the screen appears. The same is happening if I use a DP cable.
I also have problems with programs (like Vivaldi Browser) not showing after a standby. The icon is there and the program is running but it’s interface is not shown. Instead, the desktop image is repeated.
It’s a dual boot system with Windows 11 and there I have no such problems so the hardware should be okay.


inxi -zv8                                                                                                                                                        ✔ 
System:
  Kernel: 6.10.0-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.10-x86_64
    root=UUID=a9848445-01a9-48d8-ad7e-49eb66432441 rw rootflags=subvol=@
    nvidia_drm.fbdev=1 nvidia_drm.modset=1 udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.3.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX B550-F GAMING WIFI II v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI: American Megatrends v: 3002 date: 02/23/2023
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse PID:0085
    serial: N/A charge: 55% (should be ignored) rechargeable: yes
    status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard PID:0068
    serial: N/A charge: 55% (should be ignored) rechargeable: yes
    status: discharging
  Device-3: hidpp_battery_2 model: Logitech K520 serial: <filter>
    charge: 70% (should be ignored) rechargeable: yes status: discharging
Memory:
  System RAM: total: 64 GiB available: 62.7 GiB used: 3.02 GiB (4.8%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3666 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-4000C18-16GVK serial: N/A
  Device-2: DIMM_A2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3666 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-4000C18-16GVK serial: N/A
  Device-3: DIMM_B1 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3666 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-4000C18-16GVK serial: N/A
  Device-4: DIMM_B2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3666 MT/s volts: note: check curr: 1 min: 1 max: 1
    width (bits): data: 64 total: 64 manufacturer: G-Skill
    part-no: F4-4000C18-16GVK serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 0 microcode: 0xA201025
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 2360 high: 3600 min/max: 2200/4950 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3524 2: 2200
    3: 2200 4: 2200 5: 2639 6: 2879 7: 2200 8: 2200 9: 2200 10: 2200 11: 2200
    12: 2200 13: 2200 14: 2200 15: 2200 16: 3600 17: 2200 18: 2200 19: 2200
    20: 2200 21: 2200 22: 2200 23: 2200 24: 2200 bogomips: 177694
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm_lock syscall tce topoext tsc tsc_scale umip user_shstk
    v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq
    wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
    xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  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: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Vulnerable: Safe RET, no microcode
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA AD102 [GeForce RTX 4090] vendor: Micro-Star MSI
    driver: nvidia v: 550.100 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: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: none off: HDMI-A-1
    empty: DP-1,DP-2,HDMI-A-2 bus-ID: 07:00.0 chip-ID: 10de:2684
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.1
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 139 s-size: 702x400mm (27.64x15.75")
    s-diag: 808mm (31.81")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled
    model: LG (GoldStar) HDR 4K serial: <filter> built: 2022 res: 3840x2160
    hz: 60 dpi: 140 gamma: 1.2 chroma: red: x: 0.682 y: 0.310 green: x: 0.267
    y: 0.663 blue: x: 0.149 y: 0.047 white: x: 0.314 y: 0.329
    size: 697x392mm (27.44x15.43") diag: 806mm (31.7") ratio: 16:9
    modes: 3840x2160, 2560x1440, 1920x1080, 1280x720, 1024x768, 800x600,
    720x576, 720x480, 640x480
  EDID-Warnings: 1: parse_edid: unhandled CEA mode 97 2: parse_edid:
    unhandled CEA mode 96 3: parse_edid: unhandled CEA mode 95 4: parse_edid:
    unhandled CEA mode 94 5: parse_edid: unhandled CEA mode 93
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.100
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
    memory: 23.43 GiB
  API: Vulkan v: 1.3.279 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 4090 driver: nvidia v: 550.100 device-ID: 10de:2684
    surfaces: xcb,xlib
Audio:
  Device-1: NVIDIA AD102 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 07:00.1 chip-ID: 10de:22ba class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.10.0-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.2.1 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 14c3:0608
    class-ID: 0280
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 06:00.0
    chip-ID: 8086:15f3 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
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-5:2 chip-ID: 0e8d:0608
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.27 TiB used: 298.14 GiB (12.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 2TB size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 46.9 C scheme: GPT
  ID-2: /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
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 588.62 GiB size: 588.62 GiB (100.00%)
    used: 43.13 GiB (7.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: a9848445-01a9-48d8-ad7e-49eb66432441
  ID-2: /_DATA raw-size: 1.24 TiB size: 1.24 TiB (100.00%)
    used: 255.01 GiB (20.0%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
    label: N/A uuid: 060246b8-07a8-4549-97fd-e20db268e964
  ID-3: /_Linux_PhotoBackup raw-size: N/A size: 5.41 TiB
    used: 1.04 TiB (19.2%) fs: nfs4
    remote: 192.168.10.30:/volume1/Linux_Photobackup
  ID-4: /_SERVER_Lilly raw-size: N/A size: 5.23 TiB used: 647.86 GiB (12.1%)
    fs: nfs4 remote: 192.168.10.19:/volume1/Lilly
  ID-5: /_SERVER_PhotoBackup raw-size: N/A size: 5.23 TiB
    used: 647.86 GiB (12.1%) fs: nfs4
    remote: 192.168.10.19:/volume1/Photo_Backup
  ID-6: /_SYN_Backup_1 raw-size: N/A size: 5.41 TiB used: 1.04 TiB (19.2%)
    fs: nfs4 remote: 192.168.10.30:/volume1/Syn_Backup_1
  ID-7: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 588 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 4C23-AC80
  ID-8: /home raw-size: 588.62 GiB size: 588.62 GiB (100.00%)
    used: 43.13 GiB (7.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: a9848445-01a9-48d8-ad7e-49eb66432441
  ID-9: /var/cache raw-size: 588.62 GiB size: 588.62 GiB (100.00%)
    used: 43.13 GiB (7.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: a9848445-01a9-48d8-ad7e-49eb66432441
  ID-10: /var/log raw-size: 588.62 GiB size: 588.62 GiB (100.00%)
    used: 43.13 GiB (7.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: a9848445-01a9-48d8-ad7e-49eb66432441
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 100 MiB fs: vfat label: N/A
    uuid: 3C74-8147
  ID-2: /dev/sda2 maj-min: 8:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-3: /dev/sda3 maj-min: 8:3 size: 464.88 GiB fs: ntfs label: N/A
    uuid: C6FA7565FA755323
  ID-4: /dev/sda4 maj-min: 8:4 size: 783 MiB fs: ntfs label: N/A
    uuid: FC92887A92883AE2
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-5:2 info: MediaTek Wireless_Device type: bluetooth
    driver: btusb interfaces: 3 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 0e8d:0608 class-ID: e001 serial: <filter>
  Device-2: 1-6:3 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:1939 class-ID: 0300
    serial: <filter>
  Hub-2: 1-7:4 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Hub-3: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-4: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: Logitech Optical Wheel Mouse type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 046d:c016 class-ID: 0301
  Device-2: 3-2:3 info: Logitech LX710 Cordless Desktop Laser
    type: keyboard,mouse driver: logitech-djreceiver,usbhid interfaces: 2
    rev: 1.1 speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 98mA
    chip-ID: 046d:c517 class-ID: 0301
  Hub-5: 3-3:4 info: Genesys Logic Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 3-3.2:5 info: Evoluent VerticalMouse 4 type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
    chip-ID: 1a7c:0191 class-ID: 0301
  Device-2: 3-3.4:6 info: Logitech Unifying Receiver
    type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Hub-6: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 4-3:2 info: Genesys Logic Hub ports: 4 rev: 3.2
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 05e3:0626
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 38.1 C mobo: N/A gpu: nvidia temp: 46 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
  Packages: pm: pacman pkgs: 1272 libs: 330 tools: pamac pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    2: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    3: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    4: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    5: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
    6: http://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    7: https://mirror.yandex.ru/mirrors/manjaro/stable/$repo/$arch
    8: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    9: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    10: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    11: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    12: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    13: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    14: http://manjaro.grena.ge/stable/$repo/$arch
    15: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    16: http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    17: http://ftp.dei.uc.pt/pub/linux/manjaro/stable/$repo/$arch
    18: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
    19: https://mirrors.nic.cz/manjaro/stable/$repo/$arch
    20: https://mirror.23m.com/manjaro/stable/$repo/$arch
    21: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    22: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    23: http://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    24: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    25: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    26: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    27: https://manjaro.ynh.ovh/stable/$repo/$arch
    28: https://linorg.usp.br/manjaro/stable/$repo/$arch
    29: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    30: http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    31: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    32: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
    33: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    34: https://mirrors2.manjaro.org/stable/$repo/$arch
    35: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    36: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    37: https://mirror.albony.xyz/manjaro/stable/$repo/$arch
    38: https://mirror.funami.tech/manjaro/stable/$repo/$arch
    39: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    40: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    41: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    42: https://manjaro.kurdy.org/stable/$repo/$arch
    43: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    44: https://mirrors.xtom.de/manjaro/stable/$repo/$arch
    45: https://mirrors.tuna.tsinghua.edu.cn/manjaro/stable/$repo/$arch
    46: http://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
    47: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    48: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    49: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    50: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    51: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    52: https://mirrors.ustc.edu.cn/manjaro/stable/$repo/$arch
    53: http://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    54: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    55: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    56: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    57: http://ftp.uni-kl.de/pub/linux/manjaro/stable/$repo/$arch
    58: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    59: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    60: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    61: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
    62: https://mirror.zetup.net/manjaro/stable/$repo/$arch
    63: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
    64: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
    65: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    66: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    67: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
    68: http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    69: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    70: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    71: https://mirrors.xtom.jp/manjaro/stable/$repo/$arch
    72: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
    73: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    74: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    75: https://mirror.init7.net/manjaro/stable/$repo/$arch
    76: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    77: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    78: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    79: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    80: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    81: https://mirror.ibakerserver.pt/manjaro/stable/$repo/$arch
    82: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    83: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    84: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    85: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    86: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
Processes:
  CPU top: 5 of 453
  1: cpu: 4.5% command: vivaldi-bin pid: 1612 mem: 230.1 MiB (0.3%)
  2: cpu: 4.1% command: vivaldi-bin pid: 1579 mem: 304.2 MiB (0.4%)
  3: cpu: 3.9% command: vivaldi-bin pid: 1743 mem: 279.0 MiB (0.4%)
  4: cpu: 3.1% command: konsole pid: 2422 mem: 187.4 MiB (0.2%)
  5: cpu: 2.2% command: vivaldi-bin pid: 1539 mem: 350.4 MiB (0.5%)
  Memory top: 5 of 453
  1: mem: 477.1 MiB (0.7%) command: plasmashell pid: 1266 cpu: 1.8%
  2: mem: 350.4 MiB (0.5%) command: vivaldi-bin pid: 1539 cpu: 2.2%
  3: mem: 304.2 MiB (0.4%) command: vivaldi-bin pid: 1579 cpu: 4.1%
  4: mem: 279.0 MiB (0.4%) command: vivaldi-bin pid: 1743 cpu: 3.9%
  5: mem: 230.1 MiB (0.3%) command: vivaldi-bin pid: 1612 cpu: 4.5%
Info:
  Processes: 453 Power: uptime: 10m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 25.02 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.1.1 alt: 13 Shell: Zsh v: 5.9
    default: Bash v: 5.2.26 running-in: konsole inxi: 3.3.35

mhwd -li                                                                                                                                                         ✔ 
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
          video-nvidia            2024.05.03               false            PCI


Warning: No installed USB configs!

Hello,
Was it working before and they showed up since the last update from yesterday?

Did you try switching different Kernels?

Fast boot in Bios deactivated?

Fast startup in Windows also disabled?

Something what could also help is switching to Wayland in SDDM (bottom left login screen).

I only noticed this behavior 2 days ago. (But I have not used the machine for around 3 Weeks.)
2 days ago I replaced a failing HDMI cable (occasionally the screen went black for a second) with a DP cable. From then on I had no GRUB anymore and could not enter the BIOS either. Somehow the change activated fast boot in the BIOS. I explicitly set it to off when I installed Manjaro and I havo no idea how a cable change could invoke it again.
I needed some help here in the forum to get back GRUB to work again as that was shot by the attempts to get back my BIOS screen. That problem is solved already but now this new problem arose.
Today I made a system update and also installed a newer kernel but that doesn’t solved the Problem.
I have now a new HDMI cable (no black outs) but the problem persist.
Fast boot is now deactivated again in the Bios and GRUB is showing correctly.
I thought a fresh install of Manjaro will automatically set Wayland and I did not paid attention to that.
I will test that an report back…

EDIT:
I changed to Wayland and tested standby. That worked and the display cam back but now I have other display problems. The screen is flickering and there are tons of display problems:



Something is wrong with the display driver or some other display setting.
(I can barely type this message.)

EDIT 2: I forced a reinstall of the nvidia driver and I got these warning messages:

==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]

Are these any way relevant?

Even a driver or your OS (Win11) can mess around with your UEFI Bios.
A Bios Password could probably help there.

Offtopic
How do you manage to switch between Manjaro/Win11?

Did you had installed Win11 with tweaks (Rufus for example) to disable TPM & Secure Boot?

Or do you have different Bios Profiles when switching between Win/Linux, you go in bios to load the right profile?

The output looks normal to me, this warnings coming up on every install on a release update.

I don’t think a reinstall about the driver would help here anyways, you probably make it worse now because of the dependencies…

I hope you have a timeshift snapshot ready, when you start fiddling around.

Windows was installed by the previous owner of the machine. I installed an additional M2 SSD and installed Manjaro and followed the procedure presented by the Manjaro installation manager.

Now that I rebooted the machine, some things have changed:

  • the Manjaro boot text messages have a larger font.
  • boot screen appears okay but as soon as I enter my password it switches to a black screen with a large mouse pointer.
  • pressing CTRL-ALT-F2 switches to a higher resolution pointer (but no other screen content.)

I think, I will completely reinstall Manjaro and see if it makes a difference.
Would it make sense to ditch dual boot (GRUB) and simply choose the boot order from the BIOS if I want to switch OS?
My main OS is Manjaro but sometimes I need native Windows (not a virtual machine).

EDIT: the machine is fresh so I can reinstall Manjaro if needed.

EDIT 2: X11 brings up the desktop fine.

First things first, Linux is not Windows… so reinstall your Driver’s never will help (besides data corruption, but then you got other problem’s).

Plz stay away from that.

If the previous owner is a untrusted person, i would delete/reinstall Windows.
And i would also clean your EFI Room in Bios, i would even reset your Bios… because of the possibility from a Boot Virus.

But all this don’t help you with your blackscreen issue right now.
Im just saying it, if you want to reinstall your system.

Simply put, this should not (is not) possible. I also note comments from your previous thread:

A lot of repetition there. :wink:

A few points worth consideration, which may or may not be overly helpful at this point:

  • Use complete Display Port cables (DP to DP) rather than DP to HDMI converter cables (or similar); or the complete HDMI cable you now appear to have.
  • Your BIOS battery may be failing (typically $2 for a new one) which might explain why your BIOS settings have not been retained; and thus the subsequent loss of boot configuration mentioned in your previous thread.
  • Is it possible your mainboard has a shared port, and that both the M.2 port and the port that shares the pathway cannot be used simultaneously? A deep dive into your mainboard manual should reveal whether or not this is true in your case.

With regards the current standby issue:

You have no swap space configured. If you are confusing standby with hibernation, the latter will simply fail without swap. Even using true standby modes, swap might be beneficial.

These are only generic warnings – an annoyance that they appear, but otherwise of no consequence.


Regarding having Wayland and Nvidia coexist nicely; these links may be helpful:

I’m afraid I can’t offer much beyond that (amdgpu user here).
I wish you luck. Cheers.

1 Like

Im actually using Win10 and Manjaro on separated disk and i just press F12 Key for choosing the Disk (OS) to boot from, i never had to reinstall Grub or any boot hickups since i installed Manjaro (4 year’s) ago.

If you a gamer like me, (and i think you are, when i look at your system) i can recommend to buy a external SSD and use your NVMe for gaming instead to waste the performance on Manjaro :wink:

2 Likes

I too highly recommend using separate disks when multibooting Windows and Linux. I believe you are already doing that.

Thanks for the suggestions. :+1:
I completely factory reset Windows (as I did not had the user credentials) after I bought the machine and so all previous user content was erased. Regarding boot virus, I do not see any sign of it and as I need to use the machine and don’t have the necessary knowledge of messing with the BIOS, I rather not reset it.

Regarding the DP cable. I never use mixed cables with adapters. Either DP or HDMI. I also never would have imagined that simply changing a cable would alter a BIOS setting. As I did not do anything else, I have no other explanation for what happened.

Every other BIOS setting was retained and the MB is only 1 year old so in IMHO a failing battery is less likely.

I explicitly not set swap as the machine has 64 GB of RAM and as I know (again, consider my limited IT knowledge) swap is not recommended on SSDs.
I only use standby (which requires power to be constantly present) and never use hibernation. (Also on Windows.)

I’m not a gamer, rather a 3D “artist” and that’s why I need the machine with more graphic performance.

Windows and Manjaro are on two separate disks but the Manjaro installer used the dual boot method. I guess, this was not such a good idea.

When I reinstall Manjaro nd before doing so disconnect the Windows SSD, then Manjaro will be installed without GRUB and I can switch OSs from the BIOS boot order menu. Right?

You need to improve your Forum Skills a little, because you mismatched your response between @soundofthunder and me.

Simply quote the point and answer to the person in future. Otherwise this gets really confusing here.

1 Like

Disconnecting all other disks apart from the disk you are installing an OS to, is always recommended; this ensures no complication (example; writing to the wrong ESP) because other disks are then not present during install.

Reconnect disks only after installation has fully completed.

Manjaro will always install GRUB; (AFAIK) there is no option not to, as there is with some other distributions. Make sure os-prober is also installed and activated (OS Prober is the mechanism that detects another OS during boot).

Find further information on os-prober and other multiboot caveats in my article:

And it can get even more confusing as not everyone speaks/understands English natively. Of course it doesn’t take Einstein to appreciate that, but it gave me an excuse to use the quoting as an example.

Simply select text you wish to quote, and the quote button should appear immediately above the selection. Click quote, and the selected text appears in your post wherever the cursor happens to be. Cheers.

1 Like

I think you can already switch between your OS booting, with F12 Key (depends on the Motherboard) when booting and you don’t need Grub for that.

Under Windows your Pagefile is badly used by the OS.
Under Linux the Swapfile/Swap partition is used much better… it can’t hurt to have it activated, 5 Gbyte should be enough, as long you don’t hibernate your system.

In case you don’t want to reinstall right now, you can maybe try this to get Wayland working again.

1 Like

Swap is not heavily utilised in Linux (generally) and especially not with 64G (or greater) RAM at your disposal, however, I’d usually suggest having it if/when needed, is better than not. It actually makes good sense to have swap on the fastest medium you have.


Which kernel are you using?
I’m guessing that it might be kernel 6.9.x, or the new 6.10.x.

I seem to recall recently someone had success with a similar (Nvidia-related) issue by switching to kernel 6.6 (LTS), which helped with their Wayland-Nvidia issues.

See Manjaro Kernels for information on how to do that, if you wish to test the theory.

What you suggest is probably the solution, adding the modules to mkinitcpio and adding the kernel parameters. But there might be still some little issues on Nvidia+Wayland combo. We’ll see, it depends on the applications he uses. I would try what you suggested, but stay on X11 if it works on X11 after doing the above steps.

Uff why you using btrfs? Is btrfs set to default today on a fresh install?

Recommend for beginners is still ext4 partition… btrfs is for the advanced user’s who are aware about the pro’s & con’s.

I personally still using X11 on my Nvidia 2080Ti, i saw already a few limitation’s around Wayland (application related) with my AMD laptop, but Wayland just works better after Plasma6 update.

I think that newer nvidia Models (40X0 cards) running worse on X11 and some nvidia user’s might want to switch to Wayland because of this reason. :thinking:

I come to this conclusion after i monitored the different nvidia user’s around this forum, that there could be something different between my nvidia Gen and theirs, that shows a different behavior between X11/Wayland.

@omano
I think one X11 should be replaced with Wayland :upside_down_face:

No, however there was a recent issue which resulted in misgivings after choosing BTRFS during install. I don’t use it, so didn’t pay much attention to the specifics. This was only within the last few weeks, so a search should reveal something. I presume it should have already been addressed.


@thinman

Additionally, the black screen is a frequent issue in the forums. You might have some luck searching/reading through many of the similar issues described.

These search results may prove fruitful (using black screen waking from standby as the search terms):

Good luck.

I doubt that but maybe, I never had one on hands. For sure Wayland with Nvidia in current Plasma 6 works better than before, I didn’t initially notice I was on Wayland when the initial Plasma 6 update released on Unstable. It is when I launched Audacious (in Winamp mode) that I noticed the app was completely broken, and then I found out my system was on Wayland :smiley: I switched back to X11 and the app works good there. I switched to AMD card now, but still using X11 until Wayland is perfect.

No this is what I meant, if after adding modules to mkinitcpio (then rebuilding images) and adding kernel parameters (then rebuilding GRUB and rebooting) it works properly on X11, just stay on X11.

1 Like

So this changes improves not only for Wayland (nvidia) user’s but also for X11 user’s?