Thanks, I'll try to take a look at the source if I get a chance next
week.  Any tulip developers out there know off hand if this is enabled?
Or can be disabled?

Thanks,

Alex

David Christensen wrote:
> 
> Alex,
> 
> Looking at the back of a Linksys EtherFast 10/100 manual I happen to have,
> they describe two different remote wake-up events, Magic Packet and Link
> Change.  The first one is pretty obvious and is probably not related to
> your problems, but the second one may be.  The manual states ""Link Change
> is a remote wake up event that is triggered by any change in the EtherFast
> card's link state."  Plugging in a LAN cable is the example given that
> would turn the system on.  You may have to look at the driver source to see
> if this is enabled by default or you may have to modify the driver to
> disable this "feature" on the card.
> 
> Regarding the WOL cable, this was used for older motherboards before PCI
> 2.2,
> though it is still present on newer motherboards to support older PCI cards.
> A PCI 2.2 compliant motherboard and NIC use the #PME signal on the PCI bus
> to signal the wake.
> 
> Dave
> 
> >
> > I have an athlon system with a iwill kk266 motherboard (via
> > kt133A).  I
> > have a linksys 10/100 PCI ethernet card with wake on lan
> > capabilities.
> > Anyway, when I shut the PC down it turns off, but refuses to
> > stay off.
> > Within a minute or two, it turns itself on again.  If i run over and
> > turn it off by hitting the power putton, it turns off, but then comes
> > back on again at a later somewaht arbitrary time (1 minute to several
> > hours later).  I originally got the WOL card so I could
> > remotely boot my
> > PC, but at this point it has turned out to be more trouble than it's
> > worth.  I tried to disable WOL inthe BIOS, but that didn't change
> > anything.  So I removed the three pin cross connect that connects the
> > card to the WOL header on the motherboard.  That fixed it for a few
> > days, but now it's doing it again, even without the cable installed.
> > the only fix is to unplug the ethernet cable when I turn it off.
> >
> > I suspect the problem has something to do with WOL vs. resume on LAN.
> > the system should only turn on when it recieves a magic packet, but it
> > seems that any packet may cause it to boot (or resume, but since it is
> > in the "off" state, boot).  I've only been using APM, but perhaps acpi
> > is required for this to work properly.  As far as why it does
> > this when
> > the 3 pin WOL connector was not used, I'm not sure, maybe something to
> > do with PCI 2.2.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/