Posts by chewitt

    There is low appetite among current staff to add a package manager to our deliberately HTPC-client focussed distro. We are more interested to know what the 3-4 extra apps are that everyone has a burning desire to run (as long as they aren't content stealing/theft/piracy tools) so we can consider packaging them as addons or asking the linuxserver.io folks to add a lightweight docker container.

    Installing docker adds directories where binaries live to the shell PATH so you can run commands. However, PATH is not updated dynamically so if you have a shell open before you install docker, it can't find the binaries until you log out and back in again. Once you log in again the new shell has the updated PATH and can find them.

    "MPEG-4 part 10" refers to a section of the H.264 specification. It does not mean 10-bit video (which is a problem on most hardware). If you look at the ffmpeg analysis a few lines before CDVDVideoCodecFFmpeg::Open in the log:

    Code
    1. 14:28:18.222 T:139708148455168 INFO: ffmpeg[7F10568F9700]: Stream #0:0(eng): Video: h264 (High), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc

    I've no idea what the problem is, but ^ that shows standard 8-bit H.264 video not 10-bit, so that's not the issue.

    The original error is caused by the kernel boot= param being wrong or (more likely confused) so it fails to mount the partition with the SYSTEM file and dumps you into the initramfs debug shell (which is pretty limited). If you're installing this doesn't make sense because the entire install process runs within the initramfs environment (in the KERNEL file) and you never reach the point in the boot process where SYSTEM would be required.


    So I think the USB bootloader is finding boot params on the SSD (for normal boot) but then you have some kind of disk label clash that results in it failing to find the SYSTEM file and boot fails. If you already made a backup of the existing system and exported that off-box for safe keeping, boot from an Ubuntu LiveUSB and reformat the SSD (any format is okay) then try to reinstall.

    It also crashes in High Sierra and possibly older versions of the OS too. I believe Apple has changed something with respect to app Sandboxing in their latest security update as even disabling GateKeeper (which has been reactivated despite me previously disabling it) doesn't permit the app to work as it did before. We will investigate, but that will take time so for now you will need to use another app. Etcher works well.

    Nope. The mali T820 GPU in the S912 is has a completely different architecture to the mali M450. Another project (panfrost) is working on support but that is some way off yet. We've managed to render bits of the Kodi GUI with panfrost, but not all of the bits simultaneously :)

    Some teamwork this afternoon resulted in LE running "lima" for the first time :)






    Definitely some rough edges to polish before we can consider using it in releases, but having testable code is a good start. It's not shown in the images but this was running on an S905X board.

    I'm interpreting the request as 100+ man-hours of fiddling around with underused staging code to create something complex that will be a pain in the rear to support considering the average skill level of our userbase. The alternative is searching eBay for a wireless basestation that can share printers over a network. The last Apple Alrport Express I acquired for exactly this purpose was £12 including postage. If you're retired and/or have nothing better to do with your time .. feel free to experiment. If you're not and you value your time .. use the right tools for the job! :)

    It rather depends on where you are in the world. In a number of EU countries there are popular satellite and terrestrial broadcast channels (even HD ones) that use interlacing so it's important for people using Kodi's DVB capabilities.


    Using an RPi as the back-end should be fine.

    LE is using tar from busybox not the full GNU tar binary so there are limitations in what tar options are covered - and that specific archive is using something that isn't supported. If you gunzip the file first then untar is shows "tar: invalid tar magic" when trying to expand the archive. You'll need to download and uncompress the archive somewhere else then move the files over. If you're doing it frequently you can probably copy the GNU tar binary over from another distro (as long as it's compiled for the same CPU/arch things usually work) and use that instead.