Hey guys,
So I SSH’d into my box now and did the customary poking around and much to my delight I saw that the ethernet chip did support WOL.
ethtool eth0
Settings for eth0:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 8
Transceiver: external
Auto-negotiation: on
Supports Wake-on: ug
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes
However setting it proves not to be so good.
ethtool -s eth0 wol g
Cannot set new wake-on-lan settings: Operation not supported
not setting wol
Can someone enlighten me as to why this would be so. Far as I knew there were no physical connections needed for WOL it is just something that is built into the interface. So why can it not be changed? Is this some sort of exotic ethernet device that pehaps needs a driver rewrite?
Curious.
Hey guys,
So I SSH’d into my box now and did the customary poking around and much to my delight I saw that the ethernet chip did support WOL.
ethtool eth0
Settings for eth0:
Supported ports: [ TP AUI BNC MII FIBRE ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 8
Transceiver: external
Auto-negotiation: on
Supports Wake-on: ug
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes
However setting it proves not to be so good.
ethtool -s eth0 wol g
Cannot set new wake-on-lan settings: Operation not supported
not setting wol
Can someone enlighten me as to why this would be so. Far as I knew there were no physical connections needed for WOL it is just something that is built into the interface. So why can it not be changed? Is this some sort of exotic ethernet device that pehaps needs a driver rewrite?
Curious.
Please don’t spam the forum with identical threads… If the subforum you placed it in was an issue, as the OP, you could have easily changed the subforum under the edit title section.
Vero 4K doesn’t support WOL.
Exactly how is it disabled then? Because the ethernet chipset seems to support it.
It’s not disabled.
Vero 4K uses an Synopsys IP Core for Ethernet PHY. Depending on the implementation,capabilities can vary. There is a common upstream driver that we use.
Sam
I don’t get it, why would you want WOL for a device that is always on and has such low power consumption?
Lower power than on standby? I doubt it. But why not have WOL? Plenty of Home automation relies on it and it is idée tout faite. Why else would you have CEC functionality in the 4K if you were not relying on the fact you can power things back up from standby when you want to? What if you want to put the 4K in a mobile home, do you really want it running all the time draining your batteries when you are not using it?
There are plenty of reasons why WOL is a good idea for any network connected device.
Do you have the source for this driver? I would be curious to know why it reports back that WOL modes are available but not allow you to implement them. It might well be just a simple kernel flag that is needed.
It’s not a setting that prevents this from working. You can of course find the Vero 3 kernel tree in GitHub
Sam
@sam_nazarko, this is a pertinent question.
Considering the power draws from the Vero, it’s probably best to keep it on 24/7 but still…
I already answered this in a different thread.
WOL is not supported
wouldn’t heat up? wouldn’t that shorten the life of the vero 4K?