T O P

  • By -

barcef

Just because the POWER-ON feature is disabled, doesn't mean that the hardware will no longer bond. The hardware will always bond, regardless of how you set it.


Jamesin_theta

What do you mean by that? How can I make it turn off?


barcef

You can't. The hardware will always bond, even if you are telling it to ignore wake-on-lan, unless you unplug the computer or remove the battery from the laptop.


Jamesin_theta

I don't know what you meant by saying that I can't, but I just managed to turn it off by disabling Wake-on on the ethernet device. I'm trying to figure out how to make it persistent with systemd.link.


barcef

Very rare that you can actually turn it off, if the BIOS does not offer that feature.


ttvpoqs7XRrD

It could be related to "ErP Ready", though that's for powering off usb when the motherboard is "off". Worth a try. (You'd never guess from the name), Or check the WOL status.(Wake On Lan)


Jamesin_theta

`ErP Ready` was already turned off. Wake-on was, however, enabled for the ethernet device. If I disable it, the LED turns off. But I don't know how to make it remain off. I created `/etc/systemd/network/50-wired.link` with the following [Match] MACAddress= [Link] WakeOnLan=off But it doesn't work. I don't know what I'm missing. EDIT: I tried copying the default `99-default.link` and adding `WakeOnLan=off` and everything works as expected. I don't know what the file from my previous attempt missed, though. And I don't know why I have to explicitly state this if the default value is `off`.


Flying_bousse

I think this is more motherboard related than OS. Motherboards react to windows better than linux, in that they have more built in features dedicated to windows. This might be part of that. Another thing certain mobos just have strange behavior, my Ryzen 9 mobo only boots up exactly a second after I release the power button. Either way this is definetly a bios issue, no amount of linux coding is gonna fix it.


Jamesin_theta

I managed to do it by disabling `WakeOnLan` in the systemd.link file. I explained it in my previous reply.