Posts by HiassofT

  • No audio on intel baytrail minipc

    Thanks for the logs! dmesg spam seems to be gone, but there are lots of Alsa errors in the kodi log. I think it's best to focus on getting speaker-test working.

    I looked through the alsaucm docs and noticed I missed an important step: after setting the _verb we also need to enable the (output) device. The output devices "Headphones" and "Speaker" look like good candidates.

    Please try these commands:

    Code
    alsaucm -c bytcr-rt5640 set _verb HiFi
alsaucm -c bytcr-rt5640 set _enadev Headphones

    Then run speaker-test -c 2 -t sine again and upload dmesg.

    If it didn't work try with the Speakers device - but before we need to disable the Headphones device

    Code
    alsaucm -c bytcr-rt5640 set _disdev Headphones
alsaucm -c bytcr-rt5640 set _enadev Speaker

    According to the manual using the "reset" command should also work, this should allow us to start from scratch:

    Code
    alsaucm -c bytcr-rt5640 reset
alsaucm -c bytcr-rt5640 set _verb HiFi
alsaucm -c bytcr-rt5640 set _enadev Speaker

    Try speaker-test again and grab dmesg.

    If you get any errors on the terminal these would be interesting, too.

    so long,

    Hias

  • problem with "longpress" actions in keymap.xml under LibreELEC (Leia) v8.90.009 ALPHA

    Read through the IR remote wiki page Infrared Remotes [LibreELEC.wiki] , it contains detailed descriptions and examples which commands to use and how. eg to stop kodi and eventlircd you have to use

    Code
    systemctl stop kodi
systemctl stop eventlircd

    The posting you linked to includes the same keytable file as we already include in LibreELEC - so that won't help. Also better don't follow the instructions from that post, thinks have change a bit since then and blindly copying udev rule files may make things worse.

    It could be that your old configuration settings are somehow interfering so it's best to drop them. Delete all files in .kodi/userdata/keymaps/ and then reboot so you can start from scratch.

    Before you start tweaking kodi's keymap file verify that kodi is receiving all buttons correctly. Enable debug logging, ssh in and run the following command to get a "live view" on kodi's logfile:

    Code
    tail -f .kodi/temp/kodi.log

    Now press buttons on your remote. For each button press you should see 2 lines logged like these:

    Code
    12:54:03.957 T:1936904864 DEBUG: Keyboard: scancode: 0x66, sym: 0x0116, unicode: 0x0000, modifier: 0x2000
12:54:03.957 T:1936904864 DEBUG: HandleKey: home (0xf088) pressed, action is FirstPage

    The first line tells you which keycode kodi received, the scancodes should be different for all buttons on your remote. If it's not something's wrong with the ir-keytable configuration.

    The second line tells you the resulting action after kodi applied it's keymap.xml files - you can use this info to verify if you got your keymap.xml file right after you started tweaking it.

    so long,

    Hias

  • No audio on intel baytrail minipc

    Can you test this build: libreelec-generic.x86_64-9.0-devel-20181217224448-658cde5.tar

    It includes the Alsa UCM configuration tool and files needed to manually setup baytrail audio.

    After boot quickly ssh in and stop kodi so dmesg doesn't get spammed with "no backend DAI" messages:

    Code
    systemctl stop kodi

    Then run alsaucm to configure the audio device

    Code
    alsaucm -c bytcr-rt5640 set _verb HiFi

    Now use speaker-test to check if you can get audio from the analog output / Line out:

    Code
    speaker-test -c 2 -t sine

    Abort speaker-test with control-c after a couple of seconds and then post dmesg - if you didn't get audio it could be because something else is still missing and/or you may need a different firmware file (maybe the one from the windows driver you mentioned).

    If you got audio, start kodi again with systemctl start kodi and check if it works there, too. If it does. add the alsaucm command to autostart.sh to make the configuration permanent.

    so long,

    Hias

  • No audio on intel baytrail minipc

    Thanks a lot for the logs, the firmware error is gone which is a good sign!

    I've checked the alsa-devel mailing list and it looks like baytrail needs some userspace configuration in place before the audio device can be used.

    This stuff (alsaucm) is currently missing in LibreELEC, I'll prepare a new build and post an update when it's finished.

    so long,

    Hias

  • Enabling Serial / UART on Raspberry pi 3B

    Can you test if this build works: libreelec-rpi2.arm-9.0-devel-20181217124947-c8d99e0.tar

    We were missing the driver for the miniuart in the RPi kernels - probably noone noticed that until now as most people only used the pl011 UART (I also usually just disable BT to get a full serial console).

    I did a quick test with this build, with an IQaudio DAC board installed on an RPi3B and console=ttyS0,115200 worked with it (that didn't work before).

    so long,

    Hias

  • LibreElec + Cinergy DVB-S2 Dual Tuner + Terratec Remote generates double key events

    Thanks a lot for testing and the logs, everything's fine (except that the CrazyCat driver registers IR devices for both of the 2 receivers).

    The lirc device is fine, you usually get it with IR receivers (the Lirc option in LE 8.2 settings controlled the lircd userspace daemon, this is something different).

    crazycat I think this could be fixed by registering an rc-core device only for one of the 153b:1181 / 153b:1182 USB devices. Looks like the IR receiver is connected to both of the devices on the dual tuner card so enabling IR on both of them results in doubled IR events. Can you have a look at that?

  • No audio on intel baytrail minipc

    Sorry, false alarm, the firmware is already included in the image, so it's something else.

    It looks like the audio driver is built into the kernel and at driver probe time the firmwares from the system image aren't available yet. I'll have a look at it and report back - probably building the audio driver as a module should work fine.

    so long,

    Hias

  • No audio on intel baytrail minipc

    Thanks for the log!

    It looks like we're missing a firmware file:

    Quote

    [ 2.824531] intel_sst_acpi 80860F28:00: Direct firmware load for intel/fw_sst_0f28.bin failed with error -2

    Could you update to LibreELEC 8.90.009 and then run the following 2 commands

    Code
    mkdir -p /storage/.config/firmware/intel
wget -O /storage/.config/firmware/intel/fw_sst_0f28.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/intel/fw_sst_0f28.bin

    After that reboot so the kernel can pick up the firmware.

    Please post dmesg again and drop us a line if it worked or not.

    so long,

    Hias

  • problem with "longpress" actions in keymap.xml under LibreELEC (Leia) v8.90.009 ALPHA

    I completely forgot that LibreELEC 8 still used the old, proprietary amremote / remote.conf mechanism on Amlogic devices. In LE 9 this was switched to ir-keytable so the same mechanism like on all other Linux devices can be used. This is probably the reason why you got keyboard events on LE8 and the keycodes are a bit different.

    As for the non-working buttons: quite probably the keytable contains problematic KEY_ values that Kodi can't handle.

    To find out which ones they are stop kodi and eventlircd and run "ir-keytable -t", then look at the KEY_xxx values of the non-working buttons.

    Then copy the wetek_play_2 keytable from /usr/lib/udev/rc_keymaps to .config/rc_keymaps and change the problematic KEY_xxx entries to something kodi can handle - KEY_F1..KEY_F15 should work for example (any other keys that you'd typically find on a normal keyboard should work fine, too).

    Then activate and test the keytable as described on the wiki page.

    I had a quick look at the wetek_play_2 keytable and found a few odd entries like KEY_COMPOSE or KEY_CAPSLOCK. These could be problematic.

    so long,

    Hias

  • LibreElec + Cinergy DVB-S2 Dual Tuner + Terratec Remote generates double key events

    Thanks a lot for the logs!

    As suspected the card isn't supported by the official linux kernel drivers but uses the out-of-tree CrazyCat drivers.This is good to know since we now know whom to bother with this issue.

    I haven't used Live/Run mode myself yet but I thought it would store user/configuration data on the USB stick. So selecting a different DVB driver set might work. Could you give that a try?

    so long,

    Hias

  • Probleme mit Hauppauge WinTV-solo HD

    Mit ein wenig Overclocking und entsprechender Kühlung (ein etwas grösserer Kühlkörper langt) läuft DVB-T2 HD (1080p50 HEVC) am RPi3B und RPi3B+ flüssig.

    Für DVB-T/T2 am RPi ist der offizielle Raspberry Pi TV Hat sehr gut geeignet - der funktioniert einwandfrei.

    Mit einem GPIO Extender, um den TV Hat etwas höher zu setzen, ist auch genug Platz für einen Kühlkörper - ich verwende hier die BGA-STD-065 von ABL (ca 28x28mm Grundfläche und ca 11mm hoch).

    so long,

    Hias

  • problem with "longpress" actions in keymap.xml under LibreELEC (Leia) v8.90.009 ALPHA

    Kodi recevies the remote button presses as LIRC events, not keyboard events, and Kodi doesn't support longpress with those.

    I'm not exactly sure how it was handled in LE 8.2 but if you got keyboard events from the remote it was most likely a bug. The LIRC translation by eventlircd is needed because Kodi doesn't support a lot of the buttons on remotes in keyboard mode - see the wiki for details Infrared Remotes [LibreELEC.wiki]

    You can disable the LIRC translation via a custom 98-eventlircd.rules udev rule file but keep in mind that this is not officially supported and you might have to change the remote keymap as well so it contains only keycodes that kodi can handle. If you are prepared to go this route you can completely disable LIRC translation by eventlircd by creating an empty udev rule file:

    Code
    : > /storage/.config/udev.rules.d/98-eventlircd.rules

    so long,

    Hias