I've recently tested LE12 images booting from SD card and an eMMC module without problems. Are you using the "odroid-c2" image with upstream u-boot, or the "box" image? .. the latter has no u-boot so won't boot the board. If that's not the issue I'll need to see UART logs. NB: LE proactively disables the flashing blue LED activity indicator, but it will still flash at the start of boot until the disable script fires and stops it, which is usually around the time Kodi starts.
Posts by chewitt
-
-
Would it affect importing/updating a large library or is that mostly network bound?
If you added content it makes negligible difference as most time is spent querying internet sources. If you didn't then it will complete faster as the small file read/write is improved. Overall, as said before, you're not missing anything.
-
Just write the LE image to the SSD and then power it on. The RPi firmware supports boot from nvme.
-
Follow https://wiki.libreelec.tv/configuration/…ration-advanced to configure any remote.
I don't have the code knowledge to implement a software-decode path for 10-bit H264, so given the general lack of development on the decoders it's rather unlikely to happen - although I will ask the Pi devs (who have done the work on ffmpeg side). IIRC the 10-bit H264 format is not supported in Amlogic silicon so software fallback is the only option (and hence the legacy images do that).
-
See https://github.com/chewitt/LibreE…a9db6d4f8041b46
Skip the first patch hunk with VERSION changes if on LE12 as I'm on LE13/master branch and GCC things are different. The rest should be the same as the kernels are currently the same in both branches.
You should be able to just respin the image to pick-up the changes.
-
I made a mistake and tried to upload Armbian to the internal memory. I don't see anything on TV at the moment. The uart connection reports a similar header as in this post.
You have erased (overwritten) u-boot on the internal storage. Android recovery files won't work as there is no u-boot to provide the recovery app, and imaging recovery.img to an SD card won't work as it contains u-boot for emmc, not u-boot for SD/USB.
Create a USB or SD from https://test.libreelec.tv/12.0/Amlogic/w…etek-hub.img.gz and see if the device boots to LE?
If yes, download this backup-file and transfer it to /storage over SSH, then run "emmctool w /storage/backup-hub.tar.gz" and it will expand and restore a raw emmc (dd) backup of the original Android OS to the box. You should then be able to boot the LE12 "box" image .. or have another go at ruining things with Armbian, as you like.
If the device boots but gets stuck at u-boot, you found the issue that resulted in "wetek-hub" (booting upstream u-boot) images being discontinued. The box sees noise on the UART and boots to console. If you have the UART connected you should be able to access the console and run the commands in here: https://github.com/LibreELEC/Libr…_autoscript.src (or one of the other bootscripts in that folder) to boot into LE. If using a USB stick you might need to run "usb start" first.
-
-
The maximum MTU size supported on RPi boards is 1500, hence the "Invalid argument" error.
See https://github.com/raspberrypi/linux/issues/5561 and https://github.com/raspberrypi/linux/pull/5534 and an earlier refused PR trying to add the same (not something I'd recommend trying) https://github.com/raspberrypi/linux/pull/5419.
It might be possible to get Jumbo frames with an external USB-C NIC, but I couldn't recommend one, and IMHO there's no real need for Jumbo frames on RPi hardware. RPi 0/1/2/3 are too slow to really benefit and RPi4/5 are already fast enough that the benefit will be negligible under real-world usage (the only real difference will be under un-real lab tests).
-
You need to find another remote that combines all those functions then..
-
Nice, I will push the same change to master sometime soon. I will probably avoid the temptation to bump LE12 on the basis of "let sleeping dogs lie" but master will be usable until Kodi bumps to 'P' and DB versions start to diverge.
-
Where am I wrong?
/storage/storage-win requires a storage-storage-win.mount file.
/storage/win would match the storage-win.mount file that you created.
-
have the same problem
Which specific problem? .. there are several different things in the thread.
-
-
Banned add-ons are installed. No support.
-
This is the add-on icon that was created for a previous attempt at an add-on, if you wanted something that follows LE house-style.
-
The timeout messages are harmless. The kernel splat is undesirable but ultimately harmless too (it's a WARNING, not an ERROR).
TL/DR: If you don't know what something is in a log, always share the entire log, because then you share all the actually useful info and not just the couple of irrelevant bits that you (wrongly) guessed were important.
-
I am seeing temps of 140-150F in system info of Kodi. That seems way too high.
150ºF = 65ºC, which is getting warm, but comfortably within the operating range for an RPi board. These things are designed to be stuffed in a case that's suffocating in dust running some industrial use-case. You can run them considerably hotter than yours. As long as the CPU is not being thermally throttled, all is fine.
-
I have no idea what is different/special about a C300 pro and you're not sharing boot logs or anything that would be useful, so nothing that I can do.
