It's the same old story - a Linux system newly installed on
a laptop will go to sleep when the lid is closed, but doesn't
wake up properly when the lid is opened again. I've searched
the web and found dozens of messages dealing with problems
like this, with no two exactly the same and few showing a
resolution.
Here's my variant. I have a laptop belonging to a friend
who I'm trying to free from the evil clutches of Windows 10.
It's an Acer Aspire 57332-4406. I shrank the Windows partition
to half its size, booted a Debian 9.8.0_amd64 network install
CD that I had burned on another machine, and successfully
installed Debian in the freed disk partition, using mostly
default options with Xfce as the screen manager. I installed
GRUB in the MBR, setting up the machine for dual booting.
I downloaded and installed Seamonkey and made it the default
web browser. I also installed Thunderbird and successfully
copied the user's profile from the Windows partition.
The machine works fine until I close the lid and open it again.
It seems to wake up, but the screen remains black (although its
backlight is on). I can SSH into the laptop from another machine
and run it remotely. If I enter "shutdown" from the remote
machine the screen will briefly show shutdown messages before
powering down.
Running dmesg shows what looks largely like a successfull
sleep and re-awaken, although sprinkled through the wakeup
process are the following suspicious-looking messages:
ehci-pci 0000:00:1c.0: System wakeup disabled by ACPI
pcieport 0000:00:1c.0: System wakeup disabled by ACPI
rtc_cmos 00:01: System wakeup disabled by ACPI
Are these relevant? Any hints as to where to look next?
--
/~\ cgi...@kltpzyxm.invalid (Charlie Gibbs)
\ / I'm really at ac.dekanfrus if you read it the right way.
X Top-posted messages will probably be ignored. See RFC1855.
/ \ Fight low-contrast text in web pages!
http://contrastrebellion.com