Posts by chewitt

  • [x86-64] Playing Videos crashes Kodi LE13nightly

    Code
    info <general>: CAddonMgr::FindAddons: visualization.fishbmc v21.0.2.2 installed
info <general>: CAddonMgr::FindAddons: visualization.goom v21.0.2.2 installed

    You are running LE13 (K22) which uses OpenGL graphics but you still have LE12 (K21) visualization add-ons installed and these are compiled for OpenGLES. It's a wrong and probably crashy combination.

    Force a repo refresh and make sure you're running 'Piers' versions of add-ons. AFAIK there should be v22 versions of everything.

  • A95xF1 install

    If the box has previously been used with CE images, recovery boot (toothpick etc.) MUST be re-invoked else vendor u-boot looks for the wrong filenames and LE images simply won't boot. So one possibility is that you haven't quite gotten the hold/release timing to invoke that correct yet. Some manufacturers tweak the timings so it can be a fiddly and failure-prone process.

    The p281 or Tanix TX3 mini device-trees should boot the box as they're basically the same. The TX3 device-tree also describes the VFD display on the front so p281 would be recommended, but even if yours doesn't have a VFD display (or perhaps a differently wired one) that difference is harmless to boot. Other 'S905X' device-trees will likely boot the box too, but S905W would be preferred as the W chip runs slower so 'overclocking' can cause lock-ups.

    You can also see if appending video=HDMI-A-1:1920x1080M@60D to boot params in uEnv.ini makes a difference? - This forces the initial HDMI state to 1080p in-case the box is trying to negotiate some other unsupported (sometimes 4K) mode with the TV.

    The "box" image here: https://chewitt.libreelec.tv/testing/ has been boot tested on a TX3 mini in the last couple of days (due to upstreaming work on support for VFD displays) so I know the image is good. The codebase of the image is newer the LE11/12 images that you tried, but from a boot-files perspective nothing changed.

    The only thing that's really useful in this scenario is the UART boot logs that show what the box actually did, but most users don't have a UART cable, and most cheaper Android STBs don't have the UART pins wired on the board, so normally we can only guess at problems /shrug

  • MLB TV Add-on Crashing

    Perhaps the add-on needs adjusting to the Python version that LE uses then? although LE12.0 is not 'current' or 'recent' now so I rather doubt that's the issue. Regardless, it's not our add-on or our code. Please report the issue to the add-on author(s).

  • Hyper-V Support?

    Quote from jbinkley60

    I .. was wondering whether any more thought has been given to add support for Hyper-V virtual environments given the purchase of VMware by Broadcom and their apparent reduced interest in supporting the end user community ?

    I can't recall the last time anyone on staff talked about using the Virtual image for development purposes, so I'm highly confident there have been zero thoughts about Hyper-V support. If people did want to run an image on something non-vmware the go-to these days would probably be Oracle Virtualbox since it's $free, already works, and doesn't require Windows. On the server side Proxmox seems to be what people are using.

  • [Odroid-C2] 4K MKV Playback

    I can only pseudo-read the current driver code and I'm not aware of what the underlying 4K on GXBB issue was so I can't comment on what the current dimensions cap achieves or avoids. As the current driver is in an 'abandoned' development state I'll also avoid making changes in the LE sources, although changing the max resolution to 1920 x 1920 to support portrait 1080p media is probably okay as the memory usage will remain the same. I'd say "report back if you encounter any weird stuff" but as the drivers are not in a finished state there's plenty of known weird stuff to find :)

  • [XR819] How to add the WiFi driver to LibreELEC

    There is no upstream driver and no current attempt to author an upstreamable driver that I can see.

    This appears to be the most widely used driver source that I can see: https://github.com/fifteenhex/xradio and this probably makes it the 'least worst' to use (the repo README is honest). This chipset has quite a reputation for being rubbish once you start looking-for and finding information on it.

    LE has zero interest in adding out-of-tree drivers with no upstream plan to the buildsystem, but a self-built image can probably be done. I spotted some notes here: RE: How helpful will this be to getting LibreELEC on allwinner android boxes? and the zip file posted there contains some examples of the kernel device-tree changes that would be needed alongside the kernel driver itself. There are other threads that mention XR819 but they look to be mostly users asking for drivers and being told that it's not supported.

    Unless you like the development challenge (with the likelihood of a poor experience outcome even if successful) I'd probably just get myself a USB wifi dongle or a USB-powered Ethernet/WiFi bridge dongle and not go down the self-built image route.

    If you do, the Realtek out-of-tree drivers found in older LE images (LE11 for example) are probably a good starting point for cribbing the format for a simple buildsystem package that compiles the driver.