But same network works with LE11 and CoreElec with Kodi 21 without issues. All 3 of my NUCs using LE12 crash.
I’m running a Kodi debug session now using my NUC8 LE12.
Posts by HomerJau
-
-
Update: Two different NUCs with latest LE12 both crash playing different movies after around 30 minutes or so.
I’ll create logs tomorrow and upload them.
-
chewitt Thanks for your reply. I now have solved my Intel NUC issues today with latest nightly and changing my NFS chunk size and Cache settings. I discovered the cache settings don’t seem to be applied until LibreElec is restarted.
With NFS and Cache chunk = 128kb, NFS set to v4 and cache size = 192MB I no longer get crashes when playing media or scanning my media into the music library. My NUC11pro with NVME SSD shows CPU at > 200% during the scan with debug enabled which I’ve never seen previously (my network is 2.5GBE, NUC - switch - NAS) -
Why does latest LE12 nightly (Generic) not include updates to Linux and Mesa?
I have 3 different model Intel NUCs (8, 11 pro and 12 pro) that all crash to LibreElec boot screen when playing for a few minutes, video or music, on all recent LE12 builds). If I install LE11 no problems. CoreElec on AMlogic no problems. So I presume it’s Linux, NFS or Mesa. Log shows nothing. -
These test files are courtesy of HomerJau (Assuming it is the same user on QuadrophonicQuad):
https://drive.google.com/file/d/1dWB93r…iew?usp=sharing
Yea. That’s me.Opening all the channels in that screen grab does not mean all the output channels are sending data. For the Android Kodi quad fix all the only 4 channels have data so the output is pure Quad, even though all the output channels are active (all but ‘quad’ are silent). Anyway the true test is to listen to each speaker not look at the AVR graphic.
-
I reported a bug that Kodi wouldn’t play quad (4.0) pcm files on Android. The fix was to send 5.1 (4.0 with two silent channels: L, R, s, s, Ls, Rs). That was implemented in Kodi 21 Android builds back in February and tested on Firestick 4K Max.
AudioTrack: Simplify Channel selection by fritsch · Pull Request #24554 · xbmc/xbmcAll major Android devices have issues opening more "fine grain" audio channel configurations besides Stereo, 5.1 or .7.1 - use AE's feature to silently add…github.com -
Small cache (64MB) and ‘Adaptive’, small chunk size (32kb) and NFS version 4 seems to solve my network problems with two Synology NAS (and I need to have both on, although that may have been fixed during betas).
-
After attempting a EDID fix I accidently discovered a fix:
Remove '3840x2160 24Hz' and '23.976' from whitelist and set both Kodi's 'Allow 3:2 pulldown' and 'Allow Double Refresh Rates' to ON (Enabled).
Now everything playing.
(The accidental discover after I reinstalled LE12 from scratch I found 23.976 played and 24Hz did not, I had forgotten to Whitelist 23.976).
-
I’m running ‘standard’ LE12 nightlies, I first noticed this a couple weeks ago when swapping NUCs around. I’m currently running nightly from 31 March.
It may not be a LE issue as when the NUC is switched on the Intel NUC boot splash appears to be in HDR mode. But this issue only occurs when it’s directly connected to the TV, never when it’s connected via my AVR.
-
When I connect my Intel NUC direct to my 4K Sony TV the display is always in HDR mode (HDR always on). It never switches off.
When same NUC is connected via my AVR to TV all runs as expected, HDR is only activated when I play HDR media and off when playback stopped.
How can I solve the direct connection ‘HDR always on’ issue? (I want to use ARC to my AVR)
-
LE 12 Beta1 build in all tests below, with 4k resolutions 'white' listed, latest firmware (same issues with all recent nighlies)
I have a NUC11TNKi3 which works perfectly with latest Denon AVR4800H with LG CX 4k TV.
Same NUC11TNKi3 with my Denon AVR3400H and Sony A8F 4K TV plays everything except 4K (always shows blank screen for any 4K file) and is completely unresponsive. Both AVR and TV are HDMI 2.0b
My old NUC8BEHi3 with my Denon AVR3400H and Sony A8F 4K TV plays everything including 4K perfectly.
Looking at the NUC11TNKi3 logs there is an EDID error:
2024-03-21 13:05:45.992 T:1079 debug <general>: CDRMUtils::OpenDrm - opened render node: /dev/dri/renderD128
2024-03-21 13:05:46.021 T:1079 info <general>: CDRMUtils::FindConnector - using connector: HDMI-A-1
2024-03-21 13:05:46.021 T:1079 info <general>: CDRMUtils::FindEncoder - using encoder: 307
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMUtils::FindCrtc - original crtc mode: 1920x1080 @ 60 Hz
2024-03-21 13:05:46.021 T:1079 info <general>: CDRMUtils::FindPlanes - using crtc: 98
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMUtils::FindPlanes - using video plane 31
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMUtils::FindPlanes - using 10bit gui plane 40
2024-03-21 13:05:46.021 T:1079 debug <general>: CDRMAtomic::InitDrm - initialized atomic DRM
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Error parsing EDID:
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] ----------------------------------------------
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Block 1, CTA-861 Extension Block:
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Speaker Allocation Data Block: Deprecated bit F16 must be 0.
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] Colorimetry Data Block: Reserved bits MD0-MD3 must be 0.
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info]
2024-03-21 13:05:46.021 T:1079 error <general>: [display-info] ----------------------------------------------
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] make: 'DENON, Ltd.' model: 'DENON-AVR'
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] supports hdr static metadata type1: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] supported eotf:
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] traditional sdr: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] traditional hdr: false
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] pq: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] hlg: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] luma min: '0' avg: '0' max: '0'
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] supported colorimetry:
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] xvycc_601: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] xvycc_709: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] sycc_601: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] opycc_601: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] oprgb: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] bt2020_cycc: false
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] bt2020_ycc: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] bt2020_rgb: true
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] st2113_rgb: false
2024-03-21 13:05:46.021 T:1079 info <general>: [display-info] ictcp: false
2024-03-21 13:05:46.148 T:1079 debug <general>: CWinSystemGbm::InitWindowSystem - initialized DRM
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 60.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 60.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 59.940063 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 50.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 24.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 4096x2160 @ 23.976025 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 59.940063 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 50.000000 Hz
2024-03-21 13:05:46.149 T:1079 info <general>: Found resolution 1920x1080 with 3840x2160 @ 30.000000 HzCan anyone help me to resolve this issue please?
-
Da Flex The wiki should be updated. It still has ‘config.txt’ with no reference to ‘cmdline.txt’ -
Moved to another section asfter a week of no response
-
I started all over today using another usb 3 stick and a different usb port. Installation went much smoother, although still quite slow. After a few hours of updating windows and drivers, I had to download 2 missing drivers (chipset & audio)
I used Rufus to create the bootable usb key fro a Win10 iso and didn’t need to install any drivers. It just booted to Windows and I ran the hdmi update. No need to install drivers all I wanted was to run that firmware exe.
Note the image option: ‘Windows to Go’ below
-
The HDMI Firmware update failed
I spent hours with the portable version of Windows 10 on the NUC. It was painfully slow…
Did you use a USB 3 stick and insert in one of the USB 3 ports? Mine was pretty fast and responsive.
-
Thanks heitbaum
My issue is now resolved. I ended up creating a entry in my samba.conf and can now access via Windows Explorer with path:
\\IP ADRESSS\Folder Name and can copy files as I want.
THX
-
Unzip and copy them into a folder on the Drive (e.g. C:\HDMI).
The Win system has a browser so you can download using that link. I think I whacked mine on my NAS and copied them from there.
I also have Samsung NVME SSDs so I installed the Samsung Magician s/w on the win usb to update the SSD firmware. (I'm ashamed to say I now own 4 x Intel NUC8s. So did them all. (Someone was selling used i5 BEHs on ebay for 190AUD inc 2 x 8GB RAM, 500GB SSD and new power supplies)
-
