There’s a lot of posts that talk about issues concerning how sleep works and the files involved. But none of them actually say how to wake up your computer from sleep. The reason I’m asking this is because on multiple computers across many different distros over the years, I have never been able to get my computer to wake back up successfully from sleep. I always have to hard reset. One might conclude that I’m simply not doing it properly, so that’s why I’m asking. How do you wake your computer from sleep?
If by sleep you mean standby/suspend, then I simply move my mouse or type on the keyboard. And the computer wakes up. (S3 Mode)
If you mean hibernation, then the power button is pressed because the system shuts down completely after it saves the current state on the disk. (S4 Mode)
In both cases the computer sleeps. What is it?
2 Likes
It’s standby, using the “deep” option, not s2idle.
[********@Toshiba ~]$ cat /sys/power/mem_sleep
s2idle [deep]
Like I said, this has never worked properly of any Linux computer I’ve ever used. It’s more of an inconvenience than anything, but I would like to figure it out, if possible.
Well you can check the journal:
journalctl --boot -1 | sed -n -r "/Starting.+Suspend/,/Finished.+Suspend/p"
There you would get a clue what happens on wake up. Probably try suspending in non-graphical environment (multi-user.target). The log is much cleaner then.
So, should I kill the graphical environment from a tty and then try to suspend?
You could do that, but that is saver:
systemctl set-default multi-user.target
systemctl reboot
Now you get the text-login. Login there and try:
systemctl suspend
wake it up… keyboard or just power button. Then:
systemctl set-default graphical.target
systemctl reboot
Now you can take a look at the journal with:
journalctl --boot -1 | sed -n -r "/Starting.+Suspend/,/Finished.+Suspend/p"
1 Like
Alright, well it didn’t wake up without issues. None of the keys would wake it up, so I reluctantly pressed the power button like you said. Single press, no hold. The screen came on and was blank for about a minute and then it rebooted itself. After getting back to graphical and entering…
journalctl --boot -1 | sed -n -r "/Starting.+Suspend/,/Finished.+Suspend/p"
…I found that there was no output whatsoever. Nothing. So, I’m not really sure what happened or how to proceed.
try another boot… see:
journalctl --list-boots
Or just 0 instead of -1
I was able to find it using -2, the following is the output:
May 14 18:02:06 Toshiba systemd[1]: Starting System Suspend...
May 14 18:02:06 Toshiba wpa_supplicant[715]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all
May 14 18:02:06 Toshiba wpa_supplicant[715]: nl80211: deinit ifname=wlp1s0 disabled_11b_rates=0
May 14 18:02:06 Toshiba kernel: PM: suspend entry (deep)
May 14 18:02:06 Toshiba systemd-sleep[920]: Performing sleep operation 'suspend'...
May 14 18:02:06 Toshiba kernel: Filesystems sync: 0.233 seconds
May 14 18:02:41 Toshiba kernel: Freezing user space processes
May 14 18:02:41 Toshiba kernel: Freezing user space processes completed (elapsed 0.001 seconds)
May 14 18:02:41 Toshiba kernel: OOM killer disabled.
May 14 18:02:41 Toshiba kernel: Freezing remaining freezable tasks
May 14 18:02:41 Toshiba kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
May 14 18:02:41 Toshiba kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 14 18:02:41 Toshiba kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 14 18:02:41 Toshiba kernel: ata1.00: Entering standby power mode
May 14 18:02:41 Toshiba kernel: ACPI: EC: interrupt blocked
May 14 18:02:41 Toshiba kernel: ACPI: PM: Preparing to enter system sleep state S3
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI: EC: event blocked
May 14 18:02:41 Toshiba kernel: ACPI: EC: EC stopped
May 14 18:02:41 Toshiba kernel: ACPI: PM: Saving platform NVS memory
May 14 18:02:41 Toshiba kernel: Disabling non-boot CPUs ...
May 14 18:02:41 Toshiba kernel: smpboot: CPU 1 is now offline
May 14 18:02:41 Toshiba kernel: microcode: CPU0: new patch_level=0x06001119
May 14 18:02:41 Toshiba kernel: ACPI: PM: Low-level resume complete
May 14 18:02:41 Toshiba kernel: ACPI: EC: EC started
May 14 18:02:41 Toshiba kernel: ACPI: PM: Restoring platform NVS memory
May 14 18:02:41 Toshiba kernel: LVT offset 0 assigned for vector 0x400
May 14 18:02:41 Toshiba kernel: microcode: CPU0: new patch_level=0x06001119
May 14 18:02:41 Toshiba kernel: Enabling non-boot CPUs ...
May 14 18:02:41 Toshiba kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
May 14 18:02:41 Toshiba kernel: microcode: CPU1: new patch_level=0x06001119
May 14 18:02:41 Toshiba kernel: ACPI: \_PR_.C001: Found 2 idle states
May 14 18:02:41 Toshiba kernel: CPU1 is up
May 14 18:02:41 Toshiba kernel: ACPI: PM: Waking up from system sleep state S3
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230628/exsystem-141)
May 14 18:02:41 Toshiba kernel: ACPI: EC: interrupt unblocked
May 14 18:02:41 Toshiba kernel: ACPI: EC: event unblocked
May 14 18:02:41 Toshiba kernel: rtlwifi: rtlwifi: wireless switch is on
May 14 18:02:41 Toshiba kernel: ata4: SATA link down (SStatus 0 SControl 300)
May 14 18:02:41 Toshiba kernel: [drm] PCIE GART of 1024M enabled (table at 0x00000000001D6000).
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: WB enabled
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000020000c18
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000020000c1c
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000020000c04
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000020000c08
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c
May 14 18:02:41 Toshiba kernel: radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000020000c10
May 14 18:02:41 Toshiba kernel: debugfs: File 'radeon_ring_gfx' in directory '1' already present!
May 14 18:02:41 Toshiba kernel: debugfs: File 'radeon_ring_dma1' in directory '1' already present!
May 14 18:02:41 Toshiba kernel: debugfs: File 'radeon_ring_dma2' in directory '1' already present!
May 14 18:02:41 Toshiba kernel: [drm] ring test on 0 succeeded in 3 usecs
May 14 18:02:41 Toshiba kernel: [drm] ring test on 3 succeeded in 3 usecs
May 14 18:02:41 Toshiba kernel: [drm] ring test on 4 succeeded in 3 usecs
May 14 18:02:41 Toshiba kernel: debugfs: File 'radeon_ring_uvd' in directory '1' already present!
May 14 18:02:41 Toshiba kernel: [drm] ring test on 5 succeeded in 1 usecs
May 14 18:02:41 Toshiba kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 14 18:02:41 Toshiba kernel: [drm] UVD initialized successfully.
May 14 18:02:41 Toshiba kernel: debugfs: File 'radeon_ring_vce1' in directory '1' already present!
May 14 18:02:41 Toshiba kernel: debugfs: File 'radeon_ring_vce2' in directory '1' already present!
May 14 18:02:41 Toshiba kernel: usb 3-3: reset high-speed USB device number 2 using ehci-pci
May 14 18:02:41 Toshiba kernel: ata2.00: configured for UDMA/100
May 14 18:02:41 Toshiba kernel: [drm] ring test on 6 succeeded in 10 usecs
May 14 18:02:41 Toshiba kernel: [drm] ring test on 7 succeeded in 3 usecs
May 14 18:02:41 Toshiba kernel: [drm] VCE initialized successfully.
May 14 18:02:41 Toshiba kernel: [drm] ib test on ring 0 succeeded in 0 usecs
May 14 18:02:41 Toshiba kernel: [drm] ib test on ring 3 succeeded in 0 usecs
May 14 18:02:41 Toshiba kernel: [drm] ib test on ring 4 succeeded in 0 usecs
May 14 18:02:41 Toshiba kernel: psmouse serio2: synaptics: queried max coordinates: x [..5692], y [..4680]
May 14 18:02:41 Toshiba kernel: [drm] ib test on ring 5 succeeded
May 14 18:02:41 Toshiba kernel: [drm] ib test on ring 6 succeeded
May 14 18:02:41 Toshiba kernel: [drm] ib test on ring 7 succeeded
May 14 18:02:41 Toshiba kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 14 18:02:41 Toshiba kernel: ata1.00: Entering active power mode
May 14 18:02:41 Toshiba kernel: sd 0:0:0:0: [sda] Starting disk
May 14 18:02:41 Toshiba kernel: ata1.00: configured for UDMA/133
May 14 18:02:41 Toshiba kernel: OOM killer enabled.
May 14 18:02:41 Toshiba kernel: Restarting tasks ...
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci_bus 0000:01: Allocating resources
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci_bus 0000:02: Allocating resources
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci_bus 0000:06: Allocating resources
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: done.
May 14 18:02:41 Toshiba kernel: random: crng reseeded on system resumption
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci_bus 0000:01: Allocating resources
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci_bus 0000:02: Allocating resources
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci_bus 0000:06: Allocating resources
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: PCI bridge to [bus 06]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [io 0x1000-0x1fff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0600000-0xf07fffff]
May 14 18:02:41 Toshiba kernel: pci 0000:00:14.4: bridge window [mem 0xf0800000-0xf09fffff pref]
May 14 18:02:41 Toshiba kernel: PM: suspend exit
May 14 18:02:41 Toshiba systemd-sleep[920]: System returned from sleep operation 'suspend'.
May 14 18:02:42 Toshiba systemd[1]: systemd-suspend.service: Deactivated successfully.
May 14 18:02:42 Toshiba systemd[1]: Finished System Suspend.
I’m not really sure what most of this means, to be honest. Your thoughts?
Well, actually it works, when I look at the log. So, linux itself is not the blocker here.
At 18:02:06 it sleeps and it wakes up at 18:02:41.
This is a problem with your BIOS/UEFI. You could say that the developers made something that doesn’t comply with open standards. It is Windows specific at the end.
Probably use an older kernel for such a old machine: 5.4, 5.10, 5.15.
1 Like
I’m not sure I understand. The BIOS is Windows specific?
Most off-the-shelf computers are indeed configured and marketed with Windows users being the target demographic; this often includes BIOS settings. I think this is all that was implied.
The suggestion is that the issue is likely related to your BIOS/UEFI implementation or configuration; neither of which Linux has any control over. It is further suggested that using:
…might be more compatible. I would likely add kernel 6.1 (LTS) to that list aswell.
Cheers.
1 Like
Vendors typically choose Windows as their preinstalled OS, therefore they test Windows in combination with the BIOS. And often the devs just write lines of code just to please Windows, but not to comply with open standards, which Linux strictly follows. Therefore most Laptops are Windows specific, probably less these days, but in the past that was common practice.
2 Likes
And there is no way to fix the ACPI?
inxi -Farz
Kernel: 6.6.30-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
root=UUID=3a2f3cc6-1e22-49a7-bc17-fe595afba496 rw quiet splash apparmor=1
security=apparmor resume=UUID=a1b8b401-6adc-48f1-8419-f0f94f2c2496
udev.log_priority=3
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm4 v: 4.18.0
with: xfce4-panel tools: light-locker avail: xtrlock vt: 7 dm: LightDM
v: 1.32.0 Distro: Manjaro base: Arch Linux
Machine:
Type: Laptop System: TOSHIBA product: Satellite C875D v: PSCBGU-007006
serial: <superuser required>
Mobo: AMD model: PLCSC8 serial: <superuser required> part-nu: PSCBGU
uuid: <superuser required> UEFI-[Legacy]: Insyde v: 6.30 date: 12/06/2012
Battery:
ID-1: BAT0 charge: 26.3 Wh (100.0%) condition: 26.3/49.5 Wh (53.0%)
volts: 12.3 min: 10.8 model: TKBSS NS2P3SZMC4WR type: Li-ion serial: N/A
status: full
CPU:
Info: model: AMD A4-4300M APU with Radeon HD Graphics bits: 64 type: MT MCP
arch: Piledriver level: v2 built: 2012-13 process: GF 32nm family: 0x15 (21)
model-id: 0x10 (16) stepping: 1 microcode: 0x6001119
Topology: cpus: 1x cores: 2 smt: enabled cache: L1: 96 KiB
desc: d-2x16 KiB; i-1x64 KiB L2: 1024 KiB desc: 1x1024 KiB
Speed (MHz): avg: 1361 high: 1400 min/max: 1400/2500 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1400 2: 1323
bogomips: 9985
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Trinity 2 [Radeon HD 7420G] vendor: Toshiba driver: radeon
v: kernel alternate: amdgpu arch: TeraScale-3 code: Northern Islands
process: TSMC 32nm built: 2010-13 ports: active: LVDS-1
empty: HDMI-A-1,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:9992 class-ID: 0300
Display: x11 server: X.org v: 1.21.1.13 compositor: xfwm4 v: 4.18.0
driver: X: loaded: radeon unloaded: modesetting alternate: fbdev,vesa
dri: r600 gpu: radeon display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-size: <missing: xdpyinfo>
Monitor-1: LVDS-1 mapped: LVDS model: Seiko Epson 0x504b built: 2011
res: 1600x900 hz: 60 dpi: 106 gamma: 1.2 size: 382x215mm (15.04x8.46")
diag: 438mm (17.3") ratio: 16:9 modes: max: 1600x900 min: 640x480
API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1
drv: swrast surfaceless: drv: r600 x11: drv: r600 inactive: gbm,wayland
API: OpenGL v: 4.5 vendor: mesa v: 24.0.6-manjaro1.1 glx-v: 1.4
direct-render: yes renderer: AMD ARUBA (DRM 2.50.0 / 6.6.30-2-MANJARO LLVM
17.0.6) device-ID: 1002:9992 memory: 500 MiB unified: no
API: Vulkan Message: No Vulkan data available.
Audio:
Device-1: AMD Trinity HDMI Audio driver: snd_hda_intel v: kernel
bus-ID: 00:01.1 chip-ID: 1002:9902 class-ID: 0403
Device-2: AMD FCH Azalia vendor: Toshiba driver: snd_hda_intel v: kernel
bus-ID: 00:14.2 chip-ID: 1022:780d class-ID: 0403
API: ALSA v: k6.6.30-2-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.0.5 status: off tools: pw-cli
Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
type: plugin tools: pacat,pactl,pavucontrol
Network:
Device-1: Realtek RTL8188CE 802.11b/g/n WiFi Adapter driver: rtl8192ce
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0
chip-ID: 10ec:8176 class-ID: 0280
IF: wlp1s0 state: up mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Toshiba
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000
bus-ID: 02:00.0 chip-ID: 10ec:8136 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Info: services: NetworkManager,wpa_supplicant
Drives:
Local Storage: total: 465.76 GiB used: 36.54 GiB (7.8%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Hitachi model: HTS545050A7E380
size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
tech: HDD rpm: 5400 serial: <filter> fw-rev: A7A0 scheme: MBR
Partition:
ID-1: / raw-size: 458.49 GiB size: 450.23 GiB (98.20%) used: 36.2 GiB (8.0%)
fs: ext4 dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 7.26 GiB used: 343.8 MiB (4.6%)
priority: -2 dev: /dev/sda2 maj-min: 8:2
Sensors:
System Temperatures: cpu: 46.8 C mobo: N/A gpu: radeon temp: 45.0 C
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 1243 libs: 473 tools: pamac pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://uvermont.mm.fcix.net/manjaro/stable/$repo/$arch
2: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
3: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
4: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
5: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
6: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
7: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
8: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
9: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
10: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
11: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
12: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
13: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
14: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
15: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
16: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
17: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
18: http://mirror.fcix.net/manjaro/stable/$repo/$arch
19: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
Info:
Memory: total: 4 GiB note: est. available: 3.3 GiB used: 1.68 GiB (50.8%)
Processes: 181 Power: uptime: 1d 45m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 1.31 GiB services: upowerd,xfce4-power-manager
Init: systemd v: 255 default: graphical tool: systemctl
Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: Bash v: 5.2.26
running-in: xfce4-terminal inxi: 3.3.34
If you have BIOS updates you could do them.
But the machine is also rather old.
I think it’s just one of those things that I’ll just have to continue to live with, which is fine. But in using Linux for over the last decade (I started with Xubuntu 12.04 when I was still in High School, I’ve been using Manjaro for the last three), the sleep function has literally always done this to me across multiple distros and machines. So, I’ve definitely learned to live without it, but it would be nice to have. It’s just one of those things, I guess. Anyways, thank you all for your time and insight.
If it’s helpful, I found:
This BIOS seems to address: Made a change to the LID power setting., so maybe it’s related to your ongoing sleep issues. Updating to that BIOS version could potentially improve things. Obviously if BIOS is already at v6.50, it won’t help much at all.
- The latest available BIOS seems to be: v6.50 (2012-12-13)
- ACPI Flash BIOS version 6.50 for Satellite C870D/C875D
- Toshiba C875D-S7331 Specifications (sourced from https://usermanual.com)
Cheers.
inxi output shows 6.30
1 Like