Hi all,
Currently running LibreELEC 8.0.2 on a Mac mini (Mid-2011). Wake on lan used to work when I had OpenELEC running on the same machine. But since moving to LibreELEC, wake on lan no longer works.
Wondering if it was possible to change a setting somewhere to get it working again?
Cheers,
Zolt
Which OE release worked?
It would have been 6.0 or 6.0.3. As I skipped version 16 of Kodi and went from Kodi 15 to 17.
Are you talking about WOL being sent from the mac mini to a NAS? .. or WOL waking the mac mini itself?
I've seen complaints about people not being able to wake mini's from suspend using IR remote controls in the past and although the actual reason is not understood it has something to do with kernel changes that result in the box going into S4 state and the IR receiver not being powered to receive the wake signal. Those reports always have a "but it used to work on <some older release>" comment. I'd hypothesise your issue probably has it's roots in the same kernel changes. It's nothing specific about moving from OE to LE, it's all about something in the kernel and you'd see the same issue if you moved from OE 6.0 to OE 8.0 as well.
Sorry mate, should have provided more details. I'm referring to WOL waking the Mac Mini itself using the WOL function in the Kodi Remote v1.5.5 app on iOS.
Similar behaviour to what's in the thread below. Ie, when waking up the Mac Mini now the blinking light turns solid, but nothing comes up on the screen. Oh and I'm not using the Apple Remote.
Macmini (2012) wakeup from suspend with apple remote is broken
Yup. As per previous comment, something changed in the kernel and it's in S4 not S3
Ah ok. So you're saying the kernel change puts it to sleep in S3 mode instead of S4? So it's broken on all devices, or specific to that particular hardware?
Other way around, things are now in S4 (a deeper sleep state) not S3. It's probably a general kernel change but the only complaints we see are from mac mini users so it's not impacting our normal "Generic" user population. I'd guess the root cause is something in the mac firmware that's not handled or excepted in the kernel correctly. Unfortunately none of the developer team are experts in kernel power management and I'm the only person who has a mac mini (an 2007 device which is a complete sh1t to boot Linux on) and I don't have the time/patience/inclination to see if my box is relevant to the problem; it's old and has completely different firmware to the 2010+ device people report issues against.
No worries, thanks for the info.
