pm-suspend doesn't respect wol settings of network interface
Bug #711517 reported by
Wout van Heeswijk
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pm-utils (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pm-utils
When pm-suspend it issues a "ethtool -s "${d##*/}" wol g>/dev/null 2>&1" it disregards the fact that i've set a ethtool -s eth0 wol ug.
This causes the system to not wake up from my desired packet types.
In my quest to finding out why my system wouldn't wake from unicast I found out that there are several locations where wol settings are done. powernap for one has a setting (which is overruled by pm-suspend).
I think there should be a system wide config file for ethtool (/etc/default/
To post a comment you must log in.
I forgot, i'm using Ubuntu server 10.10