Posts by ghtester

Unfortunately, most likely your SD card is dead / out of life...

In such cases sometimes the SD card becomes read only and it's not possible to reformat it anymore.

The same issue as described in post #1 encountered even after upgrade LE 11 Nightly to latest version with kernel 6.0.0.

But it looks better after RPi 4B bootloader upgrade to latest version dated 2022-10-12 (so far the issue did not appear). Needs more time than 2 days to be sure it's OK but I hope it is as the bootloader upgrade is related with USB.

rpi-eeprom/release-notes.md at master · raspberrypi/rpi-eeprom

Installation scripts and binaries for the closed sourced Raspberry Pi 4 EEPROMs - rpi-eeprom/release-notes.md at master · raspberrypi/rpi-eeprom

github.com

Edit - unfortunately just encountered the same issue during the Timeshift seeking...

132659.396070] rpivid feb10000.codec: Missing DPB ent for col

[132659.396486] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[132659.397525] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[132659.397926] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[132741.643836] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[132745.963354] usb 1-1.1.3: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110

[132748.096711] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132750.230054] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132752.363375] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132754.496876] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132756.630196] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132758.763513] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132760.897088] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132763.030241] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132765.163614] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132767.297317] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132769.430459] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132769.430506] usb 1-1.1.3: dvb_usb_v2: streaming_ctrl() failed=-110

[132771.567012] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132773.697214] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132775.830518] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132777.963920] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132780.097282] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132782.230707] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132784.363937] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132784.492153] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[132784.492181] rpivid feb10000.codec: Missing DPB ent for col

[132786.497305] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132788.630730] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132790.767868] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132792.898907] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132795.030814] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132797.164161] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132799.297729] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132801.430876] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132803.564258] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132805.697712] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132807.831082] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132809.964359] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132812.097746] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132814.231211] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132816.367830] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132818.498810] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132820.631232] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132822.764744] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132824.898026] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132827.031405] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132829.164778] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132831.298072] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132833.431437] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132835.564812] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132837.698184] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132839.831758] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132841.967738] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132844.098298] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132846.231745] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132848.365170] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132850.498415] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132852.631793] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132854.765229] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132856.898649] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132859.031897] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132861.165333] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[132863.301984] usb 1-1.1.3: dvb_usb_v2: usb_bulk_msg() failed=-110

BTW. looking around the error message, I have found this: https://github.com/raspberrypi/linux/issues/3809

So it looks the old issue is back in new kernel releases...

Didn't you try the sync command before unplugging the USB storage?

See for instance this webpage: https://www.kaper.com/notes/linux-sy…or-copy-to-usb/

In general, both Tvheadend Server Addons 4.2 and 4.3 have their own folder so the settings are independent as well.

You can install both versions at the same time but always have only one of them enabled.

You may perhaps copy the configuration files from 4.2 to 4.3 but I did not try it so no experience to share...

Then you may play with audio_pwm_mode option.

Look here: RE: Composite Video in LE10 on RPi4

Look here: RE: Unable to output analog audio out of Raspberry Pi 4 !

I would try adding hdmi_force_hotplug=1 to /flash/config.txt file. And if it does not help, see the post #6.

It's hard to say but it looks the current HDMI detection procedure needs to be optimized a bit.

So I would try to configure the LE to work with some fixed monitor settings, to boot properly and work even without monitor attached.

One way could be through kernel boot parameters (look here: Force HDMI OUTPUT ), the second way (which helped me when I permanently lost HDMI audio on my old monitor after some recent LE 11 Nightly update) could perhaps be the EDID save from working configuration (working monitor attached) as outlined above. Hope this could help. Try to run getedid create at home before travelling and you'll see... If it does not help, you may remove it through getedid delete and then reboot LE.

BTW. Maybe it could be useful for developers to have the edid files from not-working configurations to analyze.

If i am not mistaken, the edid create saves the edid-HDMI-A-1.bin file to /storage/.config/firmware/edid/ folder (and also edid-HDMI-A-2.bin for devices with two HDMI ports like RPi 4B etc.).

And it's possible to look what's there with:

edid-decode /storage/.config/firmware/edid/edid-HDMI-A-1.bin

With working monitor connected, run getedid create command from SSH console and then try connecting with non-working monitors.

OK, I understand. I'll try to find a method to reproduce the issue. I don't know if there are some USB related kernel parameters to tune up which I could try...

Hello, thanks for the feedback, I can't confirm as I don't plan reverting, hopefully the issue will disappear in future with some kernel update.

The bad thing is I can't reproduce it easily whenever I want even on the current LE release, because it's more or less a random trouble.

I believe it could be a kernel issue as I have found some similar issue reports across platforms, for instance like these:

Linux 5.15.32 sometimes failing to initialize USB · Issue #5064 · raspberrypi/linux

Describe the bug Hi! I have built a yocto-image for my CM4, and I'm using linux 5.15.32 from this repository. The CM4's USB2 lines are connected to a…

github.com

[Bug 215095] New: USB ehci error -110 and soft lockup on kernel 5.15.4 as kvm guest

Keyboard & mouse stop working with kernel Ubuntu-5.13.0-22.22-387-g0fc979747dec - xhci: Fix command ring pointer corruption while aborting a command

tl;dr: Keyboard & mouse don't work with certain kernels. Not asking for a workaround, I already have that. Using git bisect, I have identified the exact…

askubuntu.com

I am experiencing a serious issues related to USB layer on two RPi 4B devices running LE 11 Nightly builds, currently with 5.15.61 Linux kernel.

The issue often happens when the DVB-T2 tuner is switched to another channel, sometimes after moving the timeshift point.

Then sometimes the communication with USB devices is stopped and can be restored only after switching the RPi's USB ports off and on (with uhubctl app).

Tested with both USB2 and USB3 ports - ihe issue is the same, also with USB device connected through USB hub. In past the same HW configuration (DVB-T2 adapter connected directly to USB2 port) worked stable.

1) RPi 4B/4GB, DVB-T2 USB adapter MyGica, LE 11 Nightly running from microSD card

[169263.505276] rpivid feb10000.codec: PPS changed

[169271.569528] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[169271.569554] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.569569] rpivid feb10000.codec: Missing DPB ent for col

[169271.569892] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.569908] rpivid feb10000.codec: Missing DPB ent 2, timestamp=0, index=-1

[169271.570661] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.570682] rpivid feb10000.codec: Missing DPB ent 2, timestamp=0, index=-1

[169271.571438] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.582707] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.582743] rpivid feb10000.codec: Missing DPB ent for col

[169271.583107] rpivid feb10000.codec: Missing DPB ent 2, timestamp=0, index=-1

[169271.583979] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.584007] rpivid feb10000.codec: Missing DPB ent for col

[169271.606637] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[169271.606683] rpivid feb10000.codec: Missing DPB ent for col

[169271.617299] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.622094] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169271.623300] rpivid feb10000.codec: Missing DPB ent 2, timestamp=0, index=-1

[169274.794931] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[169278.516161] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[169278.516191] rpivid feb10000.codec: Missing DPB ent for col

[169278.516705] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169278.517243] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169278.517756] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[169283.314023] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[169288.378889] usb 1-1.4.3: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110

[169290.512245] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169292.645613] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169294.779013] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169296.912419] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169299.045814] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169301.179150] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169303.312507] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169305.445876] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169307.579278] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169309.712668] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169311.849398] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169313.979432] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169313.979458] usb 1-1.4.3: dvb_usb_v2: streaming_ctrl() failed=-110

[169316.112800] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169318.249541] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169320.379557] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169322.512963] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169324.646339] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169326.779696] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169328.913097] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

[169331.046493] usb 1-1.4.3: dvb_usb_v2: usb_bulk_msg() failed=-110

2) RPi 4B/2GB - DVB-T2 USB adapter Astrometa, LE 11 Nightly running from USB/SATA adapter + SATA HDD

With this configuration the USB issue does not happen so often but leads to complete LE crash as it is running from USB/SATA adapter.

It seems the issue is related with 5.15 kernel revision which brought the unstability to USB layer.

Unfortunately I don't own this kind of HW so can't offer any personal experience. So just some links to posts of another users with the same / similar issue:

Posts by rua1 - LibreELEC Forum

Post

RE: Unofficial LE for RK356x RK3328\RK3399 RK3588(s) RK3576

[…]

No, nvme don't found on this stage. Message on TV screen obtained. ls /dev is without nvme, only mmcblk1 and 2.

nvme found only after run kodi with version 20200201 . With versions 20200205 and 20200127 nvme not found never. If I copy fdt file from version 0201 to 0205, then with it nvme is also present after run kodi.

rua1

February 11, 2020 at 4:16 PM

Thread

Rock Pi 4 PCIe NVMe M.2 SSD not accessible

Samsung 970 Evo connected to the M.2 slot is not mounted. I have also tested a m.2 ssd from Intel, same problem, I can't access the drive.

If I connect the M.2 SSD via USB 3.0 it works fine.
Any ideas how to fix the problem? Or have I to wait for a new build from LibreElec?

Bier2020

April 4, 2019 at 8:36 PM

Perhaps some of developers could give a comment on this.

If the image was written correctly, perhaps your USB/HDD adapter is not supported by kernel.

Try another imaging tool to confirm the issue still persist, also check if the FAT partition is active.

You may also test the latest LE 11 Nightly build from test.libreelec.tv and if the issue is still the same, use another USB/HDD adapter.

Or maybe with autostop.sh you can initiate a shutdown script on your NAS with some delay (to reflect LE reboot time) and use autostart.sh to stop it.

BTW. you can have installed both 4.2 and 4.3 at the same time (of course just one version enabled and the second one disabled) as each version has its own folder.

So it's easy to experiment with copying setting files.

So you probably restored the same what you deleted...

Try to read this thread and follow the adviced steps (valid for safe mode after bootloop):

Post

LibreELEC-RPi2.arm-11.0-nightly-20220723-Boot loop after Kodi image

After updating from "LibreELEC-RPi2.arm-11.0-nightly-20220721-06fd018.img" to "I only get a boot loop.
I'm back to an older version.
My WiFi stick "EDIMAX -EW-7612UAn V2" hasn't been recognized for a long time. It still worked with the LibreELEC V10 final.

Malocher

July 23, 2022 at 5:39 PM