HP Z420 doesn’t complete internet shutdown to router

English Network/Internet
1

System is EFI, secure boot disabled, Win10 & Leap 15.4, Ethernet connected to router.
Just looking for suggestions for the internet connection to allow for complete close at system shutdown.
I will get images of the Ethernet panels if needed.

When I shutdown the PC down regardless of how it is done, there is an ‘amber’ (10/100 Mbps) light on the router that should be off. To me that indicates the internet connection is still on @ low speed.
When running that light is white(1000Mbps).

I have looked at the internet connection properties, and it looks right. May need a bit of tweaking, I don’t know?

Where to start looking at the connection settings so it fully shuts down ?

Incidentally, Win10 does a complete internet shutdown @ power off.

2

Is Wake on LAN or similar enabled in BIOS settings?

The question is really more hardware question than Network/Internet.

3

Is there a way to automatically disconnect Network Managers connection at shutdown?

I have three EFI machines with Leap 15.4 and Windows 10.
If I connect them to the router via Ethernet, Leap leaves a ‘connection’ showing on the router panel (the amber light - low speed).

When I start Win10 then do a shutdown it disconnects the connection(no amber light).

Other question is:
will wicked maintain the connection at shutdown like Network Manager does?

BIOS:
WAKE ON lAN is disabled.
Network WAKE is disabled
NIC - I don’t know what that is, but I left it alone.

4

Show output of “ethtool interface-name” as root after Leap is booted.

1 Like
5

localhost:~ # ethtool interface-name
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
netlink error: no device matches name (offset 24)
netlink error: No such device
No data available

6

@Bill_L interface-name means eth0, or eno1 etc, check the output from ip a command.

Just unplug the system power cord… HP and others have lights out management capabilities for remote control powered from the system power supply. You need to look at the BIOS setup.

7

I can’t find anything in the BIOS that relates to ‘lights out management’
Any ideas about what to look for??
It is a work station that does not have server capabilities(just don’t know)

Opensuse, I added a WiFi connection. It still displays the amber light on the router.
I deleted the Ethernet connection, and the amber light is still glowing at shutdown

I can’t get to the power cored easily to unplug it.

Still question why windows shuts it down(no amber) and Leap doesn’t.

8

You could still provide the output I requested earlier.

9

OK! here is the COMPLETE output:

**ls -lR /boot/efi**
/boot/efi:
total 1
drwxr-xr-x 5 root root 1024 Jan 18 20:14 EFI

/boot/efi/EFI:
total 3
drwxr-xr-x 2 root root 1024 Jan 16 18:55 Boot
drwxr-xr-x 4 root root 1024 Jan 16 18:50 Microsoft
drwxr-xr-x 2 root root 1024 Jan 18 20:15 opensuse

/boot/efi/EFI/Boot:
total 1551
-rwxr-xr-x 1 root root 1587552 Jan 16 19:49 bootx64.efi

/boot/efi/EFI/Microsoft:
total 6
drwxr-xr-x 40 root root 5120 Jan 16 18:50 Boot
drwxr-xr-x  2 root root 1024 Jan 16 18:55 Recovery

/boot/efi/EFI/Microsoft/Boot:
total 5843
-rwxr-xr-x 1 root root   36864 Jan 20 18:45 BCD
-rwxr-xr-x 1 root root   65536 Jan 16 18:50 BCD.LOG
-rwxr-xr-x 1 root root       0 Jan 16 18:55 BCD.LOG1
-rwxr-xr-x 1 root root       0 Jan 16 18:55 BCD.LOG2
-rwxr-xr-x 1 root root   65536 Jan 16 20:01 BOOTSTAT.DAT
drwxr-xr-x 2 root root    2048 Jan 16 18:55 Fonts
drwxr-xr-x 3 root root    1024 Jan 16 18:55 Resources
drwxr-xr-x 2 root root    1024 Jan 16 18:55 bg-BG
-rwxr-xr-x 1 root root    4933 Sep  7 22:07 boot.stl
-rwxr-xr-x 1 root root 1587552 Jan 16 19:49 bootmgfw.efi
-rwxr-xr-x 1 root root 1571168 Jan 16 19:49 bootmgr.efi
drwxr-xr-x 2 root root    1024 Jan 16 18:55 cs-CZ
drwxr-xr-x 2 root root    1024 Jan 16 18:55 da-DK
drwxr-xr-x 2 root root    1024 Jan 16 18:55 de-DE
drwxr-xr-x 2 root root    1024 Jan 16 18:55 el-GR
drwxr-xr-x 2 root root    1024 Jan 16 18:55 en-GB
drwxr-xr-x 2 root root    1024 Jan 16 18:55 en-US
drwxr-xr-x 2 root root    1024 Jan 16 18:55 es-ES
drwxr-xr-x 2 root root    1024 Jan 16 18:55 es-MX
drwxr-xr-x 2 root root    1024 Jan 16 18:55 et-EE
drwxr-xr-x 2 root root    1024 Jan 16 18:55 fi-FI
drwxr-xr-x 2 root root    1024 Jan 16 18:55 fr-CA
drwxr-xr-x 2 root root    1024 Jan 16 18:55 fr-FR
drwxr-xr-x 2 root root    1024 Jan 16 18:55 hr-HR
drwxr-xr-x 2 root root    1024 Jan 16 18:55 hu-HU
drwxr-xr-x 2 root root    1024 Jan 16 18:55 it-IT
drwxr-xr-x 2 root root    1024 Jan 16 18:55 ja-JP
-rwxr-xr-x 1 root root   32616 Sep  7 22:07 kd_02_10df.dll
-rwxr-xr-x 1 root root  380240 Sep  7 22:07 kd_02_10ec.dll
-rwxr-xr-x 1 root root   27488 Sep  7 22:07 kd_02_1137.dll
-rwxr-xr-x 1 root root  240992 Sep  7 22:07 kd_02_14e4.dll
-rwxr-xr-x 1 root root   45392 Sep  7 22:07 kd_02_15b3.dll
-rwxr-xr-x 1 root root   45408 Sep  7 22:07 kd_02_1969.dll
-rwxr-xr-x 1 root root   32600 Sep  7 22:07 kd_02_19a2.dll
-rwxr-xr-x 1 root root   21344 Sep  7 22:07 kd_02_1af4.dll
-rwxr-xr-x 1 root root  299360 Sep  7 22:07 kd_02_8086.dll
-rwxr-xr-x 1 root root   19800 Sep  7 22:07 kd_07_1415.dll
-rwxr-xr-x 1 root root   50000 Sep  7 22:07 kd_0C_8086.dll
-rwxr-xr-x 1 root root   18784 Sep  7 22:07 kdnet_uart16550.dll
-rwxr-xr-x 1 root root   28512 Sep  7 22:07 kdstub.dll
drwxr-xr-x 2 root root    1024 Jan 16 18:55 ko-KR
drwxr-xr-x 2 root root    1024 Jan 16 18:55 lt-LT
drwxr-xr-x 2 root root    1024 Jan 16 18:55 lv-LV
-rwxr-xr-x 1 root root 1351536 Sep  7 22:07 memtest.efi
drwxr-xr-x 2 root root    1024 Jan 16 18:55 nb-NO
drwxr-xr-x 2 root root    1024 Jan 16 18:55 nl-NL
drwxr-xr-x 2 root root    1024 Jan 16 18:55 pl-PL
drwxr-xr-x 2 root root    1024 Jan 16 18:55 pt-BR
drwxr-xr-x 2 root root    1024 Jan 16 18:55 pt-PT
drwxr-xr-x 2 root root    1024 Jan 16 18:55 qps-ploc
drwxr-xr-x 2 root root    1024 Jan 16 18:55 ro-RO
drwxr-xr-x 2 root root    1024 Jan 16 18:55 ru-RU
drwxr-xr-x 2 root root    1024 Jan 16 18:55 sk-SK
drwxr-xr-x 2 root root    1024 Jan 16 18:55 sl-SI
drwxr-xr-x 2 root root    1024 Jan 16 18:55 sr-Latn-RS
drwxr-xr-x 2 root root    1024 Jan 16 18:55 sv-SE
drwxr-xr-x 2 root root    1024 Jan 16 18:55 tr-TR
drwxr-xr-x 2 root root    1024 Jan 16 18:55 uk-UA
-rwxr-xr-x 1 root root    9796 Dec  7  2019 winsipolicy.p7b
drwxr-xr-x 2 root root    1024 Jan 16 18:55 zh-CN
drwxr-xr-x 2 root root    1024 Jan 16 18:55 zh-TW

/boot/efi/EFI/Microsoft/Boot/Fonts:
total 13175
-rwxr-xr-x 1 root root 3695830 Dec  7  2019 chs_boot.ttf
-rwxr-xr-x 1 root root 3878309 Dec  7  2019 cht_boot.ttf
-rwxr-xr-x 1 root root 1985767 Dec  7  2019 jpn_boot.ttf
-rwxr-xr-x 1 root root 2372900 Dec  7  2019 kor_boot.ttf
-rwxr-xr-x 1 root root  177888 Dec  7  2019 malgun_boot.ttf
-rwxr-xr-x 1 root root  175429 Dec  7  2019 malgunn_boot.ttf
-rwxr-xr-x 1 root root  145684 Dec  7  2019 meiryo_boot.ttf
-rwxr-xr-x 1 root root  144017 Dec  7  2019 meiryon_boot.ttf
-rwxr-xr-x 1 root root  165524 Dec  7  2019 msjh_boot.ttf
-rwxr-xr-x 1 root root  163496 Dec  7  2019 msjhn_boot.ttf
-rwxr-xr-x 1 root root  157064 Dec  7  2019 msyh_boot.ttf
-rwxr-xr-x 1 root root  155438 Dec  7  2019 msyhn_boot.ttf
-rwxr-xr-x 1 root root   44760 Dec  7  2019 segmono_boot.ttf
-rwxr-xr-x 1 root root   86077 Dec  7  2019 segoe_slboot.ttf
-rwxr-xr-x 1 root root   85764 Dec  7  2019 segoen_slboot.ttf
-rwxr-xr-x 1 root root   48992 Dec  7  2019 wgl4_boot.ttf

/boot/efi/EFI/Microsoft/Boot/Resources:
total 92
-rwxr-xr-x 1 root root 92472 Dec  7  2019 bootres.dll
drwxr-xr-x 2 root root  1024 Jan 16 18:55 en-US

/boot/efi/EFI/Microsoft/Boot/Resources/en-US:
total 13
-rwxr-xr-x 1 root root 12816 Dec  7  2019 bootres.dll.mui

/boot/efi/EFI/Microsoft/Boot/bg-BG:
total 160
-rwxr-xr-x 1 root root 81448 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/cs-CZ:
total 203
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80400 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45576 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/da-DK:
total 201
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/de-DE:
total 210
-rwxr-xr-x 1 root root 83256 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 83472 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46120 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/el-GR:
total 212
-rwxr-xr-x 1 root root 84280 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 84496 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46600 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/en-GB:
total 152
-rwxr-xr-x 1 root root 77112 Sep  7 22:07 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 77112 Sep  7 22:07 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/en-US:
total 197
-rwxr-xr-x 1 root root 77112 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 77112 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45072 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/es-ES:
total 205
-rwxr-xr-x 1 root root 81208 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45880 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/es-MX:
total 160
-rwxr-xr-x 1 root root 81208 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/et-EE:
total 154
-rwxr-xr-x 1 root root 78136 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 78136 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/fi-FI:
total 203
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80424 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/fr-CA:
total 163
-rwxr-xr-x 1 root root 82744 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 82960 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/fr-FR:
total 210
-rwxr-xr-x 1 root root 83256 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 83472 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/hr-HR:
total 158
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80400 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/hu-HU:
total 210
-rwxr-xr-x 1 root root 83256 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 83472 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/it-IT:
total 204
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80936 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/ja-JP:
total 180
-rwxr-xr-x 1 root root 69432 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 69664 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 43016 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/ko-KR:
total 179
-rwxr-xr-x 1 root root 68920 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 69136 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 43024 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/lt-LT:
total 156
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79400 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/lv-LV:
total 156
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79376 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/nb-NO:
total 200
-rwxr-xr-x 1 root root 78648 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 78864 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/nl-NL:
total 205
-rwxr-xr-x 1 root root 81208 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45368 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pl-PL:
total 206
-rwxr-xr-x 1 root root 81720 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81720 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pt-BR:
total 203
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pt-PT:
total 204
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80400 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/qps-ploc:
total 53
-rwxr-xr-x 1 root root 54072 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/ro-RO:
total 157
-rwxr-xr-x 1 root root 79672 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79880 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/ru-RU:
total 203
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80912 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 44856 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/sk-SK:
total 159
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80904 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sl-SI:
total 157
-rwxr-xr-x 1 root root 79672 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79880 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sr-Latn-RS:
total 159
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80912 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sv-SE:
total 202
-rwxr-xr-x 1 root root 79672 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79888 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45072 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/tr-TR:
total 201
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79376 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/uk-UA:
total 160
-rwxr-xr-x 1 root root 81736 Sep  7 22:07 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81760 Sep  7 22:07 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/zh-CN:
total 170
-rwxr-xr-x 1 root root 64824 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 65040 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 42512 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/zh-TW:
total 170
-rwxr-xr-x 1 root root 65040 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 64824 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 42512 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Recovery:
total 32
-rwxr-xr-x 1 root root 16384 Jan 16 19:01 BCD
-rwxr-xr-x 1 root root 16384 Jan 16 18:55 BCD.LOG
-rwxr-xr-x 1 root root     0 Jan 16 18:55 BCD.LOG1
-rwxr-xr-x 1 root root     0 Jan 16 18:55 BCD.LOG2

/boot/efi/EFI/opensuse:
total 3128
-rwxr-xr-x 1 root root  846240 Jan 18 23:34 MokManager.efi
-rwxr-xr-x 1 root root      58 Jan 18 23:34 boot.csv
-rwxr-xr-x 1 root root     125 Jan 18 23:34 grub.cfg
-rwxr-xr-x 1 root root 1275904 Jan 18 23:34 grub.efi
-rwxr-xr-x 1 root root  143360 Jan 18 23:35 grubx64.efi
-rwxr-xr-x 1 root root  934680 Jan 18 23:34 shim.efi
10

@Bill_L I believe it was the ethtool output…

1 Like
11

My bad! I read the wrong request from @arvidjaar.
I’ll get the ethtool output later this evening.

@malcolmlewis , can you remove that mess of data I wrongfully posted?

12

Sorry for the coonfusion I seem to have foisted on me!! Here is the ethtool output as requested.

localhost:~ # ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes

13

@arvidjaar
Sorry for the confusion I seem to have had foisted on me!! Here is the ethtool output as requested.

localhost:~ # ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes

14

@malcolmlewis , I put a remote switch to turn the PC off after using Leap. Not elegant, but it works.

15

@Bill_L so your interface wake-on option is set to g which is “Wake on MagicPacket”. Try disabling with ethtool -s eth0 wol d

1 Like
16

Changed ‘wake-on from ‘g’ to ‘d’

I’ll see later if it turns the router light off, or back to amber.
Will also look at the ‘Supports wake-on pumbg’ switches.

17

Setting ‘wake-on to d appears to have done it. No amber light on shutdown last evening. Will monitor it for a few days before it take the remote switch out.

An aside: the end of the command ‘wol d’ brings an old Harry Chapin song to mind. ‘WOLD’

18

This is a ‘may as well quit trying’ situation for now.
Using the ‘ethtool -s eth0 wol d’ works for the session. When I start the machine it reverts back to the ‘g’ option(Wake on MagicPacket).
I have been through the man pages for ethtool, but that is a no go for me. The only thing I saw was a reference to negotiation on/off switches, but I doubt that will do any good.

Just don’t know! This is the first HP machine that does(workstation oppose to just a PC).

Back to the remote on/off switch.
Thanks for your patience and help.

19

@Bill_L just create a simple systemd service to run the command…

#/etc/systemd/system/disable_wol.service

[Unit]
Description=Disable WOL on eth0
After=network.service

[Service]
Type=oneshot
ExecStart=/usr/sbin/ethtool -s eth0 wol d

[Install]
WantedBy=multi-user.target

Enable and start the service and should be good to go.

20

Just so this dense user doesn’t mess things up:
I create the file in the path at the top?
Then add the other things to the file with an editor? (nano, vm ??)
Then start the service?
Trying from a CLI prompt just returned a bash error.