Hi all, I used to be able to wake my HP Proliant server using either Windows or Linux wol clients, however that was when it was running Windows, since installing Linux ( OpenSuse 13.1 ) I can’t wake it up , I’ve tried wakeonlan / etherwake from my Debian box and EMCO tools from a Windows 7 box ( all of which worked before ) and no worky. , I’ve checked the MAC address and it hasn’t changed ( I have known them to change by something cloning them ) so I’m asking the experts.
Did you use ethtool to check what is supported on the device nd what is switched on?
as root, where is ofcourse the device name. Is that still eth0 in 12.3, else find out with
When you do not have ethtool, first install with YaST the package with the same name.
Hi there, I checked with
and it states wol: g which means wol is supported I believe
Well, of course that is in the man page of ethtool. But basicaly you are right, allthough in my 13.1 it says:
Supports Wake-on: g Wake-on: g
which is, strange enough, different from what you have.
In any case, that is what I wanted to check. In my case, it won’t work, because while the NIC does support it, the system (BIOS) doesn’t. In your case, you say it worked earlier, thus I assume that hardware and firmware are supporting this.
BTW I have tested it here on another system (wake from my router) and that worked, thus nasicaly 13.1 is able to do this.
But at the moment I am out of ideas. Hope others tune in.
I shortened the output for brevity i actually got the same as you - shame you are out of ideas though - thanks for your help
Please refrain from doing this n the future, You will then probably be seen as unreliable. Best is to copy from the terminal the prompt, the command, the output and the next prompt. Copy them between CODE tags in the post. You get the CODE tags by clicking on the # button in the tool bar of the post editor. And when you change anything in what you copied/pasted (e.g. for security reasons), please say so. People here are not clairvoyant and they will take all computer text litteraly (same as the computer does).
I’ve been trying to help you via your other thread on this topic at LXF forums. Anyway, I dug up this thread (post #13 onwards)
The OP claimed that the NIC was getting powered off completely at shut down, thereby preventing WOL from working as intended. They added added a couple of commands to a systemd file to make sure that it was reactivated and configured to wake up again.
ifconfig eth0 up ethtool -s eth0 wol g
I’m not sure why they chose that particular .shutdown file (and it would probably be better to add via a script using a dedeicated .service file) but it apparently worked for them. I’m sure others could refine this idea if necessary.
Ok apologies for that
Hi there ferrari, thought I might stand a better chance of help posting here but blow me down I get you again - you certainly get around, I’ll try what you suggest tonight as unfortunately I’ve got to work today - thanks very much for your help - shall I continue here or lxf with this thread ?
Here is good for openSUSE-related help.
To refine/clarify my last post, it is possible to add a script (located within /usr/lib/systemd/system-shutdown/) that get executed on shut-down. So you could create a custom script, with the required lines to keep the NIC active and WOL enabled.
Good man i will try that
Hi Ferrari I tried putting the commands in the shutdown script but no joy ;-(
Did you make sure that the script file was marked executable?
chmod +x <name-of-script.sh>
I actually put the code in the existing script - I also put another line in the script to write a simple message to a text file ( just to verify that the script was actually run ) and the file was not written to so not sure what’s happening here.
Can you share the script lines here? It might help others to assist further. It’s not clear to me if this an issue of trying to keep the card alive after shutdown/suspend, or an issue of getting the magic packet to the client machine. I don’t use WOL, so haven’t played with it at all. How do you send the magic packet? Is there a router in between?
It might be worth reviewing the following wiki page:
ifconfig eth0 up ethtool eth0 wol g echo 'Trying to keep eth0 alive' > /home/pjk/wolshut.txt
As mentioned in the thread you pointed me to I put these lines ( apart from the last line ) in /usr/lib/systemd/system-shutdown/mdadm.shutdown, and as I mentioned earlier the wolshut.txt file is not being created which tells me either the script is not firing or /home/pjk isn’t available when the machine is shutting down
But it is not normal to have eth0 in openSUSE 13.1 (I have e.g. enp1s8). Or did you do something to revert to the old naming schema?
Hi there yes I changes the name of the interface in network options, I’ve checked with ifconfig that it is there and it is so that’s not the problem, it appears that the shutdown script is not being run for some reason. Does it run if I issue a reboot command or only when I actually power off the machine using shutdown ? thanks for your help.
On 05/24/2014 06:16 AM, pkfox wrote:
> hcvv;2645133 Wrote:
>> But it is not normal to have eth0 in openSUSE 13.1 (I have e.g. enp1s8).
>> Or did you do something to revert to the old naming schema?
> Hi there yes I changes the name of the interface in network options,
> I’ve checked with ifconfig that it is there and it is so that’s not the
> problem, it appears that the shutdown script is not being run for some
> reason. Does it run if I issue a reboot command or only when I actually
> power off the machine using shutdown ? thanks for your help.
One thing to remember: In a script run at bootup or shutdown, you can never
count on the environment. In particular, you cannot count on having the PATH
variable set to any particular value. Always use a full path for all entries.
Try using /sbin/ifconfig, /sbin/ethtool, and /usr/bin/echo. Things in /usr/bin
and /usr/local/bin should be OK, but I doubt that /sbin is in the path.
I’m having the same problem on 13.1. I have added the script specified with the full path for each command and it runs successfully. A couple things that I have done to make me believe this problem is with opensuse.
-Without the shutdown script, my nic light will turn off just after hitting init 0 and it will not turn back on.
-With the script, the light turns off after init 0, but then it will turn back after a couple seconds, but unfortunately a few seconds later when the computer turns off, so does the nic.
-Something else that I have done that will allow WOL to work is boot into opensuse and do a hard shutdown of the machine (holding down the power button) and at this point, WOL works.
There is something happening after the shutdown script runs that is just shutting off the nic and it is driving me mad! I might just get a different nic and see if it helps. Output of lspci for nic section is
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09)
From my searching, I have found that there are some issues with the 8169 driver that came with it and there are a few bugs out there, I installed the 8168 from realtek and that didn’t help either.
pkfox… what ethernet controller do you have?