Posts by HiassofT

  • [RPi4] HiFiBerry Digi2 Pro not found

    I couldn't find any info what the Hifiberry folks changed between rev 2.1 and 2.2 but I found a post where a user got his Digi+ pro working with a slight hardware modification - something similar might work with the Digi2 Pro as well:

    https://support.hifiberry.com/hc/en-us/community/posts/15842018863261/comments/16381227323677

    From the looks of it Hifiberry messed up their hardware design and I'm wondering why they didn't wire up the WM8804 reset to a GPIO pin like outlined in the reference design in the WM8804 datasheet, this likely would have avoided the powerup issues.

    The Linux driver supports this and the Allo DigiOne and the Cirrus WM5102 dtoverlays use this, just not the Hifiberry and other WM8804 based SPDIF soundcards.

    so long,

    Hias

  • Nightly Builds

    VDPAU has been deprecated for quite a while now, Nvidia's moved to the CUDA based nvdev/nvenc API.

    As kodi doesn't support nvdec the nvidia-vaapi-driver is now used - kodi uses vaapi and the nvidia-vaapi-driver "translates" that to nvdec.

    Nvidia RTX50XX (plus future models) aren't supported in LE as they would require a different kernel driver (which only supports very recent nvidia cards so we can't just switch to that as it would drop support for a lot of older cards).

    Trying to support nvidia cards has been a huge PITA in the last year (even more painful than before) and is bloating our images a lot (all the proprietary nvidia libraries and firmwares are huge) so I wouldn't be surprised if we end nvidia support sooner than later.

    so long,

    Hias

  • [RPi5] After EEPROM update LibreELEC did not start

    Likely you pulled the plug too early - wait until firmware update in LE settings comes back with the "OK" dialog (this takes about half a minute or so), then reboot using the reboot option in kodi's power menu. Never ever just pull the plug!

    On RPi5 the update is performed as soon as you choose "yes", the reboot is then only necessary to activate the updated bootloader.

    so long,

    Hias

  • [RPi5] Loading "iwlwifi" WiFi driver

    We've now added the iwlwifi (and rtw88/89 PCIe wifi) drivers in the LE12.2 and LE13 branches. If things go well you should be able to test with official nightlies from https://test.libreelec.tv/ in a couple of hours.

    Note: we haven't included firmware files, you have to add them on your own. For the ty firmware variant the 6.12 kernel now seems to want the 89 api version:

    Code
    rpi5:~ # modinfo iwlwifi | grep firmware | grep ty
firmware:       iwlwifi-ty-a0-gf-a0.pnvm
firmware:       iwlwifi-ty-a0-gf-a0-89.ucode

    so long,

    Hias

  • ws2812-pio-rp1 Kernel Driver seems not functional on RPi5

    Thanks for the log!

    The log shows you have hyperhdr running, better stop that to ensure it's not accessing the /dev/leds0 device node.

    Also you seem to have some "99-com.rules" udev rules - what do you set up there?

    We're building the kernel straight from the RPi kernel repo - only with modified config. AFAICT everything should be in place in our kernel so I have no idea what could be causing the issue. As the ws2812 driver doesn't log any errors/warnings it's hard to tell what the issue may be.

    Device major/minor numbers shouldn't matter at all, they are dynamically allocated nowadays.

    Before opening an issue on the RPi kernel repo better triple-check that it's not some configuration/setup issue on your side, eg try with a plain LE installation on a separate SD card with just the dtoverlay added - and nothing more. Also maybe try asking on the RPi forum first, the Interfacing section might be a good place.

    so long,

    Hias

  • ws2812-pio-rp1 Kernel Driver seems not functional on RPi5

    Please provide a full log: ssh in, run "pastekodi" and post the URL.

    I don't have any WS2812 LEDs here so can't test with real hardware, but just adding the dtoverlay with default settings shows both the rp1-pio and ws2812-pio-rp1 drivers being successfully loaded:

    Code
    rpi5:~ # dmesg | grep rp1
[    1.978635] rp1 0002:01:00.0: bar0 len 0x4000, start 0x1f00410000, end 0x1f00413fff, flags, 0x40200
[    1.987721] rp1 0002:01:00.0: bar1 len 0x400000, start 0x1f00000000, end 0x1f003fffff, flags, 0x40200
[    1.996988] rp1 0002:01:00.0: enabling device (0000 -> 0002)
[    2.003186] rp1 0002:01:00.0: chip_id 0x20001927
[    2.395815] genirq: irq_chip rp1_irq_chip did not update eff. affinity mask of irq 161
[    2.712353] rp1-firmware rp1_firmware: RP1 Firmware version eb39cfd516f8c90628aa9d91f52370aade5d0a55
[    2.722320] rp1-pio 1f00178000.pio: Created instance as pio0
[   12.224635] /axi/pcie@1000120000/rp1/spi@50000/wm5102@0: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/spi@50000/wm5102@0/ldo1
[   12.422735] ws2812-pio-rp1 ws2812_pio@4: Instantiated 60 LEDs on GPIO 4 as /dev/leds0

    ```BTW: We can't build rp1-pio as a module as that would result in the RPi5 DPI DRM driver being built as a module instead of builtin to the kernel - which means DPI displays wouldn't have display output during boot. If building rpi1-pio as builtin indeed is the culprit then that's a bug in the rp1-pio or ws2812-pio-rp1 driver and should be reported as an issue on the RPi kernel repo.

    so long,

    Hias

  • [x86-64] CEC broke after updating to LE 12.2.0

    Have you tried resetting the CEC settings to default? If in doubt, stop kodi and delete the CEC settings file (systemctl stop kodi; rm /storage/.kodi/userdata/peripheral_data/cec_CEC_Adapter.xml) and reboot.

    LE 12.2 ships with a newer libcec (latest version 7.1.1 instead of the ancient 4.0.7 in LE12) and some of your old settings may be incompatible or wrong.

    so long,

    Hias

  • Can't map LIRC-Buttons

    Not sure if we have some best practice guide where to put user scripts, you can store them anywhere in /storage, keep in mind though that only the .config and .kodi folders will be backed up by the backup/restore function in LE settings.

    We have a "Showcase" forum here, guess that'd be a good place to present your scripts/settings

    Showcase

    so long,

    Hias

  • Can't map LIRC-Buttons

    Unfortunately no, kodi uses a hardcoded set of button codes.

    There is/was an attempt to improve kodi input handling and support remotes via keyboard input handling but it wasn't finished and hasn't been updated for quite a while now...

    [input] fallback to direct libinput mapping by oliver · Pull Request #26039 · xbmc/xbmc
    Description This is a possible fix for #16834 when using the GBM system. This approach adds a fallback mapping table, which is used when XKB cannot map a key…
    github.com

    so long,

    Hias

  • Can't map LIRC-Buttons

    You have to use the remote section of the keymap and map kodi remote button codes, not keycodes, to actions.

    See the devinput section of /usr/share/kodi/system/Lircmap.xml to see how input key codes are mapped to button codes

    so long,

    Hias

  • Using a remote control with lircd.conf in LibreElec(12)/Kodi?

    Hmm, you seem to have masked the lircd.socket unit - that's not good, it's needed as lircd is a socket activated service and lircd-uinput starts it by connecting to the socket.

    Remove /storage/.config/system.d/lircd.socket and also /storage/.config/system.d/multi-user.target.wants/eventlircd.service and /storage/.config/system.d/multi-user.target.wants/lircd-uinput.service (the latter two are already enabled by the system), then reboot.

    so long,

    Hias