Posts by ghtester

Quote from emveepee

Thanks for taking time to provide feedback ghtester. The scan tables that I download with the nextpvr service https://github.com/LibreELEC/Libr…ce/addon.py#L34 should be be the same ones that TVHeadend uses. I did suggest to CvH that they should be placed in a common location as opposed to being part of each PVR but that is not available yet.

For the "code page" issue is the data correct in either Kodi(pvr.nextpvr) or the web browser? I am trying to determine where the issue might be. For the OTA guide the character set is in the EIT data and there might be an issue with the utf conversion if both are incorrect.

You absolutely should not be using the web player if it is hosted by the RPi for broadcast TV it is not powerful enough for the on-fly-transcoding. It may not crash the server but the transcoding can no doubt max out the system. There is also about a 15 second lag in web playback before a tuner can be used. Personally, I don't think the web player provides a good PVR experience anyway but I also like using a remote. Some people are mouse/desktop users and use IPTV that doesn't need transcoding or have an x64 device with h/w transcoding and appreciate it.

If you experience issues with playback in pvr.nextpvr when you don't touch the web server I would be interested in seeing the NextPVR logs especially if Kodi is crashing on the raw mpeg ts streams.

The logs level is in config.xml the default is <LogLevel>DEBUG</LogLevel> which is probably correct during the initial testing but you can change it to ERROR at some point. The entire data area, logs, database, channel icon, art etc can also be stored on better storage if you want by editing this line in the service startup https://github.com/LibreELEC/Libr…xtpvr.start#L14

OTA EPG updates are designed to be scheduled daily in off hours when you aren't watching or recording. That could be an advantage for TVHeadend if it never interferes with the broadcasts.

Thanks again for helping out.

Display More

Thanks for your reply, it's great to see a developer's interest to improve his product.

As there are still some minor DVB-T providers here, the cz-All scan table should contain two sections for every frequency, like this (tested and working for both DVB-T and DVB-T2 providers):

[CHANNEL]

DELIVERY_SYSTEM = DVBT

FREQUENCY = 474000000

BANDWIDTH_HZ = 8000000

CODE_RATE_HP = 2/3

CODE_RATE_LP = NONE

MODULATION = QAM/64

TRANSMISSION_MODE = 8K

GUARD_INTERVAL = 1/8

HIERARCHY = NONE

INVERSION = AUTO

[CHANNEL]

DELIVERY_SYSTEM = DVBT2

FREQUENCY = 474000000

BANDWIDTH_HZ = 8000000

CODE_RATE_HP = AUTO

CODE_RATE_LP = AUTO

MODULATION = QAM/AUTO

TRANSMISSION_MODE = AUTO

GUARD_INTERVAL = AUTO

HIERARCHY = AUTO

The EPG text has a bad coding in both Kodi & web browser, it's the same and I believe the reason is the ISO-6937 coding is used here (AFAIK) for EPG ( https://en.wikipedia.org/wiki/T.51/ISO/IEC_6937 ) . So instead of local character with diacritics I see two characters - first is a sign of diacritic and second one is an ASCII character.

I don't use web player, just tested quickly and the primary reason for opening the web interface was a configuration of some NPVR parameters which are not available in Kodi NPVR add-ons settings. Currently I don't need transcoding, I am watching the Live-TV from RPi but a "must have" feature for me is timeshift (to RAM). So I was looking where I need to enable it and surprisingly it's only under Streeaming options - Live TV method - Transcoded submenu in NPVR client add-on. It looks it have to be enabled there and then it's necessary to switch the Live TV method to Timeshift from Transcoded. It's a bit confusing. Now I have the Streaming options - Live TV method in NPVR client set to Timeshift and switching channels works. When playing with this settings, not just NPVR client but even Kodi restarted sometimes. You can look at some recent logs here: http://mysharegadget.com/809460486

I have experienced the playing was stopped suddenly, maybe it could be visible in the log but I don't remember the time.

There are issues with timeshift but I am sure Kodi is buggy in this part of functionality - I saw the .ts files created by NPVR in /tmp/ramdisk folder, i could copy them to permanent folder and play using VLC remotely but in Kodi I suddenly could not "rewind" to starting point. I never had such strange and random troubles with timeshift on Windows with several DVB-T applications like on LE/Kodi. This works really bad here and at least Kodi and Tvheadend should be significantly improved in this part, but I see the lowest priority of LiveTV...

Thanks for sharing details regarding to logs / data area settings, it's helpful.

In fact I don't know how exactly TVH works with EPG (as previously mentioned, it's buggy and I am sometimes experiencing corrupted items), I think without Internet connection it can't grab EPG despite it should get it OTA. But it works somehow and soon or later I see EPG on all channels.

With NPVR, so far I don't see EPG on many channels despite the Automatic EPG update was initiated. Maybe I should try to increase the Seconds per freq: parameter. To be tested...

I still see the streaming interruption (when the Automatic EPG update occurs) as an issue, I understand the reason but there should be any alternative...

Thanks for your work, I believe NPVR has a potential to be very useful for many users.

Quote from emveepee

I would be interested in you expanding on your comments about NextPVR specifically as it relates to functionality of pvr.nextpvr vs pvr.hts and stability of the server (missed recordings and server failures). I believe these are things that can be addressed. Ignore the web server playback since that is not expected to be useful on anything other than IPTV with any Arm devices.

Since NextPVR only records raw mpeg ts streams, does that change anything regarding pvr.nextpvr playback. While Linux support is relatively new and LE support even newer, pvr.nextpvr has been playing these same raw streams from Windows servers for years and we don't often get comments that timeshift is unstable. You may just have poor quality streams, which can easily be tested by creating recordings.

At first I had to edit the cz-All scan table to add DVBT2 items otherwise only DVB-T channels were found (in our country the move to DVB-T2 occured a couple years ago). Luckily it was easy to find the appropriate table but I had to edit it manually.

Another issue is with EPG code page which does not reflect national characters and so far I did not find a settings where it could be configured.

When I played with the timeshift settings, several times the add-on stopped working, sometimes even Kodi restarted.

The worst issue I am now facing to is that after switching the Live TV channel the error Playback failed is returned in Kodi and Streaming Failed (transcoder exited) when I try to play a channel with web player. Then the nextpvr service needs to be restarted. Sometimes the similar issue happen with a report from web player there's no free tuner (despite it is). Maybe the change of timeshift path to ramdisk could be an issue, I need more time for testing. Nevertheless, it looks the nextpvr service is writing to filesystem (logs?) quite often which is a thing you don't want when booting LE from micro SD card (and so far I did not find a settings to prevent that).

Another issue is with EPG update (there's a timestamp setting for this) which interrupts the ongoiing LiveTV streaming.

From my experience on RPi 4b / LE 9 -12:

- Tvheadend is a great product but with some serious bugs which there are for years (timeshift unstable and buggy, EPG corruption, issues with subtitles on version 4.3 ).

- NPVR I am now testing on RPi 4b / LE 12 and unfortunately I have to say it's much worse regarding to functionality/configurability and stability

Just to confirm this annoying bug is still present in LE 12 Nightly ( nightly-20230527-557e821 (RPi4.aarch64) ).

Also sometimes the audio stream (usually AAC) is not detected at all after switching Live TV channels, even though the signal quality is great.

After upgrade from LE11 to LE12 nightly-20230522-794a8ad (RPi4.aarch64) Raspberry Pi Tools (Team LibreELEC - 11.0.0.0) is not working properly anymore and it looks there's no updated version yet.

python /storage/downloads/shutdown.py &

LE:~ # Traceback (most recent call last):

File "/storage/downloads/shutdown.py", line 10, in <module>

import RPi.GPIO as GPIO

File "/storage/.kodi/addons/virtual.rpi-tools/lib/RPi/GPIO/__init__.py", line 23, in <module>

from RPi._GPIO import *

ImportError: /storage/.kodi/addons/virtual.rpi-tools/lib/RPi/_GPIO.so: wrong ELF class: ELFCLASS32

[1]+ Done(1) python /storage/downloads/shutdown.py

OK, I understand, thanks.

For those who fell into the same issue, this should be enough to revert to LE 10.0.4 (as the time interval from reboot to crash is long enough):

cd /storage/.update
wget -c https://releases.libreelec.tv/LibreELEC-Generic.x86_64-10.0.4.img.gz
touch /storage/.update/.nocompat

Thanks for a quick reply. Is there any workaround known yet (except moving back to LE 10.0.4) please?

http://ix.io/4sAk

When a SD cards turns out to read-only, usually it means it's gone. Please note the write cycles are limited on such media so even a high quality SD cards can't be expected to live forever if there are daily writes from running OS (and LE can generate writes very quickly in some occassions if you don't tune up the logging options).

The better solution is to avoid using SD cards and switch to HDD connected through USB/SATA adapter instead.

The same issue with:

nightly-20230225-ef1ce97 (RPi4.arm)

Linux LE 6.1.12 #1 SMP Sun Feb 26 01:05:07 UTC 2023 aarch64 GNU/Linux

[ 2336.473419] rpivid feb10000.codec: PPS changed

[ 2336.507158] rpivid feb10000.codec: PPS changed

[ 2336.557833] rpivid feb10000.codec: PPS changed

[ 2336.589999] rpivid feb10000.codec: PPS changed

[ 2336.623415] rpivid feb10000.codec: PPS changed

[ 2336.657970] rpivid feb10000.codec: PPS changed

[ 2336.692130] rpivid feb10000.codec: PPS changed

[ 2336.715026] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2336.756830] rpivid feb10000.codec: PPS changed

[ 2336.790121] rpivid feb10000.codec: PPS changed

[ 2336.823444] rpivid feb10000.codec: PPS changed

[ 2336.857484] rpivid feb10000.codec: PPS changed

[ 2336.891210] rpivid feb10000.codec: PPS changed

[ 2336.959178] rpivid feb10000.codec: PPS changed

[ 2336.972596] rpivid feb10000.codec: PPS changed

[ 2336.988454] rpivid feb10000.codec: PPS changed

[ 2338.848351] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2340.981671] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2340.981697] usb 1-1.2.3: dvb_usb_v2: streaming_ctrl() failed=-110

[ 2340.987204] rpivid feb10000.codec: rpivid_h265_stop

[ 2343.115065] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2345.248423] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2347.381740] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2349.515097] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2351.648426] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2353.781799] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2355.915119] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2358.048480] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2360.181873] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2362.315142] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2364.448501] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2366.581837] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2368.715190] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[ 2370.848522] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-110

Even worse behaviour with latest LE 11 nightly-20230209-07249c1:

3107.877784] rpivid feb10000.codec: PPS changed

[ 3107.911497] rpivid feb10000.codec: PPS changed

[ 3107.960575] rpivid feb10000.codec: PPS changed

[ 3108.069702] rpivid feb10000.codec: rpivid_h265_stop

[ 3109.160469] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-71

[ 3109.175288] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[ 3109.251825] usb 1-1.3: device descriptor read/64, error -71

[ 3109.312652] usb 1-1.2: USB disconnect, device number 3

[ 3109.312673] usb 1-1.2.3: USB disconnect, device number 6

[ 3109.431854] usb 1-1.3: device descriptor read/64, error -71

[ 3109.568395] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3109.611913] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[ 3109.688619] usb 1-1.3: device descriptor read/64, error -71

[ 3109.771821] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3109.771851] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3109.868648] usb 1-1.3: device descriptor read/64, error -71

[ 3110.048723] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[ 3110.048895] usb 1-1.3: Device not responding to setup address.

[ 3110.255426] usb 1-1.3: Device not responding to setup address.

[ 3110.462000] usb 1-1.3: device not accepting address 4, error -71

[ 3110.535353] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[ 3110.535552] usb 1-1.3: Device not responding to setup address.

[ 3110.568795] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3110.742249] usb 1-1.3: Device not responding to setup address.

[ 3110.948823] usb 1-1.3: device not accepting address 4, error -71

[ 3110.967458] rpivid feb10000.codec: rpivid_h265_start: (1024x544)

[ 3110.971998] rpivid feb10000.codec: SPS changed

[ 3110.972015] rpivid feb10000.codec: PPS changed

[ 3110.972038] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0

[ 3111.055547] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3111.055577] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3111.055585] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3111.959200] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3112.866194] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3112.979070] usb 1-1.4: stat urb: status -71

[ 3112.979123] usb 1-1.4: cmd cmplt err -71

[ 3112.979535] usb 1-1.4: stat urb: status -71

[ 3112.979748] usb 1-1.4: cmd cmplt err -71

[ 3112.980013] usb 1-1.4: stat urb: status -71

[ 3112.980106] usb 1-1.4: cmd cmplt err -71

[ 3113.773124] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3114.467316] usb 1-1.4: stat urb: status -71

[ 3114.467352] usb 1-1.4: cmd cmplt err -71

[ 3114.680135] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3115.587072] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3116.494044] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3117.401011] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3118.307973] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3119.214944] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3120.121919] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3121.028869] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3121.935835] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3122.842797] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3123.749760] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3124.656715] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3125.567006] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3126.470628] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3127.377580] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3128.284541] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3129.191498] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3130.098456] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3131.005411] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3131.912361] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3132.819306] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3133.726259] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3134.633218] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3135.540162] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3136.447109] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3137.354052] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3138.261001] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3139.171278] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3140.074884] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3140.981839] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3141.888771] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3142.795716] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3143.305878] sd 0:0:0:0: [sda] tag#23 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD

[ 3143.305900] sd 0:0:0:0: [sda] tag#23 CDB: opcode=0x2a 2a 00 03 08 13 80 00 00 08 00

[ 3143.305912] sd 0:0:0:0: [sda] tag#21 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD

[ 3143.305918] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 02 37 eb 00 00 00 10 00

[ 3143.305928] sd 0:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD

[ 3143.305933] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 03 02 0f 50 00 00 08 00

[ 3143.702656] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3144.532893] sd 0:0:0:0: [sda] tag#8 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD

[ 3144.532914] sd 0:0:0:0: [sda] tag#8 CDB: opcode=0x2a 2a 00 02 b8 31 60 00 00 70 00

[ 3144.549566] scsi host0: uas_eh_device_reset_handler start

[ 3144.609591] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3144.623310] usb 1-1.4: reset high-speed USB device number 5 using xhci_hcd

[ 3144.699782] usb 1-1.4: device descriptor read/64, error -71

[ 3144.879826] usb 1-1.4: device descriptor read/64, error -71

[ 3145.059886] usb 1-1.4: reset high-speed USB device number 5 using xhci_hcd

[ 3145.133242] usb 1-1.4: device descriptor read/64, error -71

[ 3145.313291] usb 1-1.4: device descriptor read/64, error -71

[ 3145.500030] usb 1-1.4: reset high-speed USB device number 5 using xhci_hcd

[ 3145.500200] usb 1-1.4: Device not responding to setup address.

[ 3145.516526] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3145.706728] usb 1-1.4: Device not responding to setup address.

[ 3145.913300] usb 1-1.4: device not accepting address 5, error -71

[ 3145.986657] usb 1-1.4: reset high-speed USB device number 5 using xhci_hcd

[ 3145.986951] usb 1-1.4: Device not responding to setup address.

[ 3146.193540] usb 1-1.4: Device not responding to setup address.

[ 3146.400134] usb 1-1.4: device not accepting address 5, error -71

[ 3146.400413] scsi host0: uas_eh_device_reset_handler FAILED err -19

[ 3146.400426] sd 0:0:0:0: Device offlined - not ready after error recovery

[ 3146.400433] sd 0:0:0:0: Device offlined - not ready after error recovery

[ 3146.400439] sd 0:0:0:0: Device offlined - not ready after error recovery

[ 3146.400444] sd 0:0:0:0: Device offlined - not ready after error recovery

[ 3146.400471] sd 0:0:0:0: [sda] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=31s

[ 3146.400480] sd 0:0:0:0: [sda] tag#8 CDB: opcode=0x2a 2a 00 02 b8 31 60 00 00 70 00

[ 3146.400486] I/O error, dev sda, sector 45625696 op 0x1:(WRITE) flags 0x800 phys_seg 14 prio class 2

[ 3146.400534] sd 0:0:0:0: [sda] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=33s

[ 3146.400540] Aborting journal on device sda9-8.

[ 3146.400542] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 03 02 0f 50 00 00 08 00

[ 3146.400547] I/O error, dev sda, sector 50466640 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2

[ 3146.400555] EXT4-fs warning (device sda9): ext4_end_bio:343: I/O error 10 writing to inode 390927 starting block 6308330)

[ 3146.400556] EXT4-fs error (device sda9): ext4_journal_check_start:83: comm VideoPlayer: Detected aborted journal

[ 3146.400580] sd 0:0:0:0: [sda] tag#21 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=33s

[ 3146.400582] sd 0:0:0:0: rejecting I/O to offline device

[ 3146.400589] sd 0:0:0:0: [sda] tag#21 CDB: opcode=0x2a 2a 00 02 37 eb 00 00 00 10 00

[ 3146.400590] I/O error, dev sda, sector 45596672 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2

[ 3146.400592] EXT4-fs error (device sda9) in ext4_reserve_inode_write:5836: Journal has aborted

[ 3146.400595] I/O error, dev sda, sector 37219072 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 2

[ 3146.400600] I/O error, dev sda, sector 45596672 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2

[ 3146.400603] EXT4-fs warning (device sda9): ext4_end_bio:343: I/O error 10 writing to inode 390979 starting block 4652384)

[ 3146.400605] EXT4-fs error (device sda9): ext4_dirty_inode:6040: inode #390927: comm tvh:log: mark_inode_dirty error

[ 3146.400607] Buffer I/O error on dev sda9, logical block 1081344, lost sync page write

[ 3146.400613] Buffer I/O error on device sda9, logical block 34144

[ 3146.400617] EXT4-fs error (device sda9) in ext4_dirty_inode:6041: Journal has aborted

[ 3146.400622] JBD2: I/O error when updating journal superblock for sda9-8.

[ 3146.400628] EXT4-fs warning (device sda9): ext4_end_bio:343: I/O error 10 writing to inode 390979 starting block 4652385)

[ 3146.400634] EXT4-fs error (device sda9): ext4_journal_check_start:83: comm tvh:log: Detected aborted journal

[ 3146.400643] sd 0:0:0:0: [sda] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=33s

[ 3146.400650] sd 0:0:0:0: [sda] tag#23 CDB: opcode=0x2a 2a 00 03 08 13 80 00 00 08 00

[ 3146.400655] I/O error, dev sda, sector 50860928 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2

[ 3146.400662] EXT4-fs warning (device sda9): ext4_end_bio:343: I/O error 10 writing to inode 390927 starting block 6357616)

[ 3146.400666] I/O error, dev sda, sector 36945920 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2

[ 3146.400670] Buffer I/O error on device sda9, logical block 1739376

[ 3146.400676] I/O error, dev sda, sector 36945920 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2

[ 3146.400681] Buffer I/O error on dev sda9, logical block 0, lost sync page write

[ 3146.400694] EXT4-fs (sda9): I/O error while writing superblock

[ 3146.400700] EXT4-fs (sda9): Remounting filesystem read-only

[ 3146.400702] EXT4-fs error (device sda9): ext4_journal_check_start:83: comm kworker/u8:3: Detected aborted journal

[ 3146.400730] I/O error, dev sda, sector 36945920 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2

[ 3146.400738] I/O error, dev sda, sector 36945920 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 2

[ 3146.400743] Buffer I/O error on dev sda9, logical block 0, lost sync page write

[ 3146.400757] EXT4-fs (sda9): I/O error while writing superblock

[ 3146.400765] EXT4-fs (sda9): failed to convert unwritten extents to written extents -- potential data loss! (inode 390927, error -30)

[ 3146.400813] Buffer I/O error on device sda9, logical block 1690090

[ 3146.400826] EXT4-fs (sda9): failed to convert unwritten extents to written extents -- potential data loss! (inode 390979, error -30)

[ 3146.400859] Buffer I/O error on device sda9, logical block 34145

[ 3146.400916] Buffer I/O error on dev sda9, logical block 0, lost sync page write

[ 3146.400933] EXT4-fs (sda9): previous I/O error to superblock detected

[ 3146.400950] Buffer I/O error on dev sda9, logical block 0, lost sync page write

[ 3146.400961] EXT4-fs (sda9): I/O error while writing superblock

[ 3146.401644] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3146.401667] usb 1-1.2.3: dvb_usb_v2: streaming_ctrl() failed=-19

[ 3146.405222] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3146.405244] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3146.405253] usb 1-1.2.3: dvb_usb_v2: usb_bulk_msg() failed=-19

[ 3146.405818] dvb_usb_v2: 'MyGica Mini DVB-(T/T2/C) USB Stick T230C:1-1.2.3' successfully deinitialized and disconnected

[ 3146.412256] usb 1-1.2.4: USB disconnect, device number 7

[ 3146.680976] rpivid feb10000.codec: rpivid_h265_stop

[ 3146.696910] usb 1-1.2: new high-speed USB device number 8 using xhci_hcd

[ 3146.770482] usb 1-1.2: device descriptor read/64, error -71

[ 3146.960522] usb 1-1.2: device descriptor read/64, error -71

[ 3147.140366] usb 1-1.2: new high-speed USB device number 9 using xhci_hcd

[ 3147.217298] usb 1-1.2: device descriptor read/64, error -71

[ 3147.400704] usb 1-1.2: device descriptor read/64, error -71

[ 3147.510856] usb 1-1-port2: attempt power cycle

[ 3148.103984] usb 1-1.2: new high-speed USB device number 10 using xhci_hcd

[ 3148.104286] usb 1-1.2: Device not responding to setup address.

[ 3148.311005] usb 1-1.2: Device not responding to setup address.

[ 3148.517413] usb 1-1.2: device not accepting address 10, error -71

[ 3148.597433] usb 1-1.2: new high-speed USB device number 11 using xhci_hcd

[ 3148.597680] usb 1-1.2: Device not responding to setup address.

[ 3148.807815] usb 1-1.2: Device not responding to setup address.

[ 3149.017558] usb 1-1.2: device not accepting address 11, error -71

[ 3149.017939] usb 1-1-port2: unable to enumerate USB device

[ 3149.018911] usb 1-1.3: USB disconnect, device number 4

[ 3149.100943] usb 1-1.3: new high-speed USB device number 12 using xhci_hcd

[ 3149.177859] usb 1-1.3: device descriptor read/64, error -71

[ 3149.364601] usb 1-1.3: device descriptor read/64, error -71

[ 3149.544395] usb 1-1.3: new high-speed USB device number 13 using xhci_hcd

[ 3149.617994] usb 1-1.3: device descriptor read/64, error -71

[ 3149.801385] usb 1-1.3: device descriptor read/64, error -71

[ 3149.908369] usb 1-1-port3: attempt power cycle

[ 3150.501360] usb 1-1.3: new high-speed USB device number 14 using xhci_hcd

[ 3150.501651] usb 1-1.3: Device not responding to setup address.

[ 3150.708313] usb 1-1.3: Device not responding to setup address.

[ 3150.914805] usb 1-1.3: device not accepting address 14, error -71

[ 3150.991487] usb 1-1.3: new high-speed USB device number 15 using xhci_hcd

[ 3150.991774] usb 1-1.3: Device not responding to setup address.

[ 3151.198506] usb 1-1.3: Device not responding to setup address.

[ 3151.404946] usb 1-1.3: device not accepting address 15, error -71

[ 3151.405438] usb 1-1-port3: unable to enumerate USB device

[ 3151.406387] usb 1-1.4: USB disconnect, device number 5

[ 3151.407776] blk_print_req_error: 4 callbacks suppressed

[ 3151.407788] device offline error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2

[ 3151.520147] device offline error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2

[ 3151.520539] EXT4-fs (sda7): unmounting filesystem.

[ 3151.521018] device offline error, dev sda, sector 5578752 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2

[ 3151.521046] device offline error, dev sda, sector 5578752 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2

[ 3151.521053] Buffer I/O error on dev sda7, logical block 0, lost sync page write

[ 3151.521077] EXT4-fs (sda7): I/O error while writing superblock

[ 3151.630837] device offline error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2

[ 3151.634135] device offline error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2

[ 3151.635963] FAT-fs (sda11): Directory bread(block 513) failed

[ 3151.635996] FAT-fs (sda11): Directory bread(block 514) failed

[ 3151.636005] FAT-fs (sda11): Directory bread(block 515) failed

[ 3151.636015] FAT-fs (sda11): Directory bread(block 516) failed

[ 3151.636023] FAT-fs (sda11): Directory bread(block 517) failed

[ 3151.636032] FAT-fs (sda11): Directory bread(block 518) failed

[ 3151.636041] FAT-fs (sda11): Directory bread(block 519) failed

[ 3151.636057] FAT-fs (sda11): Directory bread(block 520) failed

[ 3151.636066] FAT-fs (sda11): Directory bread(block 521) failed

[ 3151.636074] FAT-fs (sda11): Directory bread(block 522) failed

[ 3151.636215] EXT4-fs error (device sda12): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.636283] EXT4-fs error (device sda10): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.636364] EXT4-fs error (device sda12): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.636389] EXT4-fs error (device sda10): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.639600] systemd-journald[308]: Data hash table of /run/log/journal/877ce4b44928576324bb64375caf6b34/system.journal has a fill level at 75.1 (1537 of 2047 items, 524288 file size, 341 bytes per hash table item), suggesting rotation.

[ 3151.639623] systemd-journald[308]: /run/log/journal/877ce4b44928576324bb64375caf6b34/system.journal: Journal header limits reached or header out-of-date, rotating.

[ 3151.665295] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #130305: comm samba-autoshare: reading directory lblock 0

[ 3151.675095] sd 0:0:0:0: [sda] Synchronizing SCSI cache

[ 3151.767498] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3151.801679] Buffer I/O error on dev sda10, logical block 139265, lost sync page write

[ 3151.801793] JBD2: I/O error when updating journal superblock for sda10-8.

[ 3151.801802] Aborting journal on device sda10-8.

[ 3151.805634] Buffer I/O error on dev sda10, logical block 139265, lost sync page write

[ 3151.805715] JBD2: I/O error when updating journal superblock for sda10-8.

[ 3151.805770] EXT4-fs error (device sda12): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.807002] EXT4-fs (sda10): unmounting filesystem.

[ 3151.811904] EXT4-fs error (device sda12): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.813877] EXT4-fs error (device sda12): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.818735] EXT4-fs error (device sda12): __ext4_find_entry:1663: inode #2: comm udevil: reading directory lblock 0

[ 3151.831817] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK

[ 3151.850771] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #130305: comm samba-autoshare: reading directory lblock 0

[ 3151.868088] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #130305: comm samba-autoshare: reading directory lblock 0

[ 3151.868167] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #130305: comm samba-autoshare: reading directory lblock 0

[ 3151.905122] usb 1-1.4: new high-speed USB device number 16 using xhci_hcd

[ 3151.915207] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #130321: comm crond: reading directory lblock 0

[ 3151.985345] usb 1-1.4: device descriptor read/64, error -71

[ 3152.165401] usb 1-1.4: device descriptor read/64, error -71

[ 3152.345253] usb 1-1.4: new high-speed USB device number 17 using xhci_hcd

[ 3152.418811] usb 1-1.4: device descriptor read/64, error -71

[ 3152.598862] usb 1-1.4: device descriptor read/64, error -71

[ 3152.705784] usb 1-1-port4: attempt power cycle

[ 3152.768393] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3153.305488] usb 1-1.4: new high-speed USB device number 18 using xhci_hcd

[ 3153.305792] usb 1-1.4: Device not responding to setup address.

[ 3153.512490] usb 1-1.4: Device not responding to setup address.

[ 3153.718930] usb 1-1.4: device not accepting address 18, error -71

[ 3153.769339] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3153.795624] usb 1-1.4: new high-speed USB device number 19 using xhci_hcd

[ 3153.795898] usb 1-1.4: Device not responding to setup address.

[ 3154.002571] usb 1-1.4: Device not responding to setup address.

[ 3154.209075] usb 1-1.4: device not accepting address 19, error -71

[ 3154.209474] usb 1-1-port4: unable to enumerate USB device

[ 3154.770184] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3155.771015] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3156.771858] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3157.360005] Buffer I/O error on dev sda12, logical block 1081344, lost sync page write

[ 3157.360034] JBD2: I/O error when updating journal superblock for sda12-8.

[ 3157.360039] Aborting journal on device sda12-8.

[ 3157.360046] Buffer I/O error on dev sda12, logical block 1081344, lost sync page write

[ 3157.360053] JBD2: I/O error when updating journal superblock for sda12-8.

[ 3157.772692] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3158.773753] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3159.774975] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3160.776314] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3161.324808] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #2: comm tvh:tasklet: reading directory lblock 0

[ 3161.324961] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #2: comm tvh:tasklet: reading directory lblock 0

[ 3161.777613] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3162.778658] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

[ 3163.779497] EXT4-fs error (device sda9): __ext4_find_entry:1663: inode #390958: comm PVRManager: reading directory lblock 0

This should not be necessary as one-time keymap configuration is enough if you configure the /storage/.config/rc_maps.cfg file properly. Then just run the ir-keytable one times with auto-load parameter (for instance ir-keytable -a /storage/.config/rc_maps.cfg -s rc0 ).

You may also need a proper firmware file. Maybe Linux4Media cineS2 DVB-S2 Twin Tuner - LinuxTVWiki ?

Look here: https://kodi.wiki/view/Keyboard_controls

The keywords are Player Process Info, Video Debug Info and Player Debug Info.

Look here: https://www.linuxtv.org/wiki/index.php/DVB-T2_USB_Devices

Quote from gibbon

Personally I was thinking about getting DVB-T2 USB stick. But I don't know how good is their support under LE and Kodi.

AFAIK current latest LE & Kodi releases does NOT have a special support for DVB-T2 USB sticks. So you have to check whether the DVB-T USB stick you wish to use is supported by Linux kernel (release that current LE is running on) or not.

Yeah I am experiencing the issue quite often but for me it's not easy to apply the patch to LE. I suppose this would need a LE compilation from scratch and it seems to be a bit complex for me to do it.

I am running LE 11 Nightly builds, updating every couple days. Hoping that issues I have will be fixed by LE developers some day. Unfortunately it looks that Live TV (DVB-T and related) has a rather low priority - I understand there are more important things to do and the time is limited as this is non-commercial project and developers are working on it at their free time.

You may give it a try.

BTW. What I am also experiencing is an occasional EPG corruption on LE running on RPi 4B (some program descriptions are incomplete / screwed up). I have reported it here a long time ago but it's still the same. And it seems this does not happen on the same LE version running on x86 machine. As it is random and I don't have the x86 and RPi 4B devices at the same location, it's hard to compare but I don't remember seeing this issue on x86.