Few Linux problems are as annoying as a laptop that refuses to stay asleep. You close the lid or press suspend on Linux Mint, the screen goes dark, and two seconds later the fans spin up and the login screen is back. Or the opposite direction of the same fault: you choose suspend and nothing happens at all. Either way, something is waking the machine the moment it tries to sleep, or blocking sleep outright.
This guide works through the causes in the order they most often appear on Mint. Most instant-wake problems are fixed in the first two sections.
Quick Answer
Run cat /proc/acpi/wakeup to list devices that can wake the laptop, then disable the guilty ones, commonly USB devices, the network card, or Bluetooth, using sudo sh -c 'echo XHC > /proc/acpi/wakeup' with the device name from the list. Also check journalctl after a failed suspend to see the wake reason, update your kernel through Update Manager, and turn off Wake-on-LAN in Mint and in the BIOS. One misbehaving USB device causes most instant wakes.
First, Work Out Which Problem You Have
Suspend faults come in three flavours, and the fix depends on which one you have:
- Instant wake: The laptop suspends, then wakes within a few seconds every time.
- Random wake: It sleeps properly but wakes minutes or hours later, often in a bag.
- Refuses to suspend: You choose suspend and the screen flickers or locks, but the machine never actually sleeps.
Start with a clean test. Save your work, unplug every USB accessory, and suspend from the menu while watching the power light, which usually pulses slowly while suspended. If it sleeps fine unplugged, an accessory is your culprit.
Step 1: Find and Disable Wake-Up Devices
Linux keeps a list of hardware allowed to wake the system. USB controllers, keyboards, network cards, and Bluetooth radios often sit on that list, and any one of them can fire a wake event from a tiny electrical flicker.
- Open a terminal and view the wake-up list:
cat /proc/acpi/wakeup. - Read the output. Each row starts with a device name such as
XHC,GLAN, orPEG, followed by a status of enabled or disabled. - Note the enabled devices.
XHCis the USB controller,GLANis usually the wired network, and entries mentioningRPare often PCI devices such as Wi-Fi cards. - Disable one suspect at a time. For the USB controller, run:
sudo sh -c 'echo XHC > /proc/acpi/wakeup'. - Run
cat /proc/acpi/wakeupagain and confirm that device now shows disabled. - Suspend and test. If the laptop stays asleep, you found the cause. If it still wakes instantly, re-enable nothing yet; disable the next suspect and test again.
Work through suspects one by one and note what you changed. Changing everything at once hides the real cause.
Making the change permanent
The wake-up list resets at every boot, so save a working fix. Create a small script in /usr/local/bin/ containing your disable commands and call it from a systemd unit with ExecStart pointing at the script. Test the script first, then enable the service with sudo systemctl enable followed by its name.
The official Linux Mint forums contain many model-specific suspend threads, and searching your exact laptop model there often reveals which device other owners had to disable.
Step 2: Read the Log After a Failed Suspend
Guessing is slow. The system journal usually records why a suspend failed or what woke the machine.
- After an instant wake, open a terminal straight away.
- Review the recent power events:
journalctl -b 0 | grep -i -E 'suspend|wake|PM:'. - Look for lines about suspend entry, suspend exit, and any device named near a wake message.
- If a driver reports it cannot suspend, note its name. A failing driver explains the refuses-to-suspend flavour, because the kernel cancels sleep when a device will not power down.
- Try suspending from the terminal with
systemctl suspendand watch for error messages printed immediately.
If the logs point at one driver, the fix is usually updating or changing it, which the next section covers.
Step 3: Update the Kernel and Drivers in Mint
Mint makes kernel changes safer than most distributions, because Update Manager lets you install and roll back kernels graphically. Laptops often sleep properly on a newer kernel after failing on an older one.
- Open Update Manager and apply normal updates first.
- Open the View menu and choose Linux Kernels.
- Install the newest kernel in the currently supported series, then reboot into it.
- Test suspend several times, including with your usual accessories attached.
- Open Driver Manager and check for a recommended alternative driver for your Wi-Fi or graphics hardware if suspend still fails.
- If the new kernel makes things worse, reboot, choose the previous kernel from the boot menu’s advanced options, and remove the new one in Update Manager.
Also check your laptop maker’s BIOS updates, since makers quietly fix sleep bugs there. Apply them only from the maker’s official page for your exact model.
If you also run Ubuntu on another machine, the device-hunting approach in our guide to checking which device keeps waking an Ubuntu laptop from sleep uses the same commands and pairs well with this one.
Step 4: Turn Off Network and Bluetooth Wakes
Wake-on-LAN lets the network card wake the machine on a special packet, and some drivers wake on almost any traffic. Bluetooth devices can also reconnect and wake the system.
- In Mint, open your network connection settings and disable Wake-on-LAN for the wired connection if you never use it.
- Check the BIOS setup for Wake-on-LAN and wake-from-USB options and turn off the ones you do not need.
- Test one night with Bluetooth switched off. If the instant wakes stop, a Bluetooth accessory is reconnecting; remove and re-pair it, or leave Bluetooth off before suspending.
- For USB, test with the mouse receiver or hub unplugged. Cheap hubs and docks are frequent instant-wake offenders.
Step 5: Check the Basics That Block Suspend
If the laptop refuses to suspend at all, look at simpler blockers before deep fixes. A program can hold an inhibitor that prevents sleep, and a nearly full or faulty system disk can break the suspend process on some setups.
- List active sleep blockers:
systemd-inhibit --list. Media players and some browsers appear here while active. - Close listed programs and test suspend again.
- Check free space with
df -hand make sure your system partition is not completely full. - Disconnect external drives and test, because a failing USB drive can stall the suspend sequence.
- Try suspending from a fresh session right after login, before opening your usual programs, to separate system faults from app faults.
Common Mistakes and Useful Tips
- Disabling every wake device at once: You may fix the wake problem but lose wake-from-keyboard, and you will not know which device was guilty. Change one at a time.
- Forgetting the change resets at boot: A manual fix in
/proc/acpi/wakeuplasts only until restart. Make it permanent with a startup script or service once you know it works. - Testing with the lid and menu mixed together: Test menu suspend first with the lid open. Lid problems and suspend problems are different faults.
- Ignoring the hot bag warning sign: A laptop waking in a bag gets hot and drains its battery. Until your fix is proven over several days, suspend only on a desk, or shut down fully for travel.
- Skipping the kernel test: Many Mint suspend faults are simply an old kernel meeting new hardware. One kernel update often ends weeks of frustration.
- Leaving Wake-on-LAN on by default: If you never wake your laptop over the network, that feature is pure risk for random wakes. Turn it off in both Mint and the BIOS.
Conclusion
An instant wake on Linux Mint almost always has a name, and /proc/acpi/wakeup plus the journal will usually tell you it. Disable the guilty wake device one at a time, make the change permanent once it works, keep your kernel current through Update Manager, and switch off Wake-on-LAN and stray Bluetooth wakes. Test over a few real days, not just once, and your laptop will stay asleep until you actually want it awake.
Frequently Asked Questions
Why does my Mint laptop wake the second it suspends?
An enabled wake-up device is almost always firing immediately, most often the USB controller reacting to a hub, receiver, or dock, or the network card with Wake-on-LAN active. List devices with cat /proc/acpi/wakeup and disable suspects one at a time, testing after each change.
Is suspend the same as hibernate on Linux Mint?
No. Suspend keeps your session in memory and uses a little power, waking in seconds. Hibernate saves the session to disk and uses no power, but wakes more slowly and is not enabled by default on Mint. Instant-wake faults described here affect suspend.
My fix works until I reboot. How do I keep it?
Wake-up settings in /proc/acpi/wakeup reset at boot. Put your working disable commands in a small script and run it at startup through a systemd service or Mint’s Startup Applications, so the fix is reapplied automatically on every boot.
Can a kernel update really fix suspend?
Yes. The kernel contains the drivers and power code that handle sleep, and laptop suspend fixes arrive regularly. Mint’s Update Manager lets you install a newer kernel and roll back safely, which makes this one of the lowest-risk fixes to try.
The laptop wakes in my bag and gets hot. What should I do now?
Stop suspending it for travel until the wake source is fixed. Shut it down fully before putting it in a bag, and work through the wake-device list at home. A machine that wakes in an enclosed bag can overheat and damage its battery.


Leave a Reply