Posts by racko

    perhaps the sdcard just isn't compatible with that device.

    Very possible but it would be good to find out why, just to know what kind of SD cards I need for it to work.

    I did another test. I added sdhci.debug_quirks2=4 in cmdline.txt:

    boot=UUID=2410-0508 disk=UUID=09814adf-0b3e-462b-ad3f-abd8815b9b92 sdhci.debug_quirks2=4 quiet

    This way LibreELEC started but only once. After restart LE doesn't boot again and I get this error message ...

    *** Error in mount_flash: mount_part: Unknown filesystem ***
    ### Starting debugging shell for boot step: mount_flash... type exit to quit ###

    ... and when I checked cmdline.txt it was empty, it doesn't had any line. :)

    I added the entire line in cmdline.txt and LE started. After restart it happened the same - it didn't boot and cmdline.txt was empty again.

    I don't know what does it means.

    What is the difference between these two SD cards apart from their capacity?

    SanDisk is working and Samsung doesn't work with the switcher with RPI4 8GB. Both of them are working when inserted directly in RPi.

    use the "blkid" command to check the disk label. You can do this with LibreELEC but because you don't have a booting system you may have to put the sdcard in another PC (linux).

    1. I formatted and flashed again LE on the Samsung SD card. I inserted it first directly in RPi4 and started LE. This what I get using ssh:

    LibreELEC:~ # blkid
    /dev/mmcblk0: PTUUID="ee03917a" PTTYPE="dos"
    /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL_FATBOOT="LIBREELEC" LABEL="LIBREELEC" UUID="2410-0508" TYPE="vfat" PARTUUID="ee03917a-01"
    /dev/mmcblk0p2: LABEL="STORAGE" UUID="09814adf-0b3e-462b-ad3f-abd8815b9b92" TYPE="ext4" PARTUUID="ee03917a-02"
    /dev/loop0: TYPE="squashfs"
    LibreELEC:~ #

    2. I booted Ubuntu on my computer from a USB stick. I inserted the SD card in the reader and I opened the cmdline.txt from LibreELEC. it is looking like this:

    boot=UUID=2410-0508 disk=UUID=09814adf-0b3e-462b-ad3f-abd8815b9b92 quiet 

    3. I inserted the same SD card in the switcher and I started RPi. After the rainbow square the screen stays black for 20-30 seconds after I get this message:

    *** Error in mount_flash: mount_common: Could not mount UUID=2410-0508 ***
    ### Starting debugging shell for boot step: mount_flash... type exit to quit ###


    I just bought this switcher and I have a problem. My RPi4 is booting LE from both SD cards inserted in the switcher but only when LE is installed on a SanDisk 16GB and a Kingston 16GB.

    It doesn't boot from Samsung Evo+ 32GB. I even tried with only the Samsung card inserted in the switcher, in both positions, no boot.

    It starts booting LibreELEC, the LE logo is appearing on the screen and right after I get an error message related to mounting problems or something like that (I can take a picture with the error messages if needed).

    LE is booting from the same Samsung SD card if I insert the SD card directly in RPi (without using the switcher) so I know the SD card is good.

    I don't have other SD cards to test so I could not figure it out what is the problem. Anyone knows why it's happening this?

    Thank you!

    Well, the USB controller which RPi 4B has it's not the one of best ones regarding to compatibility with older USB devices - I have an old USB HUB, working everywhere except RPi 4B.

    I cannot say that is a compatibility problem with the RPi USB controller, the wireless keyboard is working just fine. The problem is that when I'm connecting it, this is affecting another USB device connected to RPi4. In my case, the USB sound output over S/PDIF is messed up.

    USB can be "fun", there are ton of odd devices out there, and especially audio (and video/webcam) devices can easily break if other devices consume too much bandwidth. Which is probably what the keyboard is doing (for whatever reason, probably because it has a somewhat broken USB configuration...).

    I did a few more tests, including with LibreELEC 10.0 BETA2 and the same thing happens. I tried even with a basic wireless mouse instead of the keyboard, with same outcome.

    To whom can I address this issue? I don't understand if this bug is related to RPi4 hardware/firmware, Kodi, LibreELEC or a combination of those.

    In meantime I discovered another annoying issue: CEC stops working on RPi4 if another CEC enabled device is connected to the TV. This puts me in a very difficult situation as I don't have any posibility to control Kodi on LibreELEC. If I connect the keyboard the sound gets broken over USB and I cannot use the TV remote because CEC is not working (I have another CEC enabled device connected on my TV). The only way to control Kodi is using a remote control app from my smartphone. I cannot also choose what to boot from PINN because I cannot use a mouse or a keyboard. I used to use the TV remote control for this but now I can't use it anymore because of the CEC issue. Now, that's a funny situation ...😄

    I have to admit that these issues are pretty frustrating, I wasn't expecting to this when I bought my RPi4. On my old RPi3 I don't have any of these problems, everything is working as is supposed to.

    Hi all!

    The problem is still present using RPi4 8GB and TV Samsung UE55NU8055.

    The HDMI cable is connected to the first RPi4's port, next to the USB-C power input.

    CEC is working only if the RPi4 is the only device connected to TV (so I can assume the HDMI cable is ok). If I add another CEC enabled device (Xiaomi Mi Box S in my case), CEC stops working on RPI4. If Mi-Box is on stand by with CEC enabled, CEC doesn't working on RPi4. If I disable CEC on Xiaomi or I unplug the power cord, CEC starts working again on RPi4.

    I'm using a RPi3 for more than three years in exactly the same setup and I never experienced this problem. I suppose this issue is a software problem related to the RPi4 and/or LibreELEC/Kodi.

    It would be nice to have this issue solved somehow, it has been a while since this problem was reported by a lot of users.

    Hi Hias! Believe it or not, I found the problem. You can see it in the attached picture.

    It's beyond my understanding, it didn't crossed my mind that this wireless keyboard could interfere with another USB device and cause such a problem. I used it in the last two years on my Rpi3 without any problems and when I bought the Rpi4 I've just hooked it in an USB port and left it there.

    A few minutes ago I said to try one more time the RPi4 from the ground, without HifiBerry Digi+ Pro attached and I also removed the keyboard dongle. I flashed Volumio in first place and when I tried to play a 96/24 FLAC the big surprise came up. It plays everything as it should on Volumio.

    I flashed LE 9.2.6, it's working perfect, no problems at all.

    I did a few tests and I tried all four RPi's USB ports with different combinations. Everytime I was inserting the keyboard dongle in the RPi the USB audio output was messed up.

    I don't know why this is happening and if this is normal but is good to know about this issue. Maybe it could be solved if it's related to the software.

    Thanks a lot for your effort in helping me and I'm really sorry for the time you lost but, as I said, it didn't crossed my mind.

    speaker-test -t sine -c 2 -r 44100 -F S24_3LE -b 200000 -p 50000 -D iec958:CARD=Audio,DEV=0

    Hi Hias, can I run something similar under RPiOS but with 96kHz/24-bit, to check if it's working?

    I wasn't able to solve this problem, I have issues using Volumio. I can only stream 44.1/16, I get an error message when I try streaming 96/24. I tried also to stream a mp3 and I received the same error, very strange. FLAC, WAV and ALAC 44.1/16 are working also.

    I tried MoOde as well, the same problem as with Volumio. I just don't get it... :(