It's bundled with the second/alternative LEIoT distro that's now part of the LE buildsystem.
Posts by chewitt
-
-
polo_joe Compose is not included with the standard Docker add-on because it's a HUGE file. I will get around to submitting a separate add-on for it at some point so it that can be downloaded alongside Docker if required. Until then you'll need to wget an appropriate arch file from https://github.com/docker/compose/releases to somewhere on /storage and execute it manually.
-
Maybe bug came back again?
Nope.
Share a Kodi debug log that demonstrates the issue.
-
Go read the wiki article that I linked and implement "adjust refresh" and the whitelist as discussed there. Or at least provide a Kodi debug log that demonstrating the issue so we can see what the media properties are, and then what config (or lack thereof) forced them to be adapted to for playback, which is likely the issue.
-
Also, I get a popup with the 3 installation options (live, run, or install to HDD) every time I boot from that USB drive.
Type "run" and it will expand the /storage partition to 100% size for persistent storage and then run from the USB stick. If you do "live" it will boot from USB but the install is not persistent. It defaults to install .. which requires you to pick a target device to install to, which cannot be the USB stick.
-
Please share debug UART logs showing u-boot and (maybe) kernel boot output from both LE13 and DietPi images.
-
balbes150 Жду тестового оборудования
-
To understand what might be happending we'll need to know what sources the image you're using is built from (as we didn't build or provide the image, and we're not mind readers) and to see UART logs showing u-boot and system output during boot.
In the absence of that info ..
-
Sorry, no clue. I've long used a NAS in the network to avoid USB drives so can't speak from any experience.
-
Is there somebody who can help me?
LE 9.2.8 is old now so our first response is going to be "Please test a current release" to eliminate all the fixes and updates that were made since (there's been a few). I appreciate there are possible reasons for remaining on LE9.2 with an RPi3, but even if there's an issue and that can be pinpointed (sharing some debug logs would be a good first step) there's not going to be any fixes in that release, it's a long dead codebase.
NB: Tvheadend has evolved too. How old?
-
The "amlogic" branch has current changes. You don't need to report on updates if things work the same as before.
-
Maybe I buy an adapter that is not jmicron
There's enough reports on that adapter for me to think it has firmware problems, so probably not a terrible idea.
-
ozarks Panfork was a fork of panfrost (hence the name) hacked/adapted for ARM Mali Valhal hardware while "panthor" was still in the earlier stages of development. As panthor is now developed and upstream it's been superseded. In theory Direct-to-Plane with DRMPRIME decoding should be the default used; although until I have some RK3588 hardware to test with (some is allegedly being sent to me) i'm unable to do anything beyond theorize what's missing or required.
balbes150 please push changes to your GitHub repo, thanks.
-
There's nothing on the LE side to prevent boot from USB, but I've sometimes found that Android boxes will only boot from a specific USB port, and some boxes refused to boot from one. Roll dice and see what happens
-
dominion The fix (merged several weeks ago) was for all hardware so whatever your issue is, it's something else.
-
LE13 dropped "wl" because it broke compat with the kernel and it's not been maintained (no new version) in years. We chose not to enable "b43" as an alternative because although it's technicaly "in-kernel" it's similarly abandoned and unmaintained and the likely audience of impacted users can probably be counted on one hand. As previously commented, if you have one of those cards intalled somewhere it's probably simple and cheap to swap it for something better.
-
LE13 nightlies are bumped to Linux 6.15.1 and images in my test share are bumped to Linux 6.16-rc1. No functional changes are expected .. the media drivers are still abandoned.
-
I dare say that as Wayland development matures, solutions will be created.
The issue is known about in the Wayland ecosystem for many years already so I woulnd't hold breath or hope of a solution. NB: It's generally not an issue as Kodi GBM works well, although on new hardware where the DRM layer is still maturing there might be some glitches to resolve.
