Posts by chewitt

  • Unable to install from USB,new to this. Am I doing it right?

    Three suggestions that might work:

    a) Enable "legacy boot" in BIOS settings which should disable EFI boot.

    b) Boot from any other Linux distro USB and run "dd if=/path/to/LibreELEC-Generic.x86_64-9.0.2.img of=/dev/sda bs=1M" (checking the disk you want to write to is /dev/sda .. and noting the image is uncompressed to .img not .img.gz). This writes the USB image to the HDD, and in theory this should boot, time out the same way, but this time it self-installs to the HDD not the USB so you end up with a working install.

    c) Remove the HDD and put it in a USB caddy to write the image to the HDD .. different way to the same result as B.

    A is easier than B which is marginally more complex but requires no extra hardware like C

  • Libreelec 9.2 and HDR

    RPi4 haardware is capable of HDR but LE (and all other RPi distros) have no "software" support for HDR at the current time. It's still being worked on and might part of the future LE10 (Kodi v19) release if things keep going at the current rate of progress. No promises though.

  • LibreELEC 9.2: Pi4 picking the wrong resolution (720 instead of 1080i)

    Kodi outputs progressive and interlaced media output is faked, e.g. 1080i@25 (typical PAL content) will be output as 1080p@50 (one interlaced frame per refresh, so double the number of interlaced frames). This means even if it can see 1080i in the list, it will choose 720p as the desktop resolution. I forget how things have evolved over Kodi releases, but IIRC this has been the behaviour for some time but older releases wrongly reported things so people believe they were using 1080i desktop in the past when they weren't.

  • What aspects of hardware is supported under AMLogic mainline at the moment.

    The commit message is misleadingly worded. VP9 and HEVC share some common pluming which is provided by that commiit. In the same series you also have the full VP9 decoder. HEVC is still missing from the line-up. We are now in the odd situation of having the firmware that was missing a few months ago, but now the driver is absent. Previous patches that added HEVC support are not aligned to the updated firmware and recent compliance changes in APIs .. so rework is needed. Google (who is funding most of the current development) cares most about H264 and VP9 so those are being done first (annoyingly).

  • Emulators on x86 platform

    Kodi sucks a bit at presenting games, there is still no database to store the configuration needed for a specific game rom. In short, Emulators are just background plumbing and are not the thing you navigate from. You need to start from a game rom, then you're prompted for the Emulator to use with that rom. Then the game launches. This is where add-ons like "Internet Archive Game Launcher" are useful, because they create the searchable front-end interface to navigate from. The only games that will show up under "Home > Games" are games that are natively compiled to run on the host platorm (no emulator involved) e.g. 2048 and the Bomberman clone in our game repo.

  • [Solved] OSMC WiFi dongle on RPi

    Code
    mkdir -p /storage/.config/firmware/mediatek
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/mt7610u.bin -O /storage/.config/firmware/mediatek/mt7610u.bin
reboot

    ^ run those commands (mind the line-wrap on wget) .. working?

  • Use Raspberry Pi 3 A+ as Airplay receiver in car

    If the phone ends up with a link-local address (169.x.x.x) the iPhone will not see the connection as routable so data continues to work as normal. The hotspot feature in ConnMan (the connection manager) only allows you to set on/off and ssid/passphrase though (same as the phone hotspot which is what the feature was designed for) .. so it's not possible to set/control that.

    In theory if you share a hotspot from the phone you achieve the same thing (RPi and Phone have an IP connection) but the phone remains the internet connected device. I've never tested to see whether the Phone can see the Kodi Airplay target in this mode though. Go see if that works?

  • RPI3B+ to RPI4B

    To do it the lazy but more risk-prone way, you need to SSH in and run three commands:

    Code
    touch /storage/.update/.nocompat
wget http://releases.libreelec.tv/LibreELEC-RPi4.arm-9.2.0.tar
reboot

    This will disable the compat check (else we detect RPi4 is the wrong image for your RPi2(3) device and abort update) and then we download the RPi4 image and reboot. On reboot it will update to the RPi4 image. On reboot after updating it should fail to boot. You can now power off the RPi3 and move the SD card to the RPi4, which should boot. Remove any overclock/tuning etc. from config.txt before booting the RPi4 - it's not necessary.

    If you want to play safe, make a backup first, then you can always clean install the RPi4 and restore the previous configuration.

  • [unoffical] LE-9.2/9.80-Images for RK3229/RK3228

    The reason the SSV6051P driver works on the RK BSP kernel (and current Amlogic BSP kernels) has nothing to do with RK having better open-source compatibility. It is simply due to RK using an old kernel. I forget the exact kernel version where things break, but once you move beyond Linux 4.11 or 4.12 there are major crypto API changes and the driver no longer compiles. If you're lucky RK might task one of their internal devs to rewrite it at some point, but IMHO that's a long shot.

  • access windows shares

    Support for "SMB browsing" only exists in the SMB1 (NT1) protocol which is now deprecated almost everywhere due to the huge number of security issues it contains. There is no native support for browsing in SMB2 or higher, it's not part of the protocol, you have to use an entirely new discovery protocol (ONVIF). "under the hood" Kodi uses the Samba smbclient which does not include ONVIF support, so once you start using SMB2 or SMB3 (the default in Kodi v17 and up and all current versions of Windows) there is no support for browsing. If browsing is essential, i.e. you're not capable of learning an alternative way of doing things, you must downgrade all your 'server' devices to SMB1 and then force both min/max SMB protocol support in the Kodi SMB client to SMB1. Then everything speaks SMB1 which supports browsing. If you choose the sensible option and keep your devices on SMB2 you just need to configure things properly (once, in sources.xml) and that should be it. As a rule anything you serve media from should be on a static address (via DHCP reservation in the router is easiest) and then you can configure sources using an IP or a hostname. As long as something on the network is a master browser the names should resolve. At least, that's my personal experience. I set sources.xml once ~8 years ago pointing at a device called MEDIABOX and haven't changed it since (the box has changed, but the share names remained the same, so no reason to change clients).