Raspberry Pi kernel update breaks RPi 5b USB 3 functions

ARM General system
1

Tonight’s update on the RPi 5b resulted in major USB problems.
The kernel update to linux-rpi-16k-6.6.39-1 was the problem.
Down grading kernel to linux-rpi-16k-6.6.37-2 fixed the problems.

I have not checked yet whether the Raspberry Pi 4b has the same problem.
linux-rpi-6.6.39-1 and linux-rpi-6.6.39-1
I will test the RPi 4b as quickly as possible and report back here.

I recommend not doing any updates to existing systems.

Also, since the RPi images do a
pacman -Syu
before adding your chose DE, installing the latest RPI image will fail.

Pudge

EDIT:
RPi 4b
Tested the RPi 4b with the linux-rpi-6.6.39-1 kernel and everything is OK.

RPi 5
On the RPi 5 with linux-rpi-16k-6.6.39-1 and connect a USB SSD to the USB 2 connector, and it works as expected.

Do the same with the USB SSD conneted to the USB 3 connector and it fails.

4 Likes
2

I have my pi400 hooked to usb with an ssd so i could update and see if it dies?

Edit:

The pi 400 has two usb 3.0 and one usb 2.0 and i have the ssd connected to one of the usb 3.0 ports. The mouse is connected to the usb 2.0 port. I updated and rebooted and it works as expected.

2 Likes
3

@ricklinux
Thank you for the feedback on the RPi 400. I had not gotten around to checking it yet.

It appears that the RPi 4b and RPi 400 are not affected by this update.

On the RPi 5 only the USB 3 ports are affected. The USB 2 ports are working albeit slower.

Pudge

2 Likes
4

I didn’t really do any testing but just reporting that i updated and my Pi400 did reboot and the drive is working. On the Pi400 i have to use a boot quirk for usb to work with my ssd on usb. I think it is because of the adapter as the ssd is in a external case with usb connection. So it maybe is that adapter? I’ve never tried any other sdd drives but this is how i got it working originally. I think it’s the same issue to get it to boot off of a usb thumb drive which i have never done. I used the ssd to install it by hooking it up to my desktop first and imaged it. Then i booted it off the Pi400 and installed EOS. Really haven’t used it that much.

Edit: I use usb-storage.quirks=0080:a001:u in /boot/cmdline.txt

0080:a001 i refers to the device i guess.

1 Like
5

I have a work around for this .
I added

linux-rpi-16k-6.6.37-2
linux-rpi-16k-headers-6.6.37-2

to the EndeavourOS repository in github.

Thus if you have your /etc/pacman.conf setup with the endeavouros repo listed first as:

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

[endeavouros]
SigLevel = PackageRequired
Include = /etc/pacman.d/endeavouros-mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

[alarm]
Include = /etc/pacman.d/mirrorlist

When updating, it will look for linux-rpi-16k-6.6.37-2 in the endevouros mirrors first and it will determine linux=rpi-16k is up to date.

When a new kernel becomes available, I can simply delete the linux-rpi-16k packages from the EnOS repos.

I have tested this on existing installs and it works.
This should also work with the existing rpi5 image and the server-rpi image.

Pudge

6

This problem has been fixed on linux-rpi-16k-6.6.40-1 which is available in the Archlinux ARM repositories.

Pudge

3 Likes
7

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.