Re: USB device fails to attach

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Tue, 5 Aug 2025 02:29:19 +0300
    From:        Valery Ushakov <uwe%stderr.spb.ru@localhost>
    Message-ID:  <aJFCT1rmaaBVIrFZ%snips.stderr.spb.ru@localhost>

  | I think you are misinterpeting.

You're right, I did ... and as it happens I have a similar (but
different) device I haven't used in years (this one has readers for
a bunch of different card types, but also 3 USB 2 ports).   I plugged
it into another USB2 hub I have sitting on my desk, and what the
kernel (11.99.1) did was:

[ 177296.465492] uhub20: port 1, device not enabled
[ 177296.842500] uhub20: port 1, device not enabled
[ 177297.242509] uhub31 at uhub20 port 1: vendor 1a40 (0x1a40) USB 2.0 Hub (0x0101), class 9/0, rev 2.00/1.11, addr 13
[ 177297.242509] uhub31: single transaction translator
[ 177297.243509] uhub31: 4 ports with 4 removable, self powered
[ 177297.957525] uhub31: device problem, disabling port 4
[ 177316.829922] uhub31: detached
[ 177316.829922] uhub31: at uhub20 port 1 (addr 13) disconnected
[ 177317.217930] uhub31 at uhub20 port 1: vendor 1a40 (0x1a40) USB 2.0 Hub (0x0101), class 9/0, rev 2.00/1.11, addr 13
[ 177317.217930] uhub31: single transaction translator
[ 177317.219932] uhub31: 4 ports with 4 removable, self powered
[ 177317.919945] uhub31: device problem, disabling port 4
[ 177318.371955] umass15 at uhub31 port 4 configuration 1 interface 0
[ 177318.372956] umass15: Generic (0x14cd) Mass Storage Device (0x125c), rev 2.00/3.00, addr 14
[ 177318.372956] umass15: using SCSI over Bulk-Only
[ 177318.391963] scsibus15 at umass15: 2 targets, 1 lun per target
[ 177318.540961] sd15 at scsibus15 target 0 lun 0: <Mass, Storage Device, \001\000\000\001> disk removable
[ 177318.540961] sd15: drive offline

uhub20 is (I am guessing) the hub I connected it to, uhub31 will be
a hub in this device for its 3 USB slots (which are empty) and the
attachment for the card reader (which looks to be port 4).

This suggests that NetBSD should be able to handle devices like this
at least - so again, I suspect that we just might not have the proper
code to handle your one.

Whether it works with a card installed I have no idea, I'm not sure
I still have any around to test.

kre