Hp 650 G1 turns on after shutdown

bake55 · Post by **bake55** » Tue Mar 16, 2021 11:10 am

Hi,

My spec:
Beside spec provided on the internet,
laptop has a dead battery and It has only integrated graphic card and 4gb of ram.

Laptop was at my friend place for cleaning purpose (yes, he has some tech degree).
I can't remember if problem started before or after cleaning, but I think I have deja vu

that this started sometime before last year.
When I shut it down (not by button) after like 30-60 seconds it turns back on, I realized I have those 30 seconds to unplug the AC adapter.

(I have stock Mint.)

Last year my old landlord was thinking laptops are like toasters,
not a prob if you unplug AC adapter when laptop is ON.
He did it ONCE, so since then I was hiding all my devices from him.

Post by **SMG** » Tue Mar 16, 2021 4:05 pm

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

bake55 · Post by **bake55** » Sat Apr 17, 2021 7:03 am

Sorry for the late response, I wanted to see if there is the same problem on Windows 10.
Turns out the problem disappeared on win10...

But I had some driver problems on win10 so I decided to install latest Mint.
Problem is still here on MINT.

Code: Select all

john@john:~$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Xfce 4.14.2 tk: Gtk 3.24.13 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP ProBook 650 G1 
  v: A3009CD10002 serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: Hewlett-Packard model: 1993 v: KBC Version 16.3C serial: <filter> 
  BIOS: Hewlett-Packard v: L77 Ver. 01.46 date: 07/30/2018 
CPU:
  Topology: Dual Core model: Intel Core i5-4210M bits: 64 type: MT MCP 
  arch: Haswell rev: 3 L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 20752 
  Speed: 838 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 798 2: 799 
  3: 798 4: 799 
Graphics:
  Device-1: Intel 4th Gen Core Processor Integrated Graphics 
  vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0416 
  Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) 
  v: 4.5 Mesa 20.2.6 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:03.0 
  chip ID: 8086:0c0c 
  Device-2: Intel 8 Series/C220 Series High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:8c20 
  Sound Server: ALSA v: k5.4.0-72-generic 
Network:
  Device-1: Intel Ethernet I217-V vendor: Hewlett-Packard driver: e1000e 
  v: 3.2.6-k port: 3080 bus ID: 00:19.0 chip ID: 8086:153b 
  IF: enp0s25 state: down mac: <filter> 
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: ef80 
  bus ID: 02:00.0 chip ID: 8086:08b1 
  IF: wlo1 state: up mac: <filter> 
Drives:
  Local Storage: total: 111.79 GiB used: 8.53 GiB (7.6%) 
  ID-1: /dev/sda vendor: Silicon Power model: SPCC Solid State Disk 
  size: 111.79 GiB speed: 6.0 Gb/s serial: <filter> rev: 71.1 scheme: MBR 
Partition:
  ID-1: / size: 27.37 GiB used: 8.09 GiB (29.5%) fs: ext4 dev: /dev/sda1 
  ID-2: /home size: 80.20 GiB used: 447.2 MiB (0.5%) fs: ext4 dev: /dev/sda6 
  ID-3: swap-1 size: 1.86 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 44.0 C mobo: 0.0 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list 
  1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 201 Uptime: 11m Memory: 3.76 GiB used: 1.28 GiB (33.9%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: xfce4-terminal inxi: 3.0.38

Post by **SMG** » Sat Apr 17, 2021 9:59 am

According to Software and drivers for HP ProBook 650 G1 Notebook PC, the latest BIOS is 01.50. There are several fixes in the version between what you have and the latest.

Machine:
Type: Laptop System: Hewlett-Packard product: HP ProBook 650 G1
v: A3009CD10002 serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 1993 v: KBC Version 16.3C serial: <filter>
BIOS: Hewlett-Packard v: L77 Ver. 01.46 date: 07/30/2018

It's possible that update may clear this issue. If not, we'll probably need to check the logs to find out what is happening.

bake55 · Post by **bake55** » Sat Apr 17, 2021 1:35 pm

I made a bootable usb on my windows device. Inserted usb and started my laptop and it won't update, I even tried Network update via Lan and got "you have latest version".

I am thinking to install win10 and update... but I think that's not a problem since my laptop didn't turned on itself
on previous Win10 system.

Post by **SMG** » Sat Apr 17, 2021 1:45 pm

After you get an automatic reboot when you attempt to shut down (do not pull out the power cable), run the following in a terminal:
journalctl -rb | nc termbin.com 9999
It prints the journal log information of the boot cycle in reverse order (so the reason for the reboot should be near the top) and sends it to termbin. It will return with a url address that you should post in your next reply.

Please also run the following:
journalctl -rb -1 | nc termbin.com 9999
which will give another url. Because I'm not sure what is happening, I'm not sure which one will give us the information we want. Hopefully, one of those two will.

bake55 · Post by **bake55** » Sat Apr 17, 2021 2:24 pm

1 log
https://termbin.com/ry43

2 log
https://termbin.com/i7zw

Post by **SMG** » Sat Apr 17, 2021 4:57 pm

bake55 wrote: ⤴Sat Apr 17, 2021 2:24 pm 1 log
https://termbin.com/ry43

This is your current boot cycle which started Apr 17 20:20:27. That means Mint started 18 seconds after the prior boot cycle ended.

bake55 wrote: ⤴Sat Apr 17, 2021 2:24 pm2 log
https://termbin.com/i7zw

This is the boot cycle before it. These are the last few lines which are lines normally seen at the end of the journal.

Code: Select all

Apr 17 20:20:09 john systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 17 20:20:09 john systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 17 20:20:09 john systemd-journald[343]: Journal stopped

Sending SIGTERM is sending the termination signal to the hardware. Once the journal ends, nothing more is written to it, but it's possible lines may be written to the screen after the journal stops.

It is possible there is something in the power delivery system of the computer (battery, adapter, etc.) which might be causing the restart and not something from Mint. Do you have any external devices such as a docking station attached to the computer? That caused this type of situation to happen for someone else (although I think that showed up in the log--I can't recall for sure).

The only suggestion I have is to press the Escape key when you see the Mint logo at shutdown. That will clear the "quiet splash" part of shutdown and show the messages on the screen. See if there are any messages after the journal stop message.

bake55 · Post by **bake55** » Sun Apr 18, 2021 2:58 am

I tried Esc on logo and it print something really fast, turns on again.
I have only AC adapter on my laptop, no battery.

Post by **SMG** » Sun Apr 18, 2021 1:59 pm

Is there a "Wake on LAN" option in your BIOS/UEFI?

Are you using an HP power adapter?

The initial powering on of a computer is done by the hardware. Your computer is pretty fast, but, when it restarts after shutting down, are you able to get into BIOS? Are you seeing a flash of the HP logo (presuming you normally see the HP logo when you start the computer)?

bake55 · Post by **bake55** » Mon Apr 19, 2021 3:14 am

It wasn't ON.
https://imgur.com/a/N2DcrFP

I see HP logo on start.

Post by **SMG** » Mon Apr 19, 2021 10:08 pm

I just ran a test on my HP laptop. I normally shut down the computer each night, but I did the Restart option to check if the HP logo came up. It did, but I found something interesting in the logs.

This is what came up when I did the restart. Notice Mint sends the Reboot command when it wants the computer to restart.

Code: Select all

Apr 19 21:02:12 SMG-HP-6360t systemd-journald[297]: Journal stopped
Apr 19 21:02:12 SMG-HP-6360t systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 19 21:02:12 SMG-HP-6360t systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Shutting down.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Reached target Reboot.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Finished Reboot.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: systemd-reboot.service: Succeeded.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Reached target Final Step.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Finished Shuts down the "live" preinstalled system cleanly.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: casper.service: Succeeded.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Reached target Shutdown.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: lvm2-monitor.service: Succeeded.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Reached target Unmount All Filesystems.
Apr 19 21:02:12 SMG-HP-6360t systemd[1]: Deactivated swap /swapfile.

Here is what happened when it shutdown last night. Notice Mint sent the Power-Off signal to my laptop. (I have an older laptop for which I normally have the battery removed to keep down the recharge cycles so it lasts longer.)

Code: Select all

Apr 18 23:04:17 SMG-HP-6360t systemd-journald[297]: Journal stopped
Apr 18 23:04:17 SMG-HP-6360t systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 18 23:04:17 SMG-HP-6360t systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Shutting down.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Reached target Power-Off.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Finished Power-Off.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-poweroff.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Reached target Final Step.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Finished Shuts down the "live" preinstalled system cleanly.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: casper.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Reached target Shutdown.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: lvm2-monitor.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-backlight@backlight:acpi_video0.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-backlight@backlight:intel_backlight.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Create System Users.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-sysusers.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped target Local File Systems (Pre).
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped target Local File Systems.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Create Volatile Files and Directories.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: systemd-update-utmp.service: Succeeded.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Reached target Unmount All Filesystems.
Apr 18 23:04:16 SMG-HP-6360t systemd[1]: Deactivated swap /swapfile.

I copied both logs from the "Deactivated swap /swapfile" line to the end. If you scroll through the two options, you'll notice the Power-Off one is longer than the Reboot one. That is because when the system is told to Reboot by Mint, a "warm" boot happens. The hardware is not powered down completely to restart.

Your shutdown looks similar to my shutdown. (Yours is a bit longer, but I do not have a swap partition.) Yours does not look like the Reboot one. That leads me to believe the restart is happening because of something in your hardware.

Code: Select all

Apr 17 20:20:09 john systemd-journald[343]: Journal stopped
Apr 17 20:20:09 john systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 17 20:20:09 john systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 17 20:20:09 john systemd[1]: Shutting down.
Apr 17 20:20:09 john systemd[1]: Reached target Power-Off.
Apr 17 20:20:09 john systemd[1]: Finished Power-Off.
Apr 17 20:20:09 john systemd[1]: systemd-poweroff.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Reached target Final Step.
Apr 17 20:20:09 john systemd[1]: Finished Shuts down the "live" preinstalled system cleanly.
Apr 17 20:20:09 john systemd[1]: casper.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
Apr 17 20:20:09 john systemd[1]: Reached target Shutdown.
Apr 17 20:20:09 john systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Apr 17 20:20:09 john systemd[1]: lvm2-monitor.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 17 20:20:09 john systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopped Create System Users.
Apr 17 20:20:09 john systemd[1]: systemd-sysusers.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 17 20:20:09 john systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Apr 17 20:20:09 john systemd[1]: Stopped target Local File Systems (Pre).
Apr 17 20:20:09 john systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Apr 17 20:20:09 john systemd[1]: Stopped File System Check on /dev/disk/by-uuid/23e6138e-d4d9-4625-8a5e-cd8369637614.
Apr 17 20:20:09 john systemd[1]: systemd-fsck@dev-disk-by\x2duuid-23e6138e\x2dd4d9\x2d4625\x2d8a5e\x2dcd8369637614.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Reached target Unmount All Filesystems.
Apr 17 20:20:09 john systemd[1]: Unmounted /home.
Apr 17 20:20:09 john systemd[1]: home.mount: Succeeded.
Apr 17 20:20:09 john systemd[1]: Deactivated swap /dev/disk/by-uuid/2e620b5c-25ee-4a97-a0c2-e2d56f82225c.
Apr 17 20:20:09 john systemd[1]: dev-disk-by\x2duuid-2e620b5c\x2d25ee\x2d4a97\x2da0c2\x2de2d56f82225c.swap: Succeeded.
Apr 17 20:20:09 john systemd[1]: Deactivated swap /dev/sda5.
Apr 17 20:20:09 john systemd[1]: dev-sda5.swap: Succeeded.
Apr 17 20:20:09 john systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000000000000000-part5.
Apr 17 20:20:09 john systemd[1]: dev-disk-by\x2did-wwn\x2d0x5000000000000000\x2dpart5.swap: Succeeded.
Apr 17 20:20:09 john systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part5.
Apr 17 20:20:09 john systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart5.swap: Succeeded.
Apr 17 20:20:09 john systemd[1]: Deactivated swap /dev/disk/by-partuuid/e45f82fb-05.
Apr 17 20:20:09 john systemd[1]: dev-disk-by\x2dpartuuid-e45f82fb\x2d05.swap: Succeeded.
Apr 17 20:20:09 john systemd[1]: Deactivated swap /dev/disk/by-id/ata-SPCC_Solid_State_Disk_A4720777193000019475-part5.
Apr 17 20:20:09 john systemd[1]: dev-disk-by\x2did-ata\x2dSPCC_Solid_State_Disk_A4720777193000019475\x2dpart5.swap: Succeeded.
Apr 17 20:20:09 john systemd[1]: Unmounting /home...
Apr 17 20:20:09 john systemd[1]: Stopped target Local File Systems.
Apr 17 20:20:09 john systemd[1]: Stopped Create Volatile Files and Directories.
Apr 17 20:20:09 john systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Apr 17 20:20:09 john systemd[1]: systemd-update-utmp.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
Apr 17 20:20:09 john systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight.
Apr 17 20:20:09 john systemd[1]: systemd-backlight@backlight:intel_backlight.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Apr 17 20:20:09 john systemd[1]: Stopped Load Kernel Modules.
Apr 17 20:20:09 john systemd[1]: systemd-modules-load.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopped Apply Kernel Variables.
Apr 17 20:20:09 john systemd[1]: systemd-sysctl.service: Succeeded.
Apr 17 20:20:09 john systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:intel_backlight...
Apr 17 20:20:09 john systemd[1]: Deactivating swap /dev/disk/by-id/ata-SPCC_Solid_State_Disk_A4720777193000019475-part5...
Apr 17 20:20:09 john systemd[1]: Stopped target Swap.

bake55 wrote: ⤴Mon Apr 19, 2021 3:14 amIt wasn't ON.

I didn't ask you if it was on; I asked you if the option even existed. I'm trying to help you figure out what is happening. Something is telling the laptop to start and it does not appear that Mint is doing it.

I suppose it's possible it could be a faulty power switch if it is not something related to the battery/charging system. I do not know how the electrical system is designed to handle a "dead battery" situation. It's possible the dead battery put it into a state of constant restart because there is no need to conserve the battery's energy. I do not know the design criteria, so that is a guess on my part.

That is all I have been able to determine. I do not have any other ideas to investigate. Maybe someone else will have other ideas and will post.

bake55 · Post by **bake55** » Tue Apr 20, 2021 3:13 am

I don't think it's HW problem.
Problem disappeared on win10

senjoz · Post by **senjoz** » Tue Apr 20, 2021 7:51 am

I have some ideas. Some may look slightly silly but I mention them anyway.

I would boot in a Mint live installation session from the USB key, shutdown the machine from there and wait if the machine will restart after 30 to 60 seconds.

In Xfce power manager I would choose for "When the power button is pressed" option "Shut down" and for "On critical battery power" option "Shutdown". I would restart and then shut down the mahine with a short press on the power button.

If the above mentioned would not help, I would go to the Bios and disable all non essential devices like wlan, lan, camera, fingerprint, tpm, sound and similar.

If the above mentioned would not help, I would go through all Bios settings and change every setting which could affect boot. If I would find a "Power monitor circuit" or "Power on unit when lid is opened", I would also change those settings. Last one is my favorite.

Regards, Jože

EDIT: I would try those ideas also with the battery inserted, despite it being dead.

Post by **SMG** » Tue Apr 20, 2021 9:26 am

bake55 wrote: ⤴Tue Apr 20, 2021 3:13 amI don't think it's HW problem.
Problem disappeared on win10

Then why isn't everyone with Mint having this problem, if according to you the problem is with Mint?

Win10 updates have been known to make BIOS/UEFI changes. There have been plenty of posts on this forum describing that happening.

senjoz has made some good suggestions. See if any of those help or provide clues as to what might be happening.

bake55 · Post by **bake55** » Wed Apr 21, 2021 4:33 am

senjoz wrote: ⤴Tue Apr 20, 2021 7:51 am I have some ideas. Some may look slightly silly but I mention them anyway.

I would boot in a Mint live installation session from the USB key, shutdown the machine from there and wait if the machine will restart after 30 to 60 seconds.

In Xfce power manager I would choose for "When the power button is pressed" option "Shut down" and for "On critical battery power" option "Shutdown". I would restart and then shut down the mahine with a short press on the power button.

If the above mentioned would not help, I would go to the Bios and disable all non essential devices like wlan, lan, camera, fingerprint, tpm, sound and similar.

If the above mentioned would not help, I would go through all Bios settings and change every setting which could affect boot. If I would find a "Power monitor circuit" or "Power on unit when lid is opened", I would also change those settings. Last one is my favorite.

Regards, Jože

EDIT: I would try those ideas also with the battery inserted, despite it being dead.

Without battery:

1. I tried in XFCE power manager...
2. I reset my Bios to factory.
3. I tried booting with Live USB and then shut down and it didn't restart.
4. After I turned it back on and shut down it restarts again.

With battery:
1. I tried in xfce power manager...
2. I tried pressing shut down button and it restarts.

What now?

LDevil · Post by **LDevil** » Tue May 24, 2022 4:16 pm

I had similar problems with HP 640 G1, I was unable to turn it off. It was turning on automatically after a few seconds.
After disabling Wake on LAN, Wake on USB and USB charging in BIOS problem is gone. Maybe there is no need to disable all these options, but I was not interested in finding most optimal solution.

Prlwytzkofski · Post by **Prlwytzkofski** » Sat Jul 09, 2022 1:09 pm

I had this same problem too on an HP 650 G1. In my case, turning off the Wake-on-LAN "Feature" in the BIOS/UEFI settings solved the problem. But this was the second laptop I experienced this with. After upgrading the BIOS on the first one, I lost essential hardware info stored in an EEPROM. I got a "new" refurbished one... First all went well, but after some testing and installing the restart problem reappeared. Wake-on-LAN was on... Fingers crossed this won't happen again at the user's desk.

Prlwytzkofski · Post by **Prlwytzkofski** » Sat Jul 09, 2022 2:42 pm

I did a termbin upload:

Code: Select all

[*-- Logs begin at Sat 2022-07-09 11:43:06 CEST, end at Sat 2022-07-09 18:43:04 CEST. --
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.8581] manager: NetworkManager state is now CONNECTED_GLOBAL
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd-resolved[620]: Using degraded feature set (UDP) for DNS server 192.168.178.1.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: Listening on routing socket on fd #21 for interface updates
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: failed to init interface for address fe80::f75:6904:c254:dc07%2
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: unable to create socket on enp0s25 (5) for fe80::f75:6904:c254:dc07%2#123
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: bind(21) AF_INET6 fe80::f75:6904:c254:dc07%2#123 flags 0x11 failed: Cannot assign requested address
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: Listen normally on 4 lo [::1]:123
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: Listen normally on 3 enp0s25 192.168.178.54:123
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: Listen normally on 2 lo 127.0.0.1:123
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: Listen and drop on 1 v4wildcard 0.0.0.0:123
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: Listen and drop on 0 v6wildcard [::]:123
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1840]: proto: precision = 0.075 usec (-24)
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd[1]: Started Network Time Service.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1837]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /run/ntp.conf.dhcp -u 106:111
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[1837]: ntpd 4.2.8p12@1.3728-o (1): Starting
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd[1]: Starting Network Time Service...
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd[1]: Stopped Network Time Service.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd[1]: ntp.service: Succeeded.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd[1]: Stopping Network Time Service...
jul 09 18:43:04 prlw-HP-ProBook-650-G1 ntpd[792]: ntpd exiting on signal 15 (Terminated)
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5420] device (enp0s25): Activation: successful, device activated.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5413] policy: set 'Ethernetkabel' (enp0s25) as default for IPv4 routing and DNS
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5412] manager: NetworkManager state is now CONNECTED_SITE
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5399] manager: NetworkManager state is now CONNECTED_LOCAL
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5393] device (enp0s25): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5390] device (enp0s25): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd[1]: Started Network Manager Script Dispatcher Service.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 dbus-daemon[644]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 systemd[1]: Starting Network Manager Script Dispatcher Service...
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5212] device (enp0s25): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): state changed unknown -> bound
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option subnet_mask          => '255.255.255.0'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option routers              => '192.168.178.1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option requested_wpad       => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 dbus-daemon[644]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=645 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option requested_time_offset => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option requested_subnet_mask => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option requested_static_routes => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option requested_routers    => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option requested_root_path  => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5197] dhcp4 (enp0s25): option requested_rfc3442_classless_static_routes => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_ntp_servers => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_nis_servers => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_nis_domain => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_ms_classless_static_routes => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_interface_mtu => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 avahi-daemon[638]: Registering new address record for 192.168.178.54 on enp0s25.IPv4.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_host_name  => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 avahi-daemon[638]: New relevant interface enp0s25.IPv4 for mDNS.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_domain_search => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_domain_name_servers => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_domain_name => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 avahi-daemon[638]: Joining mDNS multicast group on interface enp0s25.IPv4 with address 192.168.178.54.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option requested_broadcast_address => '1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option ntp_servers          => '192.168.178.1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option next_server          => '192.168.178.1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option ip_address           => '192.168.178.54'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option expiry               => '1658248984'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option domain_name_servers  => '192.168.178.1'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5196] dhcp4 (enp0s25): option domain_name          => 'fritz.box'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5195] dhcp4 (enp0s25): option dhcp_lease_time      => '864000'
jul 09 18:43:04 prlw-HP-ProBook-650-G1 avahi-daemon[638]: Registering new address record for fe80::f75:6904:c254:dc07 on enp0s25.*.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 avahi-daemon[638]: New relevant interface enp0s25.IPv6 for mDNS.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 avahi-daemon[638]: Joining mDNS multicast group on interface enp0s25.IPv6 with address fe80::f75:6904:c254:dc07.
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5069] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5061] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5051] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5041] manager: NetworkManager state is now CONNECTING
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5021] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.5010] device (enp0s25): Activation: starting connection 'Ethernetkabel' (eba02140-299c-3697-b705-f3add0123d5d)
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.4991] policy: auto-activating connection 'Ethernetkabel' (eba02140-299c-3697-b705-f3add0123d5d)
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.4969] device (enp0s25): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
jul 09 18:43:04 prlw-HP-ProBook-650-G1 NetworkManager[645]: <info>  [1657384984.4958] device (enp0s25): carrier: link connected
jul 09 18:43:04 prlw-HP-ProBook-650-G1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s25: link becomes ready
jul 09 18:43:04 prlw-HP-ProBook-650-G1 kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
jul 09 18:42:51 prlw-HP-ProBook-650-G1 pkexec[1742]: prlw: Executing command [USER=root] [TTY=unknown] [CWD=/home/prlw] [COMMAND=/usr/sbin/mate-power-backlight-helper --set-brightness 5273]
jul 09 18:42:51 prlw-HP-ProBook-650-G1 pkexec[1742]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
jul 09 18:42:50 prlw-HP-ProBook-650-G1 pkexec[1735]: prlw: Executing command [USER=root] [TTY=unknown] [CWD=/home/prlw] [COMMAND=/usr/sbin/mate-power-backlight-helper --set-brightness 1582]
jul 09 18:42:50 prlw-HP-ProBook-650-G1 pkexec[1735]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
jul 09 18:42:17 prlw-HP-ProBook-650-G1 xdg-desktop-por[1428]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list
jul 09 18:42:17 prlw-HP-ProBook-650-G1 ntpd[792]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
jul 09 18:42:17 prlw-HP-ProBook-650-G1 ntpd[792]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
jul 09 18:42:16 prlw-HP-ProBook-650-G1 systemd[1]: systemd-hostnamed.service: Succeeded.
jul 09 18:42:16 prlw-HP-ProBook-650-G1 ntpd[792]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
jul 09 18:42:15 prlw-HP-ProBook-650-G1 ntpd[792]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
jul 09 18:42:11 prlw-HP-ProBook-650-G1 ntpd[792]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
jul 09 18:42:01 prlw-HP-ProBook-650-G1 pkexec[1641]: prlw: Executing command [USER=root] [TTY=unknown] [CWD=/home/prlw] [COMMAND=/usr/sbin/mate-power-backlight-helper --set-brightness 5273]
jul 09 18:42:01 prlw-HP-ProBook-650-G1 pkexec[1641]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1]: Removed slice User Slice of UID 117.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1]: Stopped User Runtime Directory /run/user/117.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1]: user-runtime-dir@117.service: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1056]: run-user-117.mount: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1]: run-user-117.mount: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1]: Stopping User Runtime Directory /run/user/117...
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1]: Stopped User Manager for UID 117.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[1]: user@117.service: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Reached target Exit the Session.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Finished Exit the Session.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: systemd-exit.service: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Reached target Shutdown.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed Sound System.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: pulseaudio.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed debconf communication socket.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: pk-debconf-helper.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed GnuPG cryptographic agent and passphrase cache.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: gpg-agent.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed GnuPG cryptographic agent (ssh-agent emulation).
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: gpg-agent-ssh.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: gpg-agent-extra.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: gpg-agent-browser.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed GnuPG network certificate management daemon.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: dirmngr.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Closed D-Bus User Message Bus Socket.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: dbus.socket: Succeeded.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Stopped target Timers.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Stopped target Sockets.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Stopped target Paths.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Stopped target Basic System.
jul 09 18:41:54 prlw-HP-ProBook-650-G1 systemd[884]: Stopped Virtual filesystem service.]

Maybe someone can shed a light on this. It looks as if the LAN connection restarts after losing time-sync.
The OS is Mint MATE 20.3 64bit, 8GB ram 240GB SSD Core i5-4310M No dual-boot.
I had to set the UEFI to legacy otherwise the laptop did not boot after installation, it looped continuously until stopped by the ESC-key and do an install from a stick again to get things running. BTW, the restart problem occurred on windows and on a Mint USB-boot also.

AndyMH · Post by **AndyMH** » Sat Jul 09, 2022 3:31 pm

Prlwytzkofski, if you are going to paste a wall of output, at least use code markers to make it more readable for others, second, it is considered bad manners to hijack someone else's post.

bake55 you are running a 5.4.0-72 kernel, this has been updated several times, I'm currently running 5.4.0-121. Try doing an update, the later kernel might fix the problem. In the past I have had the same problem, never knew what caused the problem, it went away, might have been a kernel update that fixed it.

Linux Mint Forums

Hp 650 G1 turns on after shutdown

Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown

Re: Hp 650 G1 turns on after shutdown