My system is: Intel CC820 motherboard (which supports PME# wake up for wake on LAN) 3com 3C905C which also supports wake on LAN via PME# Linux 5.5 The motherboard BIOS is later than one that reports an issue with WOL and this particular network card was fixed. But when I turn off the PC (shutdown or poweroff commands or front panel button), it cannot be restarted via WOL. The network light on the Ethernet card goes off so it looks like power is not being retained on the card. Although both the card and the motherboard have WOL headers my understanding is that these are not necessary if using PME# - is that correct? (I don't happen to have a WOL cable so can't just try one to confirm). How can I make Linux shutdown and leave the Ethernet power on? The common suggestion on the 'net is to remove the "-i" switch from the shutdown script, but it was not present to start with.
At Wed, 06 Oct 2010 21:33:25 +0100 CentOS mailing list <centos at centos.org> wrote:> > My system is: > Intel CC820 motherboard (which supports PME# wake up for wake on LAN) > 3com 3C905C which also supports wake on LAN via PME# > Linux 5.5 > > The motherboard BIOS is later than one that reports an issue with WOL > and this particular network card was fixed. > > But when I turn off the PC (shutdown or poweroff commands or front > panel button), it cannot be restarted via WOL. The network light on > the Ethernet card goes off so it looks like power is not being > retained on the card. > > Although both the card and the motherboard have WOL headers my > understanding is that these are not necessary if using PME# - is that > correct? (I don't happen to have a WOL cable so can't just try one to > confirm).Wondering if there is a BIOS setting for enabling PME# (and/or a setting/jumper on the NIC for this as well -- maybe ethtools or the 3COM tool (I believe there is a Linux port available) can set this.> > How can I make Linux shutdown and leave the Ethernet power on?I believe you need configure the power management setting in the BIOS to leave the system in 'standby' mode or something like that, rather than 'power off'. That is, the ACPI 'power off' command yields 'standby' mode (or something like that).> > The common suggestion on the 'net is to remove the "-i" switch from > the shutdown script, but it was not present to start with. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >-- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller at deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/
On 10/20/2010 02:13 PM, centos at crighton.me.uk wrote:> On Wed, 20 Oct 2010 14:04:51 -0400, you wrote: > > > >> To get mine to work under fedora I had to run ethtool and turn on the >> wol option. >> Also it seemed to get reset after used wol to start it up so in my >> rc.local I put >> /sbin/ethtool -s eth1 wol g >> /sbin/ethtool -s eth0 wol g >> > ethtool -s eth0 wol g results in a message "Cannot get current > wake-on-lan settings: Operation not supported" even though both the > motherboard and NIC do support WOL. > >Hmm... [root at centostest ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 32 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: d Current message level: 0x00000007 (7) Link detected: yes [root at centostest ~]# ethtool -s eth0 wol g [root at centostest ~]# uname -a Linux centostest 2.6.18-164.6.1.el5 #1 SMP Tue Nov 3 16:18:27 EST 2009 i686 athlon i386 GNU/Linux [root at centostest ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 32 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes [root at centostest ~]# -- Stephen Clark *NetWolves* Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark at netwolves.com http://www.netwolves.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20101020/67560184/attachment-0002.html>
On Wed, 20 Oct 2010 14:38:43 -0400, you wrote:>On 10/20/2010 02:13 PM, centos at crighton.me.uk wrote: >> On Wed, 20 Oct 2010 14:04:51 -0400, you wrote: >> >> >> >>> To get mine to work under fedora I had to run ethtool and turn on the >>> wol option. >>> Also it seemed to get reset after used wol to start it up so in my >>> rc.local I put >>> /sbin/ethtool -s eth1 wol g >>> /sbin/ethtool -s eth0 wol g >>> >> ethtool -s eth0 wol g results in a message "Cannot get current >> wake-on-lan settings: Operation not supported" even though both the >> motherboard and NIC do support WOL. >> >> >Hmm... > >[root at centostest ~]# ethtool eth0 >Settings for eth0:<snip> This is the same output from my system: [root at backup ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 24 Transceiver: internal Auto-negotiation: on Current message level: 0x00000001 (1) Link detected: yes [root at backup ~]# ethtool -s eth0 wol g Cannot get current wake-on-lan settings: Operation not supported not setting wol [root at backup ~]# uname -a Linux backup 2.6.18-194.17.1.el5 #1 SMP Wed Sep 29 12:51:33 EDT 2010 i686 i686 i386 GNU/Linux
Reasonably Related Threads
- XCP 1.0 beta Realtek 8168 nic not working
- Attempting to checksum a non-TCP/UDP packet errors rolling across screen
- Attempting to checksum a non-TCP/UDP packet errors rolling across screen
- gigE -> 100Mb problems
- Bonding Eth interfaces - unexpeceted results