Posts by chewitt

Quote from Masutin

Sadly, no. Sorry for troubling you. The storage seems faulty. The installation starts as usual with partition resizing, etc. A reboot brings mount errors, need to exit, more errors (Kernel panic). Kodi may appear, but setting it up ends in (a need to do) a reboot. The final series of errors is failed services and dependencies. There may also appear a request to do a repair, but to no avail.

I have tried several systems, new and old, with similar results. Alas, the attempts have ruined a working AE installation, seemingly irrevocably. Flashing the Android image doesn't produce a working system anymore, previously not perfect but possible. I'll ask elsewhere if there can be images to flash in Android Recovery, it works.

Thanks for your help!

Once you boot LE we've configured (overwritten) properties in the u-boot environment for LE filenames. To return to a legacy image you will need to force recovery boot again. This makes vendor u-boot search for legacy image bootscripts that will overwrite those properties with the info needed to boot legacy images again. It's fairly simple to flip between legacy and LE images; but it's not as simple as just inserting and removing the SD card, you need to invoke the recovery process. Restoring the original Android image will also reset things to a state where any legacy image (or LE) can hook u-boot and set things correctly.

From the description: vendor u-boot does hooks LE correctly, the initial boot/resizing of the SD card completes, and you can reach Kodi. At this point you should have a working install. To isolate further issues I would avoid immediate installation of add-ons and just reboot several times to prove the initial setup is valid. If there are failed services they are likely minor things, but I would need to see a log file from the box: enable debug mode in Kodi, then reboot and run "pastekodi" one minute later and share the URL.

Errors involving storage are odd. The upstream kernel doesn't understand the Amlogic custom partition scheme used to create filesystems on the internal emmc storage so AMLGX kernels will see a /dev/mmcblkX device with no visible partition scheme or mountable filesystems; ergo there will be no attempt to mount filesystems (and thus no errors from them). That means errors are more likely to come from the SD card, in which case the issue may be the maximum speed of the mmc device being too high (some boxes with lower-spec components need to force it to lower speeds to avoid instability). There are two ways to test that. One is using a device-tree file that forces 50MHz (not 100MHz or 200MHz) and the other is using an old slow SD card (not a fancy fast one) or perhaps a USB key (which is not an mmc device). Any chance of that?

Enable SSH in the LE settings add-on and use PuTTY (Google it and install it) then login (user = root, pass = libreelec) and run the command.

RTL8812BU chipset .. which has no support in the upstream kernel: http://en.techinfodepot.shoutwiki.com/wiki/TP-LINK_Archer_T3

Oleg moved his repo to Bitbucket. I forget the URL, but even if you find it, his habit of summing all changes into a single (date coded) commit means each commit has 1000+ changes and it's impossible to find anything meaningful in his branches. Good luck

Quote from NickC

If I have read correctly I need to install System Tools from the LibreElec repo to do this.

Nope. You can partition with 'parted' .. no need for fdisk.

No logs = No problem (and likely no further interest in investigating).

Quote from rigowetekplay2

Am i doing something wrong?

Yup, everything. Please read this first: https://wiki.libreelec.tv/hardware/amlogic

Quote from Ge0rge

What can I do to get CEC working?

Most x86_64 devices don't support CEC on their HDMI connections, and those that do typically only support Power ON/OFF. IIRC some NUCs support the Pulse8 adapter being added via an internal board header to extend featues. It's quite different to the ARM world where most box and board devices have native CEC capabilities.

LE will support them once the upstream kernels we are based upon support core essentials like HDMI, Ethernet, mesa for GPU, and all the hardware decoders which are almost the same as existing chips (but enough different to need some work). There is quite a lot of activity from some of the professional development shops and Rockchip community sources (including some of our own contributors). All the media folks poking code are people we know (and who know us) so once things start to progress I'm sure we'll start taking a closer interest.

NB: It's probably possible to frankenstein an image today using the downstream vendor kernel and mali blobs etc. That's fine for desktop and industrial focussed distros like Manjaro and Armbian but "all the media stuff needs to work" for LE support and this is always the weakness in downstream kernels. It will be a fairly simple to get the basics for an image, but a large effort to get right, and all that effort will be superseded once upstream support kicks in, and we already have plenty of things to work on with existing RK SoCs .. so best to be patient.

Quote from twilightened

It is interesting that 10.95.1 is downloadable from the official server with a small link edit for a couple days now but it hasn't been announced nor it is added to the official download page.

There's this thing called "real life" .. it gets in the way sometimes

Yes, we have partitioning tools (parted) and text editors (nano) in the OS.

Latest public is 10.95.0 and I have no clue what device-tree file work on your random box. I suggest you read the article I linked.

Boot from an Ubuntu LiveUSB .. It has a GUI and all the tools you need to partition the drive (Gparted) and install Grub. The idea is to use that to set-up the iMac to run LE (only).

You will need to experiment with device-trees a little. Read: https://wiki.libreelec.tv/hardware/amlogic

I've no idea how the feature works, but programattically, how do you expect Kodi to know that the remote device is already turned on?

You only need to update when you need to update. Otherwise "if it works, don't fit it" applies.

As the purpose of the configuration you've applied is clearly download of content from torrent and usenet sources, I'll remind you of the project stance towards piracy and our forum rules. You are welcome to do what you like, but we aren't going to encourage others to follow in your footsteps so I've removed the URL from your post.

I'm doubtful the underlying Android (or legacy LE) firmware can be an influence as (from thebence screenshots) the box is clearly booting into LE which means vendor u-boot is really only responsible for some low-level power functions at that point; the kernel has taken over. And if we reach far enough into userspace boot to see the Kodi boot splash (sometimes.. it's a timing thing) it's most unusual for a virgin Kodi instance to not then reach the home screen. The usual reason for 'hangs' at that point are truncated DB files (rare on first boot, but it happens from time to time) but that's a simple thing to remove (with SSH access). To comment more, I really need to see some logs from a box, not photo's of boot screens as the output there misses a lot of detail.

That said, if you're happy to reflash an original vendor firmware and repeat the install it will eliminate that from suspicion. I've put an updated image here https://chewitt.libreelec.tv/testing/LibreE…95.2-box.img.gz (ignore the version number)