Author Topic: Problem recovering from a Sleep mode  (Read 1336 times)

Offline some1

  • Newly Subscribed
  • *
  • Posts: 10
  • Karma: 1
  • New Forum User
    • View Profile
Problem recovering from a Sleep mode
« on: July 01, 2018, 05:55:59 am »
I did fresh install of Peppermint 9 and everything seems to work good except recovery from a sleep mode.

After I close a lid, laptop goes into sleep mode as expected, but when I open it again I'm mostly stuck with a garbled screen, or sometimes mouse cursor is missing, for some reason.

My laptop specs,
Code: [Select]
System:    Host: LenovoR500 Kernel: 4.15.0-23-generic x86_64 bits: 64 Desktop: N/A
           Distro: Peppermint Nine
Machine:   Device: laptop System: LENOVO product: 273232G v: ThinkPad R500 serial: N/A
           Mobo: LENOVO model: 273232G serial: N/A
           BIOS: LENOVO v: 7YET85WW (3.15 ) date: 02/13/2012
CPU:       Dual core Intel Core2 Duo P8400 (-MCP-) cache: 3072 KB
           clock speeds: max: 2267 MHz 1: 1455 MHz 2: 1469 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RV620/M82 [Mobility Radeon HD 3450/3470]
           Display Server: x11 (X.Org 1.19.6 )
           drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1680x1050@60.11hz
           OpenGL: renderer: AMD RV620 (DRM 2.50.0 / 4.15.0-23-generic, LLVM 6.0.0)
           version: 3.3 Mesa 18.0.0-rc5
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.15.0-23-generic
Network:   Card-1: Intel PRO/Wireless 5100 AGN [Shiloh] Network Connection
           driver: iwlwifi
           IF: wlp3s0 state: up mac: <filter>
           Card-2: Broadcom Limited NetLink BCM5787M Gigabit Ethernet PCIE
           driver: tg3
           IF: ens5 state: down mac: <filter>
Drives:    HDD Total Size: 91.7GB (19.0% used)
           ID-1: /dev/sda model: Patriot_Flare size: 60.0GB
           ID-2: USB /dev/sdb model: Patriot_Memory size: 31.7GB
Partition: ID-1: / size: 55G used: 8.0G (16%) fs: ext4 dev: /dev/sda1
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 57.0C mobo: 56.0C
           Fan Speeds (in rpm): cpu: 2985
Info:      Processes: 168 Uptime: 6 min Memory: 699.5/1923.9MB
           Client: Shell (bash) inxi: 2.3.56

Offline rod_stone

  • Member
  • ***
  • Posts: 55
  • Karma: 1
  • New Forum User
    • View Profile
  • Peppermint version(s): 7
Re: Problem recovering from a Sleep mode
« Reply #1 on: July 16, 2018, 12:04:10 pm »
The same problem here. Has no one responded to your question as yet?

Offline Lord Rodin

  • Jr. Member
  • **
  • Posts: 43
  • Karma: 2
  • New Forum User
    • View Profile
  • Peppermint version(s): 9
Re: Problem recovering from a Sleep mode
« Reply #2 on: August 05, 2018, 06:28:54 pm »
A conflict between the BIOS power management and Linux power management is the most common cause of such wake-up failure. Experiment with different settings in the BIOS to see if that might solve the problem. For example, a PC might not wake up if Advanced Power Management (APM) is enabled in the Power Options of Control Panel, the BIOS is configured to suspend the computer, and the BIOS time-out value is less than the value configured in Linux. To correct this, you would set the BIOS time-out to be higher than the Linux time-out.

Offline caskin

  • Newly Subscribed
  • *
  • Posts: 12
  • Karma: 1
  • New Forum User
    • View Profile
  • Peppermint version(s): 9
Re: Problem recovering from a Sleep mode
« Reply #3 on: August 10, 2018, 06:52:57 pm »
I have tried so many things to fix this myself but I just stick to putting laptop to sleep with power button. It always comes out of sleep mode perfectly that way.
As far as the graphics glitch, installing laptop-mode-tools fixes that but you just end up with a blank screen instead. You can remove laptop-tools and effect is persistent.
I just change run-level and restart lightdm. People have had luck changing to GDM from what I've read, but I had no such luck.
Funny thing is, I never had this problem until 4.10 and later.  :(