Non-resuming of display after suspending in 6.13.8-2, but 6.13.5 rt does slowly?

Been having issues with getting the display to revive the GUI after suspending the machine. It affected my TW install in kernels newer than 6.12.6, but Manjaro soldiered on into 6.13.5 -rt . . . but flames out with 6.13.8-2. The machine boots and runs the system fine until suspending. Then when trying to wake up from suspend, the machine starts up, but the display stays black.

Since the problem started in TW back in January there hasn’t been too much success in diagnosing the problem, only solutioni has been to essentially lock in 6.12.6. This problem has been recurring for quite awhile; usually the solution has been to move the kernel forward to the Backport kernel. But in the case of TW, the newer kernels have not offered the solution.

As a relative newbie to Manjaro I don’t have too much background that I can use to troubleshoot the problem . . . question is, why, on the same “legacy” machine, can I run a system with a newer kernel in Manjaro, but those same approx. kernels will not revive the display in TW?? And then, now, with the latest 6.13 it does not. I believe I did awhile back test the Manjaro 6.14 kernel, but that did not help.

I have a '12 Mac Mini that just uses mobo graphics and that will revive from suspend in what I believe is the 6.13.8 option, the '12 Mac Pro is running out of gas on the lastest standard kernels. Any thoughts on work arounds would be appreciated.

~]$ inxi -zv8
System:
  Kernel: 6.13.0-3-rt5-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.13-rt-x86_64
    root=UUID=4b916772-18f6-4b7c-b47c-eb0fa3796eff rw quiet
    udev.log_priority=3
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: light-locker vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Apple product: MacPro5,1 v: 0.0
    serial: <superuser required> Chassis: type: 7 v: Mac-F221BEC8
    serial: <superuser required>
  Mobo: Apple model: Mac-F221BEC8 serial: <superuser required>
    uuid: <superuser required> UEFI: Apple v: 138.0.0.0.0 date: 07/30/2018
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.61 GiB used: 4.05 GiB (26.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 4 EC: Single-bit ECC
    max-module-size: 16 GiB note: est.
  Device-1: DIMM 1 type: DDR3 detail: N/A size: 4 GiB speed: 1066 MT/s
    volts: N/A width (bits): data: 64 total: 72 manufacturer: 0x85F7
    part-no: 0x463732353155363246393333334700520000 serial: <filter>
  Device-2: DIMM 2 type: DDR3 detail: N/A size: 4 GiB speed: 1066 MT/s
    volts: N/A width (bits): data: 64 total: 72 manufacturer: 0x85F7
    part-no: 0x463732353155363246393333334700520000 serial: <filter>
  Device-3: DIMM 3 type: DDR3 detail: N/A size: 4 GiB speed: 1066 MT/s
    volts: N/A width (bits): data: 64 total: 72 manufacturer: 0x85F7
    part-no: 0x463732353155363246393333334700520000 serial: <filter>
  Device-4: DIMM 4 type: DDR3 detail: N/A size: 4 GiB speed: 1066 MT/s
    volts: N/A width (bits): data: 64 total: 72 manufacturer: 0x85F7
    part-no: 0x463732353155363246393333334700520000 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Xeon W3565 bits: 64 type: MT MCP arch: Nehalem level: v2
    built: 2008-10 process: Intel 45nm family: 6 model-id: 0x1A (26) stepping: 5
    microcode: 0x1D
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1596 min/max: 1596/3325 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 1596 2: 1596 3: 1596
    4: 1596 5: 1596 6: 1596 7: 1596 8: 1596 bogomips: 51068
  Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
    cpuid cx16 cx8 dca de ds_cpl dtes64 dtherm dts ept est flexpriority
    flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor msr
    mtrr nonstop_tsc nopl nx pae pat pbe pdcm pebs pge pni popcnt pse pse36
    pti rdtscp sep ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc vme vmx vnmi vpid xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow 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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; 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 GK110 [GeForce GTX 780] vendor: eVga.com. driver: nouveau
    v: kernel non-free: series: 470.xx+ status: legacy-active (EOL~2024-09-xx)
    arch: Kepler-2 code: GKxxx process: TSMC 28nm built: 2012-2018 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 2 speed: 5 GT/s ports:
    active: HDMI-A-1 empty: DP-1,DVI-D-1,DVI-I-1 bus-ID: 05:00.0
    chip-ID: 10de:1004 class-ID: 0300 temp: 41.0 C
  Display: x11 server: X.Org v: 21.1.16 compositor: xfwm4 v: 4.20.0 driver:
    X: loaded: modesetting alternate: fbdev,vesa dri: nouveau gpu: nouveau
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1280x1024 s-dpi: 96 s-size: 338x270mm (13.31x10.63")
    s-diag: 433mm (17.03")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: ViewSonic VA951S
    serial: <filter> built: 2014 res: mode: 1280x1024 hz: 60 scale: 100% (1)
    dpi: 86 gamma: 1.2 chroma: red: x: 0.655 y: 0.333 green: x: 0.322 y: 0.608
    blue: x: 0.149 y: 0.059 white: x: 0.314 y: 0.329
    size: 376x301mm (14.8x11.85") diag: 482mm (19") ratio: 5:4
    modes: 1280x1024, 1920x1080, 1280x960, 1280x800, 1152x864, 1280x720,
    1024x768, 832x624, 800x600, 720x480, 640x480, 720x400
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
  Info: Tools: de: xfce4-display-settings x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel 82801JI HD Audio driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:3a3e class-ID: 0403
  Device-2: NVIDIA GK110 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    link-max: gen: 2 speed: 5 GT/s bus-ID: 05:00.1 chip-ID: 10de:0e1a
    class-ID: 0403
  API: ALSA v: k6.13.0-3-rt5-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.4.1 status: off tools: pw-cli
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: active with:
    1: pulseaudio-alsa type: plugin 2: pulseaudio-jack type: module
    tools: pacat,pactl,pavucontrol
Network:
  Device-1: Intel 82574L Gigabit Network driver: e1000e v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 09:00.0 chip-ID: 8086:10f6
    class-ID: 0200
  IF: enp9s0 state: down mac: <filter>
  Device-2: Intel 82574L Gigabit Network driver: e1000e v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 0a:00.0
    chip-ID: 8086:10f6 class-ID: 0200
  Device-3: Broadcom BCM4322 802.11a/b/g/n Wireless LAN
    vendor: Apple AirPort Extreme driver: wl v: kernel modules: ssb pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 0d:00.0 chip-ID: 14e4:432b class-ID: 0280
  IF: wls5 state: dormant mac: <filter>
  IF-ID-1: enp10s0 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,wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Apple Built-in Bluetooth 2.0+EDR HCI driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 5-1.1:3
    chip-ID: 05ac:8215 class-ID: fe01 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 4 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.74 TiB used: 48.16 GiB (1.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT1000MX500SSD1
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 032 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM010-2EP102
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC43 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD10EZEX-00BN5A0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 3.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
    fw-rev: 1A01 scheme: GPT
  ID-4: /dev/sdd maj-min: 8:48 vendor: SanDisk model: Ultra size: 14.61 GiB
    block-size: physical: 512 B logical: 512 B type: USB rev: 2.1 spd: 480 Mb/s
    lanes: 1 mode: 2.0 tech: N/A serial: <filter> fw-rev: 1.00 scheme: MBR
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RW GH80N rev: PL04
    dev-links: cdrom
  Features: speed: 32 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r state: running
Partition:
  ID-1: / raw-size: 48.26 GiB size: 47.21 GiB (97.81%) used: 21.6 GiB (45.8%)
    fs: ext4 dev: /dev/sdb7 maj-min: 8:23 label: N/A
    uuid: 4b916772-18f6-4b7c-b47c-
  ID-2: /boot/efi raw-size: 286 MiB size: 285.4 MiB (99.79%)
    used: 7.3 MiB (2.6%) fs: vfat dev: /dev/sda5 maj-min: 8:5 label: N/A
    uuid: E592-
  ID-3: /home raw-size: 90.04 GiB size: 88.07 GiB (97.81%)
    used: 26.55 GiB (30.1%) fs: ext4 dev: /dev/sdb10 maj-min: 8:26 label: N/A
    uuid: 64c5dba2-bacd-4459-9904-
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 13.06 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/sdb11 maj-min: 8:27 label: N/A
    uuid: 01988475-fd31-486a-a258-
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 200 MiB fs: vfat label: EFI
    uuid: 67E3-
  ID-2: /dev/sda10 maj-min: 8:10 size: 155.52 GiB fs: ext4 label: N/A
    uuid: 50f7f65f-5963-49a9-b091-
  ID-3: /dev/sda2 maj-min: 8:2 size: 309.92 GiB fs: hfsplus
    label: High Sierra uuid: a2775dc9-eb23-316b-a4d8-
  ID-4: /dev/sda3 maj-min: 8:3 size: 619.9 MiB fs: hfsplus
    label: Recovery HD uuid: 4815c1b0-16a2-3b33-b224-
  ID-5: /dev/sda4 maj-min: 8:4 size: 310.4 GiB fs: hfsplus
    label: FutureShock uuid: 3a958b85-2be4-36cb-a8bc-
  ID-6: /dev/sda6 maj-min: 8:6 size: 46.57 GiB fs: ext4 label: N/A
    uuid: 907551ab-87d2-41c0-9b56-
  ID-7: /dev/sda7 maj-min: 8:7 size: 46.57 GiB fs: ext4 label: N/A
    uuid: 929e9949-2d18-424c-be4a-
  ID-8: /dev/sda8 maj-min: 8:8 size: 46.57 GiB fs: ext4 label: N/A
    uuid: 3011fcb2-1618-4d9a-975a-
  ID-9: /dev/sda9 maj-min: 8:9 size: 14.9 GiB fs: swap label: N/A
    uuid: d3f92ffb-ed1e-4f91-a030-
  ID-10: /dev/sdb1 maj-min: 8:17 size: 200 MiB fs: vfat label: EFI
    uuid: 67E3-
  ID-11: /dev/sdb2 maj-min: 8:18 size: 234.03 GiB fs: hfsplus
    label: 1Macinto uuid: 632a31b3-7430-3c28-a992-
  ID-12: /dev/sdb3 maj-min: 8:19 size: 234.03 GiB fs: hfsplus
    label: 2Macinto uuid: 93f0ad8c-baed-3a31-8811-
  ID-13: /dev/sdb4 maj-min: 8:20 size: 619.9 MiB fs: hfsplus
    label: Recovery HD uuid: 11b8a168-b278-3d38-8df7-
  ID-14: /dev/sdb5 maj-min: 8:21 size: 148.7 GiB fs: hfsplus
    label: 3MacintoMavrik uuid: ee616cc5-97f5-3568-8841-
  ID-15: /dev/sdb6 maj-min: 8:22 size: 63.73 GiB fs: ext4 label: disk2s12
    uuid: 937d2de2-907c-4aac-9ce9-
  ID-16: /dev/sdb8 maj-min: 8:24 size: 48.83 GiB fs: ext4 label: N/A
    uuid: f0aaf13b-c57b-4f2a-b606-
  ID-17: /dev/sdb9 maj-min: 8:25 size: 48.83 GiB fs: ext4 label: N/A
    uuid: ab58c2d1-47b2-4b63-
  ID-18: /dev/sdc1 maj-min: 8:33 size: 200 MiB fs: vfat label: EFI
    uuid: 67E3-
  ID-19: /dev/sdc2 maj-min: 8:34 size: 279.17 GiB fs: hfsplus
    label: MacintoUno uuid: 8037621e-c63c-3884-bfb4-
  ID-20: /dev/sdc3 maj-min: 8:35 size: 619.9 MiB fs: hfsplus
    label: Recovery HD uuid: 15f8192a-a9d0-3409-a5b9-
  ID-21: /dev/sdc4 maj-min: 8:36 size: 343.98 GiB fs: hfsplus
    label: MacintoDos uuid: 6073161c-00c1-3827-9f81-
  ID-22: /dev/sdc5 maj-min: 8:37 size: 50.97 GiB fs: ext4 label: N/A
    uuid: 9f39fc44-d590-4a43-9544-
  ID-23: /dev/sdc6 maj-min: 8:38 size: 46.57 GiB fs: ext4 label: N/A
    uuid: d4853378-2816-4678-8308-
  ID-24: /dev/sdc7 maj-min: 8:39 size: 46.57 GiB fs: ext4 label: N/A
    uuid: 17bcb813-d05e-4cc3-bcdf-
  ID-25: /dev/sdc8 maj-min: 8:40 size: 148.3 GiB fs: ext4 label: N/A
    uuid: 598d1ebe-6ad9-4491-b95a-
  ID-26: /dev/sdc9 maj-min: 8:41 size: 14.9 GiB fs: swap label: N/A
    uuid: ee6d03c4-27ea-4218-8b30-
  ID-27: /dev/sdd1 maj-min: 8:49 size: 33 MiB fs: vfat label: SG2DBOOT
    uuid: B5B2-9BB7
  ID-28: /dev/sdd2 maj-min: 8:50 size: 265 MiB fs: vfat label: SG2DISOS
    uuid: B575-ABAB
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-2: 2-0:1 info: full speed or root hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-3: 2-3:2 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
  Device-1: 2-3.1:4 info: Apple Aluminium Keyboard (ANSI) type: keyboard,HID
    driver: apple,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 05ac:024f class-ID: 0301
    serial: <filter>
  Device-2: 2-3.2:5 info: Sunplus Innovation Gaming mouse [Philips SPK9304]
    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: 98mA
    chip-ID: 1bcf:08a0 class-ID: 0301
  Device-3: 2-5:3 info: SanDisk Ultra type: mass storage driver: usb-storage
    interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 224mA chip-ID: 0781:5581 class-ID: 0806 serial: <filter>
  Hub-4: 3-0:1 info: full speed or root hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-5: 4-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-6: 5-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-7: 5-1:2 info: Broadcom BCM2046B1 USB 2.0 Hub (part of BCM2046
    Bluetooth) ports: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    chip-ID: 0a5c:4500 class-ID: 0900
  Device-1: 5-1.1:3 info: Apple Built-in Bluetooth 2.0+EDR HCI
    type: bluetooth driver: btusb interfaces: 4 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 05ac:8215
    class-ID: fe01 serial: <filter>
  Hub-8: 6-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-9: 7-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
  Hub-10: 8-0:1 info: full speed or root hub ports: 2 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1d6b:0001
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 45.0 C mobo: N/A gpu: nouveau temp: 41.0 C
  Fan Speeds (rpm): N/A gpu: nouveau fan: 990
Repos:
  Packages: pm: pacman pkgs: 1433 libs: 486 tools: pamac pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    2: https://manjaro.kurdy.org/stable/$repo/$arch
    3: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    4: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    5: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    6: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    7: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    8: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 335
  1: cpu: 200% command: ps pid: 12714 mem: 3.87 MiB (0.0%)
  2: cpu: 7.8% command: firefox pid: 2510 mem: 774.1 MiB (4.8%)
  3: cpu: 5.7% command: firefox pid: 11204 mem: 401.5 MiB (2.5%)
  4: cpu: 3.4% command: firefox pid: 4653 mem: 393.1 MiB (2.4%)
  5: cpu: 2.2% command: firefox pid: 3001 mem: 421.8 MiB (2.6%)
  Memory top: 5 of 335
  1: mem: 774.1 MiB (4.8%) command: firefox pid: 2510 cpu: 7.8%
  2: mem: 421.8 MiB (2.6%) command: firefox pid: 3001 cpu: 2.2%
  3: mem: 401.5 MiB (2.5%) command: firefox pid: 11204 cpu: 5.7%
  4: mem: 393.1 MiB (2.4%) command: firefox pid: 4653 cpu: 3.4%
  5: mem: 335.1 MiB (2.0%) command: firefox pid: 4222 cpu: 0.8%
Info:
  Processes: 335 Power: uptime: 4h 3m states: freeze,standby,mem,disk
    suspend: deep avail: s2idle,shallow wakeups: 3 hibernate: platform
    avail: shutdown, reboot, suspend, test_resume image: 6.22 GiB
    services: upowerd,xfce4-power-manager Init: systemd v: 257
    default: graphical tool: systemctl
  Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: Bash v: 5.2.37
    running-in: xfce4-terminal inxi: 3.3.38

What does TW mean or stand for?

It is not wise to use -rt kernels unless you know what you are doing and have a specific reason for it.

Apple hardware often needs special boot parameters or module options - the Arch wiki is a good source of information. Perhaps you find your model mentioned there.

1 Like

I also had waking from hibernation and from sleep then hibernate broken with kernel 6.10, 6.11 and 6.12, what worked is only 6.6.

But kernel 6.14 seems to fix the problem on my laptops using Intel iGPU.

1 Like

Did you mean resume from suspend? :wink:

Please review the following and edit your topic title to be clear and concise about the issue:

TW is openSUSE’s Tumbleweed. As far as “rt” kernel goes, I was just working backward in the GUI Manjaro kernel app from the newest 6.14, which did not work, to 6.13.8 also not working, and then the next line was the rt kernel . . . which does in fact revive the display when resuming from suspend. It isn’t a zippy revival, but it does work . . . and so does the rest of basic function.

I think I have a few kernels now installed in Manjaro . . . but so far it runs some of the 6.13 options, but TW only gets me to 6.12.6.

I’ll have to stop back on the forum to adjust the subject line to include the phrase, “resume from suspend” . . . which is what the problem is, i.e., NOT resuming from suspend in the 6.13.8-2 kernel and higher, so far.

… there are very few situations wherein a realtime kernel is either needed or recommended, especially not with the hardware you have listed.

Typically, a realtime kernel might be used for strictly high-end professional audio application, and even then, rarely.

Kernel 6.12 (LTS) is likely the optimum kernel to use with your hardware at this time. There is no pressing need to use the latest and greatest kernel; even 6.6 (LTS) is a valid choice for older hardware.

I personally use 6.12 (LTS) with 6.6 (LTS) as a failsafe. Unlike you, this system is running KDE Plasma on Wayland, with AMD graphics.


It’s possible that your issue is linked to the Nvidia graphics. Search the forum, and you might find something related.

Regards.

1 Like

Alrighty, I removed the RT kernels and 6.12.21-4 LTS was available to install, so I added that kernel.

Subject line has been edited to include “resuming” for clarification of the problem.

system logs could help shedding light on your issue

In the second of the two provided links is a howto provide system/error logs.

Not much more than speculation is possible without those.

Alrighty . . . looked at that link, found the “journalctl” command, copied it and pasted it in the console . . . kept coming back as “no file or directory” found . . . cut it down to just the “cat journalctl” and same response.

Usually that data is miles long . . . sometimes a mention of “error” is found.

Of other note, had a thread here asking about how to add/subtract kernels and the reply was, "Kernels are handled by Manjaro settings >kernel app so I have been adding and removing kernels that way.

I think the newest kernel installed was 6.13.8 . . . which I don’t think resumes from suspend . . . but, in just running a fairly large pacman upgrade . . . in there was listed a 6.13.9 kernel . . . ran it through and rebooted into it for testing purposes. TBD

Indeed, it’s usually many many lines …
however:
the command there (which I had in mind) was:
journalctl --boot=-1 --priority=3 --catalog --no-pager

the --boot= parameter can be adjusted
and
there are no cute cats in there - and also not the cat command :face_with_peeking_eye:

There is dmesg as well - but only for the current boot

That was the command that I ran . . . perhaps I self-sabotaged by putting sudo in front of it?? I just ran that straight command in my Mini’s install of Manjaro and it did return a few basic lines with some basic errors.

In passing many years on linux forums sometimes it is assumed that the command will be run as sudo . . . and sometimes as root, etc.

I’ll have to get back over to the offending Mac Pro and run it straight, as user, and then I’ll post back with the data.

sudo or not will make no difference in a standard setup - either the user account you are using has got the rights to read the journal - or it doesn’t.

dmesg is different - it always needs sudo

Perhaps make it a habit to first try without sudo - you’ll be told when and why it doesn’t do what you wanted.

systemctl ... is such a command - it will prompt you for the admin users password - no sudo needed

You may need to leave out or adjust the --priority=3 parameter - it may be too restrictive, it only prints out messages with priority “error”.

from "man journalctl"
-p, --priority=
           Filter output by message priorities or priority ranges. Takes either a single numeric or textual log level (i.e. between 0/"emerg" and 7/"debug"), or a range of
           numeric/text log levels in the form FROM..TO. The log levels are the usual syslog log levels as documented in syslog(3), i.e.  "emerg" (0), "alert" (1),
           "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7). If a single log level is specified, all messages with this log level or a lower
           (hence more important) log level are shown. If a range is specified, all messages within the range are shown, including both the start and the end value of the
           range. This will add "PRIORITY=" matches for the specified priorities.

If a command doesn’t run without sudo - just type sudo !! on the very next line
and you don’t need to go back and edit the command

1 Like

Hmm . . . so looking at what must be yesterday’s boot of Manjaro does show some “dbus FAILS” . . . . Don’t know enough to know if that has significance. It does seem to be physically more data than showed up in my other machine’s version of Manjaro . . . . I don’t use bluetooth on the desktop, so those errors aren’t critical in the daily operation.

~]$ journalctl --boot=-1 --priority=3 --catalog --no-pager
Apr 12 12:04:27 no-MacPro bluetoothd[991]: Failed to set mode: Failed (0x03)
Apr 12 12:04:40 no-MacPro dbus-broker-launch[1415]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Apr 12 12:04:49 no-MacPro lightdm[1450]: gkr-pam: unable to locate daemon control file
Apr 12 12:04:51 no-MacPro dbus-broker-launch[1487]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.
Apr 12 12:05:50 no-MacPro systemd[1467]: Failed to start Tracker file system data miner.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 571 and the job result is failed.
Apr 12 12:05:51 no-MacPro systemd[1467]: Failed to start Tracker file system data miner.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 592 and the job result is failed.
Apr 12 12:05:51 no-MacPro systemd[1467]: Failed to start Tracker file system data miner.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 613 and the job result is failed.
Apr 12 12:05:51 no-MacPro systemd[1467]: Failed to start Tracker file system data miner.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 634 and the job result is failed.
Apr 12 12:05:51 no-MacPro systemd[1467]: Failed to start Tracker file system data miner.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 655 and the job result is failed.
Apr 12 12:05:51 no-MacPro systemd[1467]: Failed to start Tracker file system data miner.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 676 and the job result is failed.
Apr 12 12:38:37 no-MacPro bluetoothd[991]: Failed to set mode: Failed (0x03)
Apr 12 12:38:37 no-MacPro pulseaudio[1702]: org.bluez.BatteryProviderManager1.UnregisterBatteryProvider() Failed: org.bluez.Error.DoesNotExist:Provider does not exist
Apr 12 12:38:37 no-MacPro bluetoothd[991]: Failed to set mode: Failed (0x03)
Apr 12 12:38:40 no-MacPro dbus-broker-launch[4033]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
░░ Subject: Invalid service file
░░ Defined-By: dbus-broker
░░ Support: https://groups.google.com/forum/#!forum/bus1-devel
░░ 
░░ A service file is a ini-type configuration file.
░░ 
░░ It has one required section
░░ named [D-BUS Service]. The section contains the required key 'Name', which
░░ must be a valid D-Bus name that is unique across all service files. It also
░░ contains at least one of the two optional keys 'SystemdService' and 'Exec',
░░ as well as optionally the key 'User'. Exec must be a valid shell command and
░░ User must be a valid user on the system.
░░ 
░░ A service file should be named after the D-Bus name it configures. That is
░░ a file containing Name=org.foo.bar1 should be named org.foo.bar1.service.
░░ For backwards compatibility, we only warn when files do not follow this
░░ convention when run as a user bus. The system bus considers this an error
░░ and ignores the service file.

If anything useful is to be gleaned from the journal, I think it is best to NOT restrict the output to --priority=3 (errors)

post the whole output to, for example,

0x0.st

journalctl --boot=-1 | curl -F 'file=@-' https://0x0.st

post the link you get back in response - it is where the whole output will be visible to you and others

1 Like

Seemed to return the link very quickly. considering it might be a large file?

https://0x0.st/8fH5.txt

[edit] In looking through that data, I see it shows the “lifecycle” of the session. What I need to try is to boot the now non-reviving 6.13.9 kernel and then suspend, and then after I have to shut down, reboot back and then run this command again. To show potential issues happening when I suspend the machine . . . . In that lonked data I don’t believe I did and then it was with the kernel that does revive, slowly, but does revive/resume.[/edit]

[edit2] done as per previous edit, suspended the machine, and it didn’t resume the display . . . w/6.13.9 . . . .
https://0x0.st/8fX1.txt [/edit]

[edit3:] Looking through the second journalctl . . . it shows getting to “suspend” but then it doesn’t show anything from when the machine spins up to resume from suspend . . . display stays black. It just shows that it “deeply suspended” and then nothing for the minute plus I was waiting for the display to come back, but didn’t. The report just ends with the suspending, nothing showing that I hit the power button to cut out of the black display. [/edit]

Today is “Manjaro” day . . . booting what was previously the last kernel that would resume from suspend, 6.12.21 . . . today that kernel failed to reinvigorate the display after what was 2.5 hours in “suspension” . . . .

Up until today that kernel would work to resume display function, albeit, slowly, it did work. Today that ask was a “heavy lift” that was half done. The machine fires up . . . it thinks about resuming the display . . . then today, nope, not doing it.