10-24-2019, 02:20 AM
(This post was last modified: 10-24-2019, 02:32 PM by TheOldPresbyope.)
So then I wrote
As Tim noted in a later post, at this point you were working with an RPi4B. I've since found that the uas driver shows up in all my RPi4B systems, but not, for example, in my RPi3A+ system. Apparently it supports the new hardware in the 4. [ed: Ah, but I didn't have an SSD hanging on my RPi3A+ when I did the test. The following is still true.]
In any case it's not causing the knock-on effect I alluded to.
I have a USB-interfaced Khadas Tone Board connected to an RPi4B and it's enumerated as card 1, so hw: 1,0.
At this point, I'm out of ideas.
Regards,
Kent
Quote:Maybe that other USB device which showed up in the dmesg output caused ALSA to skip card 1.
...dmesg output...
[ 6.629683] usbcore: registered new interface driver uas
"UAS" stands for USB Attached SCSI, about which I know nothing I didn't just learn from a Google search. I don't know if or why it would confuse the ALSA enumeration process.
As Tim noted in a later post, at this point you were working with an RPi4B. I've since found that the uas driver shows up in all my RPi4B systems, but not, for example, in my RPi3A+ system. Apparently it supports the new hardware in the 4. [ed: Ah, but I didn't have an SSD hanging on my RPi3A+ when I did the test. The following is still true.]
In any case it's not causing the knock-on effect I alluded to.
I have a USB-interfaced Khadas Tone Board connected to an RPi4B and it's enumerated as card 1, so hw: 1,0.
At this point, I'm out of ideas.
Regards,
Kent
