I found that I wanted a way that was a bit more knowledgeable about which sessions I wanted to keep awake. Luckily systemd has a facility for inhibiting sleep/hibernate, etc. with Inhibitor Locks and the tool systemd-inhibit.
The following will inhibit sleep:
sudo systemd-inhibit --mode=block --what=sleep tail --pid=$$ -f /dev/null
Here's a slightly more ...
Sounds like a USB3 UAS problem. Do this...
Bus 004 Device 021: ID 0480:a00c Toshiba America Inc
USB Attached SCSI (UAS) or USB Attached SCSI Protocol (UASP) is a computer protocol used to move data to and from USB storage devices such as hard drives (HDDs), solid-state drives (SSDs), and thumb drives. UAS depends on the USB protocol, and uses the standard ...
I've been having the same issue, it's extremely annoying! However I found (after days of research) a solution that may not solve the "wakeup after suspend" problem, but now my system is shutting down and restarting as it should.
Even though I can't find the original post, the site I found it from was stephenwagner.com.
Here is what they suggested ...
The similar problem has occured on my Lenovo Yoga laptop when touchscreen and stylus were not working.
Solution proposed by @pjcigan helped me with the touchscreen but not with stylus. For that, you need to restart more drivers.
sudo modprobe -r wacom
sudo modprobe -r wacom_w8001
sudo modprobe -r wacom_i2c
sudo modprobe -r wacom_serial4
I've finally found an answer/workaround. I've installed KDE Plasma (Kubuntu) and all my issues are gone!
Looks like GNOME is just buggy in combination with an Intel on-board gpu.
If anyone knows why this is the case, please let me know!
I had this same problem for my ubuntu 20.04 for driver version 460.91.
So I ran the following commands:
sudo apt purge nvidia-*
sudo apt autoremove
I did not install another version after removing these drivers.
After this, the problem was fixed.
I had a similar issue with my Asus Zenbook 13 running Ubuntu 20.04. I didn't have any drivers listed in Software & Updates > Additional Drivers (as I didn't have a dedicated GPU).
I experimented further, nonetheless, and under the Developer Options tab I checked Pre-released updates (focal-proposed). After that I updated the system (sudo apt update &...
The solution I'm using is a udev rule that disables wakeup from a particular USB device. It should be agnostic to which port the device is plugged in to.
Create /etc/udev/rules.d/90-usb-wakeup.rules with the following content (modify idVendor and idProduct as appropriate, see output from lsusb):
# Disable waking up from Logitech unified receiver
If you installed mate desktop after you installed vanilla Ubuntu then you have to remove GNOME desktop so that the login screen will be the Mate Lock screen.
Then, you can go to your settings System>Preferences>Look and Feel>Screensaver> Then tick "Lock screen when screensaver is active".
modprobe doesn't help here, the best chance is to reset the USB bus for this malfunctioning or missing device.
Look for the USB ID in the form of VID:PID of the device with lsusb. Install usbutils and issue usbreset VID:PID. After this, the device should be functioning again without unplugging and replugging. The bus reset is not exactly equal, but should be ...
This is something that I have seen in the past on an HP ProBook and a Dell Precision notebook. The issue came down to the machine not quite going to sleep and, because it wasn't sleeping, it couldn't be woken with a keypress from an external keyboard. Like your machine, though, the built-in keyboard would allow the machine to resume. In the end, the solution ...
The various modprobe solutions didn't work for me. What did work was switching to a text-only tty and then back to graphics, with Ctrl+Alt+F3 and then Ctrl+Alt+F2. Note that switching to a different graphical session with Ctrl+Alt+F1 and then back to my original graphical session with Ctrl+Alt+F2 didn't work.
Note: the F<number>s for your system might ...
I have the same laptop and the exact same problem. Been trying to figure it out for the past week. Same results in shutdown logs. Spent some time chasing various errors in the logs (cpufreq, Disk unmount errors, LUKS, fsck, etc), but didn't make a difference. I was able to revert back to kernel 188.8.131.52-generic and everything was back to normal. That ...
Since UEFI version 1.30, the patch given in the accepted answer is no longer needed. To enable sleep mode under Linux with the latest BIOS, reboot your laptop and in the BIOS settings under "Config", change the "Sleep State" setting to "Linux" instead of "Windows 10".
Finally, with the ...
I was able to fix this (after trying lots of different fixes and progressively making this worse) by getting a fresh install of Ubuntu 20.04 LTS and choosing to use kernel 5.11.0-27-generic (which came with the install) instead of the newer 5.11.0-43-generic that is the default at the time of writing. So maybe it was a kernel problem all along and I just ...
Add the following two lines to your systemd script:
I have not tried this. So, it may not work. Please see all the links below and try other solutions listed there.
Same issue on Lenovo laptop after a recent system update. This was not an issue before the recent system update.
The system has only AMD integrated GPU, so Nvidia drivers won't help. The HDMI connected screen works fine after unlock, so the noise appears only on the laptop's own monitor.
The issue is with a bug in the AMD GPU driver that ships with Linux ...
I know that this is an old post, but I frequented this constantly over the last few weeks trying to find an answer and I thought hopefully someone else will come along like me and see this instead.
In Terminal I ran uname -sr and it returned Linux 5.13.0XXXXXXX-generic
I then went to here and scrolled down to the bottom.
This is the different updates for ...
With a suitable cable, you can connect an HDMI monitor to a DisplayPort output and it will work fine. (Note: the other way round will not work.)
Is Ubuntu fully updated?
Is the system firmware fully up-to-date?
For odd, hard-to-trace issues concerning power management, including suspend/resume and hibernate/wake, my 1st recommended step is always simply this: check that your system firmware is current, and if it's not, update it.
This resolves a lot of such problems, in my experience.
During shut down, many things happen, including properly writing out data cached in the computer memory (RAM) to partitions on disk and closing these partitions. That is why a system should always be properly shut down before powering it off.
Powering off the system without shutting it down should be avoided at any price. This may or may not cause heavy ...
Since devices are more and specific to the Windows OS and the native binary NVIDIA driver mediocre at best you might have chance to make the acpi parts needed by nvidia get running again. Here is a pretty detailed explanation.
Basically you should try to tell a part of the firmware, that you are "window" device.
Open a terminal and type:
sudo nano /...
I was experiencing exactly the same thing on Lenovo L15 AMD flavor (integrated AMD Radeon).
Same thing that this issue started to appear very recently (few weeks ago) after system upgrades.
I am also running on an encrypted SSD but I haven't done any firmware upgrades. But this is not related to the GPU driver issue.
The real issue is with Linux kernel ...
In modern systemd systems, you can also use the ssh.socket service together with systemd-inhibit. Instead of running the usual ssh.service standalone, you can let systemd manage the incoming connections. Each open session now gets handled by ssh.socket which creates the instance units based on ssh@.service, so it is just a matter creating a service that ...