01:21 <Armbian-Discord> <J​eevus> Any reason I had wifi access on Orange Pi 3 LTS on setup, and after installing armbian to EMMC I lost it entirely?

03:03 <Armbian-Discord> <T​onymac32> <redacted comment about OPi booting probability>

03:05 <Armbian-Discord> <T​onymac32> Seriously though, I don't have their stuff, I've only gotten the worst examples they made. That said, no, I can't think of any reason for that to have happened. I would go to the forums and post the typical armbianmonitor -u output so folks can see if the dmesg is complaining

11:13 <stipa> there are few users reporting that wifi problem

11:14 <stipa> with OPIs

11:15 <stipa> J​eevus try to put the older version of armbian on the emmc where wifi worked

11:15 <stipa> it seems to be a regresion

17:18 <alekksander> okay, so WOL should work on armbian (bullseye) by default, right?

17:31 <CosmicDJ> alekksander: your network "card" still has to support it

17:35 <Armbian-Discord> <M​anoftheSea> systemd service? I don't use WoL, so maybe my "advice" is useless. You get what you pay for. But the idea is that the ethernet port is still running some kind of control while the system is powered down, in a way that is able to trigger the system booting up. I wouldn't expect it on SOC-integrated ports (except maybe on the mvebu). In the x86/x64 world, it's done by SMM, I think; Linux just requests it from the

17:35 <Armbian-Discord> hardware. But I'll say again that maybe I'm way off.

18:02 <Armbian-Discord> <I​gorPec> i tried WOL on helios4, it worked well

18:02 <Armbian-Discord> <I​gorPec> others i don't recall

18:06 <alekksander> in my problematic case it's odroid hc4

18:08 <Armbian-Discord> <M​anoftheSea> yeah, mvebu

18:09 <Armbian-Discord> <I​gorPec> this is very different from platform to platform, board to board

18:10 <Armbian-Discord> <I​gorPec> try standard way - perhaps it works?

18:20 <alekksander> i don't have user profile on my armbian, it runs omv and there is no gui installed (don't think it matters, but what do i know…). so i go the standard way: ethtool -s eth0 wol ug (just to be sure ethtool says "Supports Wake-on: ug" and "Wake-on: ug"), then systemctl suspend. on my other pc connected by router (arp -a answers with correct ip and mac from of server) i've tried countless wakeonlan and etherwake variations. but to my knowledge

18:20 <alekksander> simple "wakeonlan <mac>" should do the tricks. but it doesn't…

18:24 <archetech> omv has a web iface you can eneable wol on

18:25 <alekksander> there is a simple window to tick and it's enabled there

18:25 <alekksander> box*

18:26 <alekksander> but i assume it does only what ethtool does anyway

18:26 <Armbian-Discord> <I​gorPec> then suspend / wol is not supported on hc4. perhaps there are some patches by hardkernel to enable this

18:26 <archetech> id chk the forum

18:26 <archetech> over there

18:26 <Armbian-Discord> <I​gorPec> really don't know if Hardkernel managed to sort this out or not

19:10 <alekksander> okay, thank You guys! i will seek further on hardkernel forums or related

19:33 <Armbian-Discord> <I​gorPec> report back if you find something useful

19:34 <alekksander> will do

22:15 <archetech> Kernel: 5.19.0-odroid-arm64 aarch64 bits: 64

22:15 <archetech> Desktop: MATE 1.26.0 Distro: Ubuntu 22.10 (Kinetic Kudu)

22:15 <archetech> whew thats fresh

22:21 <stipa> very fresh

23:59 <Armbian-Discord> <J​ason123> What is better? Rock pi 4 or rockpro64? I am thinking about using tow boot on spi flash