|
NIC 'loses' WOL paramater/setting/value after reboot = No WOL possible
Hallo experts!
After installing the correct Linux driver for my 10GBE Marvell AQN-107 Network card (Marvell AQtion Linux driver) WOL is available and settings can be changed. Problem: After the 1st reboot the WOL parameter ist gone and cant be changed anymore! ### Installation of the driver ### Code:
root@NAS:~/Downloads/Marvell2$ modprobe ptpCode:
nexus6@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool enp2s0Code:
root@NAS:~/Downloads/Marvell2$ sudo /usr/sbin/ethtool -s enp2s0 wol g### now: after reboot & login the WOL parameter is gone ### Code:
root@NAS:~# /usr/sbin/ethtool enp2s0Code:
root@NAS:~# /usr/sbin/ethtool -s enp2s0 wol gCode:
[Unit]Code:
root@NAS:~# systemctl enable wol@enp2s0.NIC is working perfectly at 10GBit, with no problems...execpt: I cant use WOL to wake up my designated NAS!? ### Some basic info about my System ### Code:
?> Can it be that the istalled Xfce Desktop and the Network manager in this GUI causing problems? I appreciate any help you may provide! Thanks SB |
Are you sure that the wol service is actually launched? You should see that in the journal or the output of systemctl status.
I can't confirm this right now, but perhaps the ethtool command results in a kernel message. Use dmesg to check. Probably unrelated: Your unit file takes a parameter after the @ sign, but doesn't use that parameter. To remove complexity, don't put an @ in the unit file name. |
WOL working, but after boot settings gone or not accessable
Hey berndbausch!
Thx for your suggestions! I did what you suggested and renamed the /system/wol@.service to /etc/systemd/system/wol.service Yes, WOL is launching & working with the new wol.service, but only after the fresh install of the nic driver(!) At 1st restart its gone & I cant access the wol-settings of my nic anymore...like before. ### here journalctl output ### Code:
root@NAS:/lib/systemd/system-sleep# journalctl | grep wolCode:
root@NAS:/lib/systemd/system-sleep# systemctl status wol Code:
root@NAS:/lib/systemd/system-sleep# nmcli c show "Marvell 10GBE" | grep ethernet But I guess some other service, like ACPI, Systemd or openmediavault is kinda corrupting the settings while booting. The thing is: After a fresh install & activation of the NIC-driver everything looks fine - WOL is set to "d", but can be changes to "g" (magic packet) - IPv4 & 6 there, open & close ports etc: ok - 10GBE is available, performance good - no errors no collisions, streaming of a 4k/Atmos movie file: perfect - openmediavault is working perfectly but on 1st boot all lost :-( Idk, maybe the Marvell driver has a bug or wrong motherboard setting, maybe nic firmware update, wrong entries or setting in the ".conf files" for services Will start a deep dive... BTW: meanwhile I found like hundreds of unsolved WOL-related Posts in the internet for such an easy and normal thing to have... strange. Thx & later SB |
Thoughts...
Does bios/uefi hold any setting for WOL or other wakes to include sleep modes? |
Hardware Bios supporting WOL -> OS is not triggering
3 Attachment(s)
Hi jefro, thx for your thoughts!
Yes the Bios of my motherboard IP35 pro support different WOL settings + Sx-Modes (primarily) for the Onboard-LAN NIC (s.attachment) But I have disabled the Realtek Onboard-LAN and plugged a 10GBE PCI Marvell with AQN107-chipset in. When I shutdown the Computer the NIC green LED in the back keeps on blinking, the orange stays on. So I think the hardware is supporting WOL & waiting for a call from the OS, rep. Software. The whole setup looks right, until I to use it, rep. shutdown and reboot... Thx & l8 SB |
WOL working with these settings & parameters -> ACPI
Hello forum,
hello fellow readers, my guess was that the interface between hard & software, i.e. drivers or frimware, or their settings prevent WOL from running and that der ACPI-Power options are interfering. I have 1x gfx card and 1x nic in PCI-slots, so I did the below with partially success! After "systemctl hibernate" or "suspend" I can wake up the system with a Magic Packet! Problem: The system wakes up, tries a resume and somehow ends in a full reboot! ## checking ACPI conditionen, all ACPI settings disabled ## Code:
nexus6@NAS:~$ sudo cat /proc/acpi/wakeupCode:
nexus6@NAS:~$ sudo lspci -tv | grep -i ether## trying to enable wakeup setting ## Code:
echo enabled > /sys/devices/pci0000:00/0000:00:1c.0/power/wakeup ## looks like both cmd doing the jobCode:
root@NAS:~# cat /proc/acpi/wakeupCode:
[Unit]## put ACPI "enabled" in /etc/rc.local & /etc/init.d/rc.local Code:
...snipResume ends in reboot More work to do SB |
Does a normal resume from keyboard also reboot?
|
WOL working with Image saving/loading via nomodeset resume=UUID=
2 Attachment(s)
Quote:
yes, the behavior with USB wake up was the same ...but I found a solution! Solution: I realized the reboot is the result of an not working wake up, beacause of an incomplete hibernation: the image of the hibernation status was not written, so without the last known status, there's no "wake up" possible, just a reboot with "last known good" settings! Goal: force the a image-write to ram and to hard disk, maybe swap-partition on hibernate ... and force a load of the image on wake up. ## show disks to potentially write the hibernate image too ## Code:
root@NAS:~# lsblk --output NAME,FSTYPE,LABEL,UUID,MODEThe GRUB setting can be edited quite simply with the "GRUB Customizer", and/or set. I did it in the GUI via a VNC session, Not the best tool, but it works... Code:
apt-get install grub-customizerhttps://www.linux-community.de/wp-co...gs-300x224.jpg ## after editing, the actual writing in in to GRUB ## Code:
root@NAS:~# update-grub## cat /boot/grub/grub.cfg ## Code:
GRUB_CMDLINE_LINUXCode:
...snip[CODE] root@NAS:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.19.0-13-amd64 root=UUID=1748b395-819b-4356-b2ad-0d2b697199a8 ro acpi_osi=Linux nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec [CODE] ## check more ### Code:
root@NAS:~# cat /etc/default/grub## After editing, now force hibernation via CMD ## Code:
root@NAS:~# systemctl hibernateSystem closes programs & some services, writes the image to ram and then to disk and then goes into hibernate. On start the same thing vice versa... You'll find you last cmd in the shell, open folders & files in GUI resp. VNC aso.!!! So, this problem is solved (for me) and I will set it to SOLVED. Thx for your help & participation SB |
Thanks for the update and solution.
|
| All times are GMT -5. The time now is 10:26 AM. |