I’ve scoured the interwebs almost all day to try to get this to work, but I can’t seem to. I have an Asus M3A78 motherboard with the RTL8111/8168 NIC; dual booting Vista and openSUSE 11.2. I’ve tried updating the bios and enabling wol, updating the linux rtl driver, updating the vista driver and enabling through device manager, adding “netdown=no” to /etc/init.d/halt… just about everything you can think of, but the NIC doesn’t stay powered on to receive the wol magic packet. Any advice/suggestions/solutions would be greatly, greatly appreciated.
Are you sure your system is able to do WOL? You say you are multi boot with some windows, but does it work there?
I have a system where the NIC is WOL able as *ethtool *shows:
Supports Wake-on: g
Wake-on: g
But the system is not. I did ask the manufacturer and got a NO.
During my search for a working WOL I came upon this: Network Connectivity - Remote wake-up basics
HTH
joshuamims wrote:
>
> I’ve scoured the interwebs almost all day to try to get this to work,
> but I can’t seem to. I have an Asus M3A78 motherboard with the
> RTL8111/8168 NIC; dual booting Vista and openSUSE 11.2. I’ve tried
> updating the bios and enabling wol, updating the linux rtl driver,
> updating the vista driver and enabling through device manager, adding
> “netdown=no” to /etc/init.d/halt… just about everything you can think
> of, but the NIC doesn’t stay powered on to receive the wol magic packet.
> Any advice/suggestions/solutions would be greatly, greatly appreciated.
>
>
Also,make sure/check you have PME (Power Management Events ) activated if
your bios supports it
Yes, as I stated, I’ve checked an enabled such option in the bios. And, no offense to anyone, I’m not technologically iliterate. I know my mobo/bios supports Wake On Lan. As far as I can tell I have everything set correctly, but the NIC does not stay powered on in either Vista or openSUSE despite all options being set, hence my problem.
check the motherboard manufacturer for an updated bios and maybe
owner/user manual…some require you to set a switch on the board
–
palladium
As I stated, I haved updated the BIOS and enabled all relevant settings. There are no jumpers to set.
Is the NIC onboard? If so are you supplying standby power to the NIC? There is a particular pin on the power supply plug that does so. If you have a voltmeter, measure it.
On 2009-12-14, joshuamims <joshuamims@no-mx.forums.opensuse.org> wrote:
>
> As I stated, I haved updated the BIOS and enabled all relevant settings.
> There are no jumpers to set.
Have you tried waking other machines ?
Maybe the problem is in the syntax. I remember being a bit surprised about
the MAC format required.
–
Any time things appear to be going better, you have overlooked
something.
On Mon, 14 Dec 2009 18:56:02 +0000, joshuamims wrote:
> As I stated, I haved updated the BIOS and enabled all relevant settings.
> There are no jumpers to set.
If the NIC is a card in a slot, I seem to recall some systems required a
separate connection from the NIC to the motherboard to enable WoL -
though I don’t know with more modern hardware if that’s still the case or
not.
Jim
Jim Henderson
openSUSE Forums Moderator
I’ve tried all variants of the MAC, but nothing. And as far as the nic, it’s onboard. I’ve dug inside innards and find nothing that would route power to the nic either by cable or nic, just to be sure, and nothing. I don’t know why the NIC is not maintaining power, and its really upsetting.
No one else has any suggestions for me? I’m not too sure now that the NIC isn’t staying on, as I’ve read by someone else in my searches that their link light doesn’t stay, but they can still do wake on lan. But whatever the case may be, I’m still not able to get it to work. I’ve managed to wol my laptop, and it only has Windows 7, so I think that eliminates any issues that may relate to the router if any. I have read numerous forum posts saying that the RTL8168B has been nothing but problems with wake on lan, but after much tooling around they all managed to get it to work. I, however, cannot after implementing all of their workarounds/fixes. Here’s a rundown of what I’ve done so far:
-
Updated the bios for my mobo (Asus M3A78) and enabled Wake on PME and even enabled OnBoard LAN Boot ROM (which was a suggestion that I came across).
-
Updated the R8168 Linux drivers
-
edited the /etc/init.d/halt with “/sbin/ethtool -s eth0 wol g” and “sleep 10” above the last line, exec $command… (a suggestion from the MythTV wiki for this card)
-
edited /etc/init.d/halt again with NETDOWN=“no” at the top of the file
-
I even upgraded my Vista partition to Windows 7 and updated to the latest RTL8168B drivers, enabling any and all wake on lan options for the NIC in the Device Manager
-
came across another suggestion for “echo enabled >/sys/class/net/eth0/device/power/wakeup”
-
echo RLAN > /proc/acpi/wakeup to change it from “disable” to “enable”
And maybe one or two more things–maybe not as I can’t recall at this point after spending about 3 days on this–but NOTHING works. I’m at wits end and ready to just say eff it, but if anyone has any other ideas I’m all ears.
On Thu, 17 Dec 2009 00:26:01 +0000, joshuamims wrote:
> No one else has any suggestions for me?
It sounds to me like a hardware issue - unless you want to share some of
the things you’ve tried for MAC address format - “all variants” doesn’t
really tell us anything about what you’ve tried.
Jim
Jim Henderson
openSUSE Forums Moderator
I’m thinking it’s some kind of hardware issue, but all signs point to everything being set correctly as it would seem, but I dunno. As for the MACs, I’ve used dashes instead of colons, lower case letters instead of uppercase, neither dashes nor colons, even tried the MAC reversed when I came across a forum post that suggested it due to some hardware issue (I believe that had to do more with nVidia hw, but I gave it a shot). I even switched from UDP 9 to 7. Meh…
I suspect no standby power is getting to your NIC. Normally if the computer is on standby, plugging a cable into the NIC will turn on the link light. No link light probably means no standby power. It could either be a faulty PSU or a faulty mobo. You could plug in an offboard NIC and see if you can detect standby power on that.
Yeah, the standby power has been my first thought since the beginning. The only thing that throws me off is that the router shows a connection to the port it’s connected to, but I’m not sure if that’s just showing the cbale being plugged in on both ends or an actual connection; and the fact that someone has no link light on their NIC on suspend/shutdown yet still being able to wol. I suppose I’ll have to find a NIC to buy to really know for sure what’s going on.
On Thu, 17 Dec 2009 01:26:01 +0000, joshuamims wrote:
> I’m thinking it’s some kind of hardware issue, but all signs point to
> everything being set correctly as it would seem, but I dunno.
Thing is, WoL is implemented in hardware - the OS doesn’t have control at
the time it wakes up.
You might try a trace with Wireshark (if you’re familiar with that) to
see if you’re getting any sort of reply from the system after sending the
magic packet.
> As for the
> MACs, I’ve used dashes instead of colons, lower case letters instead of
> uppercase, neither dashes nor colons, even tried the MAC reversed when I
> came across a forum post that suggested it due to some hardware issue (I
> believe that had to do more with nVidia hw, but I gave it a shot). I
> even switched from UDP 9 to 7. Meh…
The version of “wol” on my system says dashes should be used. Did you
pad each octet to two digits? That may be required (ie, “00” instead of
“0” for an octet).
Jim
–
Jim Henderson
openSUSE Forums Moderator
On Thu, 17 Dec 2009 02:46:15 +0000, Jim Henderson wrote:
> The version of “wol” on my system says dashes should be used. Did you
> pad each octet to two digits? That may be required (ie, “00” instead of
> “0” for an octet).
Scratch that, I just looked at it again, and it requires colons between
the octets; dashes go between the octets for the SecureOn password.
Jim
–
Jim Henderson
openSUSE Forums Moderator
WOL is a protocol with no acknowledgement. You just send out the magic packet and the system wakes up or it doesn’t. 
On Thu, 17 Dec 2009 03:26:01 +0000, ken yap wrote:
> hendersj;2089072 Wrote:
>> You might try a trace with Wireshark (if you’re familiar with that) to
>> see if you’re getting any sort of reply from the system after sending
>> the
>> magic packet.
>
> WOL is a protocol with no acknowledgement. You just send out the magic
> packet and the system wakes up or it doesn’t. 
Ah, I see - I’ve only played with it a very little bit, and not yet so
much that I got it actually working myself.
Jim
–
Jim Henderson
openSUSE Forums Moderator
joshuamims wrote:
> I suppose I’ll have to find a NIC to buy to
> really know for sure what’s going on.
i believe this is neither an openSUSE or Linux issue, but rather a
hardware (or user:) issue, therefore i ask:
have you tried finding a forum and help here:
http://vip.asus.com/forum/default.aspx?SLanguage=en-us
–
palladium