Camera devices have no use to Kodi so the LE kernel does not enable them. Hence "lsusb" shows the device as present on the bus, but in the absence of a kernel driver nothing more happens. If you're the tinkering type, you can self-build an LE image with the required driver enabled. Have a read here: https://wiki.libreelec.tv/development/build-basics and here: https://wiki.libreelec.tv/development/git-tutorial
Posts by chewitt
-
-
LibreELEC.tv/packages/graphics/mesa/package.mk at 10.0.4 · LibreELEC/LibreELEC.tvJust enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.github.comLibreELEC.tv/packages/linux/package.mk at 10.0.4 · LibreELEC/LibreELEC.tvJust enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.github.com
Use the branch/tag selector to move to another (release/tagged) point in Git history. Use "git grep" to find things in build-system sources. The "mesa-demos" package provides glxinfo.
-
Turn all devices off and physically disconnect HDMI cables. Go make a coffee and leave it alone for 15 mins. Reconnect cables and power things on; the TV first, then the RPi4. Any change?
-
You'll see that screen if the bootrom cannot find an OS to boot. It can see an SD card is inserted, so I'd hazard a guess that the card has some kind of issue (or has failed). To narrow the problem, grab a spare SD card and create a new install, and see if that boots?
-
Please test this image:
https://chewitt.libreelec.tv/testing/LibreE…-11.80.0.img.gz (install/run from USB drive) or
https://chewitt.libreelec.tv/testing/LibreE…_64-11.80.0.tar (update existing install)
Share "pastekodi" results after, thanks.
-
The mostly likely cause (and unfortunately the hardest to debug) will be "some radio issue in your environment" .. it could be interference or loading on the AP or proximity to other devices or too-strong a signal or ..
To investigate you'd likely need to run iwd in debug mode, which will generate mountains of debug log output, which probably nobody on staff will really understand (as none of us are wireless engineers).
Pi is close-enough to run a short cable? Ethernet really is the best solution to WiFi problems (though never the answer people want).
-
There is no "make default" command or "set as default" that you can put into ConnMan service files. You can however use connmanctl to change the service order, moving a service up or down the order. I'm not sure if the first configured gets the route or there's other black-box magic involved. You might want to email the ConnMan mailing list to get answers on that kind of question.
-
I have a hunch it's this https://github.com/xbmc/xbmc/issues/23622 albeit with a slightly different use-case/presentation. If I'm right, it's not technically a bug since current Kodi GBM code is working correctly. The issue is that current Kodi GBM code doesn't handle enough rotation scenarios. The reason it stopped working is due to RPi images swithing to the GBM display pipeline (moving away from proprietary code to standards in the now-upstream kernel).
-
AFAIK there is no such thing as an RC1 remote protocol. Do you mean RC6 (which does exist)?
-
In earlier Googling I found the following reports:
[0] https://github.com/clearlinux/distribution/issues/2396
[1] https://mailman.alsa-project.org/pipermail/alsa…uly/187558.html
If my hunch is correct, the following should invoke the quirk against the correct PCI IDs (which we now have, thanks). The link Da Flex posted also mentions adding a quirk to solve the issue, and I suspect is the same issue.
ALSA: hda/hdmi: Add quirk to force pin connectivity on HP Prodesk 400 G4 · chewitt/linux@c63b9d1On this variant alsa fails to offer HDMI audio output options. Add a quirk to force connectivity. Signed-off-by: Christian Hewitt <[email protected]>github.comI'm building a tweaked LE12 image with that patch added so you can test. If it works, I'll send it upstream to the kernel. If it doesn't work there's another variant (based on the thread that Da Flex found) that we'll check.
-
All source code for our Amlogic releases is in our public GitHub repo, but that's not going to help you with running an Android apk file as we do not (and never have) supported that. TL/DR: The only OS that supports Android .apk files is Android.
-
Code
gunzip -c LibreELEC-RPi4.arm-11.0.3.img.gz | sudo dd of=/dev/disk2 bs=1mYou can use "dd" from Terminal.app to create the SD card. Something like that ^ should work. Use "diskutil list" to find the correct /dev/device for the SD card.
-
"lspci -vn" seems to work (finally got access to an Intel CPU device .. they are different to ARM boards).
-
LE is packaged so the entire OS resides in two files; the KERNEL and SYSTEM files in the first partition of whatever device you boot from. The storage (second) partition is only used for persistent data, and Kodi DB files and add-ons are the only content that might be touched during upgrades, so long-term placement of media elsewhere on /storage has no impact from upgrades. There is no need to delete media to make an update unless perhaps you reached 99%+ full on the disk (some space is required for update file unpacking).
Update from LE12 nightlies to LE12 future releases (nightly or otherwise) is simple and supported, and currently nightlies are quite stable; at least on the RPi hardware that I use.
-
We don't support install in/on/via proxmox so there's probably something missing
-
Urgh.. I'm trying to get the PCI device IDs in xxxx:yyyy format, so perhaps "lspci -vv | paste" or worst case -vvv needed.
-
RPi3B+ using LE 9.2.8 will be the "best and final" recommendation. LE 10.x and newer switch to an all-new GBM/V4L2 video pipeline where 3D support simply hasn't ever quite made the priority list for development, and while the initial RPi4 hardware is supported by the initial LE 9.2.8 release, newer iterations of RPi4 hardware need firmware that only exists in newer/current LE releases. It's possible to self-build a doctored 9.2.8 image with newer firmware etc. there's no HOWTO guide for that (although not too hard if you have a tinkering mindset). Considering the limited amount of new 3D content these days and depending on what other media you need to handle; i'd keep a spare 3B+ lying around for 3D duties when you need to play something, while using an RPi4 (or something else that meets needs) as the main player board.
-
I have tried your image (LibreELEC-AMLMX.arm-10.88.0-box.img)
You've done more than me then
Martin seems to be MIA at the moment so the best I can suggest is self-building using my AMLMX branch but with the Linux package update to use his latest kernel source (Linux 6.3 IIRC) to see if anything changed.
