Black screen, but cursor is still there, plus tty access

Hello!
First, I wasn’t sure if I should’ve put this in the Kernel & Hardware category, if I should’ve; sorry. ^^’

Anyway, I daily drive EndeavourOS, and it happens often during the week that my system freezes for a few seconds, resumes, then goes to a black screen. I do still see the cursor, and hear audio. But I’m forced to go to the TTY console, then reboot.

It could be a coincidence, but I think it often happens when interacting/using Electron apps, it’s not the first time that Discord screws up my distro.

inxi -FAZ output:

luxi@Endeavour ~> inxi -FAZ --no-host
System:
  Kernel: 6.0.6-zen1-1-zen arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.26.2
    Distro: EndeavourOS
Machine:
  Type: Laptop System: LENOVO product: 82B5 v: Lenovo Legion 5 15ARH05
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN
    serial: <superuser required> UEFI: LENOVO v: EUCN39WW date: 09/09/2022
Battery:
  ID-1: BAT0 charge: 46.7 Wh (82.1%) condition: 56.9/60.0 Wh (94.8%)
CPU:
  Info: 8-core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1738 min/max: 1400/2900 cores: 1: 1745 2: 1400 3: 2900
    4: 1400 5: 2900 6: 1400 7: 2900 8: 1400 9: 1397 10: 1400 11: 1397 12: 1400
    13: 1941 14: 1400 15: 1428 16: 1400
Graphics:
  Device-1: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] driver: nvidia
    v: 520.56.06
  Device-2: AMD Renoir driver: amdgpu v: kernel
  Device-3: Syntek Integrated Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: modesetting,nvidia
    dri: radeonsi gpu: amdgpu,nvidia,nvidia-nvswitch resolution:
    1: 1080x1920~60Hz 2: 1920x1080~60Hz 3: 1920x1080
  API: OpenGL v: 4.6 Mesa 22.2.1 renderer: RENOIR (renoir LLVM 14.0.6 DRM
    3.48 6.0.6-zen1-1-zen)
Audio:
  Device-1: NVIDIA driver: snd_hda_intel
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
  Device-4: Apple USB-C to 3.5mm Headphone Jack Adapter type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound API: ALSA v: k6.0.6-zen1-1-zen running: yes
  Sound Server-1: PipeWire v: 0.3.59 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: eno1 state: down mac: 00:2b:67:c7:4b:1b
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi
  IF: wlan0 state: up mac: XX:XX:XX:XX:XX:XX
  Device-3: ASIX AX88179 Gigabit Ethernet type: USB driver: cdc_ncm
  IF: eth1 state: up speed: N/A duplex: half mac: XX:XX:XX:XX:XX:XX
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb
  Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.38 TiB used: 120.6 GiB (8.6%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM512GDHTNI-87A0B
    size: 476.94 GiB
  ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB
  ID-3: /dev/sdb type: USB vendor: Samsung model: PSSD T7 size: 465.76 GiB (My EndeavourOS drive)
Partition:
  ID-1: / size: 346.23 GiB used: 120.6 GiB (34.8%) fs: btrfs dev: /dev/dm-0
  ID-2: /boot/efi size: 301.3 MiB used: 1.1 MiB (0.4%) fs: vfat
    dev: /dev/sdb2
  ID-3: /home size: 346.23 GiB used: 120.6 GiB (34.8%) fs: btrfs
    dev: /dev/dm-0
  ID-4: /var/log size: 346.23 GiB used: 120.6 GiB (34.8%) fs: btrfs
    dev: /dev/dm-0
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 58.6 C mobo: N/A gpu: amdgpu temp: 42.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 383 Uptime: 4m Memory: 15 GiB used: 3.83 GiB (25.6%) Shell: fish
  inxi: 3.3.23

Thanks in advance!

put log here…Not directly reboot in tty. see my topic/question.

What logs do you need?
Xorg, X11, etc?

search before ask.

@aida why so harsh?

I did my own research, though I couldn’t find anything.

The first one link is related to XFCE.
The second link is Plasma being completely frozen, though I’ll try to restart the display manager next time to see if it helps, though, it doesn’t prevent it from freezing.
Third link has something to go with SDDM/Login screen, which is not related for my issue either, but again I’ll try to restart the display manager next time.

I have that situation some times when waking up from sleep (my PC for sure :wink: ), but though it was more system related because my experience with sleep-mode is not flawless.

But it isn’t consistent and it is really rare. When reading different posts, it happens with plasma and xfce, so it is perhaps more x11 or kernel related. Or even systemd, wich hat some updates lately.

But how do I provide logs if it does happen again?
Because afaik, eos-log-tool only uses a GUI, there’s probably a log command for X11 and/or the kernel, but how I export them in a file then?

You could pipe the output of a command to eos-sendlog and get a URL that you can post on the forum.

Example: inxi -Faxxxz | eos-sendlog

1 Like

Alright, I’ll try that if it crashes again.
But just to confirm, you’ll need to display manager, X11, and PCI device log?

Have a look here:

https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

1 Like

harsh?really?
If search in forum, quite easy to find how to post log, similar situation, and REISUB

ok. i zipped.

you can use it in tty2, too.

Just tried, and it doesn’t work, it needs a display.
Unless I do the command like this:

sorry about that. I think we are talk about something like this sudo journalctl -b -a | eos-sendlog :rofl:

The endeavourOS community has the reputation to not directly told to go an use the search function but instead try to help and a reason why I joined this community.

You reaction:

is completely the opposite.

btw, I believe it is a Kernel thing, since I updated to 6.0.7 (testing), I hadn’t a single blackscreen. (touch wod)

why?

It gives a direct feeling of:
“they think I’m lazy, that I don’t want to make an effort…” but most of the time researches were done before an no solution was found.

Sometimes I don’t find the right answer because I search with the wrong terms. An here help is more welcome and constructive than imputations