wakeonlan doesn't work

Hexcode · 16. April 2014

Hey,
I've installed openmediavault on a modifiedThecus N4200Eco NAS an it works realy good.
For example the raid-config from the Thecus System was directly visible in the RAID-Menu of omv.
My problem is now, that wakeonlan doesn't work.
When booting the orginal thecus system it was no problem, but after booting OMV there is no wol usage anymore, so it must be a problem with the softwaresystem of omv and not a bios setting.
The checkbox in OMV was set so I think this shouldn't be the problem.
I think it could be a problem with the network driver, but as far as I remember both cards are Intel 82574L Gigabit network cards...
LSHW shows:

Code

H/W path                   Device     Class       Description
=============================================================
                                      system      OEM
/0                                    bus         Pineview-ICH9
/0/0                                  memory      128KiB BIOS
/0/4                                  processor   Intel(R) Atom(TM) CPU D525   @ 1.80GHz
/0/4/8                                memory      64KiB L1 cache
/0/4/9                                memory      512KiB L2 cache
/0/1d                                 memory      1GiB System Memory
/0/1d/0                               memory      1GiB DIMM DDR2 Synchronous 800 MHz (1.2 ns)
/0/1d/1                               memory      DIMM [empty]
/0/100                                bridge      N10 Family DMI Bridge
/0/100/2                              display     N10 Family Integrated Graphics Controller
/0/100/2.1                            display     N10 Family Integrated Graphics Controller
/0/100/1a                             bus         82801I (ICH9 Family) USB UHCI Controller #4
/0/100/1a.1                           bus         82801I (ICH9 Family) USB UHCI Controller #5
/0/100/1a.2                           bus         82801I (ICH9 Family) USB UHCI Controller #6
/0/100/1a.7                           bus         82801I (ICH9 Family) USB2 EHCI Controller #2
/0/100/1b                             multimedia  82801I (ICH9 Family) HD Audio Controller
/0/100/1c                             bridge      82801I (ICH9 Family) PCI Express Port 1
/0/100/1c/0                eth0       network     82574L Gigabit Network Connection
/0/100/1c.1                           bridge      82801I (ICH9 Family) PCI Express Port 2
/0/100/1c.1/0              eth1       network     82574L Gigabit Network Connection
/0/100/1c.4                           bridge      82801I (ICH9 Family) PCI Express Port 5
/0/100/1c.4/0                         storage     JMB362/JMB363 Serial ATA Controller
/0/100/1c.4/0.1            scsi0      storage     JMB368 IDE controller
/0/100/1c.4/0.1/0.0.0      /dev/sda   disk        128MB AFAYA MDM    128
/0/100/1c.4/0.1/0.0.0/1    /dev/sda1  volume      2032KiB Linux filesystem partition
/0/100/1c.4/0.1/0.0.0/2    /dev/sda2  volume      11MiB Linux filesystem partition
/0/100/1c.4/0.1/0.0.0/3    /dev/sda3  volume      30MiB Linux filesystem partition
/0/100/1c.4/0.1/0.0.0/4    /dev/sda4  volume      77MiB Extended partition
/0/100/1c.4/0.1/0.0.0/4/5  /dev/sda5  volume      9840KiB Linux filesystem partition
/0/100/1c.4/0.1/0.0.0/4/6  /dev/sda6  volume      7920KiB Linux filesystem partition
/0/100/1c.4/0.1/0.0.0/4/7  /dev/sda7  volume      59MiB Linux filesystem partition
/0/100/1c.4/0.1/0.1.0      /dev/sdb   disk        128MB AFAYA MDM    128
/0/100/1c.4/0.1/0.1.0/1    /dev/sdb1  volume      2032KiB Linux filesystem partition
/0/100/1c.4/0.1/0.1.0/2    /dev/sdb2  volume      11MiB Linux filesystem partition
/0/100/1c.4/0.1/0.1.0/3    /dev/sdb3  volume      30MiB Linux filesystem partition
/0/100/1c.4/0.1/0.1.0/4    /dev/sdb4  volume      77MiB Extended partition
/0/100/1c.4/0.1/0.1.0/4/5  /dev/sdb5  volume      9840KiB Linux filesystem partition
/0/100/1c.4/0.1/0.1.0/4/6  /dev/sdb6  volume      7920KiB Linux filesystem partition
/0/100/1c.4/0.1/0.1.0/4/7  /dev/sdb7  volume      59MiB Linux filesystem partition
/0/100/1d                             bus         82801I (ICH9 Family) USB UHCI Controller #1
/0/100/1d.1                           bus         82801I (ICH9 Family) USB UHCI Controller #2
/0/100/1d.2                           bus         82801I (ICH9 Family) USB UHCI Controller #3
/0/100/1d.7                           bus         82801I (ICH9 Family) USB2 EHCI Controller #1
/0/100/1e                             bridge      82801 PCI Bridge
/0/100/1f                             bridge      82801IR (ICH9R) LPC Interface Controller
/0/100/1f.2                scsi2      storage     82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Control
/0/100/1f.2/0              /dev/sdc   disk        1TB WDC WD10EARS-00Y
/0/100/1f.2/0/1            /dev/sdc1  volume      1999MiB Linux swap volume
/0/100/1f.2/0/2            /dev/sdc2  volume      929GiB Linux RAID partition
/0/100/1f.2/1              /dev/sdd   disk        1TB WDC WD10EARS-00Y
/0/100/1f.2/1/1            /dev/sdd1  volume      1999MiB Linux swap volume
/0/100/1f.2/1/2            /dev/sdd2  volume      929GiB Linux RAID partition
/0/100/1f.2/2              /dev/sde   disk        3TB ST3000DM001-1CH1
/0/100/1f.2/2/1            /dev/sde1  volume      1999MiB Linux swap volume
/0/100/1f.2/2/2            /dev/sde2  volume      2792GiB Linux RAID partition
/0/100/1f.2/3              /dev/sdf   disk        3TB ST3000DM001-1CH1
/0/100/1f.2/3/1            /dev/sdf1  volume      1999MiB Linux swap volume
/0/100/1f.2/3/2            /dev/sdf2  volume      2792GiB Linux RAID partition
/0/100/1f.2/0.0.0          /dev/sdg   disk        251GB WDC WD2500YS-01S
/0/100/1f.2/0.0.0/1        /dev/sdg1  volume      231GiB EXT4 volume
/0/100/1f.2/0.0.0/2        /dev/sdg2  volume      1935MiB Extended partition
/0/100/1f.2/0.0.0/2/5      /dev/sdg5  volume      1935MiB Linux swap / Solaris partition
/0/100/1f.3                           bus         82801I (ICH9 Family) SMBus Controller
/1                                    power

Alles anzeigen

Anyone know a solution for this problem?
Greetings Hexcode

davidh2k · 16. April 2014

Have a look at the following link, should give you some hints. (adding to the interface file, worked for me)

https://wiki.debian.org/WakeOnLan

Greetings
David

Hexcode · 16. April 2014

You mean "Interface setup" - I've tried:

Code

post-up /sbin/ethtool -s $IFACE wol g
        post-down /sbin/ethtool -s $IFACE wol g

on both interfaces but it doesn't work

davidh2k · 16. April 2014

Check if ethtool is installed, of course.

Code

apt-get install apt-get install ethtool

Also, whats the output from the following command:

Code

ethtool eth0 | grep Wake-on

My network interface config:

Code

# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback


# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp
    dns-nameservers 8.8.8.8 192.168.178.1
    pre-down ethtool -s $IFACE wol g

Alles anzeigen

Greetings
David

Hexcode · 16. April 2014

Code

root@NAS:~# ethtool eth0 | grep Wake-on
        Supports Wake-on: pumbg
        Wake-on: g

Interfaces:

Code

# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback


# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 192.168.2.3
    gateway 192.168.2.1
    netmask 255.255.255.0
    dns-nameservers 192.168.2.1
    post-up /sbin/ethtool -s $IFACE wol g
    post-down /sbin/ethtool -s $IFACE wol g
iface eth0 inet6 manual
    pre-down ip -6 addr flush dev eth0


# eth1 network interface
auto eth1
allow-hotplug eth1
iface eth1 inet static
    address 192.168.2.20
    gateway 192.168.2.1
    netmask 255.255.255.0
    dns-nameservers 192.168.2.1
    post-up /sbin/ethtool -s $IFACE wol g
    post-down /sbin/ethtool -s $IFACE wol g
iface eth1 inet6 manual
    pre-down ip -6 addr flush dev eth1

Alles anzeigen

The NAS is connected via eth0

Hexcode · 17. April 2014

Seems to be a problem with debian... after installing a wheezy-system there way the same problem

Solo0815 · 20. April 2014

Try this:

Zitat

Interfaces:

Code

# The loopback network interface
auto lo
iface lo inet loopback
iface lo inet6 loopback


# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 192.168.2.3
    gateway 192.168.2.1
    netmask 255.255.255.0
    dns-nameservers 192.168.2.1
     ############# NEW:
     ethernet-wol g
     ###
iface eth0 inet6 manual
    pre-down ip -6 addr flush dev eth0


# eth1 network interface
auto eth1
allow-hotplug eth1
iface eth1 inet static
    address 192.168.2.20
    gateway 192.168.2.1
    netmask 255.255.255.0
    dns-nameservers 192.168.2.1
   ############# NEW:
     ethernet-wol g
     ###
iface eth1 inet6 manual
    pre-down ip -6 addr flush dev eth1

Alles anzeigen

And:
Please have a look at /etc/init.d/halt and make sure this is enabled:

Code

NETDOWN=no

This has to be "no"

Hexcode · 24. April 2014

Tried it - doesn't work...
The original Thecus-Firmware doesn't use the normal e1000e driver - when I try lsmod on it there is only e1000e_82574

BitHoarder · 25. April 2014

Zitat von "Solo0815"

Try this:

Hmm, my system (Whitebox PC, not a Thecus) has:

Code

NETDOWN=yes

and WOL "usually" works...
I say "usually" - I thought that it definitely was working until I came home last night and couldn't wake up my NAS - so I'll try this too on my NAS.

Getting back to the OP issue, are you saying that the original Thecus OS/firmware was using e1000e_82574, or OMV?

According to this, the e1000e driver *should* be ok:
https://downloadcenter.intel.c…817&lang=eng&wapkw=82574l

Perhaps try using this latest driver?

Also - as silly as it sounds - try using the other NIC port (I'm just looking at Google images of the unit and noticed it had 2 NICs)... I remember an old PC I had (years ago) would only WOL from one NIC, not the other...

I would also recommend taking a look at this:
http://www.mythtv.org/wiki/ACPI_Wakeup

I'm guessing that most settings should be already done, but it might at least help confirm that the problem is OS/driver related rather the config related.
One final point - I noticed that with my BIOS, having "RTC Wakeup" enabled prevented WoL from working - ok, I know your BIOS had WOL working with the Thecus OS, but it's worth checking...

Oh - just thought... are there any BIOS updates available for it???

Hexcode · 25. April 2014

As far as I see there aren't any BIOS-updates or settings for wol Second NIC doesn't work - I've tried both.

The e1000e_82574 was used at the original Thecus OS, so I think they edited something on it. Seems to be version: 1.1.2-NAPI

Seems I have to install another PCIe X1 card to get it work or I have to use the crappy Thecus OS.
I think it could only be a problem with the debian System or something like that - I've read somewhere, that it could be an ACPI problem and the solution there was to use APM instead. But when I tried to disable ACPI in grub the system won't boot up -.-

-> /sys/class/net/eth0/device/power/wakeup is empty in my case - as listed here http://www.mythtv.org/wiki/Wake-on-LAN it should be enabled -> but when I try to change it the system don't save it.

Jetzt mitmachen!