Posts by chewitt

Rasplex used to be a thing (and was based on OE, then LE): https://www.rasplex.com .. but that died out.

There was also a "Plex Embedded" image for RPi/x86_64 devices (originally on OE, then LE) created by Plex staff that combined our base OS with an auto updating Plex binary, but I think that also died out over time, and I don't frequent the Plex forums these days.

I'm not sure if Plex has a dedicated Linux app now (or what would be required to run one). I have the impression that over time they moved to a more controlled (and thus restricted) client experience. If something exists it's all do-able, but that requires time/effort and the Plex universe seems to be more about desktop OS or native apps on TV's these days.

The solution is both simple; use a font that contains the the glyphs for the character sets you need, and rather complicated; as fonts that support all (or most) languages are considerably larger than most LE images

RPi boards have no real-time clock (RTC) chip so on boot the kernel log will start from the date/time of the libc release that's being used (one of the more obtuse kernel oddities). Then once the network is up, NTP (assuming it succeeds) will update the system clock to current time .. until the next reboot (rinse/repeat). You can set the time manually from the SSH console using the "date" command. NB: It's cheap and simple to add an RTC chip to an RPi board.

No idea why the network is not connecting automatically. It normally only happens with cheap USB dongles where the MAC changes on each boot: the Connection Manager (ConnMan) keys connections against the MAC so if this keeps changing, on each boot there's no stored connection and you need to enter the passcode again. That doesn't sound exactly like what you're seeing though?

video=HDMI-A-1:1280x720M@60

See if appending ^ to the kernel boot params in syslinux.cfg helps. It assumes the TV can at least handle 720p output.

A1156 is an Apple remote model number so it's not clear what era of mac mini you're using, but older ones have flakey EFI support so perhaps look at something like "rEFInd" to help things. Or if super-grub2 works: use it. LE doesn't care what bootloader has been used. NB: You can also test old LE images from https://archive.libreelec.tv/archive/ to see if they boot okay. If they do, install (with working boot files) and then update to current from there.

Googling .. (so untested). See the 2nd post here:

Debugging why NIC link comes up/down constantly

I'm detected an issue on my Ubuntu Intel NUC where the ethernet link drops and comes up again. It's a regular pattern where the NIC goes down for 4 seconds,…

unix.stackexchange.com

Quote from EBAL

Is there a version of LE that still supports install2internal and has Python 3 to support latest Netflix and YouTube addons?

In short, no. https://wiki.libreelec.tv/hardware/amlogic#install2internal

This is a script I started writing to help people image nvme drives: https://paste.libreelec.tv/together-egret.sh

The basic workflow is to download an LE image to /storage and then run "nvmetool w <filename>" where <filename> is the path to the image that you want to write to the nvme drive. It will image the drive, then expand the second partition to 100%, then rename the nvme partitions/filesystems so that you don't get a disk label/uuid clash with the probably-identical structures on an SD card.

It should work, but it's not heavily tested. The main step that it omits is setting the RPi5 eeprom to boot from nvme. Worst case you can at least crib all the commands needed to get a working setup.

Yup, spotted that in my mailbox. It's nice to see a lower cost option again.

Quote from chewitt

I have a hunch the initial requests for ipv4/ipv6.connman.org are intentionally not routed to a configured proxy as those checks are performed before the network is declared up (and thus the connection that proxy config is associated with is not yet established).

See previous statement ^ - If you want that changed, it's best to take up the discussion with the ConnMan developers.

As much as we love a whinge-o-gram post, it contains no actual descriptions of problems and no evidence/facts to investigate; not even an explanation of the hardware being used. On that basis .. no further action required

No clue and no time right now.

Quote from royrob69

Can I update to LE 13 nightly and what will il bring to me ?

These are images that will become LE13 in the future; around year-end seems to be typical for Kodi releases. The images are quite usable and stable right now, but these are development images with pre-Alpha code, so you should expect breakage and no formal support on them.

Where are the music files stored (the filesystem path)?

What sources are configured?

Changes were pushed yesterday so it's either already in the repo by now, or will show up shortly.

There's now a 2GB RPi5 board (lower cost than 4GB, but enough for LE). It's not an Android box, but it'll be better supported and a lot more reliable.

He has Android 6.0.1, which means whatever the problem is, it's not our OS, and thus not our problem to solve.

It's in the LE settings add-on.