Be more specific. How is it not working? .. black screen, error message, etc. .. and provide a Kodi debug log.
Posts by chewitt
-
-
You don't need a lirc.conf so that's fine. Go read the tutorial again slowly (and assume you don't need lirc, because 99.99% of remotes don't)
-
None that i'm aware of. I started looking at wsdd but lost enthusiasm. I'll float the idea in the team again and see if there's any takers now that 9.0 is out the door.
-
Panfrost comprises userspace mesa code which is in reasonable shape (enough to have initial patches merged into upstream mesa in recent days) but still has some lurking memory leaks and no 32-bit support which we need (no 32-bit userspace = no Netflix) and kernel side it's using a hacked ARM driver which needs to be superseded by a true panfrost driver, which is at the early stages of development. I'd guesstimate that Panfrost has a couple of months before some of the stability impacting issues are squashed.
Elsewhere in the mainline codebase we have 10-bit video and HDR, framebuffer compression, deinterlace, and multichannel audio to complete, but we have visibility on funded commercial work packages that should fill most of those blanks in the near future. There are also some signs of DVB support although the current code is "forward porting using a kernel backporting technique" so it will need restructuring to be accepted upstream, but hopefully that happens.
-
Kodi can use SMB from within Kodi. Plex (in docker) cannot access mounts via Kodi. So mount in the OS and then configure both Kodi and Plex to use the same /storage/mountpoint(s) for the remote SMB/NFS shares.
-
Sounds like a textbook case for another FLIRC device to me? https://flirc.tv/more/flirc-usb
The only bit that might/will be different is power-on, but if the Beelink box supports IR wake and the Sony remote can learn that, should be okay.
-
"it doesn't work" because it's not included in the image .. because it causes a HUGE number of support issues and provides a marginal speed bump over a fast SD card.
-
aka systemd mounts; look at the example mount files in /storage/.config/system.d/
-
Kodi auto-migrates the numerically latest database version which is from the alpha/beta install. You need to stop Kodi and then delete newer DB files so that only the older/current 8.2.5 install DB files are present. Then restart Kodi and it will migrate the 8.2.5 files.
Databases - Official Kodi Wiki has info on Kodi DB versions.
-
You all need to start telling us exactly which wifi chipsets are involved else it's impossible to speculate or investigate where the issue lies.
-
I'm not near an RPi to check, but look at cmdline.txt and make sure it's using the correct boot= and disk= label or UUID's for the USB stick.
-
Use a docker container with nginx and whatever php version you want - there's bound to be one.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Share the contents of the mount file.
-
I don't want to make big promises but I can probably build and test community WP1 and MX2 images until the drop of amcodec in LE10 or at least until the revert of the commit is the only change needed to make it work.
Once we bump to mainline kernels and clean up all the old driver packages things will break. Until then most of the 3.10 dependencies are shared with the 3.14 images so it should be a simple revert.
-
Are you writing the LE image directly to the USB stick, or cloning an existing SD card install? .. and which LE version?
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Run "touch /storage/.config/safemode.disable" and it won't be invoked, but there's some underlying problem. Add-ons are the biggest culprit.