power up on Ethernet magic packet

achallenger1 · 09-11-2005, 03:59 PM

Hi,
I have a Marvell Yukon GigE adapter (sk98lin driver), that can not only wake up, but also boot my PC when it receives an Ethernet Magic Packet. I'm also running a dual-boot system: Debian Sarge and WinXP.

Right now, if I was running Windows prior to shutting down, the computer will boot when I send it a magic packet. However, if it was running Linux, or if I killed it prior to loading an OS, it won't boot on magic packet.

In Windows, I had to go to the adapter's property sheet and check off a few relevant checkboxes to get this to work. Is there an equivalent set of settings for Linux? I found a page suggesting using "ethtool"; the following suggested command didn't work:

Code:

me$  sudo ethtool -s eth0 wol g
Cannot get current wake-on-lan settings: Operation not supported
  not setting wol

Does anyone have any other ideas?; or any ideas on how to use ethtool correctly?

Unfortunately, I can't try Wake-on-Lan from Linux (it works great when sleeping from Windows) because I don't have system standby working under Linux (too much new hardware, with kernel-level code that doesn't do power-management yet).

I don't know if it's useful, but here's some other random data, as requested for this forum:

Code:

me$ lspci
0000:00:00.0 Host bridge: Intel Corp.: Unknown device 2774 (rev 81)
0000:00:01.0 PCI bridge: Intel Corp.: Unknown device 2775 (rev 81)
0000:00:1b.0 0403: Intel Corp.: Unknown device 27d8 (rev 01)
0000:00:1c.0 PCI bridge: Intel Corp.: Unknown device 27d0 (rev 01)
0000:00:1c.4 PCI bridge: Intel Corp.: Unknown device 27e0 (rev 01)
0000:00:1c.5 PCI bridge: Intel Corp.: Unknown device 27e2 (rev 01)
0000:00:1d.0 USB Controller: Intel Corp.: Unknown device 27c8 (rev 01)
0000:00:1d.1 USB Controller: Intel Corp.: Unknown device 27c9 (rev 01)
0000:00:1d.2 USB Controller: Intel Corp.: Unknown device 27ca (rev 01)
0000:00:1d.3 USB Controller: Intel Corp.: Unknown device 27cb (rev 01)
0000:00:1d.7 USB Controller: Intel Corp.: Unknown device 27cc (rev 01)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev e1)
0000:00:1f.0 ISA bridge: Intel Corp.: Unknown device 27b8 (rev 01)
0000:00:1f.1 IDE interface: Intel Corp.: Unknown device 27df (rev 01)
0000:00:1f.2 IDE interface: Intel Corp.: Unknown device 27c0 (rev 01)
0000:00:1f.3 SMBus: Intel Corp.: Unknown device 27da (rev 01)
0000:01:02.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
0000:01:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
0000:01:04.0 Unknown mass storage controller: Integrated Technology Express, Inc.: Unknown device 8211 (rev 11)
0000:01:05.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13)
0000:02:00.0 Unknown mass storage controller: Silicon Image, Inc. (formerly CMD Technology Inc): Unknown device 3132 (rev 01)
0000:03:00.0 Ethernet controller: Intel Corp.: Unknown device 108b (rev 03)
0000:05:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0140 (rev a2)

Code:

me$ uname -r
2.6.11ac7

(would any other commands be useful?)

Matir · 09-11-2005, 04:24 PM

Out of my own curiousity, what kind of motherboard has so much unrecognized hardware?

achallenger1 · 09-11-2005, 04:42 PM

It's Asus's Intel 955X-based board.

The ITE "Unknown Mass Storage Controller" is a secondary IDE chipset; the Silicon Image one is a secondary SATA chipset. I haven't found a Linux driver yet for this particular Silicon Images chipset; I don't use it, though, so I don't care too much.

The NVIDIA VGA "Unknown device" is a GeForce 6600GT, incidentally; PCI-E card, not onboard.

I'm not sure what most of the other "Unknown"'s should be. The USB controllers are all USB 2.0, though I don't know anything more about them (they work fine, so I haven't investigated).

Matir · 09-11-2005, 04:45 PM

I suppose someone will update the driver databases soon.

What does ethtool -a eth0 show?

achallenger1 · 09-11-2005, 04:45 PM

As another thought, would this be any easier with the onboard Intel PRO/1000 Ethernet controller? Has anyone tried it before? It'd be nice to have eth0 be for the main LAN/Ethernet connection, but it's not really a big deal (the Marvell is eth0, the Intel is eth1).

Matir · 09-11-2005, 04:48 PM

I think the Intel GigE controller is a bit better supported. Also, you COULD use a different controller to wake the box than to be your primary net connection. Do both eth0 and eth1 go to the same network?

achallenger1 · 09-11-2005, 05:12 PM

eth0 goes to a local (very large) LAN / Internet connection.

eth1 is something of a waste of a high-speed GigE connection. It connects via crossover cable to an Ethernet-to-Apple LocalTalk converter box (LocalTalk was Apple's serial port-based networking structure prior to Ethernet; I believe it runs at something under 1mbps); on the LocalTalk network, there's currently one old laser printer, though I use it for old Macs on occasion as well.

eth2, incidentally, is a Firewire/IP connection to my laptop, when it's connected. I doubt this has any bearing on this problem, but you never know...

I only get one Ethernet drop for this machine, so no fancy rearranging there.

I've had trouble getting raw AppleTalk (not AppleTalk/IP) packets to go over the Marvell card in the past. This may be fixable (or it may be human error on my part), but it'd have to be fixed if I switched the ports, as LocalTalk can only handle the AppleTalk networking protocol.

Here's some more data from ethtool:

Code:

me$ sudo ethtool eth0
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 auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on

me$ sudo ethtool -a eth0
Pause parameters for eth0:
Autonegotiate:  on
RX:             on
TX:             on

Snowbat · 09-11-2005, 05:44 PM

I have the same problem in a system with onboard VIA 6103 but another system with a Realtek 8139 card does not have this problem.

achallenger1 · 09-11-2005, 06:06 PM

I tried switching eth0 and eth1; eth1 seems to remote-boot fine using both Linux and Windows. I set up the card's settings under Windows again (more descriptive texts in dialogs for an Ethernet n00b). Under the Marvell options, the Wake on Magic Packet setting was either "On" or "Off"; with the Intel options, it was either "Off", "OS controlled", or "Forced". "Forced" works for me. Maybe the Marvell's "On" meant "OS controlled"?

AppleTalk works fine over the Marvell adapter this time. Don't know why it didn't before...

Oh well, one more minor thing on this box that Linux doesn't quite support yet. I'd guess it'll be fixed eventually if anyone else cares. Just under half the stuff that wasn't working yet when I bought this machine (a few months ago) now works fine, and the stuff that's still broken is stuff that I never use.

Murmlrmpf · 12-08-2005, 02:21 PM

Is there any one who tried wake on lan with the skge driver successfully?

typo ;-)