Hi list,
I have a 3c980 NIC plugged into an Abit KT7-RAID and connected together
with a WOL cable. I can't seem to get WOL to work using the ether-wake
utility if I power the box down with shutdown(8). The only way I can
currently get WOL to work is if I reboot the box, then physically press
the power button to turn it off.
I'm loading the 3c59x.o driver using the enable_wol option, but I'm not
currently using ACPI. Looking through the 3c59x.c code, I notice it relies
on the box being put into a certain ACPI state. Will the ACPI code do this
on shutdown?
Cheers
Matt
--
"Phase plasma rifle in a forty-watt range?"
"Only what you see on the shelves, buddy."
Matt wrote:
>
> Hi list,
>
> I have a 3c980 NIC plugged into an Abit KT7-RAID and connected together
> with a WOL cable. I can't seem to get WOL to work using the ether-wake
> utility if I power the box down with shutdown(8). The only way I can
> currently get WOL to work is if I reboot the box, then physically press
> the power button to turn it off.
As far as the driver is concerned, a shutdown and a reboot are identical,
so we need to look at external causes. Presumably Linux APM or BIOS.
> I'm loading the 3c59x.o driver using the enable_wol option, but I'm not
> currently using ACPI. Looking through the 3c59x.c code, I notice it relies
> on the box being put into a certain ACPI state. Will the ACPI code do this
> on shutdown?
The driver has no dependency on the kernel's ACPI code. It
uses a function called `acpi_set_WOL' for historical reasons.
Sorry - that wasn't a lot of help :(
> As far as the driver is concerned, a shutdown and a reboot are identical,
> so we need to look at external causes. Presumably Linux APM or BIOS.
With our boards I had to track the issue that the chipset only delivered
wake events in certain sleep modes. It could be that linux shutdown puts
the system in a sleep mode that does not accept wake-events, but the
power-button override puts it in a wake-able sleep. (S5 vs S3/4 ?). Our
solution is to enable wake events in S3/4/5 on the chipset.
It could be not a net driver issue but an ACPI issue.
Tim
Andrew Morton mentioned the following:
| Matt wrote:
| >
| > I have a 3c980 NIC plugged into an Abit KT7-RAID and connected together
| > with a WOL cable. I can't seem to get WOL to work using the ether-wake
| > utility if I power the box down with shutdown(8). The only way I can
| > currently get WOL to work is if I reboot the box, then physically press
| > the power button to turn it off.
|
| As far as the driver is concerned, a shutdown and a reboot are identical,
| so we need to look at external causes. Presumably Linux APM or BIOS.
I've looked through the BIOS settings, and there doesn't seem to be much I
can change. There was one option to toggle "ACPI Suspend" between S3 and
S5 I think, and another which was something like "PM by APM", which could
be set to either Y or N. I'm not sure what other options I should be
looking for which might make a difference...I can't see anything obvios.
I've tried enabling ACPI support, but that has succeeded in confusing me
as I can't work out how to use it, acpid seems to do nothing.
Even without APM support compiled in, the box still manages to turn itself
off, (running poweroff), and every time it won't respond to WOL. In all
cases, the card is still powered up and negotiated to the switch.
Matt
--
"Phase plasma rifle in a forty-watt range?"
"Only what you see on the shelves, buddy."