What do you mean with "Piers" version of add-ons ?
Where can i decide it ?
K22 codename is "Piers" .. it just means add-ons updated to correct versions
What do you mean with "Piers" version of add-ons ?
Where can i decide it ?
K22 codename is "Piers" .. it just means add-ons updated to correct versions
There is no indication anywhere I can see that the tuner is recognised!
You didn't bother to look in the log then?
Oct 03 14:50:12 LibreELEC31 kernel: mei_hdcp 0000:00:0f.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops 0xffffffff9c31fcf0)
Oct 03 14:50:12 LibreELEC31 kernel: em28xx 1-5:1.0: New device HCW dualHD @ 480 Mbps (2040:0265, interface 0, class 0)
Oct 03 14:50:12 LibreELEC31 kernel: em28xx 1-5:1.0: DVB interface 0 found: isoc
Oct 03 14:50:12 LibreELEC31 kernel: em28xx 1-5:1.0: chip ID is em28174
Oct 03 14:50:13 LibreELEC31 kernel: em28xx 1-5:1.0: EEPROM ID = 26 00 01 00, EEPROM hash = 0xd0e2c6c8
Oct 03 14:50:13 LibreELEC31 kernel: em28xx 1-5:1.0: EEPROM info:
Oct 03 14:50:13 LibreELEC31 kernel: em28xx 1-5:1.0: microcode start address = 0x0004, boot configuration = 0x01
Oct 03 14:50:13 LibreELEC31 kernel: em28xx 1-5:1.0: AC97 audio (5 sample rates)
Oct 03 14:50:13 LibreELEC31 kernel: em28xx 1-5:1.0: 500mA max power
Oct 03 14:50:13 LibreELEC31 kernel: em28xx 1-5:1.0: Table at offset 0x27, strings=0x0e6a, 0x1888, 0x087e
Oct 03 14:50:14 LibreELEC31 kernel: em28xx 1-5:1.0: Identified as Hauppauge WinTV-dualHD DVB (card=99)
Oct 03 14:50:14 LibreELEC31 kernel: tveeprom: Hauppauge model 204109, rev C2I6, serial# 14049275
Oct 03 14:50:14 LibreELEC31 kernel: tveeprom: tuner model is SiLabs Si2157 (idx 186, type 4)
Oct 03 14:50:14 LibreELEC31 kernel: tveeprom: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
Oct 03 14:50:14 LibreELEC31 kernel: tveeprom: audio processor is None (idx 0)
Oct 03 14:50:14 LibreELEC31 kernel: tveeprom: has no radio, has IR receiver, has no IR transmitter
Oct 03 14:50:14 LibreELEC31 kernel: em28xx 1-5:1.0: We currently don't support analog TV or stream capture on dual tuners.
Oct 03 14:50:14 LibreELEC31 kernel: em28xx 1-5:1.0: dvb set to isoc mode.
Oct 03 14:50:14 LibreELEC31 kernel: em28xx 1-5:1.0: chip ID is em28174
Oct 03 14:50:15 LibreELEC31 kernel: usbcore: registered new interface driver em28xx
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: Binding DVB extension
Oct 03 14:50:15 LibreELEC31 kernel: i2c i2c-6: Added multiplexed i2c bus 9
Oct 03 14:50:15 LibreELEC31 kernel: si2168 6-0064: Silicon Labs Si2168-B40 successfully identified
Oct 03 14:50:15 LibreELEC31 kernel: si2168 6-0064: firmware version: B 4.0.2
Oct 03 14:50:15 LibreELEC31 kernel: si2157 9-0060: Silicon Labs Si2157 successfully attached
Oct 03 14:50:15 LibreELEC31 kernel: dvbdev: DVB: registering new adapter (1-5:1.0)
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
Oct 03 14:50:15 LibreELEC31 kernel: dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
Oct 03 14:50:15 LibreELEC31 kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: DVB extension successfully initialized
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: Binding DVB extension
Oct 03 14:50:15 LibreELEC31 kernel: i2c i2c-8: Added multiplexed i2c bus 10
Oct 03 14:50:15 LibreELEC31 kernel: si2168 8-0067: Silicon Labs Si2168-B40 successfully identified
Oct 03 14:50:15 LibreELEC31 kernel: si2168 8-0067: firmware version: B 4.0.2
Oct 03 14:50:15 LibreELEC31 kernel: si2157 10-0063: Silicon Labs Si2157 successfully attached
Oct 03 14:50:15 LibreELEC31 kernel: dvbdev: DVB: registering new adapter (1-5:1.0)
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)...
Oct 03 14:50:15 LibreELEC31 kernel: dvbdev: dvb_create_media_entity: media entity 'Silicon Labs Si2168' registered.
Oct 03 14:50:15 LibreELEC31 kernel: dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: DVB extension successfully initialized
Oct 03 14:50:15 LibreELEC31 kernel: em28xx: Registered (Em28xx dvb Extension) extension
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: Registering input extension
Oct 03 14:50:15 LibreELEC31 kernel: Registered IR keymap rc-hauppauge
Oct 03 14:50:15 LibreELEC31 kernel: rc rc0: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/rc/rc0
Oct 03 14:50:15 LibreELEC31 kernel: rc rc0: lirc_dev: driver em28xx registered at minor = 0, scancode receiver, no transmitter
Oct 03 14:50:15 LibreELEC31 kernel: input: Hauppauge WinTV-dualHD DVB as /devices/pci0000:00/0000:00:15.0/usb1/1-5/1-5:1.0/rc/rc0/input18
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: Input extension successfully initialized
Oct 03 14:50:15 LibreELEC31 kernel: em28xx 1-5:1.0: Remote control support is not available for this card.
Oct 03 14:50:15 LibreELEC31 kernel: em28xx: Registered (Em28xx Input Extension) extension
Oct 03 14:50:18 LibreELEC31 kernel: si2168 8-0067: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
Oct 03 14:50:18 LibreELEC31 kernel: si2168 8-0067: firmware version: B 4.0.25
Oct 03 14:50:18 LibreELEC31 kernel: si2157 10-0063: found a 'Silicon Labs Si2157-A30 ROM 0x50'
Oct 03 14:50:18 LibreELEC31 kernel: si2157 10-0063: downloading firmware from file 'dvb_driver_si2157_rom50.fw'
Oct 03 14:50:19 LibreELEC31 kernel: si2157 10-0063: firmware version: 3.0.5
Oct 03 14:50:19 LibreELEC31 kernel: si2168 6-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
Oct 03 14:50:19 LibreELEC31 kernel: si2168 6-0064: firmware version: B 4.0.25
Oct 03 14:50:19 LibreELEC31 kernel: si2157 9-0060: found a 'Silicon Labs Si2157-A30 ROM 0x50'
Oct 03 14:50:19 LibreELEC31 kernel: si2157 9-0060: downloading firmware from file 'dvb_driver_si2157_rom50.fw'
Oct 03 14:50:20 LibreELEC31 kernel: si2157 9-0060: firmware version: 3.0.5
Display More
Looks detected to me ![]()
I know that I can manually go to 12.2, but I want to see normal update working.
LE will auto-update within the same release, e.g. 12.0.0 > 12.0.1 > 12.0.2 but not 12.0.x to 12.2.x as 12.2 contains breaking changes for some hardware: not RPi boards, but there's a single rule that applies to all to avoid confusion.
TL/DR: all is working correctly, do a manual update.
Run "journalctl | paste" after booting to pastebin the system log, then share the URL generated.
For kicks, update to the latest LE12.2 nightly. It probably doesn't fix anything, but you never know.
On the assumption it doesn't: enable debug logging in Kodi, then reboot to get a clean log, then demonstrate the problem, then SSH in and run "pastekodi" to pastebin logs and generate a URL you can share here. The logfiles dir will not show anything; it is 'special' and auto-generates a set of logs when (and only when) accesed over SMB. However that results in you creating and uploading a zip archive to the forum that everyone on staff avoids investigating because we have to download, unzip, and open files. It sounds petty, but repeat it 10,000 times and the novelty wears off vs. just clicking a URL link.
The realtek device probes first and iwd sees this as phy0 and the internal Broadcom chip as phy1
Then I see Jun 26 09:44:20 KODI-Kitchen iwd[382]: NEW_INTERFACE failed: Too many open files in system
After this point I only see ConnMan mentioning wlan0 which has the MAC address of the Broadcom chip. The "Too many open files in system" failure is unusual and normally indicates an internal bug that results in a process leaking file handles; then at some point the OS hits the 'ulimit' value (in LE, this is 1024).
The first thing I would do is bump up to an LE13 nightly which has newer everything to see if that magically fixes some underlying issue in drivers or iwd or connman. If that doesn't fix it, then this should raise the 'open files' ulimit:
Then reboot and see if that changes anything? (if no, share a log again).
Has support for this adapter (RTL8192EU) been removed?
The original RTL8192EU vendor driver was dropped in LE11, but in doing that we switched over to the in-kernel RTL8XXXU driver and that remains enabled in the kernel config so LE12 'should' be the same as LE12.2 (other then the kernel being newer).
With the onboard WiFi enabled (so you can access) connect the USB WiFi stick and reboot to get a clean boot log, then SSH in and run "journalctl | paste" and share the URL here so we can see if anything interesting is logged (or not).
Is there something else I should be doing?
Sharing a log file?
NB: These days we are not too enthusiastic about adding patches that we can't drop in the future with a kernel bump, so if there are things in Issues/Forum threads that work (meaning, they need to be tested and confirmed first) someone needs to submit them to the linux-media mailing list. As long as there are signs that patch(es) will be merged upstream we will be happy to pick/backport the changes until some future kernel bump drops them. Firmware is more easily handled as we mostly have our own collection(s) and can add things to our own repo.
Also note that I'm unable to test any form of DVB hardware (as no DVB-T/DVB-S feeds) so I depend on being told what's needed.
As the issue is reported on multiple OS and different versions of Kodi, it's not a LibreELEC specific problem. You should continue to support the Netflix add-on (and inputstream.adaptive) devs as that's likely where either the issue or the solution lies.
Updating to the latest nightly image will remove the "systemd-userdb-load-credentials" error message.
Please what could result in the failed message, does it have anything to do with my box or its LE issue?
It is harmless (nothing to do with your issue) and fixed with this: https://github.com/LibreELEC/LibreELEC.tv/pull/10506
Kodi uses a 'compromise' but safe default for software deinterlacing. It's possible (with patching) to make it use other deinterlace algorithms that ffmpeg supports, but older ARM SoC boards like S905 don't have CPU grunt for the fancier ones that give better results. The S905 hardware has a dedicated deinterlace function, but software support for that only exists in the Amlogic vendor codebase that Kodi and LE moved away from. Older LE/CE images are more feature complete.
DRMPRIME is a zero-copy rendering path (nothing to do with Amazon); meaning we read the video stream and then all processing stages through Kodi, FFMpeg, and kernel drivers; exchange a pointer to the original data in memory instead of reading it from RAM, changing it in some way, then writing back to RAM again. It's more efficient, but it's use requires the kernel hardware decode drivers which are not perfect. The only alternative is to disable hardware decode and use ffmpeg software decode. Playback start and seek on HEVC media then works great, but unless the video bitrate is extremely low you won't have enough CPU grunt to handle 1080p media. If you only need to play SD or 720p media (or have faster hardware like S922X/A311D) it's an option though.
Nobody is working on the hardware decoders for several years now, so I have no expectations of improvements coming. For some users AMLGX works good-enough. For others not-good-enough. I am not a driver developer so I'm merely keeping the status-quo until either someone appears to do work, or the hardware dies out. S905 is now a decade old so the later is more likely.
udev rules; you'll need to place a modified version of the default mount rules in /storage/.config/udev.rules.d that detects your drive and then applies different config to it, and reboot for it to be overlaid (and thus overwrite) the default file.
The upstream hardware decoders aren't perfect but much depends on the source media. Some users have collections that will fail miserably. Others will find it's surprisingly usable. You'll need to experiment with a spare SD card or eMMC module.