Posts by chewitt

    The <incomplete> log shows the SoC vendor is Rockchip so I moved the thread, but SoC model is <unknown> and kernel version is <unkown> which means our ability to guess the <unknown> problem is <unknown>. The lack of technical info from you is rather annoying but also rather irrelevant, because your <unknown> hardware probably needs a Rockchip Linux 4.4 vendor kernel? and our codebase is not compatible with Rockchip vendor kernels. It was in the past, but our display and video pipeline is now dependent on modern (upstream/mainline) Linux kernel APIs that legacy kernels do not support. You might be able to frankenstein an LE image to boot and even start Kodi, but there will be no video decoding in hardware which is essential for playback on an ARM SoC device. To get a more useful answer you will need to provide more useful info.

    Code
    rm -rf /storage/.update/*
    mkdir -p /storage/.update
    cd /storage/.update
    wget https://releases.libreelec.tv/LibreELEC-RPi2.arm-9.2.8.tar
    reboot

    ^ run that from the SSH console. I'm not sure what the issue is, but if it succeeds - that's good. If it fails you should see more output from wget on why it's failing. We do use dynamic redirection to geo mirrors which occasionally (not often, but it can happen) causes weird issues.

    For iMX6 devices LE is (these days) a dumb consumer of whatever state upstream code/support is in, which is probably not brilliant. I have some minor fixes to push into master but these are for hardware support on the newer iteration of the Cubox-i (v1.5) which has different Ethernet and WiFi chips compared to the earlier variant that most LE users have. It's essentially unmaintained, but once some of the work being done on stateful v4l2m2m decoding for Raspberry Pi goes upstream (and down again) that may improve things. The LE 8.2.5 release is probably the better option on these boards .. although the Kodi version is getting old now.

    Maybe the people at Libreelec can somehow make it backwards compatible?  

    Maybe the people producing Argon cases can get their sh!t together and fix their product themselves? .. we (staff) are getting a bit fed up with the number of Argon users showing up here experiencing issues due to lack of software support and fiddly/iffy connectors/cables in ther case causing a range of connectivity problems.

    ErikSwan https://github.com/raspberrypi/linux/ <= everything is there. There will be differences between upstream mainline kernel and the downstream Pi kernel, but there's a pleasing-to-see continual upstreaming effort so the differences are not so big. Note that you also need to combine this with Pi firmware and the latest ffmpeg version; not specifically for HDR (which is more of a DRM thing) but to ensure you have the latest playback fixes. FFMpeg changes are still being hoarded downstream; the focus is still on features/fixes before that effort will start in earnest.

    If you really want to watch iperf(1) install docker and pull a container with the right version inside. I'll leave you to ponder on whether the need for docker on the host will consume CPU that could otherwise be directed towards maintaining Ethernet performance; e.g. whether or not you are the cause of observer effect ;)

    I'd also comment that you can test by playing a movie. If the movie plays fine your HTPC + NAS + Network combo is "fast enough" to watch movies and you don't need to obsess about whether the NAS is achieving best-in-class or mediocre performance. Watching movies is more fun than watching iperf (any version).

    You can edit the docker .service file (somewhere in the add-on dirs) to add the after dependency; don't forget daemon-reload afterwards to update systemd.

    I'm also fairly sure you can just dd the LE image to eMMC, I don't think RK doesn't anything too fancy with boot unlike other SoC types.

    I'm reaching the point where I read "Argon case" and some combination of audio/video problem and I skip ahead to the next thread.

    Get a flirc USB device and use any remote you like. You won't regret it.

    Most of the LE filesystem is read-only which would explain the permissions error. You need to use a writeable area like /storage or if using a removable drive, somewhere under /var/media/<drive> where the drive is auto-mounted. I'm not anywhere near an LE device to check but I'm not sure /media is a valid location in the OS.

    If you apply Pulse config via /storage/.config/pulse-daemon.conf.d/daemon.conf it will be processed at startup and overrides the embedded config file before Kodi starts. The other alternative is creating a systemd service file in /storage/.config/system.d to run commands or a script with dependencies to set when in the boot sequence the service is run, e.g. after Pulse and before Kodi.