Posts by joe65

okay, will remove that asap

thanks

Quote from mitzsch

the playback info (pressing o) is not smooth

I see this as well on an NUC 13

the info needs some remarkable time to open

- but it's alpha and in an flowing state -

with the following settings I try to watch SAT TV (Germany)

- Allow using DRM Prime decoder
- Allow HW acceleration with DRM Prime
- Prime Decoder Method: Direct to Plane

and I'm failing, seeing a spinning wheel.

When Prime Decoder Method set to EGL it is working

Questions:

wrong settings on my end ?

Info:

Monitor is an PC Monitor (Philips 278B1, 4K without HDR)

while I'm reading the gits (LE, XBMC) I'm aware of the last changes regarding rendering, etc.

I'm thinking about opening a bug report at XBMC ...

Log:

https://paste.libreelec.tv/guideless-amir.log

in the log I find

2026-05-30 14:03:32.945 T:858   warning <general>: bool KODI::WINDOWING::GBM::CDRMUtils::FindVideoAndGuiPlane(uint32_t, uint64_t, uint64_t, uint64_t): Rendering will be done through EGL. Can not find a Video Plane [3840x2160] format:YU12, modifier:LINEAR together with a Gui Plane [1920x1080] format:AR24, modifier:INTEL_Y_TILED.

Under System Display is set to 3840x2160p with Refresh Rate: 60 and that Resolution is whitelisted too ...

===

other question

while running with the above settings, esp. "Allow HW acceleration ..." and D2P: EGL

I see after hitting the o-key => Tab "Player": "Video decoder: ff-h264-drm_prime (sw)"

I guess "sw" means software ?

I need some clarification here: Why SW while HW acceleration is on (or allowed) ?

well, "allowed" means "might be on" not necessarly means "is on" ...

for me I got trouble to understand what you're trying to archive esp. how you tried to do it.

you know NFS is a client/server protocol, where a server exports directories and a client mount them.

when I read your "trying to create a share or something like that" it sounds to me you're all doing it on the client side.

- I might be wrong -

===

to your problem:

grepping after nfs throught your log gives me:

2026-05-24 14:18:55.876 T:1210    debug <general>: NFS: version: 3
2026-05-24 14:18:55.881 T:1210    debug <general>: NFS: Connected to server 192.168.178.6 and export /volume1/Backup
2026-05-24 14:18:55.881 T:1210    debug <general>: NFS: chunks: r/w 131072/131072
2026-05-24 14:19:01.563 T:985   warning <general>: FileNFS::OpenForWrite() called with overwriting enabled! - //Backup kodi/kodi.log
2026-05-24 14:19:04.591 T:985     debug <general>: CNFSFile::Close closing file volume1/Backup/Backup kodi/kodi.log
2026-05-24 14:19:25.366 T:1271    error <general>: GetDirectory - Error getting nfs://
2026-05-24 14:19:25.395 T:955     error <general>: CGUIDialogFileBrowser::GetDirectory(nfs://) failed
2026-05-24 14:19:27.332 T:1273    error <general>: GetDirectory - Error getting nfs://
2026-05-24 14:19:27.361 T:955     error <general>: CGUIDialogFileBrowser::GetDirectory(nfs://) failed

- first line: "NFS Version 3":

AFAIK and according to the LE wiki it should be version 4 (if your NFS server could talk version 4 !)

- last line:

asking google with "GetDirectory - Error geeting nfs://" told me something like "the directory your client tried to mount does NOT exist or is NOT reachable on the server"

===

my way I would investigate such an problem would be via cmdline:

- create on the NFS server the share

- ssh into your client

- create a temporary directory for an mount point with "mkdir -p /storage/NFSSHARE"

- from the client try to mount the share with something like the following command:

mount.nfs -v -o soft,intr 192.168.200.24:/home/DATA/SHARE/ /storage/NFSSHARE

ADJUST before:

- the IP Adress of the NFS server (in my example: 192.168.200.24)

- the share, what the NFS server exports (in my example: /home/DATA/SHARE/)

it doesn't hurt to reboot the NFS server or to restart the NFS service that the the server is full aware of the new share ...

- and where to mount the share (in my example: /storage/NFSSHARE)

===

one could open a 2cd ssh connection and run in that terminal "journalctl -f" what lists what the above mount command generates as messages/errors

if errors: google with the complete error string

if NO errors try to read the mounted directory with : ls -l /storage/NFSSHARE/

===

your log seems to be full of junk regarding of an non-existing directory "/Musik/YABACUBE INC/"

Quote from stefano71

Hi everyone, I need some advice on purchasing a USB-to-Ethernet adapter for the NUC mini PC where I successfully installed LibreELEC. Unfortunately, the network connector isn't working, and the ISY adapter I purchased a while ago doesn't seem to be compatible.

don't get me wrong, when I'm saying the following:

in ¨35 years of computering I never have seen that an ethernet adapter failed.

when it was the case it mostly has been cable or driver (or it was just disabled in bios (somehow)).

my sugestion therfore is:

- assuming it's an Intel NUC ! -

- check the bios setting by tickering F2-Key during boot. Hit F9 to load bios defaults, what should actived the ethnet adapter

double check that's are the correct keys (usual displayed during boot)

- afterwards also check with another ethernet cable

===

as you're talking about ISY I assume your are from germany.

If so:

Mediamarkt offers an "ISY IAD 1010-C USB" or "IAD-1010-A" and claims it is "compatible with all OS'ses" (what ever that means, but mediamarkt offers "to bring it back and get back your money")

https://www.mediamarkt.de/de/product/_isy-iad-1010-a-usb-adapter-silber-2737566.html

===

my suggestion for an todo list:

1. check bios and ethernet cable

2. try what chewitt sugested

3. try the ISY IAD from MM

okay, new install was anyway in the pipe

tried to update my nightly

during decompression it says something like:

"your fat partition is to small, it should be 1024 MB"

df -h|grep -iE 'flash|storage'
/dev/sda1 511.7M 309.9M 201.8M 61% /flash
/dev/sda2 407.7G 34.9G 372.7G 9% /storage

the nightly image increased in size: it is ~513 MB versus the elder are ~310 MB

A bug or an requirement change ???

isn't the 2cd Ram bank always active when running in dual channel mode (don't know if this the case here or if I'm right)

a memtest might run several hours.

bios update is done in ~10 minutes (plus a test run to see if it fixes the problem).

intel/asus releases bios update not just for fun !

why I'm saying this:

well read up the linked docs at the Intel microcode release page [1] for your CPU and realize that they contain serveral bugs.

some are fixed via microcode and I bet some are fixed with microcode in combination of bios updates

[1]

Releases · intel/Intel-Linux-Processor-Microcode-Data-Files

Contribute to intel/Intel-Linux-Processor-Microcode-Data-Files development by creating an account on GitHub.

github.com

Bios update ?

will/should fix serveral bugs, etc.

e.g. the last names "Platform issue fix" and I guess there had been more (alas no more viewable since the move Intel > asus)

see

NUC8i5BEK - Support

Warning: double check if this is the correct page

===

you could also turn on (naming ?) permanent logging or keep journals over reboots (somewhere in system settings; might fill your disk !)