always use omv-upgrade to upgrade from CLI.
Thx, did the work! After running omv-upgrade from cmd the entries are gone!
Merci!
SB
always use omv-upgrade to upgrade from CLI.
Thx, did the work! After running omv-upgrade from cmd the entries are gone!
Merci!
SB
Hey gderf,
thx for your reply.
Ok, did the apt-get update and apt-get upgrade. plus apt-get clean.
After reboot same screen nothing changed.
Thanks
SB
I have two entries in my updates that can neither be deleted nor ever installed.
How can I remove them?
Thanks & greetings
SB
Thx guys for that quick response & your help, but the thing is:
The system was running for days without any problems and alll of the sudden OMV-extras are missing in the Web-GUI, without any actions or interventions (execpt streaming from my NAS) from me... I mean OMV ist still working 'perfectly', except missing entry in GUI.
I hope I do not sound so penetrating, or demanding...It's really just about the reason, the why.
It's like coming to your car and every week or so a tire just goes flat for no apparent reason...
The right tip of course is: "Then pump it back up!". So you can drive again!", right!?
But the question that bothers me is: Why was the tire flat in the first place?!
I will wait a little longer for an answer that will maybe allow me to analyze this problem, or give me a clue to the cause.
I am of course very grateful for your quick help!
Thx so far
SB
Hi experts!
Im using OMV for over a year now and upgraded to 6.x last week.
Everthing worked after the update and had really not big issues, incl. the plugin "OMV-extras".
Yesterday I checked via Web-GUI (http://192.168.178.7:8081/) and couldn't find the OMV-Extra-menu entry, but everything from the OMV-Extras, like Docker with Plex runnung or Autoshutdown etc. is working fine!
- No errors, everthing is running: movie & music streaming aso. smooth, good performance, reaction of the GUI, SSH, SFTP etc.
- The Login on my Portainer-Frontend is also working, via http://192.168.178.7:9000/#!/auth
I did: Browser-refresh, different Browser. Incognito-Tab, Used my Mobile, Server-reboot, but nothing changed.
I really dont want to re-install, because I think its just a Web-GUI issue, that could be solved by setting a parameter or editing a .config somewhere...!? An I like to understand, what happened here and what exactly caused this problem.
# Output of dpkg -l | grep openm
root@MovieCloud:~# dpkg -l | grep openm
ii libopenmpt-modplug1:amd64 0.4.11-1 amd64 module music library based on OpenMPT -- modplug compat library
ii libopenmpt0:amd64 0.4.11-1 amd64 module music library based on OpenMPT -- shared library
ii openmediavault 6.0.21-1 all openmediavault - The open network attached storage solution
rc openmediavault-autoshutdown 6.0.7 all OpenMediaVault AutoShutdown Plugin
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
rc openmediavault-minidlna 6.0.3 all OpenMediaVault miniDLNA (DLNA server) plugin
rc openmediavault-omvextrasorg 6.0.8 all OMV-Extras.org Package Repositories for OpenMediaVault
rc openmediavault-resetperms 6.0 all Reset Permissions
rc openmediavault-sharerootfs 6.0-3 all openmediavault share root filesystem plugin
ii openmediavault-usbbackup 6.0-10 all openmediavault USB/eSATA backup plugin
Alles anzeigen
Any help appreciated!
Thanks a lot
SB
Hello Forum!
I like to share my following experiance...and hope it helps others.
I have always had a lean linux install with 5.x OMV 'on top' and was very satisfied so far.
Now I have decided to upgrade to 6.x, and I first got the error "This system is running a desktop environment! This setup is not supported." even though I don't have any desktop's installed!
Then I found via the u.a command
"gnome & desktop" 'parts' (in red) , which I could then delete.
root@NAS:~# dpkg --get-selections
acl install
acpi install
acpi-support-base install
acpica-tools install
acpid install
add-apt-key install
adduser install
adwaita-icon-theme install
[...]
debianutils install
deborphan install
default-jre-headless install
desktop-base install
dialog install
dictionaries-common install
diffutils install
dirmngr install
[...]
git install
git-man install
glib-networking:amd64 install
glib-networking-common install
glib-networking-services install
gnome install
gnupg install
gnupg-l10n install
gnupg-utils install
golang-docker-credential-helpers install
gpart install
gparted install
[...] install
openjdk-11-jre-headless:amd64 install
openmediavault install
openmediavault-autoshutdown install
openmediavault-keyring install
openmediavault-minidlna install
openmediavault-omvextrasorg install
openmediavault-remotemount install
openmediavault-resetperms install
openmediavault-sharerootfs install
openssh-client install
openssh-server install
openssh-sftp-server install
openssl install
[...]
xz-utils install
zlib1g:amd64 install
zlib1g-dev:amd64 install
root@NAS:~# apt-get purge gnome
Alles anzeigen
Installtion is now running and I am really curious how it will run & perform....
All the best
SB
Hello E1!
Solved the problem!
In the end it was the rsyslog service, that startet the machine and did that round robin Log file management at 01:00!
Somehiw this Service uses his own cron-type of schedule.
I just turned it of:
root@NAS:/# systemctl status rsyslog.service
* rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset:
Active: active (running) since Fri 2022-03-11 19:22:36 CET; 6min ago
Docs: man:rsyslogd(8)
https://www.rsyslog.com/doc/
Main PID: 521 (rsyslogd)
Tasks: 4 (limit: 4915)
Memory: 3.8M
CGroup: /system.slice/rsyslog.service
`-521 /usr/sbin/rsyslogd -n -iNONE
Mar 11 19:22:35 NAS systemd[1]: Starting System Logging Service...
Mar 11 19:22:36 NAS rsyslogd[521]: imuxsock: Acquired UNIX socket '/run/systemd/
Mar 11 19:22:36 NAS rsyslogd[521]: [origin software="rsyslogd" swVersion="8.190
Mar 11 19:22:36 NAS systemd[1]: Started System Logging Service.
root@NAS:/# systemctl stop syslog.socket rsyslog.service
root@NAS:/#
[SOLVED]
Alles anzeigen
Hi Zoki & thx for reading and aswering to my problem!
Your advice is definitely important, but I can't get the time zones and my current status together.... (see picture attached, made 21:07)
Am I now in Berlin exactly CET?
Thanks for helping me!
SB
Hey JohnStiles!
Thx for your reply & help.
Below the output, that you maybe like to look on!?
I cant find a specific entry.... :-/
Thanks for your help!
SB
systemctl status *timer
root@NAS:~# systemctl status *timer
* logrotate.timer - Daily rotation of log files
Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; vendor preset:
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ag
Trigger: Mon 2022-02-14 00:00:00 CET; 6h left
Docs: man:logrotate(8)
man:logrotate.conf(5)
Feb 05 22:23:02 NAS systemd[1]: Started Daily rotation of log files.
* systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-clean.timer; static; ven
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ag
Trigger: Mon 2022-02-14 03:14:35 CET; 9h left
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Feb 05 22:23:02 NAS systemd[1]: Started Daily Cleanup of Temporary Directories.
* phpsessionclean.timer - Clean PHP session files every 30 mins
Loaded: loaded (/lib/systemd/system/phpsessionclean.timer; enabled; vendor pr
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ag
Trigger: Sun 2022-02-13 18:09:00 CET; 13min left
Feb 05 22:23:02 NAS systemd[1]: Started Clean PHP session files every 30 mins.
lines 2-24
Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 00:00:00 CET; 6h left
Docs: man:logrotate(8)
man:logrotate.conf(5)
Feb 05 22:23:02 NAS systemd[1]: Started Daily rotation of log files.
* systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-clean.timer; static; vendor preset: enab
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 03:14:35 CET; 9h left
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Feb 05 22:23:02 NAS systemd[1]: Started Daily Cleanup of Temporary Directories.
* phpsessionclean.timer - Clean PHP session files every 30 mins
Loaded: loaded (/lib/systemd/system/phpsessionclean.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Sun 2022-02-13 18:09:00 CET; 13min left
Feb 05 22:23:02 NAS systemd[1]: Started Clean PHP session files every 30 mins.
lines 2-24
Loaded: loaded (/lib/systemd/system/logrotate.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 00:00:00 CET; 6h left
Docs: man:logrotate(8)
man:logrotate.conf(5)
Feb 05 22:23:02 NAS systemd[1]: Started Daily rotation of log files.
* systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories
Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-clean.timer; static; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 03:14:35 CET; 9h left
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Feb 05 22:23:02 NAS systemd[1]: Started Daily Cleanup of Temporary Directories.
* phpsessionclean.timer - Clean PHP session files every 30 mins
Loaded: loaded (/lib/systemd/system/phpsessionclean.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Sun 2022-02-13 18:09:00 CET; 13min left
Feb 05 22:23:02 NAS systemd[1]: Started Clean PHP session files every 30 mins.
* apt-daily-upgrade.timer - Daily apt upgrade and clean activities
Loaded: loaded (/lib/systemd/system/apt-daily-upgrade.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 06:27:36 CET; 12h left
Feb 05 22:23:02 NAS systemd[1]: Started Daily apt upgrade and clean activities.
* man-db.timer - Daily man-db regeneration
Loaded: loaded (/lib/systemd/system/man-db.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 00:00:00 CET; 6h left
Docs: man:mandb(8)
Feb 05 22:23:02 NAS systemd[1]: Started Daily man-db regeneration.
* anacron.timer - Trigger anacron every hour
Loaded: loaded (/lib/systemd/system/anacron.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Sun 2022-02-13 18:33:51 CET; 38min left
Feb 05 22:23:02 NAS systemd[1]: Started Trigger anacron every hour.
* apt-daily.timer - Daily apt download activities
Loaded: loaded (/lib/systemd/system/apt-daily.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 04:15:41 CET; 10h left
Feb 05 22:23:02 NAS systemd[1]: Started Daily apt download activities.
* fstrim.timer - Discard unused blocks once a week
Loaded: loaded (/lib/systemd/system/fstrim.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Sat 2022-02-05 22:23:02 CET; 1 weeks 0 days ago
Trigger: Mon 2022-02-14 00:00:00 CET; 6h left
Docs: man:fstrim
Feb 05 22:23:02 NAS systemd[1]: Started Discard unused blocks once a week.
Alles anzeigen
grep . /sys/bus/usb/devices/*/power/wakeup
root@NAS:~# grep . /sys/bus/usb/devices/*/power/wakeup
/sys/bus/usb/devices/usb1/power/wakeup:disabled
/sys/bus/usb/devices/usb2/power/wakeup:disabled
/sys/bus/usb/devices/usb3/power/wakeup:disabled
/sys/bus/usb/devices/usb4/power/wakeup:disabled
/sys/bus/usb/devices/usb5/power/wakeup:disabled
/sys/bus/usb/devices/usb6/power/wakeup:disabled
/sys/bus/usb/devices/usb7/power/wakeup:disabled
/sys/bus/usb/devices/usb8/power/wakeup:disabled
root@NAS:~#
Hello Experts!
My OMV-"Standard'-Installation is working perfectly in every way, but I have unintentional boot start.
Every night at 01:00 my OMV performs a wakeup from hibernate and I cant figure out what/which process/program is causing this.
I am running OMV (USUL) 5.6.25-1 on a DEBIAN-10 (Buster) 4.19.0-14-amd64 with Portainer & PLEX running.
I didnt edited / modified any scripts or have other installations running on that server
I checked a bunch of log-files, couldnt find a specific entry=reason
I removed the lan cable, but OMV still starting at 01:00
Is there a default setting in OMV, like in the update management that is schedeuled at 01:00?
Is there a way to find (in log file?) the process that causes the start?
Could it be that DEBIAN itself starting the server, not OMV installation?
My crontab looks like that:
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# Example of job definition:
# .---------------- minute (0 - 59)
# | .------------- hour (0 - 23)
# | | .---------- day of month (1 - 31)
# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# | | | | |
# * * * * * user-name command to be executed
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#
Alles anzeigen
Thanks a lot & sorry for my poor english
SB
Best community!
I am asking for help with the following problem:
I have mounted a disk (/dev/sda) in OMV and it is visible under Storage -> File Systems.
Under "Access Right Management" -> "Shared Folders" I have now created "Docs, "Movies", "Music", "Pics"; all are 'Referenced"'and have permissions for 'everyone' under "Privileges".
"DLNA" works, because I can browse through them on my SmartTV.
Same with SMB under Win10: all shared folders visible and accesable.
But now when I look via FTP under folder /export/ I see only one folder "Movies"...!?
Where are the other folders under FTP?
Am I looking in the wrong tree / folder?
I want to copy the data via FTP from an old NAS into the folders I created.
Does anyone know what I'm doing wrong!
Thx, regards & Sorry for my poor english
SB
Hello everyone,
I am glad to communicate a solution for the problem, that my OMV-custom NAS didnt go into a suspend or hibernate status, when not used AND couldnt get up running on WOL.
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 ##
root@NAS:~# lsblk --output NAME,FSTYPE,LABEL,UUID,MODE
NAME FSTYPE LABEL UUID MODE
sda brw-rw----
|-sda1 ext4 1748b395-819b-4356-b2ad-0d2b697199a8 brw-rw----
|-sda2 brw-rw----
|-sda5 ext4 f2a82520-6b55-4a76-b713-204b1655cdd6 brw-rw----
[B]|-sda6 swap 377438db-9374-40a5-8730-0f5827a131ec brw-rw----[/B]
|-sda7 ext4 59361bac-5777-49fe-a8f5-8b0cba191153 brw-rw----
`-sda8 ext4 bc2befe7-2381-4302-b61f-9a4ebf2eaddc brw-rw----
sdb brw-rw----
`-sdb1 ext4 Video cd5c5260-e0e7-4cff-a7e5-0180323a1bce brw-rw----
Alles anzeigen
OK, my swap-partition is sda6 and here I can see the UUID which I need for the next step.
The 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...
I added the "nomodeset"-cmd to grub-config with the UUID of the swap-partition:
## after editing, the actual writing in in to GRUB ##
## written in the /boot/grub/grub.cfg after that ##
## cat /boot/grub/grub.cfg ##
## or open the grub.cfg with an editor ##
[I]...snip[/I]
echo 'Linux 4.19.0-13-amd64 loading ...'
linux /boot/vmlinuz-4.19.0-13-amd64 root=UUID=1748b395-819b-4356-b2ad-0d2b697199a8 ro acpi_osi=Linux [B]nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec[/B]
echo 'Initiale Ramdisk loading...'
[I]...snip[/I]
## check: is it a actual setting now ##
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
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT="0"
GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec"
GRUB_CMDLINE_LINUX="acpi_osi=Linux [B]nomodeset resume=UUID=377438db-9374-40a5-8730-0f5827a131ec[/B]"
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL="console"
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE="640x480"
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID="true"
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
GRUB_DISABLE_SUBMENU="y"
Alles anzeigen
## After editing, now force hibernation via CMD ##
Please see attached pictures, I couldn't found the logs to copy from, so I took screenshots ;-D
System 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 it can be set to SOLVED.
I hope this will help someone else
SB
Hello forum!
Although I am a complete n00b when it comes to Linux and OMV, I successfully installed OMV 5.x on (top) of my Debian 10.7 installation with some random hardware & a Atlantic AQC-107 10GBE NIC.
I would like to thank you very much for all the excellent guidance and help I have been able to find here and on YT etc. from dedicated OMV users (!)
But one thing makes my life really hard, namely the configuration of any/some energy saving functions and here specifically putting OMV into a form of hibernate and waking it up again with wake-on-lan (WOL).
The whole Autoshutdown via Plugin is not working, rep. is doing nothing for me and somehow interferes or dependent on the configuration of the Debian kernel, the ACPI settings in the BIOS and in Debian-OS, the nic & network manager settings, settings in countless .conf files, services, boot options etc. aso.
What I am trying to say is: Unfortunately, simply checking the "Auto shutdown" checkbox did work for me and it looks to me, that they're many other users who are not able to configure a satisfying energy saving setup...?!
It took me more then a week to figure out how to bring my NAS-PC into hibernate from the cmd-line, but still not within / out of OMV.
Now I am searching for a way to "integrate' the below solution into my OMV installation, but have no clue where to start...
Goal is to hibernate when no one is streaming or doing a backup anything to the NAS.
This is what I like to share with you...so here's what I did:
Installed 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 conditions, all ACPI settings disabled ##
nexus6@NAS:~$ sudo cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PCI0 S5 *disabled no-bus:pci0000:00
[B]PEX0 S5 *disabled pci:0000:00:1c.0[/B]
PEX1 S5 *disabled
PEX2 S5 *disabled
PEX3 S5 *disabled
[B]PEX4 S5 *disabled pci:0000:00:1c.4[/B]
PEX5 S5 *disabled
HUB0 S5 *disabled pci:0000:00:1e.0
UAR1 S5 *disabled
UAR2 S5 *disabled
IGBE S5 *disabled
USB0 S3 *enabled pci:0000:00:1d.0
USB1 S3 *enabled pci:0000:00:1d.1
USB2 S3 *enabled pci:0000:00:1d.2
USB3 S3 *enabled pci:0000:00:1a.0
USB4 S3 *enabled pci:0000:00:1a.1
USB5 S3 *enabled pci:0000:00:1a.2
EHC1 S3 *enabled pci:0000:00:1d.7
EHC2 S3 *enabled pci:0000:00:1a.7
AZAL S5 *disabled pci:0000:00:1b.0
Alles anzeigen
## On which PCI-Express slot is my ethernet adatpter / NIC? ##
nexus6@NAS:~$ sudo lspci -tv | grep -i ether
[B]+-1c.0-[02]----00.0 [/B] Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion]
## OK, its PEX0 pci:0000:00:1c.0 but ACPI-"access" is disabled ##
## trying to enable wakeup setting ##
echo enabled > /sys/devices/pci0000:00/0000:00:1c.0/power/wakeup ## looks like both cmd doing the job
echo enabled > /sys/class/net/enp2s0/device/power/wakeup
## ok, check if its enabled now ##
root@NAS:~# cat /proc/acpi/wakeup
Device S-state Status Sysfs node
PCI0 S5 *disabled no-bus:pci0000:00
[B]PEX0 S5 *enabled pci:0000:00:1c.0[/B]
PEX1 S5 *disabled
snip...
## changes /etc/systemd/system/wol.service to ##
[Unit]
Description=Activate WOL on enp2s0 network card
After=network-online.target # network service started&online?
[Service]
Type=oneshot
ExecStart=/usr/sbin/ethtool -s enp2s0 wol g #set WOL to magic-packet
[Install]
WantedBy=basic.target
Alles anzeigen
## put ACPI "enabled" in /etc/rc.local & /etc/init.d/rc.local
...snip
/usr/sbin/ethtool -s enp2s0 wol g # idk, just setting WOL for NIC here again ;-D
echo enabled > /sys/class/net/enp2s0/device/power/wakeup
echo PEX0 > /proc/acpi/wakeup ## same as "echo enabled > /sys/devices/pci0000:00/0000:00:1c.0/power/wakeup"
echo PEX4 > /proc/acpi/wakeup ## just in case I got the wrong PCI-slot
echo HUB0 > /proc/acpi/wakeup ## USB-Hub(?) to test reactivate with usb mouse/keyboard
WOL is working
Resume ends in reboot
More work to do
SB
Whole "Story" here.
Thanks for reading all this & sorry for my poor English.
SB