Posts by chewitt

Connman actively manages content in its cache folder (means you shouldn't add stuff there when connman is running) so you need to stop the service before adding a correctly formatted profile directory and settings file and then restart the service. You shouldn't need to configure anything in iwd; the config should be passed from connman.

Note that ConnMan names the profile directory in a structured way (not plain SSID) and the SSID in the directory name and in the settings file must be a base64 encoded string; connman will not auto-convert plaintext SSID details, and since passphrase (with a non EAP) connection is the same I'd make an educated-guess that username/password in an EAP connection file also will be the same. If all else fails, the long-winded route I've seen others take for EAP connections in the past is to boot a normal desktop distro that also uses ConnMan and get the connection and config working there; then transfer the profile/settings over.

2023-07-29 02:55:49.891 T:757     debug <general>: CDRMUtils::SetMode - found crtc mode: 3840x2160 @ 30 Hz

EDID data in Kodi.log shows 1080/3840 modes fine but this ^ looks like it's trying to set 4K GUI which won't work as the silicon only supports 1080p on the GUI plane. Have you fiddled with the GUI settings on the other monitor? .. because by default we set the GUI to 1080p. If no, I can't explain, but perhaps try clearing display settings (stop kodi, delete guisettings.xml, restart kodi) or force the initial DRM output to 1080p by appending "video=HDMI-A-1:1920x1080M@60" to kernel boot params in extlinux.conf.

Params are either in uEnv.ini (box image) or extlinux.conf (board images) .. config.txt only exists on Raspberry Pi images.

If the drivers load, the network will come up, and if Kodi was told to wait until Kodi is online it generally does that reliably. However there is no magic we can do in software to fix radio issues, so if the connection is rubbish

Perhaps try forcing the HDMI output with "video=HDMI-A-1:1920x1080M@60" in boot params. Otherwise .. no clue.

LE runs Kodi on the framebuffer without any kind of "desktop" that you can minimise windows to, so playback always runs fullscreen.

To be clear, this works now/today for the 11.0.3 release. I have no plan or interest to maintain links for this over time.

AntonLacon shared a modified JSON file which I've added to my team share here: https://chewitt.libreelec.tv/releases.json

It would be reasonably simple to enable/start tethering using "connmanctl" commands, and running something two minutes after boot would be simple enough using an autostart script or systemd service. The usual challenge with these types of things is what you check to determine "not connected to the right location" to then initiated the process.

Quote from orione7

I hope that support for relatively older devices (like Nuc 6) will not be abandoned. This is one of the strengths of libreelec.

Note that "supporting old hardware" has never been something the project has aimed to do. It's just a coincidence that Intel CPU/GPU devices generally have a longer lifespan. It should be able to boot the GBM release already.

Quote from kneetzstopz

I tried in the "Custom channel" to enter "https://test.libreelec.tv/releases.json" for the "Nightly" versions but I only see the list of generic and not Legacy-Generic. Is it normal or is there an error?

Read post #14 (again)

There is almost nothing in-common between LE9 and LE11 images; so while it might be true observation it's also rather meaningless (or, not useful) because literally everything has changed (boot/kernel/kodi/etc.)

I'm wondering if adding "video=HDMI-A-1:1920x1080M@60" to kernel boot params in syslinux.cfg would help? Using the GBM (non-legacy) image would be preferred over the X11 (legacy) one.

One week suspension applied. If you register new accounts to shill post, it'll be a permanent ban.

therealwolve Your continued posts nit-picking how we adminster the forum are tiresome and taking more time/effort to respond to than dealing with actual spam (which is rare, as we have effective measures in place to prevent it). If you continue to grind the axe on this topic your forum account will be suspended so everyone can focus on helping users with actual problems.

The Generic build-system "Project" was organised into "GBM" and "X11" build-system "Devices" to emultate the build-system project/device organisation we use with ARM SoC images. This keeps the build-system compact, but the current update process only uses Project (not Device) when requesting update tar files; and the JSON data only supports the GBM files. In hindsight "Legacy" should have been done as a separate Project (as was done in the past) .. but it's a bit late now, and in the mid/long term the X11 image is hopefully dropped anyway.

cd /storage/.update
wget https://releases.libreelec.tv/LibreELEC-Generic-legacy.x86_64-11.0.3.img.gz
reboot

SSH into the box and run the above commands ^

Then say out loud "fcuk me, that was so much easier than trying to self-host images and JSON files" .. and go watch a movie or do something fun with your kids/partner/pet.

Did the deletion of a bunch of out of date files break your box? .. no

Does the 11.0.3 update fix anything critical for AMLGX installs? .. no

Can you continue using your box the same as yesterday simply by turning it on? .. yes

"nothing to see here, move along please"