Hello,
I’m sorry if this has been answered already but I have been looking and cannot figure it out. I am trying to get my Ethernet port to stay powered up after I shutdown my computer. I had no issue with this when I was using opensuse 12.2 but when I update to opensuse 12.3 it powers off after shutdown. I have run the command ethtool -s Eth0 -wol g but it did not resolve the problem. Any help would be appreciated.
Thanks,
On Sat, 04 May 2013 04:06:03 +0000, DanB1983 wrote:
> Hello,
>
> I’m sorry if this has been answered already but I have been looking and
> cannot figure it out. I am trying to get my Ethernet port to stay
> powered up after I shutdown my computer. I had no issue with this when
> I was using opensuse 12.2 but when I update to opensuse 12.3 it powers
> off after shutdown. I have run the command ethtool -s Eth0 -wol g but
> it did not resolve the problem. Any help would be appreciated.
There’s usually a BIOS setting that needs to be enabled as well - if it’s
not staying on after you shut down, that’s outside the control of the OS,
so that’s where I’d start looking.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
If he is using 12.3 at the same hardware then 12.2 it is no BIOS issue.
I had the same problem some time ago with an older PC. Eventually I found out, that it was a new kernel “feature”. At some point in time the kernel devs decided, that some peaces of network hardware did not behave well to the power management specifications; and to avoid problems arising sometimes from this misbehavior they disabled some capabilities (among them WOL) for this hardware. So starting with a certain kernel version WOL did not work any more on my hardware. The only solutions for me were: Use an old kernel or by new hardware.
With more information about the hardware, especially the network chip, this could be investigated.
Hendrik
I have an ASUS G74SX-RH71 laptop.
here is the information hwinfo gave me:
77: None 00.0: 10701 Ethernet
[Created at net.124]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF.dptbeTZujz1
SysFS ID: /class/net/eth0
SysFS Device Link: /devices/pci0000:00/0000:00:1c.5/0000:05:00.0
Hardware Class: network interface
Model: “Ethernet network interface”
Driver: “r8169”
Driver Modules: “r8169”
Device File: eth0
HW Address: 14:da:e9:bd:1b:42
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #35 (Ethernet controller)
lspci:
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06)
On 05/04/2013 07:16 AM, hendwolt wrote:
>
> If he is using 12.3 at the same hardware then 12.2 it is no BIOS issue.
> I had the same problem some time ago with an older PC. Eventually I
> found out, that it was a new kernel “feature”. At some point in time the
> kernel devs decided, that some peaces of network hardware did not behave
> well to the power management specifications; and to avoid problems
> arising sometimes from this misbehavior they disabled some capabilities
> (among them WOL) for this hardware. So starting with a certain kernel
> version WOL did not work any more on my hardware. The only solutions for
> me were: Use an old kernel or by new hardware.
> With more information about the hardware, especially the network chip,
> this could be investigated.
Please reference this “decision” the the kernel devs made.
On Sat, 04 May 2013 12:16:02 +0000, hendwolt wrote:
> If he is using 12.3 at the same hardware then 12.2 it is no BIOS issue.
Good point, I missed that part of the OP’s message somehow.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Just to verify, did you ensure ethtool reported Wake-on: g (at least) after configuring?
It might be worth also ruling out any network issues (just to be sure): if you run tcpdump upd port 9 to verify there is nothing preventing the packet from being generated and arriving (you never know, and it doesn’t hurt to check.)
Newer NICS actually retain the IP from a DHCP lease when powered off, so you can try using the unicast address and MAC in addition to the multicast address. (I was amazed to learn this recently, and yep - it really does work.)
I’d be very interesting to hear if the interface shows Wake-on: g and the packet has been verified to arrive, and if it still does not respond to either unicast or multicast addresses. That would be weird indeed.
According to ethtools WOL is set to g. The other day i had to perform a hard power down and the ethernet port stayed active after the machine was powered off.
Hard to do, because I’ve had these problems 2 years ago (or so) and I did not bookmark the webpage(s), where I found this information.
So after googling a lot, without any guaranties, it might be this one:
Hendrik
Though it might seem silly (as you know it worked previously) but could you run #tcpdump udp port 9 and send the wake on lan magic packet to the system, just to be absolutely certain the packet is arriving as expected? Otherwise, all your troubleshooting is for naught.
Hi Dan,
for years, I have been trying to get my desktop(s) to wake their lazy circuits up to a friendly nudge from my Fritzbox. BIOS settings were very clear on the subject - still, to no avail. eth0 was always powered off and slept through any wake up call.
Just last Thursday, I was idling around upstairs, not keen on upgrading from 11.3 and reading random threads of this very helpful forum. Then, in a last desperate attempt I added
wol g
in YAST, network setup, hardware settings of the network card, ethtool options. That suddenly did the trick. Now, sitting on my sofa watching the Snooker finat in Sheffield I aroused my upstairs machine to check to specs:
I have got exactly the same hardware (network) and driver as you havem on an ASUS mainboard,
configured with ifup.
openSUSE 11.3, kernel 2.6.34.10-0.4-desktop (x86_64), KDE 4.4.4
Of course, that can not be compared with an up-to-date system running the latest kernel but I found similar symptoms:
eth0 gave the impression it was shutdown and ethtool eth0 -wol g in a console did NOT do the trick.
I don’t know how that could be done with network manager, though.
rds
Kasi
I ran the #tcpdump udp port 9 and it does see the packet.
I tried adding the 'wol g" into the network config but that still did not.
My computer has multiboot mode and as long as the last OS is Windows 7 and opensuse 12.2 WOL works with no issues. It appears that when opensuse 12.3 shuts down it is forcing the Network card to power off. Is there a way that I could run a command at shutdown that would reactivate the Ethernet port?
Did you check pm-powersave.log and pm-suspend.log in /var/log for any suspicious messages?
Compared to the same logfiles in os 12.2?
Hendrik
I managed to get it working but not the best way. I copied the following lines into the file “/usr/lib/systemd/system-shutdown/mdadm.shutdown”
ifconfig eth0 up
ethtool -s eth0 wol g