20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Questions about other topics - please check if your question fits better in another category before posting here
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

Hi all,

I am having weird issue with suspend not working on HP ProBook 6560b laptop. Why this is weird is because the suspend used to work on my laptop before. I recently bought a new second hand laptop which is the exact same model and transferred HDD and RAM to it. Everything else seems to be working perfectly apart from the suspend recovery.

What happens
When I suspend the OS from the Mint menu or by pressing the power button and choosing 'suspend', the suspend seems to work well. I see no errors in /var/log/pm-suspend.log
It is impossible to resume from the suspend though, even though the computer seems to power back up, the screen stays black and the only way to get things going again is to do a hard reset by downpressing the power button.

I have tried to disable swap by doing

Code: Select all

swapoff /swapfile
But that didn't seem to resolve the problem

I have looked for a BIOS update for this laptop but one doesn't seem to exist, at least from the official HP source.

I tried to look for any Suspend settings in BIOS but they seem to be non-existent.

I tried to remove one of the two 4GB RAM modules and then suspend/resume but it did not fix it.

I tried to boot into a live USB of LM 20.1 and then suspend/resume, but I encountered the same problem with the live USB.

I tried with an earlier kernel version (5.4.0-58), but it did not help.

Code: Select all

inxi -Fxzd
System:
  Kernel: 5.4.0-89-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.8.6 Distro: Linux Mint 20.1 Ulyssa 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP ProBook 6560b v: A0001D02 
  serial: <filter> 
  Mobo: Hewlett-Packard model: 1619 v: KBC Version 97.40 serial: <filter> 
  BIOS: Hewlett-Packard v: 68SCE Ver. F.03 date: 04/27/2011 
Battery:
  ID-1: BAT0 charge: 39.6 Wh condition: 39.6/39.6 Wh (100%) 
  model: Hewlett-Packard Primary status: Full 
CPU:
  Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19953 
  Speed: 798 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 798 2: 798 
  3: 798 4: 798 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.20.11 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) 
  v: 3.3 Mesa 21.0.3 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k5.4.0-89-generic 
Network:
  Device-1: Intel 82579V Gigabit Network vendor: Hewlett-Packard 
  driver: e1000e v: 3.2.6-k port: 4060 bus ID: 00:19.0 
  IF: enp0s25 state: down mac: <filter> 
  Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi 
  v: kernel port: 4040 bus ID: 24:00.0 
  IF: wlo1 state: up mac: <filter> 
Drives:
  Local Storage: total: 698.64 GiB used: 616.30 GiB (88.2%) 
  ID-1: /dev/sda vendor: Toshiba model: MQ01ABD075 size: 698.64 GiB 
  Optical-1: /dev/sr0 vendor: hp model: CDDVDW TS-L633R rev: 0300 
  dev-links: cdrom,cdrw,dvd,dvdrw 
  Features: speed: 24 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
Partition:
  ID-1: / size: 684.49 GiB used: 616.00 GiB (90.0%) fs: ext4 dev: /dev/dm-1 
  ID-2: /boot size: 703.5 MiB used: 307.3 MiB (43.7%) fs: ext4 
  dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 46.0 C mobo: 0.0 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 225 Uptime: 50m Memory: 7.71 GiB used: 1.78 GiB (23.0%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 
I'm a bit baffled as this should be pretty much identical hardware to the one I replaced. I know that the previous hardware had also i5 processor, so what could be the problem here?

I don't the reinstalling LM 20.1 would resolve the issue as the live USB did not work either, so it must be a hardware problem?

Any ideas?

Thanks.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

I just realised myself that even though this is the exact same model number it is not the same hardware inside. The mother board is clearly a different make. The product number of the laptop is completely different. So I guess I was just unlucky with this purchase and now have to get used to Mint Desktop without suspend functionality...
User avatar
SMG
Level 25
Level 25
Posts: 31390
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by SMG »

ozka wrote: Fri Oct 22, 2021 11:29 pm I just realised myself that even though this is the exact same model number it is not the same hardware inside. The mother board is clearly a different make. The product number of the laptop is completely different. So I guess I was just unlucky with this purchase and now have to get used to Mint Desktop without suspend functionality...
Welcome to the forum, ozka.

Do you have the drive encrypted? If so, I thought there was usually a swap partition created when that happens. I do not see one here. Maybe fstab needs updated?

Also, that root partition needs some cleaning or you soon will not be able to log in.
Partition:
ID-1: / size: 684.49 GiB used: 616.00 GiB (90.0%) fs: ext4 dev: /dev/dm-1
ID-2: /boot size: 703.5 MiB used: 307.3 MiB (43.7%) fs: ext4 dev: /dev/sda5
Image
A woman typing on a laptop with LM20.3 Cinnamon.
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

Hi SMG,

thanks for
SMG wrote: Sat Oct 23, 2021 5:30 pm Do you have the drive encrypted? If so, I thought there was usually a swap partition created when that happens. I do not see one here. Maybe fstab needs updated?
Yes, it is encrypted. As far as I remember I let the installer do its thing not that long time ago when installed 20.1. By default it created only swap with size of around 1GB, even though I had 4GB of RAM at the time. I thought it was odd, so I guess that's why I went for the swap file.

Out of curiosity I went ahead and re-enabled the original swap partition from the fstab at /dev/mapper/vgmint-swap_1 and tried suspend/restore, but encountered the same problem. I doubt it would make any difference if I somehow managed to expand the swap partition.
SMG wrote: Sat Oct 23, 2021 5:30 pm Also, that root partition needs some cleaning or you soon will not be able to log in.
Partition:
ID-1: / size: 684.49 GiB used: 616.00 GiB (90.0%) fs: ext4 dev: /dev/dm-1
ID-2: /boot size: 703.5 MiB used: 307.3 MiB (43.7%) fs: ext4 dev: /dev/sda5
True that :shock:
User avatar
SMG
Level 25
Level 25
Posts: 31390
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by SMG »

ozka wrote: Sat Oct 23, 2021 10:20 pmYes, it is encrypted. As far as I remember I let the installer do its thing not that long time ago when installed 20.1. By default it created only swap with size of around 1GB, even though I had 4GB of RAM at the time. I thought it was odd, so I guess that's why I went for the swap file.
It's my understanding the reason for the swap partition is related to how the encryption is done. That swap partition is not created for swap purposes (although it can be used for it). The main purpose of that swap partition is for the encryption. I do not use encryption, so I am not sure exactly how all those pieces and parts works.

I have an HP 6360t (which is supposed to be the thin client, but it has a 120GB hard drive with a Celeron processor), but it appears to have a number of differences from yours even though mine has the exact same BIOS version. Mine has a different motherboard and Broadcom wireless. I can suspend and resume from suspend.

If you want to investigate what may be happening on your new hardware, after suspend fails to restart and you restart using the power button, you can run the following command in a terminal:
journalctl -rb -1 | nc termbin.com 9999
It will return with a url address that you should post in your next reply if you would like us to help you with it.

That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the computer not returning from suspend should be near the top) and sends it to termbin.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

This is the output on the top of that. The rest happened much earlier so is likely irrelevant.

I forgot to mention earlier that when waking up the system from sleep by pressing the power button, the fan wakes up and some lights turn on, but for example the caps and num locks are unresponsive and the wifi light indicator stays orange meaning it is not on.

Code: Select all

Oct 24 16:27:22 probook systemd[1]: Finished GRUB failed boot detection.
Oct 24 16:27:22 probook systemd[1]: grub-initrd-fallback.service: Succeeded.
Oct 24 16:27:22 probook kernel: PM: suspend entry (deep)
Oct 24 16:27:22 probook systemd-sleep[3838]: Suspending system...
Oct 24 16:27:22 probook systemd[1]: Starting GRUB failed boot detection...
Oct 24 16:27:22 probook systemd[1]: Finished Record successful boot for GRUB.
Oct 24 16:27:22 probook systemd[1]: grub-common.service: Succeeded.
Oct 24 16:27:22 probook wpa_supplicant[928]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Oct 24 16:27:22 probook nm-dispatcher[3836]: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
Oct 24 16:27:22 probook systemd[1]: Starting Suspend...
Oct 24 16:27:22 probook systemd[1]: Starting Record successful boot for GRUB...
Oct 24 16:27:22 probook systemd[1]: Reached target Sleep.
Oct 24 16:27:22 probook wpa_supplicant[928]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-100
Oct 24 16:27:22 probook NetworkManager[870]: <info>  [1635046042.0508] device (wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Oct 24 16:27:22 probook avahi-daemon[859]: Interface wlo1.IPv4 no longer relevant for mDNS.
Oct 24 16:27:22 probook avahi-daemon[859]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.86.229.
Oct 24 16:27:22 probook avahi-daemon[859]: Withdrawing address record for 192.168.86.229 on wlo1.
Oct 24 16:27:22 probook NetworkManager[870]: <info>  [1635046042.0413] dhcp4 (wlo1): state changed bound -> done
Oct 24 16:27:22 probook NetworkManager[870]: <info>  [1635046042.0413] dhcp4 (wlo1): canceled DHCP transaction
Oct 24 16:27:22 probook avahi-daemon[859]: Interface wlo1.IPv6 no longer relevant for mDNS.
Oct 24 16:27:22 probook avahi-daemon[859]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::2cec:7d27:4bc1:31db.
Oct 24 16:27:22 probook avahi-daemon[859]: Withdrawing address record for fe80::2cec:7d27:4bc1:31db on wlo1.
Oct 24 16:27:22 probook NetworkManager[870]: <info>  [1635046042.0184] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Oct 24 16:27:22 probook NetworkManager[870]: <info>  [1635046042.0176] device (wlo1): supplicant interface state: completed -> disconnected
Oct 24 16:27:22 probook NetworkManager[870]: <warn>  [1635046042.0174] sup-iface[0x562a5a83e100,wlo1]: connection disconnected (reason -3)
Oct 24 16:27:22 probook wpa_supplicant[928]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Oct 24 16:27:22 probook wpa_supplicant[928]: wlo1: CTRL-EVENT-DISCONNECTED bssid=58:cb:52:ce:9b:af reason=3 locally_generated=1
Oct 24 16:27:21 probook kernel: wlo1: deauthenticating from 58:cb:52:ce:9b:af by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 24 16:27:21 probook systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 24 16:27:21 probook dbus-daemon[864]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 24 16:27:21 probook systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 24 16:27:21 probook dbus-daemon[864]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=870 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Oct 24 16:27:21 probook NetworkManager[870]: <info>  [1635046041.8853] device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Oct 24 16:27:21 probook NetworkManager[870]: <info>  [1635046041.8849] manager: NetworkManager state is now ASLEEP
Oct 24 16:27:21 probook NetworkManager[870]: <info>  [1635046041.8848] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Oct 24 16:27:21 probook ModemManager[1017]: <info>  [sleep-monitor] system is about to suspend
User avatar
SMG
Level 25
Level 25
Posts: 31390
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by SMG »

ozka wrote: Sat Oct 23, 2021 11:39 pm This is the output on the top of that. The rest happened much earlier so is likely irrelevant.
This is the first time I've seen so many grub references at the time of suspend/sleep, but perhaps that is because the system is encrypted. However, given you were also seeing the issues on a live session, that means those lines are unlikely to be related to the issue.

I did find one other HP ProBook 6560b listed on the forum with the same motherboard so they are floating around with Mint on them. That was a different issue.

Does the old shell still work? Can you pull one of the memory sticks out of this newer-to-you one and put it in the old one and then boot to a live session? Maybe there will be something in the inxi output of the two different shells which will give an idea of where the problem may lie.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

SMG wrote: Sun Oct 24, 2021 2:35 pm Does the old shell still work? Can you pull one of the memory sticks out of this newer-to-you one and put it in the old one and then boot to a live session? Maybe there will be something in the inxi output of the two different shells which will give an idea of where the problem may lie.
My old mobo is completely dead. It will power up but the screen stays black. I am guessing maybe the onboard graphics got fried because the system started displaying some video symptoms like garbled video output just a few days before failing completely. Also it started having issues with keyboard input lag couple of weeks before the failure. Thus unfortunately I don't think I can test the old system.

I just realised that this newer currently working system is limiting me to a lower display resolution compared to the previous one. This is slightly disappointing as I was assuming that the same laptop models would give me the same specs. Oh well, live and learn.

e. typos
User avatar
SMG
Level 25
Level 25
Posts: 31390
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by SMG »

ozka wrote: Sun Oct 24, 2021 5:11 pmI just realised that this newer currently working system is limiting me to a lower display resolution compared to the previous one. This is slightly disappointing as I was assuming that the same laptop models would give me the same specs. Oh well, live and learn.
HP does not necessarily offer only one screen size per model. I've thought about getting a backup for one of mine, but finding one with the higher screen resolution (which I currently have) is not easy since one really needs to know the exact code so it can be checked on the HP site. Model number is not enough info. Most versions have the lower resolution displays.

I do not have any other ideas for the issue with your current shell. Maybe someone else will.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

As a one additional solution that I tried was to boot the system using LM 19.1 live USB in hopes that an older kernel version might have better support for the hardware. No luck with that one. I wonder if I should try with even older releases just in case :?:
User avatar
SMG
Level 25
Level 25
Posts: 31390
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by SMG »

ozka wrote: Sun Oct 24, 2021 5:23 pmI wonder if I should try with even older releases just in case :?:
There are no older releases. Only LM19 and LM20 are currently supported. LM18 went end of life in April.

I'm running LM20.2 on my HP ProBook 6360t with the 5.4 kernel and I can suspend and resume from suspend.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

SMG wrote: Sun Oct 24, 2021 5:56 pm
ozka wrote: Sun Oct 24, 2021 5:23 pmI wonder if I should try with even older releases just in case :?:
There are no older releases. Only LM19 and LM20 are currently supported. LM18 went end of life in April.

I'm running LM20.2 on my HP ProBook 6360t with the 5.4 kernel and I can suspend and resume from suspend.
Yeah. I tried the LMDE 4 just out of curiosity. I also tried LM 17.1 just out of curiousity. They both behave the exact same way what it comes to this issue.
ozka
Level 1
Level 1
Posts: 9
Joined: Fri Oct 22, 2021 10:10 pm

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by ozka »

For what it's worth, I also downloaded openSUSE Gnome live image as openSUSE seems to be officially supported by HP for this hardware. The openSUSE live system had the exact same issue with returning from suspend. That makes me think, there must be something wrong with the hardware.
User avatar
SMG
Level 25
Level 25
Posts: 31390
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: 20.1 64-bit Cinnamon suspend issues with HP ProBook 6560b

Post by SMG »

Maybe suspending by a different method might work? Here is an explanation of two terminal commands to suspend pm-suspend vs systemctl suspend?. Mint uses systemd, so I would presume sudo systemctl suspend is the preferred command, but you can try both to see if one might work. I don't give it really high hopes given how many operating systems you have tried, but it might be worth a shot.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
Locked

Return to “Other topics”