Slightly O/T: Linux help
Nov 5, 2014 | 9:46 am
#1
Original Poster
FlyerTalk Evangelist
Join Date: Nov 2002
Location: ORD
Posts: 14,772
Slightly O/T: Linux help
All right, I'm rather peeved at this (the joys of open source). Apparently, some jerk of a developer thought that it would be a good idea to remove all support for wake on LAN from the Atheros Linux driver because it made laptops resume immediately after being put to sleep. Why he didn't fix the underlying problem, I don't know.
I do know that I now have a LInux server in my living room running Ubuntu 14.04 with an Atheros AR8161, and Linux doesn't recognize that the ethernet controller supports WoL.
I don't want to have to build a new version of the driver (don't really understand how/feel comfortable with it). Does anyone know an alternative way to get WoL back, or failing that, when support will be re-added?
http://www.linuxquestions.org/questi...es-4175491464/
Thanks.
I do know that I now have a LInux server in my living room running Ubuntu 14.04 with an Atheros AR8161, and Linux doesn't recognize that the ethernet controller supports WoL.
I don't want to have to build a new version of the driver (don't really understand how/feel comfortable with it). Does anyone know an alternative way to get WoL back, or failing that, when support will be re-added?
http://www.linuxquestions.org/questi...es-4175491464/
Thanks.
Nov 5, 2014 | 9:54 am
#2
Original Poster
FlyerTalk Evangelist
Join Date: Nov 2002
Location: ORD
Posts: 14,772
Not sure why I can't edit the post above, but I wanted to add that I also see that there's a patch in the official Linux bug tracker for this, but don't know what to do with it.
Nov 5, 2014 | 10:36 am
#3
Join Date: Aug 2005
Location: SNA Rwy 20L
Programs: QF Silver
Posts: 703
Can't promise anything but would you try:
apt-get install ethtool
and add the following line to /etc/rc.local before the exit 0 statement:
ethtool -s eth0 wol g
And reboot. It's a fix that's worked for me in the past on some motherboards that wouldn't WOL properly.
Good luck
Oops, forgot to mention that you should confirm that the Ethernet port is really eth0. Since they migrated to 14.04.1 the (word that rhymes with dastards) have sometimes redefined it as p1p1, p32p1, etc. (there is a grub fix, but it's a PITA) and I'm now inspecting the ports to see where the Ethernet port actually is.
Just do an ifconfig to make sure it hadn't changed. If it did you'll have to change eth0 in the above example to whatever the heck it is now.
apt-get install ethtool
and add the following line to /etc/rc.local before the exit 0 statement:
ethtool -s eth0 wol g
And reboot. It's a fix that's worked for me in the past on some motherboards that wouldn't WOL properly.
Good luck
Oops, forgot to mention that you should confirm that the Ethernet port is really eth0. Since they migrated to 14.04.1 the (word that rhymes with dastards) have sometimes redefined it as p1p1, p32p1, etc. (there is a grub fix, but it's a PITA) and I'm now inspecting the ports to see where the Ethernet port actually is.
Just do an ifconfig to make sure it hadn't changed. If it did you'll have to change eth0 in the above example to whatever the heck it is now.
Last edited by gfunkdave; Nov 5, 2014 at 11:57 am Reason: merged consecutive posts
Nov 5, 2014 | 11:55 am
#4
Original Poster
FlyerTalk Evangelist
Join Date: Nov 2002
Location: ORD
Posts: 14,772
No, it definitely is still eth0. And I do have ethtool installed - I'd had a script in /etc/init.d/ for ages that turned on WoL at boot. But now I just get this:
Furthermore, as you can see, ethtool doesn't even recognize that the NIC supports Wake On Lan:
This is because the, er, dastardly developer I mentioned above has removed support from the driver.
So how do I get it back?
Code:
david@dalton:~$ sudo ethtool -s eth0 wol g [sudo] password for david: Cannot get current wake-on-lan settings: Operation not supported not setting wol
Code:
david@dalton:~$ sudo ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Current message level: 0x000060e4 (24804)
link ifup rx_err tx_err hw wol
Link detected: yes
So how do I get it back?
Nov 5, 2014 | 1:11 pm
#5
Join Date: Aug 2005
Location: SNA Rwy 20L
Programs: QF Silver
Posts: 703
Sorry I can't be of much help - I don't have an Atheros based card to try things on. Was hoping you might be able to back port a driver from 13.10 or something but doing a quick google search found others having the same problems as you without luck with a back port.
This article may not help - it's for an Atheros wired/wireless card where the MAC chip isn't enabled at the start for wireless (but if the MAC chip is down I would expect wired WOL to fail too). The modprobe on page 2 was reported to work for someone.
http://ubuntuforums.org/showthread.php?t=2246361&page=2
Really really stupid question now... are you running this on a desktop? If so maybe replacing the Atheros card with a cheapie Intel would be an easier approach.
This article may not help - it's for an Atheros wired/wireless card where the MAC chip isn't enabled at the start for wireless (but if the MAC chip is down I would expect wired WOL to fail too). The modprobe on page 2 was reported to work for someone.
http://ubuntuforums.org/showthread.php?t=2246361&page=2
Really really stupid question now... are you running this on a desktop? If so maybe replacing the Atheros card with a cheapie Intel would be an easier approach.
Nov 5, 2014 | 2:17 pm
#6
Original Poster
FlyerTalk Evangelist
Join Date: Nov 2002
Location: ORD
Posts: 14,772
Yeah, it is a desktop tower.
The thread I linked to on LinuxQuestions has a method to extract the driver from a different Ubuntu kernel - I'm going to try it tonight. I was just a little scared by the prospect, looking at it.
It's more an annoyance than something I'd spend any money fixing.
The thread I linked to on LinuxQuestions has a method to extract the driver from a different Ubuntu kernel - I'm going to try it tonight. I was just a little scared by the prospect, looking at it.
It's more an annoyance than something I'd spend any money fixing.