OE dropped support for i386 images after v5.0 and LE numbering starts at v7.0 so there has never been an LE release that supports i386 hardware. That said, almost all of our build-system supports 32-bit compile (as all the Raspberry Pi stuff is 32-bit) so if you're familiar with the build-system it's not too hard to effectively revert the commits that removed support and create i386 images and binary add-ons. To add perspective; older x86 hardware that needs a 32-bit image probably runs Kodi 18 worse than a Raspberry Pi Zero costing $7 so the question is always "is it worth the effort" ?
Posts by chewitt
-
-
The correct solution to this problem is (as already advised) adding an RTC chip to the board.
-
Raspberry Pi 3B and 3B+ with a little overclock and LE 9.0 firmware handle software decoding of lower bitrate 1080p HEVC files quite well. Higher bitrates and media that's also DRM encrypted (Netflix etc.) will push things over the edge, but the Pi Foundation Engineers have been quite resourceful at finding spare compute resources on the board and putting everything to work.
-
Aeon Nox has *never* been installed by default in Kodi or LE - but it's a long-time favourite in the Kodi add-on repo.
-
-
There are still some key milestones to clear before the project is interested in public testing but work planned for the new year should close critical gaps and I'd guesstimate we can start public alpha's (alongside existing releases) after 9.0 has shipped. Until then there's nothing to stop anyone building from my completely un-closed GitHub branch, though things there are often fluid and I'm not some code ninja who never makes mistakes (I'm still amused when people confuse me for a developer). I'm happy that balbes150 is releasing LE and Armbian images from the currently egregious patch-set that's being curated (with assistance from many.. it's far from a solo effort). You should consider Oleg's un-closed releases as our officially unofficial mainline test images
-
Compile [LibreELEC.wiki] .. and run "PROJECT=Amlogic DEVICE=Blah ARCH=arm make image"
-
But chevitt no longer releases assemblies on the 4.xx kernel for odroid c2 . Only for Khadas Vim.
Sounds like I need to change the private URL that I use for test images. Thanks for the tip-off
-
512MB boards can probably boot but won't deliver a good HTPC experience so we have no real-world intention of supporting or encouraging their usage. We intend to discontinue support for similarly under-resourced Raspberry Pi hardware with 512MB in the near future too.
-
Most Amlogic GXM hardware uses a DesignWare "dwc3" USB controller which is capable of supporting USB 3.0 devices, but the S912 SoC which controls the USB controller does not so GXM/S912 devices do not have USB 3.0 capabilities. The first Amlogic devices to ever support USB 3.0 are the S905X2/Y2/D2 and S922 boards.
People often mistake "lsusb" and "lshw" output as "my device is detected correctly" but that's far from reality. If I connect a USB kitchen sink to a board lshw will report there's a kitchen sink present. It can probably just see something from dwc that hints of USB 3.0 and so it reports it.
-
We reached the point where the RK 4.4 kernel mostly works, but it's an older codebase that is missing a bunch of the newer-kernel frameworks we need to use for HDR etc. and backporting doesn't make sense. So we're no in the process of rewriting DRM/KMS and FFmpeg support (using a proper stateless V4L2 decoder) and sorting other critical things from a Linux 4.20 base, and that work needs to advance further before you'll see any serious changes to RK support again (and things may get worse before better, as it's significant rework). So for now RK support "is what it is" and images will continue in an Alpha state (no Beta, no release) with Kodi and surrounding package changes, but no real-world difference to RK features.
-
Make sure "sync playback to display" is disabled else Kodi sends PCM (which is still multi-channel) and not pass-through.
-
Connect the external hard drive to the LE/HTPC box and play movies via the USB connection. Or if it's a NAS device in the network; connect to the SMB file share on the NAS. I can't think of any reason why you'd need to use FTP (or use a VPN) to access an external hard drive. NB: Kodi 18 does support SFTP but only if you install the SFTP support addon from our addon repo.
-
I'm not sure why Kodi ever went down the rabbit hole of trying to support file copies from DVD discs. I'm not really sure what the bug is or would be related to, but for consistent results either copy the disc to an ISO file or rip to mkv and don't worry about 'features' that kids aren't interested in.
-
CEC runs over the HDMI connection and allows you to use the TV remote to control other devices directly attached to the TV e.g. DVD player, HTPC with LE. You can buy TV's that support CEC, but not remotes; it's not a remote (device) protocol.
-
Fix whatever networking problem you have, then addons can be installed.
-
If you don't show me the systemd debug log I can only guess at the changes you made and what effect they had. Your problem, not my problem.
-
The .tar archive only contains files (nothing to do with ext4) so the only thing you'll need to unpack on Win7 is a tool like WinRAR. If you then try to restore specific Kodi files from a Linux install to Windows you'll have issues with file paths (as Win/Linux use different conventions) and some Linux preferences in guisettings.xml do not exist in Windows. Kodi has never officially supported cross-platform config changes so sometimes it works, and sometimes it doesn't.
