Posts by chewitt

debug <general>: bool KODI::WINDOWING::GBM::CDRMUtils::FindPlanes(): Using video plane 41
debug <general>: bool KODI::WINDOWING::GBM::CDRMUtils::FindPlanes(): Using gui plane 38
...
debug <general>: GameClient: Loading game.libretro.uae2021 in standalone mode
debug <game.libretro.uae2021>: Setting libretro pixel format "XRGB8888"

Run modetest | paste and share the URL. I'm not familiar with retroplayer internals but let's see if plane 38/41 are supporting that format (IIRC, XRGB8888 = XR24). I'm blind guessing at the problem though.

NB: Do other emulators, e.g. something simple like a SNES one, work or show the same issue?

PR is merged

[Unit]
Description=nfs-y-script
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
What=192.168.1.2:/y
Where=/storage/y
Options=nolock
Type=nfs

[Install]
WantedBy=multi-user.target

The Either use '-o nolock' to keep locks local, or start statd message comes from the underlying NFS libs but systemd knows whatever follows Options= is an option so you don't need to provide the -o prefix to nolock.

rozpruwacz please retest using an image built from the amlogic branch in my GitHub LE repo or add the hbiyik/reardonia Kodi patchset that you find in that branch to the test image.

Investigate manual mounting of an NFS share from the console. Once you have that working .. translate the working config into the required systemd mount file options. Pay particular care to the NFS protocol versions being used because modern kernels (client) might make assumptions on infrastructure (server) supporting equally modern versions of NFS, and if SMB is unperformant you probably have old server hardware running old server software. In my experience SMB works fine unless the underlying network environment is poor, and the cure for that is always fixing the environment not swapping protocols

radome  Bedford

Please see if this LE13 image solves the issue? https://chewitt.libreelec.tv/testing/LibreE…-12.90.1.img.gz

Quote from Sprintv

Is it possible that LE 13 doesn't support TvHeadend?

Tvheadend 4.3.x is widely used and we track upstream changes. It's always possible that upstream breaks itself, but as a general rule that kind of thing is a rare event.

I'd guess the add-on is checking for keysize even though it's a long deprecated option. You should flag the problem to the add-on maintainer through their GitHub issues list. The add-on is not managed by LE project staff.

What LE version? .. and does the Kodi GUI show correct (summer) time?

Also provide a Kodi debug log.

The "getedid create" process should work the same on all hardware we support these days; perhaps with a few niche exceptions among ARM SoC boards, but AMD cards should be fine. There's no harm in experimenting anyway and "getedid delete" will always clear-up the applied config if it didn't work.

Quote from Da Flex

then it looks like an FFmpeg bug to me:

In logs "error" does not always equal a fatal problem. In fact most of the time it is nothing more than the application following some kind of if/then/else decision tree when processing data. Is the file mp3; no (so log error on that path, keep processing) is more likely to be the cause (or something of that nature). If you read the log further the file is clearly being played so it wasn't fatal.

BokitoNL You didn't share the output of pastekodi so we don't see the system log (only kodi log) but I'm not seeing anything in the kodi log to indicate an HDMI output problem. I would advise to check cables and ports and also ensure config.txt is in a clean or default state without any kind of helper overrrides being used.

I've moved this into its own thread as it has nothing to do with RK development.

As this is not an LE issue you should report the problem through the Kodi issue tracker (following the issue template else it will be auto-rejected and closed). NB: In recent years Team Kodi has been mulling a complete removal of profile support and then doing a ground-up reimplementation with a better overall design; the current one has too many problems. However it's a huge amount of work and so far nobody volunteered for the task, so it remains substandard.

Run "pastekodi" and share the log URL. Let's see if there's an obvious explanation.

Quote from mitzsch

Are there any fixes for the HBR audio dropout issue in that new build?

Nothing specificially targetting the unknown problem. Figuring that one out is beyond my skill level and using Claude needs a level of strong direction else (from experience) it will makes lots of insightful sounding but garbage triage while running in token-burning circles not achieving anything.

I've posted some fresh images for RK3566/3568/3576/3588 boards to my test share. The kernel bumps to Linux 7.0, but more interesting is the inclusion of work-in-progress Kodi changes that tonemap the OSD/GUI during HDR playback so that it renders with an SDR colourspace (while video remains in HDR) instead of searing your eyeballs. The greatest benefit is seen (literally) with subtitles. There's also some minor nip/tuck fixes for VP9 playback.

Enjoy

Quote from 25characterslong

Are all users that need to access wifi in the netdev group?

The netdev group exists in LE to appease a couple of binaries that insist there should be one, but it's empty (has no members) and it is not otherwise used. ConnMan runs as root, as does almost everything else in the OS.

Quote from wedok

Does anybody know what exactly i must do to get it working?

You need to self-build an LE image with their drivers or whatever hacks are required to make their cards work patched into the Linux kernel. We used to have driver add-ons that overlaid some of the so-called "popular" card vendor drivers; but those were a complete pain to maintain and over time nobody on staff wanted to continue/make the effort and they were dropped. We encourage users who want DVB cards that "just work" under LibreELEC or any other mainstream distro to vote with their wallets and purchase products from vendors who upstream their drivers/firmware and engage in mainline kernel support for their products. TBS make some nice hardware but do not fit that description. Caveat Emptor

It's probably an Allwinner H3 device, so moved to that subforum.