Posts by Hans Gruber

Thank you, that fix has worked for me too.

Another confirmation here that DVB is working again on 012a. Massive thanks to kszaq for your hard work.

I think my TVHeadend (server) issue could be down to the new drivers? My August DVB-T210 used to show up in the webui as two devices, "Silicon Labs Si2168 : DVB-T #0" and "Silicon Labs Si2168 : DVB-C #0". Now it just show the DVB-T device although that is not working with my DVB-T aerial. Are there any logs I could upload that might be useful for diagnostics?

I don't seem to be able to get TVHeadend to work on this build. I updated from a 32bit build (a recent dev build) which was fine but now I'm just getting "No free adapter available". I've tried rm -rf /storage/.kodi/addons/packages/* and reinstalled the addons but still no luck. Any ideas?

Nice job finding out what was causing it! I can't imagine Beelink (or most other vendors) releasing another firmware update for devices they no longer manufacture, but personally I'm not that bothered about a temperature reading as long as there's no smoke coming out the back so whatever solution is easiest for you.

Quote from stormrev

Hi Hans,
can you state which box are you using exactly?
thanks

It's a Beelink Mini MX III 2GB/16GB

Yeah still having trouble booting with second image. Still hanging on Beelink logo on some boots.

Quote from 8zabi

Just tested this kernel on Sunvell T95M and now it always got past the bootlogo! Thank You!

LibreElec itself don't start, because of the changed modules not included?

ssh is working, so I can flash back the original 011 kernel

Same results here, it's fixed one thing and broken another :p

I've just updated to the latest alpha build and found this too. Also on a Intel N2820 NUC.

First and second test kernels both sadly still occasionally get stuck on beelink logo for me.

Quote from thoradia

I intend to update it. Do however not hold your breath.

It would be much appreciated

Would it be a lot of trouble to update the rTorrent addon for Kodi 8? No worries if it is.

Quote from sebastianda

Hi,

Which device tree file I should be using if I want to update from 007 to 008? My device is Beelink Mini MXIII.

This one: gxbb_p200_2G_1Gbit_RealtekWiFi.dtb

Quote from ccccsales

Boot again from SD and run installtointernal again. I have the same with my device x96.

Thanks, I'll give that a try

edit: Just to confirm that worked. Thanks again.

Is installtointernal meant to work with this? On both this and afl1's Krypton builds I get the message "filesystem corruption has been detected!" after the process completes and reboots. It appears to be working fine from an SD. I'm on a Beelink Mini MXIII with gxbb_p200_2G_1Gbit_RealtekWiFi.dtb.

I usually find when I can't see SMB shares it's Windows at fault and a reboot or two usually fixes it. Also make sure all your Windows network and sharing settings are correct.

Quote from trogggy

Does suspend work for you?

I don't normally use it so I'm not entirely sure how it's meant to work. The power button on the remote seems to turn the device off as I get the big "B" logo when I turn it back on. If I select suspend from the power menu in Kodi that appears to work as the power button then seems to just wake up the device.

All seems to be up and running and working nicely with my Mini MX III. Wifi Appears to be working but not 100% as I'm wired but I can see the wireless access point on the device. I used gxbb_p200_2G_1Gbit_RealtekWiFi.dtb.