Posts by wyup

    I'd like to do a filesystem check/repair of libreelec's current partition with e2fsck or fsck, I try to read /etc/fstab but the file is empty.

    Sometimes in case of cold reboot I'd like to check that the filesystem is ok, because I store my media library on libreelec's partition.

    Hi, I've installed latest librespot (2023-05-14) kodi plugin, version 11.80.1.1 by awiouy (Anton Voyl) on latest kodi nightly on RPI4.

    The plugin works with default options, in my case backend alsa and device hw:2,0

    #librespot -d ? gives my device:

    Code
    iec958:CARD=sndrpihifiberry,DEV=0
    Description:
    snd_rpi_hifiberry_digi, HiFiBerry Digi+ Pro HiFi wm8804-spdif-0
    IEC958 (S/PDIF) Digital Audio Output
    Supported Format(s):
    S16 S24

    I have found you can enter certain unconfigured options, since some are preconfigured by the python scripts that load the daemon (there is no systemctl service any longer to manage as audiobobo pointed out). The python acripts that load the daemon are here:

    /storage/.kodi/addons/service.librespot

    By default, cache is disabled and bitrate is set at 320 by, as default soundcard selected by kodi config.

    You can enter extra options in the librespot kodi addon config interface, I entered -f S24 and it seems to work.


    Note: apart from this client addon, I have found another Kodi .zip wrapper manual plugin for Spotify. (https://github.com/jhjdekker98/plugin.audio.spotifyd-client), and it has a link for a armhf binary on https://github.com/Spotifyd/spotifyd/releases, but I haven't tried installing it since it requires Spotify Developer account settings and copying binaries to a specific path: /resources/lib/spotifyd/spotifyd. It is an alternative to the 'official' librespot kodi plugin, and it lets you customize all options to your liking.

    NB: I'm not sure what advantage you're expecting with aarch64, but it's not going to noticeably improve anything and you will have to reinstall or remove binary add-ons) as they are not aarch64 compatible; and there will be no replacement binary add-ons in the repo as there are no ARM aarch64 releases for LE11 so the add-ons weren't built/don't exist.

    Hi, is this the same situation for RPI4 12 nightly builds? Are all add-ons binary? I say this because I'm running nightly aswell and add-ons work.

    In the past I've run nightly builds for android-tv from kodi repos without problems for basic add-ons.

    I'm waiting for next nightly build, which bumps from 6.1 to 6.4 kernel, yay! I'm expecting improvements on kernel video drivers' hardware acceleration.

    Do most 12/omega add-ons/plug-ins come natively on 64-bits now?

    I heard 12 switches to 64-bits.

    BTW, why do nightly builds occasionally take longer hiatus, such as now, 6 days and no build? (Sorry for the question, didn't want to push)

    Does it show in LE11 without any overlays?

    I tried stable Bullseye 32-bit Raspberry Pi OS without overlays, according to tv hat official guide, but I seem to have a problem recognising the Sony tv tuner chip:

    Code
     [   11.192689] cxd2880: cxd2880_attach: chip id invalid.

    I'm following advice on this post now:

    wyup
    June 27, 2023 at 8:14 PM

    Hello:

    In two cases after flashing two latest RPI4 12 nightly builds on sd card, at first boot, an error like this appears in console:

    Code
    error in mount_storage. mount_common: could not mount UUID-xxxxxxxxxxxx ***
    ## Starting debugging shell for boot step: mount_storage... type exit to quit ###

    then, as I don't have keyboard available, must cold reboot RP4 and normal boot ensues

    note: I had edited config.txt before first boot to add some audio overlay, gpio-ir and little else.

    I did a scandisk and failsafe extract the card from a Windows PC card reader, and had used LibreELEC USB-SD Creator to flash without error.

    Sdcard is a 128GB microSDXC Canvas Go Plus 170R A2 U3 V30, #1 fastest card for PI according to https://pibenchmarks.com/brand/Kingston…us_%28SD128%29/

    Strange.. if I set config.txt to defaults with latest 12 build, "cxd2880" or "dvb" don't even appear in dmesg.

    I have another audio hat, but I make sure it's not sharing tv hat GPIO pins.

    There are occurrences of this in other forums: one user bought a new hat and another did a "soldering of a new GPIO header" to a Zero W:

    https://forums.raspberrypi.com/viewtopic.php?t=232037 (soldered GPIO header)

    https://dietpi.com/forum/t/tv-hat…-properly/14998 (bought a new hat)

    Does it mean that the culprit was a faulty GPIO header? My tv hat comes with a detachable header. Some pin was slightly bent while plugging in and out, but I corrected it with tweezers and the header plugs in fine. I also tried to plug the tv hat in reverse on the upper side of the board the first time until I realized it was on the other. I don't think I need to solder anything, do I?

    Can you help if that is related to me?

    I bought recently an official RPI TV hat and installed Libreelec 12 nightly along with tvheadend 4.1 server and client. Added dtoverlay=rpi-tv and gmem=128. Did the localhost:9981 setup wizard but it doesn't find any tuner.

    Dmesg returns: "cdx2880_attach: chip id invalid". It seems the Sony cxd2880 tv tuner driver is not in the nightly kernel. Could you please add it to the nightly build?. It used to be in earlier versions. I installed latest Raspberry Pi OS 32-bit stable and I have the same problem.

    It's available here: https://github.com/torvalds/linux…ontends/cxd2880

    Code
    [   11.026954] dvbdev: DVB: registering new adapter (CXD2880)
    [   11.042537] brcmfmac: F1 signature read @0x18000000=0x15264345
    [   11.098387] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
    [   11.099534] usbcore: registered new interface driver brcmfmac
    [   11.192689] cxd2880: cxd2880_attach: chip id invalid.
    [   11.192727] cxd2880_spi: cxd2880_spi_probe: cxd2880_attach failed

    Thanks, didn't know that 12 is getting a switch to 64 bit, that is a major change!

    I'm using 12 for the moment, and have experimented temporary dropouts on wifi near the router, i have turned off bluetooth (among many tests on wifi parameters) and this seemed to help, I also applied some tweaks by another user in config.txt to fix slowness on ssh terminal (disable leds and low power wifi). Im using a semi-case heatsink, dont know if this impacts the wifi/bluetooth antenna.

    Havent gone to 11 stable to rule this out, I think I should, but too much work to undo<X.

    Thanks for the tip, developer

    It's the same like in earlier RPi4 LE versions - you need to install Tvheadend add-ons (Services-Tvheadend Server 4.2 or 4.3(Alpha) and PVR_clients-Tvheadend HTSP Client)

    I did install both: Services-tvheadend 4.1 stable and client on Le12 nightly, entered config at http://libreelec:9981/ but under Settings>DVB>TV Tuners, my PI DVB Tv tuner hat does not appear.

    Shall i add any dtoverlay for the tv hat?

    I entered dtoverlay=rpi-tv in confix.txt but I can't see the tuner in the web app.

    Hi, I'd like to control Kodi volume from CEC Samsung tv remote. As of now, Vol+ and Vol- controls the tv volume but I'd like to control Kodi volume.

    Is it possible?

    On the other hand, I have a IR sensor on a PI hat, but I don't have an additional IR remote. Can I disable/override CEC on the tv and enable my Samsung remote as a IR remote instead of CEC, so I can control Kodi Volume (and hopefully more functionality)?

    I understand. I'm an audiophile linux enthusiast planning to build an A/V Kodi Libreelec RPI4 player with an Spdif digital transport hat. Direct ALSA hardware out is the most direct, least latency output. Pulseaudio has its problems (latency,samplerate conversion..), and it's being phased out in Linux in favour of the newer PipeWire. Kodi being multiplatform shouldn't be bound to any sound server for plugins.

    Libreelec being a sandbox machine does not need an additional audio API.(even if it has Pulseaudio for Bluetooth and Network). If I did, I would move to RPIOS on debian or a specialized PC.

    I agree keeping ALSA by default is the best choice. Having eq in Kodi would be nice, but we always have ALSA to tinker with.