Post by thread:[TECH] Wake on Lan from Linux

Hi, In my Debian Linux 6.0 /etc/network/interfaces, I have: #allow wake on lan #see wiki.debian.org/WakeOnLan iface eth0 inet dhcp post-up /sbin/ethtool -s $IFACE wol g post-down /sbin/ethtool -s $IFACE wol g And it doesn't wake up when I send it wol magic packets. It *does* WOL after shutting down from Windows, accomplished by using Windows control panel to enable wake on lan, and to wake on magic packet, using the Device Manager->Atheros network adapter Advanced panel. There are no bios settings related to wake on lan. Is there something else I need to do, like additionally getting linux to set up wake on PCI events? It is a Gateway netbook, EC14 series, possibly LT20[1], with Atheros AR8131 PCI-E ethernet controller. I really want to avoid digging into the driver source code and recompiling the kernel just for this issue. lspci -vv yeilds: 01:00.0 Ethernet controller: Atheros Communications AR8131 Gigabit Ethernet (rev c0) Subsystem: Acer Incorporated [ALI] Device 029f Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 29 Region 0: Memory at 93500000 (64-bit, non-prefetchable) [size=256K] Region 2: I/O ports at 2000 [size=128] Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [48] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0100c Data: 41b1 Capabilities: [58] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 4096 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag- AttnBtn+ AttnInd+ PwrInd+ RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 unlimited, L1 unlimited ClockPM+ Surprise- LLActRep- BwNot- LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [6c] Vital Product Data Not readable Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP- SDES+ TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 14, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [180 v1] Device Serial Number ff-9d-6f-f3-00-26-9e-ff Kernel driver in use: atl1c Thanks, Joe W

On 26/02/12 17:01, Joe Wronski wrote: > Hi, > > In my Debian Linux 6.0 /etc/network/interfaces, I have: > > #allow wake on lan > #see wiki.debian.org/WakeOnLan > iface eth0 inet dhcp > post-up /sbin/ethtool -s $IFACE wol g > post-down /sbin/ethtool -s $IFACE wol g > > And it doesn't wake up when I send it wol magic packets. Oh, this is a sod to get working... I assume you've checked that Ethtool is installed? Here's an extract from my local Wiki -- it's for Ubuntu, but might work on Debian too. The troubleshooting stuff should be very useful to you :) = Wake-on-LAN on Ubuntu = == On a machine where eth0 is run in DHCP mode == In /etc/network/interfaces, assuming you want to enable WoL on eth0: auto eth0 iface eth0 inet dhcp ethernet-wol g .... other interfaces go here ... == On a machine where eth0 is run in Static mode == In /etc/network/interfaces, assuming you want to enable WoL on eth0: auto eth0 iface eth0 inet static ethernet-wol g ... static IP specs ... == On a machine where eth0 is bridged == In /etc/network/interfaces, assuming you want to enable WoL on eth0: auto eth0 iface eth0 inet manual ethernet-wol g .... bridging config here, auto br0 and all that ... If 'auto eth0' is not specified, Ethtool will NOT be run! == To prove this works == sudo ethtool eth0 Which should produce output similar to 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: No 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) drv probe link timer ifdown ifup rx_err tx_err Link detected: yes Note that "Wake-on" is set to "g". "g" means 'Magic Packet', "d" means 'Disabled'. = Waking up a machine = You need Etherwake: sudo apt-get install etherwake And to wake a machine up: sudo etherwake 12:34:56:78:9A:BC Or alternatively: sudo etherwake hostname The hostname alternate will only work if a MAC-address-to-hostname mapping is present in /etc/ethers. The MAC address alternate will always work (assuming there's a machine present on the LAN with the specified MAC address, of course!) Best of luck -- Linux can be pretty brutal when it wants to be... Cheers, -- Phil. spam_OUTpiclistTakeThisOuTphilpem.me.uk http://www.philpem.me.uk

On 2/26/2012 3:53 PM, Philip Pemberton wrote: > On 26/02/12 17:01, Joe Wronski wrote: >> Hi, >> >> In my Debian Linux 6.0 /etc/network/interfaces, I have: >> >> #allow wake on lan >> #see wiki.debian.org/WakeOnLan >> iface eth0 inet dhcp >> post-up /sbin/ethtool -s $IFACE wol g >> post-down /sbin/ethtool -s $IFACE wol g >> >> And it doesn't wake up when I send it wol magic packets. > > Oh, this is a sod to get working... I assume you've checked that Ethtool > is installed? > > Here's an extract from my local Wiki -- it's for Ubuntu, but might work > on Debian too. The troubleshooting stuff should be very useful to you :) > I've found more for other distros than debian, but it's usually helpful. Debian seems to put conf files in different places than other distros, maybe due to a security philosophy. Also, different vesions of software move things around as I've found with gnome GDM3 trying to get it to start vino-server without logging in at the machine. I know... it's a security risk, and I should just ssh to the damn thing, but all I want is an easy to configure XAMP server with the additional Wake on Lan feature, but that's another topic. {Quote hidden}> > = Wake-on-LAN on Ubuntu = > > == On a machine where eth0 is run in DHCP mode == > > In /etc/network/interfaces, assuming you want to enable WoL on eth0: > > auto eth0 > iface eth0 inet dhcp > ethernet-wol g I can't find any reference to a program or command called ethernet-wol. Teh gargoyle, it gives nothing. {Quote hidden}> ... other interfaces go here ... > > > == On a machine where eth0 is run in Static mode == > > In /etc/network/interfaces, assuming you want to enable WoL on eth0: > > auto eth0 > iface eth0 inet static > ethernet-wol g > ... static IP specs ... This is where I put the ethtool -s $IFACE wol g command. <snip> > == To prove this works == > > sudo ethtool eth0 > > Which should produce output similar to this: > Settings for eth0: <snip> > Supports Wake-on: pg > Wake-on: g > > Note that "Wake-on" is set to "g". "g" means 'Magic Packet', "d" means > 'Disabled'. I get the same: joe@Gateway-debian:~$ sudo ethtool eth0 Settings for eth0: Supports Wake-on: pg Wake-on: g So I know that ethtool tried to do the right thing when it booted. I just don't know that thing was correct, or if something else occurs when it falls asleep or shuts down. > = Waking up a machine = > > You need Etherwake: Or other tool. I say "java WakeOnLan 192.168.1.255 <MAC-address>". I guess the IP address is there to send a broadcast message on your network from the internet. I have 2 other Magic Packet senders and they all work when the target is shut down from windows, as well as on Grey2, the desktop. > > Best of luck -- Linux can be pretty brutal when it wants to be... I don't know how the linux driver writers do what they do. I can't find any info on the qualcomm web site for any of the atheros ethernet chips and can't find an 8131 at all. Even if I did, how would I learn what's been written to the registers after the machine is powered down? It's about 70 watts to leave it on full time, and that would add over 10% to my light bill. I guess I can let it go to sleep and walk over and hit the on switch when needed. Joe W