Posts by ghtester

ghtester

OK, thanks a lot for a quick reply and sorry for "hoax"...

ghtester

FYI on LE 9.80 nightly builds ( LibreELEC-RPi4.arm-9.80-nightly-20201124-59085f2.tar ) which are using ALSA audio drivers it's possible to switch audio output (Kodi - Settings / System / Audio - Audio output device) to display connected to HDMI1 and it works fine.

But the option for audio output to Default Audio Device + HDMI together is missing.

ghtester

It looks something is wrong as on the same RPi 4B HW configuration running LE 9.80 nightly (even latest 20201124) the tvservice command does not find any HDMI display connected in comparision with LE 9.2.6 official so it can't be used on LE 9.80 at all.

LE 9.80:

LE:~ # tvservice -l

0 attached device(s), display ID's are :

LE 9.2.6:

LE:~ # tvservice -l

2 attached device(s), display ID's are :

Display Number 2, type HDMI 0

Display Number 7, type HDMI 1

ghtester

Well, I am using RPi4 and had no HDMI sound issue after upgrading LE to 9.2.6.

I don't think the onboard micro HDMI connector is broken, more likely it could be a cheap cable with bad contacts. But usually if there's a video OK, the audio also works ( AFAIK both goes through TMDS channels ).

At first I would check the TV / display attached if the audio is not muted / switched off there... Or if there are external speakers connected to display...

AFAIK the secondary HDMI port on RPI4 is not supported in LE. So far I did not have a reason to play with the settings (using just the HDMI 0 port) so I don't know what is possible to do...

Just quickly tested the tvservice command which partially works on LE 9.2.6 with issues (sometimes the -v parameter is ignored, sometimes it hangs etc.) on 2 HDMI displays connected and sometimes I was able to switch video to secondary HDMI port (using -p and -o parameters on both ports but don't ask me how exactly, it's hard to reproduce it). But just the video.without sound and without LE GUI.

There's -a parameter which should display info about audio supported so maybe you can try to play with this.

LE:~ # tvservice -l

2 attached device(s), display ID's are :

Display Number 2, type HDMI 0

Display Number 7, type HDMI 1

LE:~ # tvservice -a -v7

PCM supported: Max channels: 2, Max samplerate: 192kHz, Max samplesize 16 bits.

AC3 supported: Max channels: 6, Max samplerate: 48kHz, Max rate 2040 kb/s.

LE:~ # tvservice -a -v2

PCM supported: Max channels: 2, Max samplerate: 48kHz, Max samplesize 24 bits.

LE:~ # tvservice -s -v2

state 0xa [HDMI CUSTOM RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive

LE:~ # tvservice -s -v7

state 0xa [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive

LE:~ #

ghtester

Thanks for your comment, chewitt. Yes I know you are right. I don't know (and despite some searching couldn't find / discover) any details how the info labels (related to StreamSignal and StreamSNR) works (I did not analyze the source codes as it's above my level).

But I thought it could grab it from femon or dvb-fe-tool by a simple script. In this case it would be easy (for anyone) to make a modification but it looks it's not the case.

I absolutely understand that low priority of this issue but I think if there are still the Signal and SNR values present at PVR info page, it should show the valid values or tagged them as unsupported and get removed instead.

Anyway, I am happy with the simple solution outlined above, that's suitable for me (just improved the script example a bit and configured a mapping to IR remote key). BTW. the Notification command is very useful and I am using it also for CPU high temperature warning (as sometimes one or more cores stuck at 100%).

ghtester · 0bda:b812 rtl88x2bu kernel module ghtester November 23, 2020 at 6:28 PM

Well, as it's really hard to discover what issue are you facing to without any description (or without at least the command error output ),

I am afraid anybody can hardly help you...

Usually - AFAIK - you need to load the appropriate driver module without device ID parameter. If it loads OK (it could depend on other modules which needs to be loaded before), it should recognize the device.
lsmod

dmesg

modinfo RTL88x2BU.ko

command outputs could perhaps give a hint to you.

ghtester · 0bda:b812 rtl88x2bu kernel module ghtester November 22, 2020 at 10:35 PM

Perhaps you could edit or create the /storage/.config/autostart.sh file and put there something like this: insmod /PathToFile/RTL88x2BU.ko ?

ghtester

Probably it's not a bug in fact but a feature more likely. But the question is if it shouldn't be changed a bit.

In several most fresh LE 9.80 Nightly test builds on my RPi 4B / 2GB I have experienced several unexpected crashes due to Out of memory event when oom-kill intervened.

That's due to my Timeshift settings in Tvhedadend to use RAM only with Maximum RAM size set to 1024 MB. This limit I set in past experimentally by observing the Free memory value in Kodi / System info / Summary. So now after crashes it seemed that LE is using more RAM and I'l had to decrease the Maximum RAM size to avoid Out of memory.

But I have found that the Free memory value is calculated and it is somewhat greater than free / avail Mem values reported by the top app.

It looks that Free memory formula is Mem total - Mem used but this value is greater than Mem free / avail Mem reported by top so there's an overhead somewhere.

This may be misleading as I would expect the Free memory in Kodi should display the lowest - real - value.

I wonder why the Free memory is calculated by formula and why it does not show the free or avail Mem value instead? I suppose there's a reason but shouldn't be that changed?

ghtester · Profiles problems ghtester November 19, 2020 at 7:34 PM

I would try to upgrade to latest official 9.2.6 release first and report again if the issue is the same.

ghtester · LCDproc problem ghtester November 15, 2020 at 2:55 PM

After some more extensive searching and testing I have found the reason why it did not work with the current hd44780.so driver (the same issue was in current Raspberry OS).

A couple years ago the hd44780 driver was redesigned and it looks default pinout for i2c expander was changed and pinout configure options were added.

Unfortunately so far there's no relevant information update in the LCDd.conf about it so it may confuse many users like me.

In my case it was necessary to add the pinout configuration to [hd44780 ] section of the

/storage/.kodi/userdata/addon_data/service.lcdd/LCDd.conf

file and the following settings works fine with my display and the current hd44780.so driver:

-------------------------------------

ConnectionType=i2c

Port=0x3f # depends on i2c expander type, use i2cdetect -y 1 command to check

Device=/dev/i2c-1

Size=16x2

i2c_line_RS=0x01

i2c_line_RW=0x02

i2c_line_EN=0x04

i2c_line_BL=0x08

i2c_line_D4=0x10

i2c_line_D5=0x20

i2c_line_D6=0x40

i2c_line_D7=0x80

Backlight=external

BacklightInvert=yes

----------------------------------

No file replacement is necessary anymore, just the proper configuration is the solution.

Hope this helps...

ghtester

After some more extensive testing with 3 USB DVB-T2 tuners I have found differences related to monitoring status returned by their drivers:

Astrometa Sony CXD2837ER Kodi PVR info: Signal quality:0%, SNR:0%

LibreELEC:~/tmp # dvb-fe-tool -f 1 --femon -c1

Lock (0x1f) Signal= 122.47dBm C/N= 23.00dB UCB= 0 postBER= 456x10^3

Astrometa Panasonic MN88473 Kodi PVR info: Signal quality:49%, SNR:0%

LibreELEC:~/tmp # dvb-fe-tool -f 1 --femon -c1

Lock (0x1f) Quality= Good Signal= 49.95% C/N= 23.59dB UCB= 0 PER= 0

MyGica Silicon Labs Si2168 Kodi PVR info: Signal quality:0%, SNR:0%

LibreELEC:~/tmp # dvb-fe-tool --femon -c1

Lock (0x1f) Signal= -52.00dBm C/N= 26.00dB UCB= 161640 postBER= 0

So it looks PVR info can show the Signal quality and SNR values only if the tuner driver reports these values in % but every tuner driver is returning very different values in fact, which are mostly incompatible.

It would be nice when some configurable pass-through filter could be implemented above driver layer so for any tuner model would be possible to make it working properly.

Otherwise PVR info page in Kodi should be changed to grab and display the Signal and C/N values as exactly provided by driver and not in % which is now obsolete.

ghtester

OK, as I don't know how the info labels work, I have created a temporary simple solution.

If somebody else is interested, this is a primitive example script which displays the Signal quality and SNR on screen using the Notification action.

Tested and working on LE 9.2.6 official and on LE 9.80 Nightly.

#!/bin/bash

COUNTER=0

while [ $COUNTER -lt 1000 ]; do

output_sig=$(dvb-fe-tool --femon -c1 &> /tmp/femon )

read femon_output < /tmp/femon

signal=$(echo $femon_output | cut -c 13-30)

snr=$(echo $femon_output | cut -c 31-43)

kodi-send --action="Notification($signal,$snr,1000,null)" > /dev/null

let COUNTER=COUNTER+1

sleep 1

done

ghtester

Just discovered by searching the Net that femon is a bit obsolete and there's a replacement - dvb-fe-tool - which works fine on both LE official 9.2.6 and latest LE 9.8 Nightly / RPi 4B:

=================================

LibreELEC:~ # dvb-fe-tool

Device Silicon Labs Si2168 (/dev/dvb/adapter0/frontend0) capabilities:

CAN_2G_MODULATION

CAN_FEC_1_2

CAN_FEC_2_3

CAN_FEC_3_4

CAN_FEC_5_6

CAN_FEC_7_8

CAN_FEC_AUTO

CAN_GUARD_INTERVAL_AUTO

CAN_HIERARCHY_AUTO

CAN_INVERSION_AUTO

CAN_MULTISTREAM

CAN_MUTE_TS

CAN_QAM_16

CAN_QAM_32

CAN_QAM_64

CAN_QAM_128

CAN_QAM_256

CAN_QAM_AUTO

CAN_QPSK

CAN_TRANSMISSION_MODE_AUTO

DVB API Version 5.11, Current v5 delivery system: DVBT2

Supported delivery systems:

DVBT

[DVBT2]

DVBC/ANNEX_A

Frequency range for the current standard:

From: 48.0 MHz

To: 870 MHz

Step: 62.5 kHz

============================================

LibreELEC:~ # dvb-fe-tool --femon

Lock (0x1f) Signal= -50.00dBm C/N= 23.50dB UCB= 150 postBER= 0

Lock (0x1f) Signal= -50.00dBm C/N= 23.75dB UCB= 150 postBER= 0

Lock (0x1f) Signal= -51.00dBm C/N= 23.75dB UCB= 150 postBER= 0

Lock (0x1f) Signal= -50.00dBm C/N= 23.50dB UCB= 150 postBER= 0

Lock (0x1f) Signal= -50.00dBm C/N= 23.00dB UCB= 150 postBER= 0

=============================================

These values are OK and corresponds with Status values in Tvheadend.

The question is - how to get them displayed in Kodi - PVR info (LE 9.8 - Kodi 19.0-ALPHA3) as it worked earlier (LE 9.2.6 - Kodi 18.9.0) ?

Edit - additional info I have discovered so far:

The PVR info is displayed by "o'' key press in Kodi when PVR is active or can be invoked by kodi-send --host=127.0.0.1 --button=o or by kodi-send -a "PlayerProcessInfo" when enabled in Settings / PVR&Live TV / Playback / Show signal quality

The affected (not working) info labels are:

PVR.ActStreamSignal {value)

PVR.ActStreamProgrSignal (progress bar)

PVR.ActStreamSNR (value)

PVR.ActStreamProgrSNR {progress bar)

ghtester

Thanks a lot for your quick reply and for PR created, I can confirm it was fixed in today's nightly build LibreELEC-RPi4.arm-9.80-nightly-20201110-82a92d8.tar

ghtester

As the new beta bootloader was released, I tried to upgrade it as usual (on official LE 9.2.5 it was working) but failed:

# rpi-eeprom-update -d -f /tmp/pieeprom

BCM2711 detected

Dedicated VL805 EEPROM detected

*** INSTALLING /tmp/pieeprom ***

grep: /var/lib/dpkg/info//rpi-eeprom.md5sums: No such file or directory

cat: can't open '/var/lib/dpkg/info//rpi-eeprom-images.md5sums': No such file or directory

md5sum: /tmp/tmp.C1K9IA: no checksum lines found

rpi-eeprom checksums failed - try reinstalling this package

Unable to validate EEPROM image package checksums

The current LE 9.80 Nightly installed:

LibreELEC-RPi4.arm-9.80-nightly-20201105-57711b6.tar

Raspberry Pi Tools add-on installed: 9.80.7.107

ghtester · LCDproc problem ghtester November 3, 2020 at 10:13 PM

I can confirm this issue still persists in latest official and test LibreELEC builds (9.2.5 official, 9.80 nightly) and hd44780.so file must be replaced (see the Momo90's link above) in folder /storage/.kodi/addons/service.lcdd/lib/lcdproc/ otherwise it does not work with HD44780 compatible displays connected through i2c adapter.

Edit - not necessary anymore, see the next post.

ghtester

Couldn't this be a hint?

SNR and Signal showing as zero in PVR info overlay · Issue #164 · kodi-pvr/pvr.vuplus · GitHub

ghtester

I am using the DVB-T2 adapter MyGica T230C on RPi 4B and with the same setup as in earlier official LibreELEC build 9.2.5 which worked (with checked Force old status checkbox in TV adapter config), I am not able to get the Signal quality / SNR displayed in Kodi anymore.

Service backend is Tvheadend Server 4.2 ( HTS Tvheadend 4.2.8-36 ~ LibreELEC Tvh-addon v9.80.6.123 ), PVR client is Tvheadend HTSP Client 7.2.1.1 (both installed from the Nightly Add-ons list).

Tested on some latest Nightly builds with the same results:

LibreELEC-RPi4.arm-9.80-nightly-20201024-636e32e.tar

LibreELEC-RPi4.arm-9.80-nightly-20201030-7f3b20d.tar

LibreELEC-RPi4.arm-9.80-nightly-20201031-cf5a710.tar

In TVheadend GUI on Status page the Signal quality / SNR is visible:

SNR: 29.5 dB

Signal Strength: -46.0 dBm

When tried femon, I have found that SNR is still reported with the same - fix - value which does not reflect the Tvheadend's value and the Signal value is random after every femon start:

LibreELEC:~ # femon -H