Posts by chewitt

    You can try booting the Tanix or Beelink 'box' devices on the Allwinner/H6 download page.

    LibreELEC is an appliance-like Linux. There are add-ons for most media-related things that users might want (other than piracy tools) but there is no package manager so you cannot just install things.

    You can experiement with Pulse audio to send audio over the network, but this generally sucks. There is no default/native option in the OS or Kodi to route audio to a UPnP target. Kodi can play from UPnP sources, but not 'cast' media to a UPnP target.

    There is no "Everything" mode in Picard, and I would caution against trying to stuff lots of files into the "to be scanned" pane. Your files will not always exactly match; requiring you to drag and drop things, which is easiest when there's only the files for a single album there. It will take time to go through and match/cleanup/correct all your albums. However, this is only a task you'll ever need to do once. You can train your children to do it ($free slave labour) although they often lack the obtuse knowledge of your music collection to tag everything right :D

    Two comments:

    a) If you can't boot from a USB stick, you might need to pull the drive and connect it to another PC and run the install from USB there; or write the installer image directly to the HDD and then (in the old PC again) interrupt boot and type "run" (direct from install media, which is now the HDD) instead of following the normal "install to target" flow.

    b) LE is small and lightweight which is appealing for older hardware, but we target current and recent HTPC hardware so are often missing the drivers and such needed for old hardware. If you have something so old that it won't boot from a USB stick, a more conventional distro that supports a wider range of hardware might be more appropriate.

    Our strong recommendation is to use a separate SAT>IP box or separate the 'head' end device from the player client so you can run whatever distro and distro version that works with the tuners you have, while the player client updates frequently with LE releases. The IT proverb "If it works, don't fix it" applies to anything with DVB .. it's the suckiest stuff we attempt to support.

    If the system was installed/working and then stopped; the most likely cause is the USB stick (or whatever device you boot from) has failed. LE is packaged with the entire OS contained in two compressed files (KERNEL and SYSTEM). In a conventional distro, if you have bad sectors on disk it will impact only the couple of files that are written to those sectors, and often the impacted files are not critical files so everything will appear to work until the whole disk gives up. Due to the way LE is packaged, if media corruption impacts any sector involved in storing either of KERNEL/SYSTEM the OS cannot boot at all.

    If corruption was due to something like unexpected file loss you might be able to boot Ubuntu and scan/fix the filesystem. If it was due to bad media (underlying pyhsical disk or flash memory issues) then you bin everything and start over with a new USB etc. - You might be able to get the contents or important things from /storage as that's a separate partition on the disk.

    IMHO there will only be one RPi killer, and that's another RPi :)

    RPi4 is not the best spec thing in the market, but only comparing hardware specs misses the point about RPi boards. They have massively better long-term software support, so they are reliable and continue to improve with age.

    Although bitrate is probably involved somewhere in the overall scheme of things, I'd guess internal bandwidth between IP blocks is where things are on/approaching the limit, so (repeating myself) some overclock might be helpful.

    Check how much disk space you have on the SD card (or USB, etc.). If there's not enough space the download might be truncating causing the mismatch in expected filesize vs. filesize on disk. The ChromeOS image is 1-1.2GB in size IRRC (and then you need additional space to unpack it and get the widevine lib inside).

    1. Yes

    2. No need to rename, edit uEnv.ini to use the right file. See:

    3. Right process, but will fail due to #2 being wrong

    4. Once booted from AMLGX the u-boot environment is modifed to find AMLGX boot files, meaning it will no longer find legacy image boot files. However if you remove the USB and repeat the 'toothpick' forced-recovery boot it should then search for and find the legacy image boot scripts and work with content on eMMC again.

    I don't have a U9-H so USB boot isn't tested, but it should be the same as an SD card. If it doesn't work, try different ports, or an SD card.