Posts by chewitt

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)

The Apple EFI firmware on older models is woeful in places and finnicky about bootloaders; and what works from USB isn't necessarily what will work from SATA. I'd experiment with installing Ubuntu to the HDD. If that works (and boots from the HDD) then you can boot from the LiveUSB .. erase and partition the drive for LE (512MB for boot=/dev/device and the remainder for disk=/dev/device) then copy the KERNEL and SYSTEM files to the boot partition, install Grub to the drive and setup the bootloader config file.

Create space for the partition and format it as EXT4 (must be a Linux partition type for SSH to work). Note the /dev/sdX device details for it under Linux and then modify boot params in syslinux.cfg to use disk=/dev/sdX .. then reboot. Kodi will start out with a clean install.

Quote from thebence

I wanted to try if my box boots with an older LE (eg Libreelec 8.2.2.3 as Senior Citizen wrote) but the download link in the forum ([8.2.2.3] LibreELEC 8.2 for S912) is not working. Do you have maybe a link from where i can download it?

There are no archives of those unofficial releases, sorry.

Quote from spschneer

chewitt : Any thoughts? For about the same as the RPi4 4GB I can get the OPI 3LTS and don't have to wait...how do the LE development futures compare?

I don't have one so cannot talk from personal experience, but overall H6 is now well supported as a SoC. RPi4 will always have the advantage of Kodi support being actively, attentively, and directly maintained by RPi Foundation vs. the community led efforts for Allwinner devices; but it's maybe a thin advantage as Allwinner has a strong and active community and one of its major contributors is jernej our maintainer.

Quote from peno64

On Feb 12 there is a new version released on http://ftp.vim.org/pub/mediaplayer/libreelec/ (10.95.1)

But I don't see it anounced at https://libreelec.tv/

Which changes does it have

I'm not aware that VIM are an official mirror so that's probably something self-built. Official releases are now published and being replicated to official mirrors so release should be in the next 24h.

Changes are here: https://github.com/LibreELEC/Libr….95.0...10.95.1

It's also worthwhile to see if you can use an Ubuntu LiveUSB to boot the box. If yes, the BIOS has no problem with Grub and you could always install Grub to a USB stick and then do a manual install. All our installer does to the target device is install the bootloader, create two GPT partitions; first is 512MB to hold KERNEL/SYSTEM and the bootloader config file, and second is remaining space on the drive. The config file just needs to set (in grub format) the boot= and disk= content (using /dev/device, label or GUID as you like).

cd /storage/.update
wget https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.arm-10.95.1.tar
reboot

^ That version should have fixed Ethernet and USB, and I removed the keymap so IR is in a 'blank' state. IR isn't working in the staff members box either and (so far) none of us figured out why, it's most unusual.

You might need to fiddle with BIOS settings to enable legacy mode (not EFI, although we do support EFI boot). Worst case; pull the drive and connect it to a desktop and write the LE image direct to the HDD/SSD. Then interrupt boot and type "run" to skip the normal installer process and run LE from the install media (which is the internal drive). Variations on that theme include connecting the drive to another machine and booting installing to the drive on that machine before moving the drive back to the HP box.

Put Kodi in debug logging mode, clean boot, demonstrate the problem, then run "pastekodi" and share the URL.

Quote from spschneer

Could you explain how to do that? I've only used the supplied SD creator to "install" to the MicroSD that I then use in the Cubox. I don't know how to "install" from the USB (which was also created by the SD creator?) to the "storage" (e.g. to the internal eMMC?)

The Generic image includes an installer; we assume that users boot from a USB stick and install LE to a HDD or SSD inside the box, although if you interrupt boot you can also skip the installer and run direct from the USB stick (one-time or persistently). On the ARM side of things we assume users are going to boot and run permanently from an SD card (or USB); either hooking vendor u-boot (on emmc) or using upstream u-boot that we created to boot into LE. ARM images don't support the installer .. hence you've never seen it with the Cubox.

Creating a non-static Qt6 version of the tool is simple, but this won't run on 95% of Linux desktops without lots of Qt dependencies being pre-installed and we've elected to not inflict that on our users.

Creating a static Qt6 version of the tool allows it to run basically everywhere but requires a new Qt6 static build recipe and nobody managed to guess at the right combination of juju to make that happen yet. It's one of those Linux "dark arts" challenges; sounds simple but reality is different.

Plan B (or C?) .. download the .img.gz file you need and use "dd" which is native in every OS and most Linux folks know how to use it.