Posts by chewitt

Kodi uses libaacs to read BR media and libaacs will not function unless there's a KEYDB.cfg file present with appropriate content for the disc that you are trying to play. I have no personal knowledge on makemkv so I can't comment on how you'd make that work.

The alternative is a huge number of spam bot posts per-day which is repetitive and demoralising work for the forum staff who already give up a large amount of their personal time to help the project. We value making their forum lives easier above a little wordplay inconvenience for users. Sorry but it's not going to change.

Lima submitted its kernel driver today. It's not the first submission but this time around it has a fairly distinguished list of "Signed-off-by" signatures on-board so I'm hopeful it goes into the 5.1 merge list and there's a date that I can drop one of the larger patch-sets. Panfrost also merged initial mesa stub support which will make mesa packaging easier from 19.1 onwards. All over the codebase we're starting to see lots of the jigsaw pieces slot into place although community development is often a frustratingly slow process. I'm confident that in the future we'll be able to release a single Amlogic image that supports GXBB + GXL + GXM devices, though that's a long-term goal (not in in this half of the year at least).

Blu-ray [LibreELEC.wiki]

05:21:38.302 T:1790935920   DEBUG: CurlFile::Open(0x6abf7ab8) http://mirrors.kodi.tv/addons/leia/addons.xml.gz
05:21:38.555 T:1790935920   DEBUG: CCurlFile::Open - effective URL: <http://103.1.138.206/mirrors.kodi.tv/addons/leia/addons.xml.gz>
05:21:38.626 T:1790935920   ERROR: CRepository: http://mirrors.kodi.tv/addons/leia/addons.xml.gz index has wrong digest aaec368750d01ade4908bc50e2c5bf37020fbae588d1d083f668ee2c33b59f03, expected: ������addons.xml����G�'��鯈�k��uW�y�1����F�Y���EUFWeWVf)�T?�
�Ѐv@    !��oh�fWp�?5�{�k��E,4b��_��Gdfe��

Kodi uses geographic mirrors provided by volunteer third-parties to host add-ons. It looks like the one you're accessing is out of sync so the checksum doesn't match and Kodi cannot load the repo files. The problem should correct itself with time; either because a future request will be redirected to a different mirror (if there are multiple mirrors in your part of the world) or because the mirror will resync and have the right files again. If there's a single mirror that you consistently prefer (are redirected to) and it's wrong .. there's not much you can do. Plan B is to find a Kodi mirror and download the zip file for the addon and install it manually, although YouTube has external dependencies and you'll need all those too.

Log shows the ntp service works, but the mount attempt is some time before the clock is updated.

Create /storage/.config/autostart.sh and add the command "date -s "06 FEB 2019 11:10:00" (make it to something close to current) and reboot. I'm wondering if negating the clock drift solves anything? Is there any difference when using the default (pool.ntp.org) servers?

Downgrading the connection to SMB1 shouldn't be required (as it mounts fine). It's just a workaround for some other issue. Do a clean boot, let the mount fail, and then run "journalctl -b 0 --no-pager | paste" and share the URL here.

I have a hunch the issue is ntp related.

Read post #24 again. Follow the comments in the files.

Be more specific. How is it not working? .. black screen, error message, etc. .. and provide a Kodi debug log.

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.