I have a Asus Vivobook Pro 15 OLED laptop with Intel core i7 and NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] graphics card. I installed EndeavourOS alongside windows 11 on it and everything is fully up to date. Secure boot is disabled and Fast startup is disabled in windows.
When I suspend from linux, I cannot wake the computer up again. All I see is a black screen and everything is unresponsive, there is no sound and no reaction to keys or mouse presses. After a while, the only thing my screen shows is a black screen with a hyphen ‘-’ or underscore _ ? in the top right corner. The hyphen disappears when I press Ctrl-Alt-F2. The only thing I can do is press the power button for very long and reboot the system.
Has anyone experienced this issue? I previously tried installing Ubuntu 22.04 and its problem was that NetworkManager didn’t work after suspend. I suspect from this it isn’t a distro-specific issue.
journalctl shows this since the suspend command is given and until I boot it again:
Oct 14 15:18:20 dbd-EOS systemd-logind[574]: The system will suspend now!
Oct 14 15:18:20 dbd-EOS NetworkManager[603]: <info> [1697289500.8130] manager: sleep: sleep requested (sleeping: no enabled: yes)
Oct 14 15:18:20 dbd-EOS NetworkManager[603]: <info> [1697289500.8132] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 14 15:18:20 dbd-EOS NetworkManager[603]: <info> [1697289500.8137] manager: NetworkManager state is now ASLEEP
Oct 14 15:18:20 dbd-EOS NetworkManager[603]: <info> [1697289500.8138] device (wlan0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 14 15:18:20 dbd-EOS dbus-daemon[571]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=603 comm="/usr/bin/NetworkManager --no-daemon")
Oct 14 15:18:20 dbd-EOS systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 14 15:18:20 dbd-EOS dbus-daemon[571]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 14 15:18:20 dbd-EOS systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 14 15:18:20 dbd-EOS kernel: wlan0: deauthenticating from fc:52:8d:c6:62:df by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 14 15:18:21 dbd-EOS wpa_supplicant[703]: wlan0: CTRL-EVENT-DISCONNECTED bssid=fc:52:8d:c6:62:df reason=3 locally_generated=1
Oct 14 15:18:21 dbd-EOS wpa_supplicant[703]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 14 15:18:21 dbd-EOS wpa_supplicant[703]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.0473] device (wlan0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Withdrawing address record for 2a02:2788:22a:1c5a::f on wlan0.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Withdrawing address record for 2a02:2788:22a:1c5a:7e49:edf7:683b:21e on wlan0.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.0478] dhcp4 (wlan0): canceled DHCP transaction
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2a02:2788:22a:1c5a:7e49:edf7:683b:21e.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.0479] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::32ae:efff:f1ec:faa9.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.0479] dhcp4 (wlan0): state changed no lease
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Registering new address record for fe80::32ae:efff:f1ec:faa9 on wlan0.*.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.0481] dhcp6 (wlan0): canceled DHCP transaction
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Withdrawing address record for fe80::32ae:efff:f1ec:faa9 on wlan0.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.0482] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::32ae:efff:f1ec:faa9.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.0482] dhcp6 (wlan0): state changed no lease
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Interface wlan0.IPv6 no longer relevant for mDNS.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.12.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Withdrawing address record for 192.168.0.12 on wlan0.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.1137] device (wlan0): set-hw-addr: set MAC address to F2:F8:D1:F9:A7:F2 (scanning)
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.12.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: New relevant interface wlan0.IPv4 for mDNS.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Registering new address record for 192.168.0.12 on wlan0.IPv4.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Withdrawing address record for 192.168.0.12 on wlan0.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.12.
Oct 14 15:18:21 dbd-EOS avahi-daemon[569]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.2384] device (wlan0): supplicant interface state: completed -> disconnected
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.2386] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.2386] device (wlan0): supplicant interface state: interface_disabled -> disconnected
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.2398] device (wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 14 15:18:21 dbd-EOS NetworkManager[603]: <info> [1697289501.2911] device (wlan0): set-hw-addr: reset MAC address to 48:E7:DA:A9:06:9D (unmanage)
Oct 14 15:18:21 dbd-EOS wpa_supplicant[703]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 14 15:18:21 dbd-EOS systemd[1]: Reached target Sleep.
Oct 14 15:18:21 dbd-EOS systemd[1]: Starting System Suspend...
Oct 14 15:18:21 dbd-EOS wpa_supplicant[703]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 14 15:18:21 dbd-EOS wpa_supplicant[703]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Oct 14 15:18:21 dbd-EOS systemd-sleep[1942]: Entering sleep state 'suspend'...
Oct 14 15:18:21 dbd-EOS kernel: PM: suspend entry (s2idle)
Oct 14 15:18:21 dbd-EOS kernel: Filesystems sync: 0.009 seconds
Oct 14 15:18:22 dbd-EOS kernel: rfkill: input handler enabled
The log entry for the event after the last is a boot event. So between the time sleep state ‘suspend’ and the time i shut it down, no additional events are logged.
I know it’s not a screen-specific issue because even with an external monitor the same thing happens.
If anyone can help, it’s appreciated. If not, I strongly advise against using this specific laptop model for Linux.
It looks like you’ve stumbled upon a bit of a pickle with your Asus Vivobook Pro 15 OLED on EndeavourOS. But don’t worry, we’re here to help!
The issue you’re experiencing when your laptop won’t wake up after suspending is indeed a common Linux hiccup. First, let’s rule out a few things:
Graphics Drivers: It’s often a graphics driver issue. Make sure you’re using the right NVIDIA driver. You can check what’s installed with nvidia-smi.
Kernel: The Linux kernel plays a significant role in compatibility. Make sure you’re using a recent version. You can check your kernel version with uname -r.
BIOS Update: Check if there’s a BIOS update available for your laptop. Sometimes, firmware updates can fix these types of problems.
Now, for a quick fix:
Try pressing Ctrl-Alt-F2 to switch to a different virtual terminal when it’s stuck on a black screen with an underscore (_).
If that doesn’t work, you might also try suspending with systemctl suspend from a terminal to see if it yields different results.
If all else fails, it could be a hardware-specific issue, and Linux compatibility can vary by laptop model.
Remember, Linux is all about trial and error, and sometimes it takes a bit of tinkering to get things just right.
Don’t give up on your laptop just yet! Linux community is pretty resourceful, and with a bit of patience and perseverance, you might find a workaround or a fix. And if not, there are plenty of other Linux-friendly laptops out there!
Good luck, and don’t hesitate to reach out if you have more questions!
PS: By the way, if you’re new to the world of Linux, don’t be discouraged by these initial hiccups. Linux can be incredibly rewarding once you get the hang of it!
Feel free to explore the forums, ask questions, and learn from the Linux community. There’s a wealth of knowledge out there, and we’re here to help you every step of the way. Welcome to the Linux adventure, and don’t hesitate to reach out if you need more assistance or just want to chat about all things tech!
Thanks for the quick answer!
I’ve worked with linux for a while now and have encountered many issues which I’ve been able to repair or work around. There’s no way I’ll forget or renounce using it, and that’s why I’m so bummed that this honestly expensive machine can’t run it without that major problem
I ran nvidia-smi but I’m not great at reading out technical outputs yet, here’s what I got:
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 535.113.01 Driver Version: 535.113.01 CUDA Version: 12.2 |
|-----------------------------------------+----------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+======================+======================|
| 0 NVIDIA GeForce GTX 1650 ... Off | 00000000:01:00.0 Off | N/A |
| N/A 44C P8 3W / 30W | 5MiB / 4096MiB | 0% Default |
| | | N/A |
+-----------------------------------------+----------------------+----------------------+
+---------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=======================================================================================|
| 0 N/A N/A 18473 G /usr/lib/Xorg 4MiB |
+---------------------------------------------------------------------------------------+
Apparently nothing seems to be wrong or outputting a mismatch. I’m also not sure the issue is from the GPU, because even on a black screen, some system events would be logged to the journal or the syslog, yet there’s not much on there. Do you see an issue?
As for the kernel, this is what I got: 6.5.7-arch1-1 . This seems to be a very new kernel so it’s not an issue of it being outdated. Should I switch to an LTS or Zen kernel?
Pressing Ctrl-Alt-F2 on the idle or hanging terminal just removes the underscore and brings me to an entirely black screen. There’s no response from then on, and the interaction isn’t even logged in syslog.
I’ll try systemctl suspend but from what I’ve experienced I doubt it’ll have much of an effect. Will come back with results!
Lastly, as a form of temporary workaround, is there any package or software I could use that mimics the effects of hibernation, sleep, or suspend without invoking those? Something that would make components slow down and use less resources / save power after a period of inactivity? It’s not ideal, but I’m not willing to let my machine run 24/7 with screen on.
You’re very welcome, and thanks for the detailed update!
It’s great to hear that you’re not giving up on Linux despite the challenges – that’s the spirit!
Now, let’s tackle your new findings and concerns:
NVIDIA Driver: Your NVIDIA driver version seems up-to-date, so that’s not likely the cause.
Kernel: Your kernel version is indeed current, so no need to switch to an LTS or Zen kernel in this case.
Ctrl-Alt-F2: It’s a bit puzzling that pressing those keys takes you to a black screen. It seems like there might be a deeper issue with your system.
Mimicking Sleep: While it’s not a permanent solution, you can try using tools like tlp and powertop to optimize power consumption and performance. These utilities can help extend your laptop’s battery life and make it run more efficiently when it’s not in active use.
Checking System Logs: You mentioned not finding much in the system logs during the issue. That’s a bit unusual. Still, you can try reviewing the journal logs with journalctl after the black screen issue occurs to see if there’s any additional information. The log entries around the time of the problem may provide clues.
Further Debugging: If the issue persists, you might need to do some more in-depth debugging. Tools like dmesg and syslog can sometimes reveal system anomalies, so they’re worth checking out.
Remember, Linux is all about exploration and experimentation. Even though it can be challenging at times, it’s also immensely rewarding when you conquer those hurdles.
Feel free to report back with the results of systemctl suspend, and we’ll keep brainstorming potential solutions. And if you have more questions or hit more roadblocks, just drop a line. We’re here to help!
Best of luck with your Linux journey, and kudos for your determination!
Hi, i tried systemctl suspend and the same situation was reproduced. I found out that the underscore doesn’t show up at all until I press the power button after the suspend state has started. No other key press works but this one. Seems like
Upon pressing Ctrl-Alt-F2 i found out that with Alt-F[digit] I could switch the tty. F1 showed me information about half a dozen services like NetworkManager starting up but seems to be hanging after that. No commands work, it’s like writing on a terminal while it’s running a process. After a few times switching terminals and typing out commands in the hopes of getting something, I get an unresponsive screen. Nothing moves or changes.
None of those events are even in the logs. As you can see here, I suspend the system, after it’s finished suspending it doesn’t log anything. It’s as if when woken up with the power button, it starts up a few processes (I couldn’t take a screenshot or do anything in the hung tty, sorry) but stops before it could even log the events.
Oct 14 19:04:58 dbd-EOS systemd[1]: Starting System Suspend...
Oct 14 19:04:58 dbd-EOS systemd-sleep[25033]: Entering sleep state 'suspend'...
Oct 14 19:04:58 dbd-EOS kernel: PM: suspend entry (s2idle)
Oct 14 19:04:58 dbd-EOS kernel: Filesystems sync: 0.014 seconds
Oct 14 19:04:58 dbd-EOS wpa_supplicant[734]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 14 19:04:58 dbd-EOS wpa_supplicant[734]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
-- Boot 0d42ef57bfee4a4eafbbb2473003aeb6 --
Oct 14 19:21:14 dbd-EOS kernel: microcode: updated early: 0x86 -> 0xac, date = 2023-02-27
Oct 14 19:21:14 dbd-EOS kernel: Linux version 6.5.7-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.41.0) #1 SMP PREEMPT_DYNAMIC Tue, 10 Oct 2023 21:10:21 +0000
After the last lines it just continues the usual boot log, but there are no big errors on boot so I doubt it makes sense to read those.
I’m baffled, I have no idea where the problem is or even what it is. I definitely can’t wake up my machine further than the underscore on terminal…
Thanks for the detailed update! It seems like you’re facing quite a puzzling issue.
From what you’ve described, it appears that your system is struggling to resume from suspend, and it’s hanging at a point where it should be logging critical events. This is indeed unusual.
Let’s explore some more:
NetworkManager: The fact that you see NetworkManager starting up and then hanging might suggest a potential culprit. It’s possible that there’s a conflict or issue related to your network configuration.
Kernel: While your kernel version is relatively new, there can be quirks with certain hardware and specific kernel versions. As a next step, you might want to try booting into an LTS (Long-Term Support) kernel, just to see if the issue persists. Sometimes, older kernels can be more stable for specific hardware configurations.
BIOS/UEFI Settings: Make sure to check your BIOS/UEFI settings, especially regarding power management. There might be settings there that can affect how the laptop handles suspend and resume. It’s worth poking around to see if anything stands out.
Boot Parameters: You can also try adding some boot parameters to your kernel command line to troubleshoot. Parameters like acpi=off or nomodeset might help pinpoint the issue. You can add these in your bootloader’s configuration.
Check for BIOS/UEFI Updates: Ensure your BIOS/UEFI is up to date. Manufacturers sometimes release firmware updates that address these sorts of issues.
This problem is indeed quite perplexing, and it might require some systematic troubleshooting to get to the bottom of it. Linux is fantastic, but it can be a bit finicky with certain hardware configurations.
Feel free to try these steps and let us know how it goes. And don’t hesitate to reach out if you need further assistance. We’re here to help you get your Linux adventure back on track!
But don’t worry, we’re here to help! 
