Noob Here - Linux Manjaro KDE - Woke up to my PC on a black log screen about 3 times now

[zab]

Hello All!

I am very very new to Linux. Running Linux Manjaro KDE.

1. I’ve left my PC on when I go to bed, wake up, and I find it on a black log screen.
2. I have my power set to not sleep / high perf.
3. I can’t get past the screen with any shortcut I’ve found. I have to hard shut down my PC with the power button, and then power back up. No issues.

I would love to know how to read the logs properly, or if anyone has context on what these logs mean and if there’s anything I can do.

Looking forward to learning and your replies! Sorry for the likely very obvious question

Here are the logs (I can’t attach images on this thread):

/dev/nvme1n1p2: recovering journal
/dev/nvme1n1p2: Clearing orphaned inode 4876145 (uid=1000, gid=1000, mode=0100644, size=28380)
/dev/nvme1n1p2: Clearing orphaned inode 4076133 (uid=1000, gid=1000, mode=0100644, size=59656)
/dev/nvme1n1p2: Clearing orphaned inode 4063880 (uid=1000, gid=1000, mode=0100644, size=44216)
/dev/nvme1n1p2: Clearing orphaned inode 4063362 (uid=1000, gid=1000, mode=0100644, size=38140)
/dev/nvme1n1p2: clean, 422578/30507008 files, 8337412/122018696 blocks

System:
  Kernel: 5.15.41-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
    root=UUID=09375df1-860a-4691-9c1c-fcc9c21c2ed6 rw quiet apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.5 tk: Qt v: 5.15.4 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX Z690-E GAMING WIFI v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1403
    date: 03/30/2022
Battery:
  Device-1: hidpp_battery_0
    model: Logitech G305 Lightspeed Wireless Gaming Mouse serial: <filter>
    charge: 100% (should be ignored) rechargeable: yes status: discharging
Memory:
  RAM: total: 31.1 GiB used: 4.17 GiB (13.4%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 12th Gen Intel Core i9-12900K bits: 64 type: MST AMCP
    arch: Alder Lake family: 6 model-id: 0x97 (151) stepping: 2 microcode: 0x1F
  Topology: cpus: 1x cores: 16 mt: 8 tpc: 2 st: 8 threads: 24 smt: enabled
    cache: L1: 1.4 MiB desc: d-8x32 KiB, 8x48 KiB; i-8x32 KiB, 8x64 KiB
    L2: 14 MiB desc: 8x1.2 MiB, 2x2 MiB L3: 30 MiB desc: 1x30 MiB
  Speed (MHz): avg: 1118 high: 3871 min/max: 800/5200:3900 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1854 2: 1872 3: 700
    4: 773 5: 700 6: 700 7: 700 8: 701 9: 800 10: 801 11: 1117 12: 823 13: 800
    14: 800 15: 700 16: 701 17: 800 18: 800 19: 800 20: 800 21: 971 22: 3871
    23: 3199 24: 1049 bogomips: 153024
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2 bts
    clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8 de
    ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni ht hwp hwp_act_window hwp_epp
    hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ida intel_pt invpcid
    invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b
    movdiri msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid pclmulqdq
    pconfig pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid
    rdrand rdseed rdtscp rep_good sdbg sep serialize sha_ni smap smep smx
    split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
    tm2 tme tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip
    vaes vme vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec
    xsaveopt xsaves xtopology xtpr
  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 and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 status: Vulnerable: eIBRS with unprivileged eBPF
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3080 Ti] vendor: Gigabyte driver: nvidia
    v: 510.73.05 alternate: nouveau,nvidia_drm non-free: 515.xx+
    status: current (as of 2022-05) arch: Ampere pcie: gen: 2 speed: 5 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.0
    chip-ID: 10de:2208 class-ID: 0300
  Device-2: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-5.3.4:14 chip-ID: 046d:082d
    class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 92 s-size: 1237x393mm (48.70x15.47")
    s-diag: 1298mm (51.1")
  Monitor-1: DP-2 pos: primary,top-right res: 2560x1440 hz: 144 dpi: 93
    size: 697x392mm (27.44x15.43") diag: 800mm (31.48") modes: N/A
  Monitor-2: HDMI-0 pos: bottom-l res: 1920x1080 hz: 60 dpi: 82
    size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.73.05 direct render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GA102 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
  Device-3: ASUSTek USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-4:2 chip-ID: 0b05:1996
    class-ID: 0300
  Device-4: Logitech HD Pro Webcam C920 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-5.3.4:14 chip-ID: 046d:082d
    class-ID: 0102 serial: <filter>
  Device-5: Focusrite-Novation Scarlett Solo (3rd Gen.) type: USB
    driver: snd-usb-audio bus-ID: 1-5.4:13 chip-ID: 1235:8211 class-ID: 0102
    serial: <filter>
  Sound Server-1: ALSA v: k5.15.41-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725
    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: 07:00.0
    chip-ID: 8086:15f3 class-ID: 0200
  IF: enp7s0 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
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-14:15 chip-ID: 8087:0032 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
  Local Storage: total: 2.29 TiB used: 412.28 GiB (17.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WDS200T1XHE-00AFY0 size: 1.82 TiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 614600WD temp: 48.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Western Digital
    model: WDS500G1XHE-00AFY0 size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 614600WD temp: 46.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Lexar model: USB Flash Drive
    size: 14.92 GiB block-size: physical: 512 B logical: 512 B type: SSD
    serial: <filter> rev: 1100 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 465.46 GiB size: 457.09 GiB (98.20%)
    used: 25.35 GiB (5.5%) fs: ext4 dev: /dev/nvme1n1p2 maj-min: 259:4
    label: N/A uuid: 09375df1-860a-4691-9c1c-fcc9c21c2ed6
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:3
    label: NO_LABEL uuid: A3CE-0192
  ID-3: /run/media/zab/data drive raw-size: 1.82 TiB size: 1.79 TiB (98.37%)
    used: 386.93 GiB (21.1%) fs: ext4 dev: /dev/nvme0n1p1 maj-min: 259:2
    label: data drive uuid: 8f7d8baa-8dbd-45a0-bec0-cf629cbe3dae
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 3.53 GiB fs: iso9660
  ID-2: /dev/sda2 maj-min: 8:2 size: 4 MiB fs: vfat label: MISO_EFI
    uuid: 2725-614A
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-4:2 info: ASUSTek USB Audio type: Audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 8 rev: 2.0
    speed: 480 Mb/s power: 100mA chip-ID: 0b05:1996 class-ID: 0300
  Hub-2: 1-5:3 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
    speed: 480 Mb/s power: 100mA chip-ID: 174c:2074 class-ID: 0900
  Device-1: 1-5.1:5 info: Logitech USB Receiver type: Keyboard,Mouse,HID
    driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 98mA chip-ID: 046d:c53f class-ID: 0300
  Device-2: 1-5.2:7 info: Apple Apple Watch charger type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s
    power: 500mA chip-ID: 05ac:1392 class-ID: 0300 serial: <filter>
  Hub-3: 1-5.3:9 info: Realtek RTS5411 Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    chip-ID: 0bda:5411 class-ID: 0900
  Device-1: 1-5.3.4:14 info: Logitech HD Pro Webcam C920 type: Video,Audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s
    power: 500mA chip-ID: 046d:082d class-ID: 0102 serial: <filter>
  Device-2: 1-5.4:13 info: Focusrite-Novation Scarlett Solo (3rd Gen.)
    type: Audio driver: snd-usb-audio interfaces: 4 rev: 2.0 speed: 480 Mb/s
    power: 500mA chip-ID: 1235:8211 class-ID: 0102 serial: <filter>
  Device-3: 1-6:4 info: STMicro 84M-RGB type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
    power: 200mA chip-ID: 0483:4050 class-ID: 0301 serial: <filter>
  Hub-4: 1-10:6 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-10.3:10 info: Corsair iCUE Commander CORE type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 1b1c:0c1c class-ID: 0300 serial: <filter>
  Hub-5: 1-11:8 info: Genesys Logic Hub ports: 3 rev: 2.0 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0608 class-ID: 0900
  Device-1: 1-11.3:12 info: Lexar Media LJDTT16G [JumpDrive 16GB]
    type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
    speed: 480 Mb/s power: 200mA chip-ID: 05dc:a81d class-ID: 0806
    serial: <filter>
  Device-2: 1-13:11 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 16mA
    chip-ID: 0b05:19af class-ID: 0300 serial: <filter>
  Device-3: 1-14:15 info: Intel AX210 Bluetooth type: Bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 8087:0032 class-ID: e001
  Hub-6: 2-0:1 info: Super-speed hub ports: 8 rev: 3.1 speed: 20 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-7: 2-4:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0
    speed: 5 Gb/s power: 8mA chip-ID: 174c:3074 class-ID: 0900
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 52 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 57%
Info:
  Processes: 448 Uptime: 22m wakeups: 3 Init: systemd v: 250 tool: systemctl
  Compilers: gcc: 12.1.0 clang: 13.0.1 Packages: pacman: 1229 lib: 334
  flatpak: 0 Shell: Bash v: 5.1.16 running-in: konsole inxi: 3.3.16

[YoungFellow]

Hello, and welcome to the forum!

@zab

/dev/nvme1n1p2: recovering journal
/dev/nvme1n1p2: Clearing orphaned inode 4876145 (uid=1000, gid=1000, mode=0100644, size=28380)
/dev/nvme1n1p2: Clearing orphaned inode 4076133 (uid=1000, gid=1000, mode=0100644, size=59656)
/dev/nvme1n1p2: Clearing orphaned inode 4063880 (uid=1000, gid=1000, mode=0100644, size=44216)
/dev/nvme1n1p2: Clearing orphaned inode 4063362 (uid=1000, gid=1000, mode=0100644, size=38140)

This part of the log is usually shown after a force shutdown or a crash, it means that the system is cleaning up the remains of deleted data:

An orphaned inode is a file that is “semi-deleted”: it has no more directory entry, but it’s still open in some process, so the data is still present on the disk

Read more here.

As for this part:

@zab

/dev/nvme1n1p2: clean, 422578/30507008 files, 8337412/122018696 blocks

Then I get this log at every boot up on my laptop and on my Manjaro VM

As it @Mirdarthos says:

@Mirdarthos

This confused the heck out of me as well. But it’s nothing to worry about. Just leave it to finish. It might feel like it takes a long time, but in reality it’s not so bad.

It’s because an fsck hook was added to the startup and shutdown of the PC. It just ensures that everything is healthy on your file system(s). I think it’ll be a bigger worry if it didn’t say clean...

So there’s nothing wrong, especially since you can boot up fine.

[zab]

Thanks for the follow-up!

This gives me a better understanding of what’s going on. This seems to be happening on my second nvme drive. I will give it time to see if it occurs again. And now I know that fsck places orphaned inodes in a lost+found directory.

Sounds like I don’t have much to be worried about here.
Coming from a windows environment, I would always crawl Event Viewer for shutdown or force power off logs. When I get a day off I’ll look through equivalent Linux Logs to see if I see anything else.

[Joe_Ge]

I got a similar problem with standby, that the screen is black, when i power it back up. Not sure, if its from the screen itself or from the software and the routines, what they are using there.

Anyway, i got it recently back all time, when i press ctrl-alt-F2 for a console screen, then switch back with ctrl-alt-F7 to the instance, where the GUI runs.
If that doesnt work, i simple restart lightdm with

sudo systemctl stop lightdm.service

then restart the GUI again with

sudo systemctl start lightdm.service

It will close your current session, but since i have XFCE, i can restore it normally and dont need to do a complete restart.

Your ‘black screen’ settings should be at settings - power management - screen, where you can complete turn off the black screen. Else, you maybe have still energy saving mode at your screen menu itself activated?