Suspend to RAM dosn't work

Getting your soundcard to work, using Debian on non-i386 hardware, etc

Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-10 22:38

I have desktop computer based on GIGABYTE P61-DS3-B3 motherboard. Suspend to RAM (Sleep) is working in Windows 7, but it is not working in Debian 9.6. I don't know how to resolve this problem. For any other information about my system, just ask. Thanks.
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby stevepusser » 2019-02-10 23:58

OK, install inxi, update your hardware database with sudo or as root
Code: Select all
update-usbids
update-pciids


and report the result in code tags of (as regular user)
Code: Select all
inxi -Fxxz
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, 4..20.6 kernel, wine-staging 4.0 final, Sayonara 1.1.1, Calibre 3.39.1, Pale Moon 28.3.1
User avatar
stevepusser
 
Posts: 10513
Joined: 2009-10-06 05:53

Re: Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-11 02:45

Here is the report of inxi -Fxxz


Code: Select all
System:    Host: dnevna Kernel: 4.9.0-8-amd64 x86_64 (64 bit gcc: 6.3.0)
           Desktop: KDE Plasma 5.8.6 (Qt 5.7.1) dm: sddm,sddm
           Distro: Debian GNU/Linux 9 (stretch)
Machine:   Device: desktop Mobo: Gigabyte model: P61-DS3-B3 BIOS: Award v: F2 date: 05/15/2011
CPU:       Dual core Intel Core i3-2100 (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 12368
           clock speeds: min/max: 1600/3100 MHz 1: 1599 MHz 2: 1601 MHz 3: 1654 MHz
           4: 1628 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0 chip-ID: 10de:0a65
           Display Server: X.Org 1.19.2 drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on NVA8
           GLX Version: 3.0 Mesa 13.0.6 Direct Rendering: Yes
Audio:     Card-1 NVIDIA High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 10de:0be3
           Card-2 Intel 6 Series/C200 Series Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20
           Card-3 Microdia Camera
           driver: USB Audio usb-ID: 001-003 chip-ID: 0c45:6340
           Sound: Advanced Linux Sound Architecture v: k4.9.0-8-amd64
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: de00 bus-ID: 05:00.0 chip-ID: 10ec:8168
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1000.2GB (20.8% used)
           ID-1: /dev/sda model: Hitachi_HDS72101 size: 1000.2GB
           serial: JP2940J8072B1V
Partition: ID-1: / size: 404G used: 188G (49%) fs: ext4 dev: /dev/sda6
           ID-2: swap-1 size: 8.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 40.0C mobo: N/A gpu: 51.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 242 Uptime: 3 min Memory: 1703.7/7970.9MB
           Init: systemd v: 232 runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121 running in konsole) inxi: 2.3.5
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby Head_on_a_Stick » 2019-02-11 07:10

How are you attempting to suspend?

Is there anything printed to the systemd-journal when you try?
"The trouble with the world is that the stupid are cocksure and the intelligent full of doubt." — Bertrand Russell
User avatar
Head_on_a_Stick
 
Posts: 8842
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-11 08:55

The system is configured to suspend after 15 min. but that is not happening.
When I manual try to suspend, system is going in suspend mode, but after that,
when I try to wake up the system, I get only black screen. I don't know where
is systemd-journal, maybe you can help me.
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby Head_on_a_Stick » 2019-02-11 09:16

When I manual try to suspend

How are you doing that? Which command(s) do you use?

when I try to wake up the system, I get only black screen

Sounds like it may be a video driver issue then, the journal may confirm this (hopefully).

I don't know where is systemd-journal, maybe you can help me.

Use a search engine for this sort of question, try something like "how to use the systemd journal" as a search term, there are *many* guides available and I see no reason why I should re-type them here just for you.
"The trouble with the world is that the stupid are cocksure and the intelligent full of doubt." — Bertrand Russell
User avatar
Head_on_a_Stick
 
Posts: 8842
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-11 20:43

How are you doing that? Which command(s) do you use?

I do not use command, I am using the suspend menu from the KDE star menu.

Sounds like it may be a video driver issue then, the journal may confirm this (hopefully).

Probably it is. I am pasting the part of the journal which is about resuming from suspend.
Code: Select all
Feb 11 22:15:13 dnevna kernel: smpboot: CPU 3 is now offline
Feb 11 22:15:13 dnevna kernel: ACPI: Low-level resume complete
Feb 11 22:15:13 dnevna kernel: PM: Restoring platform NVS memory
Feb 11 22:15:13 dnevna kernel: Suspended for 9.000 seconds
Feb 11 22:15:13 dnevna kernel: Enabling non-boot CPUs ...
Feb 11 22:15:13 dnevna kernel: x86: Booting SMP configuration:
Feb 11 22:15:13 dnevna kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Feb 11 22:15:13 dnevna kernel:  cache: parent cpu1 should not be sleeping
Feb 11 22:15:13 dnevna kernel: CPU1 is up
Feb 11 22:15:13 dnevna kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Feb 11 22:15:13 dnevna kernel:  cache: parent cpu2 should not be sleeping
Feb 11 22:15:13 dnevna kernel: CPU2 is up
Feb 11 22:15:13 dnevna kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 11 22:15:13 dnevna kernel:  cache: parent cpu3 should not be sleeping
Feb 11 22:15:13 dnevna kernel: CPU3 is up
Feb 11 22:15:13 dnevna kernel: ACPI: Waking up from system sleep state S3
Feb 11 22:15:13 dnevna kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 11 22:15:13 dnevna kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 11 22:15:13 dnevna kernel: saa7134 0000:04:02.0: Refused to change power state, currently in D3
Feb 11 22:15:13 dnevna kernel: PM: noirq resume of devices complete after 76.878 msecs
Feb 11 22:15:13 dnevna kernel: PM: early resume of devices complete after 0.332 msecs
Feb 11 22:15:13 dnevna kernel: usb usb1: root hub lost power or was reset
Feb 11 22:15:13 dnevna kernel: usb usb2: root hub lost power or was reset
Feb 11 22:15:13 dnevna kernel: ehci-pci 0000:00:1a.0: cache line size of 4 is not supported
Feb 11 22:15:13 dnevna kernel: rtc_cmos 00:01: System wakeup disabled by ACPI
Feb 11 22:15:13 dnevna kernel: nouveau 0000:01:00.0: DRM: resuming kernel object tree...
Feb 11 22:15:13 dnevna kernel: pcieport 0000:00:1c.5: System wakeup disabled by ACPI
Feb 11 22:15:13 dnevna kernel: ehci-pci 0000:00:1d.0: cache line size of 4 is not supported
Feb 11 22:15:13 dnevna kernel: sd 0:0:0:0: [sda] Starting disk
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: board init: gpio is ffffffff
Feb 11 22:15:13 dnevna kernel: nouveau 0000:01:00.0: DRM: resuming client object trees...
Feb 11 22:15:13 dnevna kernel: r8169 0000:05:00.0 enp5s0: link down
Feb 11 22:15:13 dnevna kernel: nouveau 0000:01:00.0: DRM: resuming display...
Feb 11 22:15:13 dnevna kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci
Feb 11 22:15:13 dnevna kernel: usb 2-1: reset high-speed USB device number 2 using ehci-pci
Feb 11 22:15:13 dnevna kernel: ata5: SATA link down (SStatus 0 SControl 300)
Feb 11 22:15:13 dnevna kernel: ata2: SATA link down (SStatus 0 SControl 300)
Feb 11 22:15:13 dnevna kernel: nouveau 0000:01:00.0: DRM: resuming console...
Feb 11 22:15:13 dnevna kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 11 22:15:13 dnevna kernel: ata6.00: configured for UDMA/133
Feb 11 22:15:13 dnevna kernel: usb 2-1.5: reset full-speed USB device number 4 using ehci-pci
Feb 11 22:15:13 dnevna kernel: usb 1-1.3: reset low-speed USB device number 4 using ehci-pci
Feb 11 22:15:13 dnevna kernel: usb 2-1.2: reset high-speed USB device number 3 using ehci-pci
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: usb 1-1.1: reset high-speed USB device number 3 using ehci-pci
Feb 11 22:15:13 dnevna kernel: PM: resume of devices complete after 2327.412 msecs
Feb 11 22:15:13 dnevna kernel: PM: Finishing wakeup.
Feb 11 22:15:13 dnevna kernel: Restarting tasks ...
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: saa7134: saa7133[0]: dsp access error
Feb 11 22:15:13 dnevna kernel: done.
Feb 11 22:15:13 dnevna rtkit-daemon[530]: The canary thread is apparently starving. Taking action.
Feb 11 22:15:13 dnevna systemd[654]: Time has been changed
Feb 11 22:15:13 dnevna rtkit-daemon[530]: Demoting known real-time threads.
Feb 11 22:15:13 dnevna systemd[1]: Time has been changed
Feb 11 22:15:13 dnevna rtkit-daemon[530]: Successfully demoted thread 1018 of process 976 (n/a).
Feb 11 22:15:13 dnevna systemd[1]: anacron.timer: Adding 4min 12.319800s random time.
Feb 11 22:15:13 dnevna rtkit-daemon[530]: Successfully demoted thread 1017 of process 976 (n/a).
Feb 11 22:15:13 dnevna systemd[1]: apt-daily-upgrade.timer: Adding 7min 33.815730s random time.
Feb 11 22:15:13 dnevna rtkit-daemon[530]: Successfully demoted thread 1016 of process 976 (n/a).
Feb 11 22:15:13 dnevna systemd[1]: apt-daily.timer: Adding 2h 58min 22.889175s random time.
Feb 11 22:15:13 dnevna rtkit-daemon[530]: Successfully demoted thread 1014 of process 976 (n/a).
Feb 11 22:15:13 dnevna systemd[1]: Starting Daily apt download activities...
Feb 11 22:15:13 dnevna rtkit-daemon[530]: Successfully demoted thread 976 of process 976 (n/a).
Feb 11 22:15:13 dnevna systemd-sleep[20020]: System resumed.
Feb 11 22:15:13 dnevna rtkit-daemon[530]: Demoted 5 threads.
Feb 11 22:15:14 dnevna NetworkManager[528]: <info>  [1549919714.4880] device (enp5s0): link connected
Feb 11 22:15:14 dnevna kernel: r8169 0000:05:00.0 enp5s0: link up
Feb 11 22:15:14 dnevna systemd[1]: Started Daily apt download activities.
Feb 11 22:15:14 dnevna systemd[1]: apt-daily.timer: Adding 1min 43.460588s random time.
Feb 11 22:15:14 dnevna systemd[1]: apt-daily.timer: Adding 8h 57min 46.965430s random time.
Feb 11 22:15:18 dnevna kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 11 22:15:18 dnevna kernel: ata1.00: configured for UDMA/133
Feb 11 22:15:18 dnevna systemd-sleep[20020]: /dev/sda:
Feb 11 22:15:18 dnevna systemd-sleep[20020]:  setting Advanced Power Management level to 0xfe (254)
Feb 11 22:15:18 dnevna systemd-sleep[20020]:  APM_level        = off
Feb 11 22:15:18 dnevna systemd[1]: Started Suspend.
Feb 11 22:15:18 dnevna systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Feb 11 22:15:18 dnevna systemd[1]: Stopped target Sleep.
Feb 11 22:15:18 dnevna systemd[1]: Reached target Suspend.
Feb 11 22:15:18 dnevna systemd-logind[479]: Operation 'sleep' finished.
Feb 11 22:15:18 dnevna systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
Feb 11 22:15:18 dnevna systemd[1]: Stopped target Suspend.
Feb 11 22:15:18 dnevna NetworkManager[528]: <info>  [1549919718.8463] manager: wake requested (sleeping: yes  enabled: yes)
Feb 11 22:15:18 dnevna avahi-daemon[482]: Withdrawing address record for 192.168.0.2 on enp5s0.
Feb 11 22:15:18 dnevna NetworkManager[528]: <info>  [1549919718.8464] manager: waking up...
Feb 11 22:15:18 dnevna avahi-daemon[482]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.0.2.
Feb 11 22:15:18 dnevna NetworkManager[528]: <info>  [1549919718.8466] device (enp5s0): state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Feb 11 22:15:18 dnevna avahi-daemon[482]: Interface enp5s0.IPv4 no longer relevant for mDNS.
Feb 11 22:15:18 dnevna NetworkManager[528]: <info>  [1549919718.8480] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 11 22:15:18 dnevna avahi-daemon[482]: Withdrawing address record for fe80::f8ab:5991:b6b2:d269 on enp5s0.
Feb 11 22:15:18 dnevna systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 11 22:15:18 dnevna avahi-daemon[482]: Leaving mDNS multicast group on interface enp5s0.IPv6 with address fe80::f8ab:5991:b6b2:d269.
Feb 11 22:15:18 dnevna avahi-daemon[482]: Interface enp5s0.IPv6 no longer relevant for mDNS.
Feb 11 22:15:18 dnevna dbus[491]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 11 22:15:18 dnevna dbus[491]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 11 22:15:18 dnevna systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 11 22:15:18 dnevna nm-dispatcher[20214]: req:1 'connectivity-change': new request (1 scripts)
Feb 11 22:15:18 dnevna nm-dispatcher[20214]: req:1 'connectivity-change': start running ordered scripts...
Feb 11 22:15:18 dnevna NetworkManager[528]: <info>  [1549919718.8810] manager: NetworkManager state is now DISCONNECTED
Feb 11 22:15:18 dnevna nm-dispatcher[20214]: req:2 'connectivity-change': new request (1 scripts)
Feb 11 22:15:18 dnevna nm-dispatcher[20214]: req:2 'connectivity-change': start running ordered scripts...
Feb 11 22:15:18 dnevna NetworkManager[528]: <info>  [1549919718.9260] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 11 22:15:18 dnevna kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready
Feb 11 22:15:18 dnevna nm-dispatcher[20214]: req:3 'down' [enp5s0]: new request (1 scripts)
Feb 11 22:15:18 dnevna nm-dispatcher[20214]: req:3 'down' [enp5s0]: start running ordered scripts...
Feb 11 22:15:19 dnevna kernel: r8169 0000:05:00.0 enp5s0: link down
Feb 11 22:15:19 dnevna kernel: r8169 0000:05:00.0 enp5s0: link down
Feb 11 22:15:19 dnevna kernel: IPv6: ADDRCONF(NETDEV_UP): enp5s0: link is not ready
Feb 11 22:15:19 dnevna PackageKit[1107]: get-updates transaction /115192_ebeedadb from uid 1000 finished with success after 369ms
Feb 11 22:15:21 dnevna ModemManager[526]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0': not supported by any plugin
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3787] device (enp5s0): link connected
Feb 11 22:15:22 dnevna kernel: r8169 0000:05:00.0 enp5s0: link up
Feb 11 22:15:22 dnevna kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3796] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3808] policy: auto-activating connection 'dnevna'
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3824] device (enp5s0): Activation: starting connection 'dnevna' (1226a429-a4d5-4187-942c-186c146d9f77)
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3828] device (enp5s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3830] manager: NetworkManager state is now CONNECTING
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3837] device (enp5s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3843] device (enp5s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 11 22:15:22 dnevna avahi-daemon[482]: Joining mDNS multicast group on interface enp5s0.IPv4 with address 192.168.0.2.
Feb 11 22:15:22 dnevna avahi-daemon[482]: New relevant interface enp5s0.IPv4 for mDNS.
Feb 11 22:15:22 dnevna avahi-daemon[482]: Registering new address record for 192.168.0.2 on enp5s0.IPv4.
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3935] device (enp5s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.3988] device (enp5s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.4003] device (enp5s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.4015] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 11 22:15:22 dnevna nm-dispatcher[20214]: req:4 'connectivity-change': new request (1 scripts)
Feb 11 22:15:22 dnevna nm-dispatcher[20214]: req:4 'connectivity-change': start running ordered scripts...
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.4619] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.4621] policy: set 'dnevna' (enp5s0) as default for IPv4 routing and DNS
Feb 11 22:15:22 dnevna NetworkManager[528]: <info>  [1549919722.4625] device (enp5s0): Activation: successful, device activated.
Feb 11 22:15:22 dnevna nm-dispatcher[20214]: req:5 'up' [enp5s0]: new request (1 scripts)
Feb 11 22:15:22 dnevna nm-dispatcher[20214]: req:5 'up' [enp5s0]: start running ordered scripts...
Feb 11 22:15:23 dnevna PackageKit[1107]: get-updates transaction /115193_eadeadba from uid 1000 finished with success after 343ms
Feb 11 22:15:23 dnevna avahi-daemon[482]: Joining mDNS multicast group on interface enp5s0.IPv6 with address fe80::f8ab:5991:b6b2:d269.
Feb 11 22:15:23 dnevna avahi-daemon[482]: New relevant interface enp5s0.IPv6 for mDNS.
Feb 11 22:15:23 dnevna avahi-daemon[482]: Registering new address record for fe80::f8ab:5991:b6b2:d269 on enp5s0.*.
Feb 11 22:15:46 dnevna systemd[654]: Time has been changed
Feb 11 22:15:46 dnevna systemd[1]: Time has been changed
Feb 11 22:15:46 dnevna systemd[1]: anacron.timer: Adding 4min 3.879732s random time.
Feb 11 22:15:46 dnevna systemd[1]: apt-daily-upgrade.timer: Adding 58min 55.401883s random time.
Feb 11 22:15:46 dnevna systemd[1]: apt-daily.timer: Adding 8h 38min 39.156579s random time.
Feb 11 22:16:00 dnevna login[570]: pam_unix(login:session): session opened for user goran by LOGIN(uid=0)
Feb 11 22:16:00 dnevna systemd-logind[479]: New session 8 of user goran.
Feb 11 22:16:00 dnevna systemd[1]: Started Session 8 of user goran.
Feb 11 22:16:44 dnevna su[20315]: Successful su for root by goran
Feb 11 22:16:44 dnevna su[20315]: + /dev/tty1 goran:root
Feb 11 22:16:44 dnevna su[20315]: pam_unix(su:session): session opened for user root by goran(uid=1000)
Feb 11 22:16:44 dnevna su[20315]: pam_systemd(su:session): Cannot create session: Already running in a session
Feb 11 22:17:01 dnevna CRON[20319]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 11 22:17:01 dnevna CRON[20320]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 11 22:17:01 dnevna CRON[20319]: pam_unix(cron:session): session closed for user root
Feb 11 22:19:02 dnevna PackageKit[1107]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
Feb 11 22:19:02 dnevna PackageKit[1107]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh
Feb 11 22:19:04 dnevna PackageKit[1107]: refresh-cache transaction /115194_bceccaab from uid 1000 finished with success after 1168ms
Feb 11 22:19:05 dnevna PackageKit[1107]: get-updates transaction /115195_aadbbbce from uid 1000 finished with success after 1099ms
Feb 11 22:19:06 dnevna PackageKit[1107]: get-updates transaction /115197_daeaceaa from uid 1000 finished with success after 340ms
Feb 11 22:19:43 dnevna PackageKit[1107]: get-updates transaction /115199_acbdbbdb from uid 1000 finished with success after 450ms
Feb 11 22:19:44 dnevna PackageKit[1107]: get-updates transaction /115200_edadcaad from uid 1000 finished with success after 329ms


Use a search engine for this sort of question...

OK, I have done that. I didn't know that there is a command for viewing journal, I was thinking it is a file like syslog. Anyway thanks.
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby Head_on_a_Stick » 2019-02-11 21:02

pythagorasmk wrote:
How are you doing that? Which command(s) do you use?

I do not use command, I am using the suspend menu from the KDE star menu.

The journal has a few messages marked "PM" so maybe it's using pm-suspend but I really don't know.

Does this work:
Code: Select all
systemctl suspend
"The trouble with the world is that the stupid are cocksure and the intelligent full of doubt." — Bertrand Russell
User avatar
Head_on_a_Stick
 
Posts: 8842
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-11 21:08

Does this work:

Code: Select all
systemctl suspend


After the command the system is going in suspend mode, but after a second it wake up by itself. After that I get login screen.
If I log on, everything is working fine.
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby Head_on_a_Stick » 2019-02-11 21:12

pythagorasmk wrote:After the command the system is going in suspend mode, but after a second it wake up by itself

https://askubuntu.com/questions/148481/how-do-i-prevent-immediate-wake-up-from-suspend-and-or-hibernation?
"The trouble with the world is that the stupid are cocksure and the intelligent full of doubt." — Bertrand Russell
User avatar
Head_on_a_Stick
 
Posts: 8842
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-11 21:37

Now everything is working, except that I must use power button to wake up the system, I cannot do it with the keyboard or mouse:(
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-11 22:07

Everything is not working. I have configured KDE to suspend after 15 min, but system is not going
to suspend after 15 min. How can I resolve this?
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby bw123 » 2019-02-11 23:23

Everything is not working. I have configured KDE to suspend after 15 min, but system is not going
to suspend after 15 min. How can I resolve this?


Configure it again, correctly. Power management is complicated in kde, and also in other desktops.

It's funny, (to me at least) I thought about your title "doesn't work" and found this...
http://ircbots.debian.net/factoids/sear ... k&term=key

Are you sure you've read these? Ask smart questions, people on here want to help.
viewtopic.php?f=30&t=47078
viewtopic.php?f=30&t=10653

Please do better, post good specific questions with more information and stop asking "how to resolve this" I see all the spamtrollbots saying that over AND OVER on here...

-- to no avail
User avatar
bw123
 
Posts: 3757
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Suspend to RAM dosn't work

Postby pythagorasmk » 2019-02-12 00:19

I must say that I am a beginner. It is very difficult for me to read Debian reference. Don't be so unfriendly to beginners.
Now I have a problem to make changes in /proc/acpi/wakeup permanent. Maybe for you is naive question, but for me it is difficult.
I think that commands like:
Code: Select all
echo USBE > /proc/acpi/wakeup

should be placed somewhere in configuration files of systemd, so they can be executed at start up, but I don't know how to do that.
Maybe you can point me link where I can read about KDE power management.
pythagorasmk
 
Posts: 18
Joined: 2015-01-18 03:40

Re: Suspend to RAM dosn't work

Postby bw123 » 2019-02-12 00:30

I also had problems with kde power mgmt and suspend. It's really unfortunate, and I did not mean to offend you. It's just that, "When y0u mess with a bull, you might get gored," and the whole linux experience for me with kde has been a nightmare of crap that doesn't work until I research it for months. (then they break it with a new version)

I solved the immediate wakeup from suspend by disabling automatic screen locking, I did dabble with the acpi/wakeup thing but didn't get anywhere that way.

make sure powerdevil is always running when you start kde, if you occasionally see the red X in systemsettings>power management then something is wrong.
User avatar
bw123
 
Posts: 3757
Joined: 2011-05-09 06:02
Location: TN_USA

Next

Return to Hardware

Who is online

Users browsing this forum: No registered users and 6 guests

fashionable