On my Odroid M1 which used to run kernel 6.6.63 / armbian 24.11.3 noble from NVME, an update to kernel 6.12.9 arrived this morning.

Afterwards the machine failed to detect an external USB disk.

 

There are some messages in the logs of the 6.12.9 boot that look suspicious to me:

 

[    2.670354] rockchip-naneng-combphy fe820000.phy: error -ENOENT: failed to get phy reset
[    2.670392] rockchip-naneng-combphy fe820000.phy: probe with driver rockchip-naneng-combphy failed with error -2

[   20.458737] platform fc800000.sata: deferred probe pending: platform: supplier fe840000.phy not ready
[   20.458786] platform fcc00000.usb: deferred probe pending: platform: supplier fe820000.phy not ready
[   20.458812] platform fd000000.usb: deferred probe pending: platform: supplier fe830000.phy not ready
 

The USB disk shows up as  "ID 2537:1066 Norelsys NS1066" on the USB bus with the 6.6.63 kernel, no trace of its USB ID shows up with the newer kernel.

 

The ID coincides with the ones contained in the kernel command line:  usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

 

Does anybody know how to get the USB disk working with that newer kernel? I downgraded to 6.6.63 for now.

 

Regards

  Mathias


 

6.6.63-armbian-hardware-monitor.log 6.12.9-armbian-hardware-monitor.log

Edited January 17, 20251 yr by rmrf

For me USB works as expected:

Spoiler

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 480M
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 002: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 003, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 002: Dev 003, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 003: Dev 004, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 12M
        |__ Port 004: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 008.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M

 

I don't have any usbstoragequirks in place because my storage devices have controllers with properly working UAS support.
I'm currently at 6.13-rc1 and will stay there at least for another two weeks.

In the mean time there was another bunch of package updates, including kernel 6.12.11, armbian-firmware and more. The said "ID 2537:1066 Norelsys NS1066" USB disk is working again with the even newer kernel 6.12.11.

On 1/23/2025 at 8:09 PM, usual user said:

I'm currently at 6.13-rc1 and will stay there at least for another two weeks.

Ok, moved on to 6.14-rc1.
No regressions were observed, only current fixes were applied, and new features were enabled.
It may take some time for some of the fixes to trickle into new stable releases, but the new features are never officially backported.

 

Moved on to 6.15-rc1 (boot-analyze-odroid-m1.pdf).

No regressions were observed, only current fixes were applied, and new features were enabled.

Edited April 15, 20251 yr by usual user