[RESOLVED] WOL issues with OMV and Realtek NIC driver

Hi there

Over the last few days, I've set up an OMV machine. This NAS really flies! I can get consistently 60~90 mbs transfer, where as XP manages only 20 mbs, and unRaid 60 mbs on the same machine.

However, I just can't get WOL working at all!
- I've search extensively on WOL in OMV and Squeeze, and tried all the suggestions I've found
- The same machine wakes happily under XP and unRaid
- WOL is enabled in the bios
- WOL is enabled in OMV web gui
- the machine is an Acer Veriton 5800 with Marvell Yukon 88E8052 PCI-E ASF Gigabit Ethernet Controller on main board
- my interfaces file looks like this (relevant part)

# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 10.1.1.200
    gateway 10.1.1.1
    netmask 255.255.255.0
    mtu 1500
    pre-down ethtool -s $IFACE wol g
    up ethtool -s $IFACE wol g

ethtool eth0 looks like this:

Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: pg
        Wake-on: g
        Current message level: 0x000000ff (255)
        Link detected: yes

I've totally run out of ideas on how to resolve this. Any help would be much appreciated. I'm no linux guru but I can get around (thanks to google).

thanks & regards

I sure did.
"- The same machine wakes happily under XP and unRaid
- WOL is enabled in the bios"

thanks

Zitat von "davidh2k"

Just a wild guess, as i don't have it in my interfaces, remove the following line:

Code

up ethtool -s $IFACE wol g

Reboot after that and shutdown again.

Greetings
David

Alles anzeigen

Thanks David. I originally didn't have that line, but my searches led me to adding it, as a way of making g persistent between boots (which it originally wasn't - but now is). In any case, it's presence or not doesn't effect the issue.

Thanks anyway

Zitat von "DaveVM"

How do you have to wake it up once it does go to sleep?

Press the front panel button.

Zitat von "DaveVM"

Do the network port LED's stay on when the computer goes to sleep?

This particular board doesn't have LED's on the NIC port. However the switch does light up orange on that port when it (the OMV PC) is powered down (normally orange for 100mbs, green for 1000mbs), which suggests it can "see" the NIC.

Zitat von "DaveVM"

Are you using the AutoShutDown plugin?

I've tried it both with and without. Currently, it's not installed as I am shutting down the OMV PC down manually with a command.

Zitat von "DaveVM"

Since it did wake before maybe it is a sleep issue rather than a wake issue.

I have the same WOL non-behaviour whether I use shutdown, pm-sleep, or pm-hibernate.

Thanks for your input!

Simon

Zitat von "tekkbebe"

What motherboard do you have?

This is the output from Piriform Speccy for the motherboard"

Motherboard
	Manufacturer	Acer
	Model	M945G
	Version	R04-A0
	Chipset Vendor	Intel
	Chipset Model	i945P/PL/G/GZ
	Chipset Revision	A2
	Southbridge Vendor	Intel
	Southbridge Model	82801GB (ICH7/R)
	Southbridge Revision	A1
		BIOS
			Brand	Phoenix Technologies, LTD
			Version	R04-A0
			Date	11/29/2006

I booted into XP to obtain this, and just again tested sleep/WOL - worked no problem.

Just found this, and it seems to describe my problem perfectly:

http://www.mythtv.org/wiki/Wak…_RTL8111.2F8168_.28etc.29

Not sure how to find out what chip I have. The two solutions seem to be getting a new NIC, or some freaky driver patching (if this is indeed my problem).

Any thoughts ?

Thanks,
Simon

Thanks for trying to help. I did have the advanced driver settings as you suggest.

Zitat von "tekkbebe"

Look at this, is similar to yours:
* Untick all boxes on that tab so the network card is not turned off.

On XP, the tickbox to enable WOL (in windows), is dependent on the first one (allow windows to turn this device off to save power). SO, disabling the first one disables WOL (in Windows). In any event, I tried it and it didn't fix the issue. But did disable WOL for Windows.

Zitat von "tekkbebe"

There are settings you cannot adjust. If you make these changes in windows, via the windows driver, then come back and try in omv. It sounds like you still have windows on another drive. Your card is turning off and that is why you have to put this line in " up ethtool -s $IFACE wol g" which you should not need to have in the in the /etc/network/interfaces.

I agree that the card is turning off, but I'm pretty sure it's Linux and not Windows thats doing it. Yes I still have XP on another drive.

Any thoughts on the Realtek driver issue I posted above?

thanks again.

Zitat von "tekkbebe"

Also, what are you using to try and wake it up?

wolcmd, wol2, wakemeonlan, directly from fritzbox router. All wake it from S state on windows boot, none from OMV / Linux.

thanks.

Hi tekkbebe

Oh I already have that set. Sorry - I should have noted that. Thanks for your help. I think we've exhausted most of it. I will attempt a derring-do patch of the kernel driver, but expect that (or rather myself) to fail. Next stop, I'll but a new NIC.

thanks again

I'll try that. Thanks again!