Posts by ghtester

Well, there're no details about SW versions that you're running, is the client add-on also Tvheadend? And what about some other add-ons (if installed) - a possible conflict there?

I had no such issue running Tvheadend HTSP Client and Tvheadend Server 4.2 add-ons locally on RPi 4B, LE 9.2.5, 9.2.6, 9.80 Nightly and 2 different USB DVB-T2 tuners.

I understand your configuration is different but maybe the Tvheadend Server's side configuration or PVR & Live TV configuration settings in Kodi may also play a role. Perhaps try to look at OTA EPG settings, disable EPG temporarily etc... Also I would try to latest LE Nightly 9.80, from my perspective it works pretty fine ( Index of / ).

Quote from megaprime421

And also can this be fixed if I format the sd card and then re flash the libreelec image cause it was working properly until today afternoon

You may try with the same or with another SD card.

Regarding to logs - you need to connect to your RPi through SSH using Putty ( Download PuTTY: latest release (0.74) ) or another SSH client.

It should be easy with default Putty settings, just enter the IP of your RPi and click Open. Default username is root and password libreelec

Then change the Putty settings (right mouse button click to blue header - Change settings - Window - Lines of scrollback --> 999999, Apply)

Then copy & paste this text to Putty's window and press Enter:

cat /storage/.kodi/temp/kodi.log

cat /storage/.kodi/temp/kodi_crash.log

dmesg

Then click the Putty's blue header again, select Copy All to Clipboard, paste your clipboard to pastebin.com and put a link here.

From this modest description and without the details provided, without logs, it is difficult to help. However, I'm guessing a problem with the SD card - it may be damaged or have a compatibility issue.

I would say you can put the .gz file as well. It just contains additional partition(s) so you can use it for installation image. But the update should work the same for .gz and .tar files (when you put it to /storage/.update folder and reboot the device). Your settings (or most of your settings) should be preserved. Always make a backup before the upgrade anyway.

FYI: Config.txt - LibreELEC.wiki

It's not there, AFAIK you can access that settings only when you play the media - then push OK, select the wheel (Settings) icon in bottom right corner, select Video settings from menu and after changing the Deinterlace method (which is currently grayed in my latest LE 9.80 Nightly) you should select Set as default for all media. It's described in some other thread here.

A different HW but I believe that on x86_64 platform it would be the same - read here: RE: Cec-client does not work on Nightly 9.8 / RPI 4B

I would also try to stop / start Kodi again after boot / power on to check if it helps (in this case adding some delay at Kodi startup could be the solution):

systemctl stop kodi

systemctl start kodi

Also for Analogue output might be necessary (perhaps it depends on LE version) to add this to /flash/config.txt file:

# Enable audio jack output

dtparam=audio=on

BTW. in latest LE 9.80 nightly which is using ALSA drivers the Audio output device configuration is a bit different from latest LE 9.2.6 official and AFAIK it does not allow output to Analogue ( = bcm2835 Headphones) jack and to HDMI at the same time anymore.

I would also recommend to replace the HDMI cable. Try shaking the current cable a little (carefully) during the operation to see what happens.

Quote from secam7

This is not the MyGica T230 or C or C v2 .

I wrote about MyGica T230A witch idVendor=0572, idProduct=689a

In fact it is T230C2 as you can see for instance here: DVB-T USB Devices - LinuxTVWiki

Although the same device ID does not always mean it's the same hardware inside (Astrometa for example), I would say MyGica is not so bad regarding this matter..

Again, there's no need of urgent patching, this tuner works fine on latest LE versions.

In LE 9.80 nightly, which I am currently using, there are only kernel drivers. Although it's not yet 100% rock stable and it may depend on which USB port is used (2.0 or 3.0), overall it works quite fine.

In LE 9.2.6 official it was also working fine, as far as I can remember, at least with CrazyCat drivers.

Edit: Ahh, the idProduct=689a is really different... A fake or a quite new product???

I see that Geniatech does not offer any Linux drivers but you may perhaps try to contact the Support or visit a forum ( Get Support from the MyGica official website ). So far I did not find any mention regarding to T230A under Linux. Maybe it will be necessary to grab the firmware from Windows driver, it also depends on HW difference from previous T230x sticks so more changes in driver sources could be a must...

There's no need of patching, this tuner works fine on latest LE versions.

Exactly. There'll be additional work to do if he won't give it up... Perhaps another way could be through irexec which I am using for several IR buttons to do everything I need and this could be configured easily (don't know if it's a good idea for a whole keyboard but it could work fine at least for some important buttons). Did not test that but I suppose this could work when there's a scan code mapping done to KEY_A etc. properly (or if it's send as fixed values by this driver). But maybe I don't understand the mce_kbd's difference...

echo /usr/bin/irexec -d /storage/.config/lircrc >> /storage/.config/autostart.sh

/storage/.config/lircrc :

begin

prog = irexec

button = KEY_A

config = kodi-send --button=a

end

begin

prog = irexec

button = KEY_B

config = kodi-send --button=b

end

...

...

OK, thanks for a correction, sorry, my fault as I have looked at my LE 9.80... And as I am using my proprietary mapping files originally copied from previous LE version (and then renamed) for a long time and everything still works fine, I did not notice the change.

So SilkBC just need to use the files which can be found in the /usr/lib/udev/rc_keymaps/ folder and does not have .toml extension in LE 9.2.x. The name is not important and can be changed but the file structure is more important and should match the LE version.

Quote from SilkBC

I have nothing in my /storage/.config/rc_keymaps folder; what *should* be in there? My actual MCEUSB remote "just works" without any files needing to be in there.

Yeah so in your case you are in defaults so the current settings should be based on /etc/rc_maps.cfg and /usr/lib/udev/rc_keymaps/libreelec_multi.toml default files located in read-only filesystem. If you read the wiki as recommended by HiassofT, I think you'll understand how it works.

I would copy libreelec_multi.toml file to /storage/.config/rc_keymaps/ folder and rc_maps.cfg to /storage/.config/ folder where you can modify them to override defaults.

At least you need to change the line in /storage/.config/rc_maps.cfg from

* rc-rc6-mce libreelec_multi.toml

to

* rc-rc6-mce /storage/.config/rc_keymaps/libreelec_multi.toml

Then use ir-keytable -a /storage/.config/rc_maps.cfg -s rc0 command to update the configuration (always stop kodi and eventlircd before using systemctl, then start them again in reverse order). Everything should work as before. Then update /storage/.config/rc_keymaps/libreelec_multi.toml file to change scancodes <--> commands assignment, apply ir-keytable -a /storage/.config/rc_maps.cfg -s rc0 again and you irw should show you the results.

In case you don't receive scan codes, you have to enable additional IR protocol, for instance to add mce_kbd (but consider HiassofT's advice above):

ir-keytable -p lirc -p nec -p rc-6 -p mce_kbd -s rc0

Also you may need to use another suitable template instead of libreelec_multi.toml for your preffered IR protocol, check the /usr/lib/udev/rc_keymaps/ folder and use the best file for you.

Edit: See below the HiassofT's correction - I did not notice that there's a change between your LE 9.2.6 and my 9.80 Nightly build so the mapping files you'll find won't have the .toml extension. Everything else should be the same regarding the described steps.

Edit2: Corrected the path for rc_maps.cfg file.

I don't know your IR devices and there're missing important details (even the LE version you are running) and I have no idea what do you have connected to LE. But if you have attached more IR devices at the same time, you need to specify the right parameters which may be different from defaults.

At first, run ir-keytable without parameters, it should list all recognized IR receivers. You should see there, among others, something like:

Found /sys/class/rc/rc2/ with:

...

Enabled kernel protocols: lirc nec

...

Found /sys/class/rc/rc0/ with:

...

Enabled kernel protocols: lirc rc-5
...

You can also see the device names there.

Then you run again for instance ir-keytable -t -s rc2 and push buttons on your IR remote control. If it has the appropriate protocol enabled, you'll see the scancodes received from rc2 device.

You need to have the /storage/.config/rc_maps.cfg configured properly and each active device should have there specified the correct path to mapping file which should be stored in /storage/.config/rc_keymaps/ folder.

For instance mceusb * /storage/.config/rc_keymaps/myIRremote

In the mapping file myIRremote you need to configure the assignment between scancodes and commands (that irw displays when the mapping is correct).

When you change the mapping file, you need to update the configuration, for instance:

ir-keytable -a /storage/.config/rc_maps.cfg -s rc0

Just FYI - on RPi 4B due to much better hardware this issue does not exist anymore, IR works fine on GPIO with LE regardless of USB data transfers.

Regarding to RPi 0-3 I think IR remote controls based on RC5/RC6 protocol could work even through GPIO receiver during long USB transfers but it might not be easy to discover the protocol type at first sight so the supported USB IR receiver is the best choice.

Well as far as I can remember, I started having this issue as well after upgrading to LE 9.2.6 (even I did not change the HDMI port).

In my case I am turning on/off the display by relay (through GPIO pin on my RPi 4B) and there was a python script switching the relay ON after LE startup. It was working fine in previous LE versions but now it's too late to 'handshake' with display booting at the same time so the display did not receive HDMI signal anymore.

I have solved it through config.txt - putting there a command for setting the appropriate GPIO pin earlier so the display is ready before Kodi starts. This works fine.