On Tue, Oct 18, 2022 at 11:31 AM Peter Boy <pboy@xxxxxxxxxxxxx> wrote: > > Hi, > > > Am 14.10.2022 um 08:54 schrieb Peter Robinson <pbrobinson@xxxxxxxxx>: > > > > On Wed, Oct 12, 2022 at 6:14 PM Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > >> > >> Peter, > >> > >> Can you try adding modprobe.blacklist=phy_rockchip_inno_usb2 to the > >> kernel command line and see if that works for you? > > > > So I'm pretty sure this is now fixed with kernel 5.19.15-301.fc37 or > > 5.19.15-201.fc36 so if you could give it a test that would be fab. It > > should be stable into F-37 RSN but you could also deploy a default > > F-36 image and update to the F-36 kernel as I think you said F-36 GA > > worked. > > > > sorry for the delay, there was so much to do … > > Kernel 5.19.15-201.fc36 works superb. Everything I tested works without any issue on my nanopc-t4, including the NVMe board. > > Unfortunately, I couldn’t fetch a suitable image for f37, yet. > > Branch 20221017 includes an older kernel, the rawhide build of today failed (https://koji.fedoraproject.org/koji/taskinfo?taskID=93172623), and rc 1.1 includes an even older kernel. RC 1.1 should have had the fixed kernel because it was a blocker. Peter _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
