[LS-WXL] Shutdown/Restart/WakeOnLan

[Panakotta00]

I have setup a fresh Bullseye installation on my LS-WXL
and I was trying to set-up WoL or other type of WakeOn-"network".
I read about some MDIO stuff here: https://github.com/1000001101000/Debian_on_Buffalo/wiki/Device-Specific-Notes#linkstation-ls400-series--v-series-ls-vlwvlqvl-and-likely-other-kirkwood-devices-ls-wxl-etc

So here is what I tried to do with the default setup (I checked that phy-tool and the script is setup already, it was by default):
I set the power switch to auto, then I shutdown the pc using sudo shutdown 0 or sudo systemctl poweroff, this essentially just caused a restart. The script seems to run fine with the correct parameter (I checked using a echo variable to file in the script).
I also tried it with sudo systemctl halt which correctly turns off the NAS, but then I tried to wake it up using magical package and it did not work. I had to disconnect and reconnect the power to do so.

So I tried to investigate a bit. Using ethtool I get Supports Wake-on: d signaling it would not support wake on lan.
Also the phytool prints ieee-phy: id:0xffffffff when run in shell and in shutdown script. I don't have any clue how this phy-tool stuff works... but it kinda seems like it doesnt really work, as it never changes even with a write.
One more thing i tried was to comment out the script and did the test above (shutdown & halt). Same exact behaviour, further showing the phy-tool stuff might actually not work.

I also tried the tests above in the On state, and I got the same exact result.

What am I doing wrong to get Wake-On-"network" like WOL working?

[1000001101000]

I looked at that briefly a few years ago with somebody. If my memory is correct that particular ethernet chip doesn't have a public datasheet and as such the opensource driver folks weren't able to implement all the features such as WOL.

I could be remembering that wrong.

I think the register value in my phy_restart script might be wrong for that model device but I believe there was more missing than just that.

I imagine the needed info could be found somewhere in buffalo's custom kernel code available on their GPL site. If you can confirm whether those features work under the stock firmware that could at least confirm whether what you want is possible or not.

Looking at this again is somewhere on my todo list, though if I'm being honest that list is growing faster than I'm working on it these days.