Broken kernel USB drivers for RPI4 rev 1.5 with VIA chip

qrp73 commented 1 year ago

Just intalled latest bookworm image from scratch with apt update && apt upgrage. And there is still present USB drivers bug which was fixed for beta version rpi-6.1.y (pulls/5642). See link: https://forums.raspberrypi.com/viewtopic.php?t=357473#p2143222

This fix is missing from current bookworm release with all latest updates (6.1.0-rpi4-rpi-v8). RTLSDR dongle don't works:

$ rtl_test
Found 1 device(s):
  0:  Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
No supported tuner found
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
Enabled direct sampling mode, input 1
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
Supported gain values (1): 0.0 
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
WARNING: Failed to set sample rate.
rtlsdr_demod_write_reg failed with -7
rtlsdr_demod_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_write_reg failed with -7

This bug was fixed for bullseye, but again appears in bookworm beta (for kernel rpi-6.1.y). It was fixed in bookworm beta, but appears again in bookworm release. So it seems something is wrong with software lifecycle, because it removes bug fix again and again and bug appears again and again...

qrp73 commented 1 year ago

Here is the patch for this issue from bullseye raspi os: https://github.com/P33M/linux/commit/fd915cc0176bb0c04281f6c01689445a6cac0dfd

And here is discussion with some details: https://github.com/raspberrypi/linux/issues/3060

Here is tested fix for this issue for bookworm beta: pulls/5642. But this fix is missing from current image and updates.

popcornmix commented 1 year ago

Yes, there hasn't been a stable (apt) kernel update yet. It will happen soon. For now, you need to use rpi-update to get the fix.

qrp73 commented 1 year ago

here is report that this issue also affect USB HDD devices: https://forums.raspberrypi.com/viewtopic.php?t=357879#p2146182

The pull request sudo rpi-update pulls/5642 solves it for USB HDD, the same as for RTLSDR USB dongle

CRGer commented 1 year ago

Hey @popcornmix, do you know when the next stable (apt) update will be? And if not where I can track if the PR #5462 is included in apt? The use of rpi-update is unfortunately not possible for me, because other packages had problems with it. Or is there another workaround available? Thanks!

qrp73 commented 1 year ago

@CRGer, it seems that they published it today. I just tried apt update && apt upgrade, at a glance works ok and the issue looks like solved. But needs to be tested on clean bookworm install, because my system previously was updated to 6.6, so the test is not clean

CRGer commented 1 year ago

Tried it on a clean install, the issue is definitely still present. But I have the latest release of Pi OS installed, where the following is used (extract from change notes), so might be different for you: " Switched from raspberrypi-kernel to Debian-based kernel packaging (linux-image-rpi-)

Switched from raspberrypi-bootloader to Debian based firmware packaging (raspi-firmware)"

popcornmix commented 1 year ago

It’s not in apt yet. We added it to an internal repo and discovered a regression that caused an issue with reboot on pi4 so that is being investigated.

But it will be out once that is resolved, hopefully in a day or two.

eric1tran commented 1 year ago

Hi @popcornmix , do you have an estimated date when a new Raspberry Pi OS will be released, which presumably has this fix in?

ghollingworth commented 1 year ago

We're intending on making a new release next week.

YipYup commented 1 year ago

For what it's worth, this issue seems present also on the latest official Ubuntu Server 22.04.3 LTS aarch64 (arm64), after updating to the current Kernel, 5.15.0-1042-raspi from 5.15.0-1034-raspi.

Symptoms:

root@hostname:~# rtl_test
Found 2 device(s):
  0:  Nooelec, NESDR SMArt v5, SN: 00000978
  1:  Nooelec, NESDR SMArt v5, SN: 00001090

Using device 0: Generic RTL2832U OEM
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7
rtlsdr_read_reg failed with -7
rtlsdr_write_reg failed with -7

root@hostname:~# journalctl -r -g "usb"

Nov 02 15:55:14 hostname kernel: usb 1-1.2: reset high-speed USB device number 4 using xhci_hcd
Nov 02 15:55:14 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:54:58 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:54:53 hostname kernel: usb 1-1.2: reset high-speed USB device number 4 using xhci_hcd
Nov 02 15:54:53 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:54:37 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:54:32 hostname kernel: usb 1-1.2: reset high-speed USB device number 4 using xhci_hcd
Nov 02 15:32:11 hostname kernel: dvb_usb_v2: 'Realtek RTL2832U reference design:1-1.1' successfully deinitialized and disconnected
Nov 02 15:32:10 hostname kernel: usbcore: deregistering interface driver dvb_usb_rtl28xxu
Nov 02 15:31:45 hostname kernel: usb 1-1.2: reset high-speed USB device number 4 using xhci_hcd
Nov 02 15:31:45 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:31:29 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:31:24 hostname kernel: usb 1-1.2: reset high-speed USB device number 4 using xhci_hcd
Nov 02 15:31:24 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:31:08 hostname kernel: usb 1-1.2: device descriptor read/64, error -110
Nov 02 15:31:03 hostname kernel: usb 1-1.2: reset high-speed USB device number 4 using xhci_hcd

Env:

root@hostname:~# uname -a
Linux hostname 5.15.0-1042-raspi #45-Ubuntu SMP PREEMPT Thu Oct 12 09:20:16 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

root@hostname:~# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

YipYup commented 1 year ago

Following up on my comment above, reverting to linux-image-5.15.0-1040-raspi from linux-image-5.15.0-1042-raspi fixed the issue for me.

I manually reinstalled the older kernel with apt install linux-image-5.15.0-1040-raspi and then ran
apt purge linux-image-5.15.0-1042-raspi, answered no to continue removing, then ran
update-initramfs -u immediately after, and finally rebooted next
reboot

It seems that this issue is caused by changes upstream. https://github.com/raspberrypi/linux/pull/5642 https://github.com/raspberrypi/linux/issues/3060

qrp73 commented 1 year ago

not relevant anymore

CRGer commented 1 year ago

Hi @qrp73 why is this not relevant anymore? Was it fixed and is included in apt-get? If no, please keep it open. Others have the issue as well. Thank you!

qrp73 commented 1 year ago

I decided to quit from rpi community, I'm tired of censorship and bullying from rpi staff. If it still actual for you, you can open your issue. I don't want to deal with rpi anymore.

JamesH65 commented 1 year ago

Still appears to be relevant.

popcornmix commented 1 year ago

why is this not relevant anymore? Was it fixed and is included in apt-get?

Yes, I believe so. #5642 is now in apt kernel.

pelwell commented 1 year ago

@qrp73 I was saddened to hear that you've experienced censorship and bullying. I don't know the incidents to which you are referring, but I have seen that your alter ego has been banned on the forums. After questioning, the moderator concerned said they had received a few complaints - again, I've not seen any examples of the complaints or what might have triggered them - but that in hindsight they may have reacted hastily.

I believe you have been unbanned, and I hope you reconsider your decision - you're clear, detailed bug reports have been very helpful.

JamesH65 commented 1 year ago

It also might be worth mentioning that many of the forum moderators are not actually employees of Raspberry Pi. If you have a problem with anything on the forum, please report the post and a staff member of Raspberry Pi will investigate; as has happened in this case.

qrp73 commented 1 year ago

@JamesH65, @pelwell I already reported it on raspberrypi.com and security@raspberrypi.com, but after 6 days there is no response, all my complaints were just ignored.

As I remember, the last thing that I wrote was a post that 27W PSU is not enough information to decide if it can be used with rpi and user needs to make sure that PSU has 5V output (which is precisely correct answer, because 27W PSU can have any voltage on the outpout and 12V 27W PSU can burn out rpi), but I see that this message was deleted and I was banned with reason "wrong, misleading and/or confusing posts".

From my point of view, banning user for correct and polite message looks very crazy. I believe there is a strong reason to leave places and communities where such behavior are practiced.

In any case thanks to all guys who helped me with issues.

pelwell commented 1 year ago

It's a shame that the actions of one private individual, not a Raspberry Pi employee, led to this, but do what you feel you have to do.

pelwell commented 1 year ago

P.S. You can email me at phil@raspberrypi.com, should you wish.

Joe-raspi commented 1 year ago

Hi, same problem here with Raspi 4 and SDR stick RTL2838UHIDIR

I upgraded fro 1042 to kernel 5.15.0-1043-raspi today but still no improvement. Same symptoms as shown above by YipYup.

With 1041 everything worked perfectly.

cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy

Joe

6by9 commented 1 year ago

Hi, same problem here with Raspi 4 and SDR stick RTL2838UHIDIR

I upgraded fro 1042 to kernel 5.15.0-1043-raspi today but still no improvement. Same symptoms as shown above by YipYup.

With 1041 everything worked perfectly.

cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy

This repo is specifically for issues about Raspberry Pi OS Bookworm release, not other distributions.

Raspberry Pi OS has moved off the 5.15 kernel in March 2023, and no commits have been made since Feb 8th 2023. If Ubuntu have released a new 5.15 kernel, then that is based on their own changes, not Raspberry Pi's.

This issue was fixed on our 6.1 tree via https://github.com/raspberrypi/linux/pull/5642, but I'm not sure it's hit a stable kernel release yet.

popcornmix commented 1 year ago

This issue was fixed on our 6.1 tree via https://github.com/raspberrypi/linux/pull/5642, but I'm not sure it's hit a stable kernel release yet.

It should be in stable. apt is: Linux version 6.1.0-rpi6-rpi-v8 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2 (2023-10-27)

which is newer than that commit. The source linux tree tag stable_20231030 also includes the commit.

Joe-raspi commented 1 year ago

Thanks a lot for feedback. So I will have to place the bug at another place or try a newer kernel ...

mattfox27 commented 12 months ago

following, same issue RPI4

mattfox27 commented 12 months ago

apt get rtl_4

Hi, same problem here with Raspi 4 and SDR stick RTL2838UHIDIR

I upgraded fro 1042 to kernel 5.15.0-1043-raspi today but still no improvement. Same symptoms as shown above by YipYup.

With 1041 everything worked perfectly.

cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy

Joe

Did you ever figure this out? I have the same issue

Joe-raspi commented 12 months ago

Hi,

Am 03.12.23 um 17:45 schrieb Matt Klimmer:

apt get rtl_4

Hi, same problem here with Raspi 4 and SDR stick RTL2838UHIDIR

I upgraded fro 1042 to kernel 5.15.0-1043-raspi today but still no improvement. Same symptoms
as shown above by YipYup.

With 1041 everything worked perfectly.

cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu"
VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu
ID_LIKE=debian HOME_URL="https://www.ubuntu.com/ <https://www.ubuntu.com/>"
SUPPORT_URL="https://help.ubuntu.com/ <https://help.ubuntu.com/>"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/ <https://bugs.launchpad.net/ubuntu/>"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy
<https://www.ubuntu.com/legal/terms-and-policies/privacy-policy>" UBUNTU_CODENAME=jammy

Joe

Did you ever figure this out? I have the same issue

Not yet, sorry.

My observations:

I have a RTL2832 stick and one older Noxon for reference (but with less sensitivity)

Both sticks are running well with openSUSE Leap 15.4 and 15.5 (x64 platform) On Tumbleweed RTL2832 is unusable.

Things were getting more worse: As I started this thread the Noxon worked stable with Ubuntu on Raspi, kernel 5.15.0-1043-raspi, the RTL2832 only worked the first time after plugging it in.

Some updates later (firmware?) both sticks don't work at all now :-(

So I will try to open a ticket at bugzilla next week. (But this would mean starting my project from scratch in case the problem can be solved for TW)

Joe

Joe-raspi commented 11 months ago

Hi Matt,

bug report is open:

https://bugzilla.opensuse.org/show_bug.cgi?id=1217860

Maybe you want to comment it.

Joe

Am 03.12.23 um 17:45 schrieb Matt Klimmer:

apt get rtl_4

Hi, same problem here with Raspi 4 and SDR stick RTL2838UHIDIR

I upgraded fro 1042 to kernel 5.15.0-1043-raspi today but still no improvement. Same symptoms
as shown above by YipYup.

With 1041 everything worked perfectly.

cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS" PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu"
VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu
ID_LIKE=debian HOME_URL="https://www.ubuntu.com/ <https://www.ubuntu.com/>"
SUPPORT_URL="https://help.ubuntu.com/ <https://help.ubuntu.com/>"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/ <https://bugs.launchpad.net/ubuntu/>"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy
<https://www.ubuntu.com/legal/terms-and-policies/privacy-policy>" UBUNTU_CODENAME=jammy

Joe

Did you ever figure this out? I have the same issue

raspberrypi / bookworm-feedback

Broken kernel USB drivers for RPI4 rev 1.5 with VIA chip #83

Symptoms:

Env: