[lug] External USB Audio - not connecting driver

[D. Stimits]

> On 08/29/2020 8:25 PM Jed S. Baer <blug at jbaer.cotse.net> wrote:
> 
>  
> On Sat, 29 Aug 2020 20:14:45 -0600 (MDT)
> D. Stimits wrote:
> 
> > If you run "lsusb" you will see an ID. If you use that ID (I'll pretend
> > it is 1234:5678) for a verbose listing, what do you see? sudo lsusb -d
> > 1234:5678 -vvv | tee log_usb.txt
> 
> Lots of output. Is there something in particular I should look for?

Post the whole verbose lsusb. This will guarantee knowing about things like what class it is.

> > Just before connecting the USB, monitor "dmesg --follow". What shows up
> > as a result of connecting this?
> 
> There's no dmesg any longer. But this is in the syslog. (double-spaced for
> bad wrapping)
> 
> usb 1-4.1: new high-speed USB device number 20 using xhci_hcd
> 
> usb 1-4.1: New USB device found, idVendor=30be, idProduct=0100, bcdDevice=
> 1.02 usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> 
> usb 1-4.1: Product: I'm Fulla Schiit
Makes me wonder...but perhaps it is just tech humor?

> 
> usb 1-4.1: Manufacturer: Schiit Audio
> 
> input: Schiit Audio I'm Fulla Schiit
> as /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.3/0003:30BE:0100.0004/input/input17
At least part of the device enumerated as an input.

> 
> hid-generic 0003:30BE:0100.0004: input,hidraw1: USB HID v1.00 Device
HID is a human interface device, and covers keyboards, mice, so on. Probably buttons on this appear as a keyboard key and some program knows how to use this. Or perhaps a key binding needs to be set up.

> [Schiit Audio I'm Fulla Schiit] on usb-0000:00:14.0-4.1/input3
> 
> checking bus 1, device 20:
> "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1"
> 
> bus: 1, device: 20 was not an MTP device
> 
> upowerd[2113]: unhandled action 'bind'
> on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.3/0003:30BE:0100.0004
The system does not seem to know how to pick a driver to go with this. Sometimes you can set up an alias if a more standard chipset has been labelled with some custom name, but if this is not something standard, then you will probably need a new driver and it wouldn't be a "standard" class either (not every part of the device may need to work, e.g., a programmable keyboard might not have anything understanding how to program the keyboard despite the rest of it working). Similar to the rest of the devices which cannot bind.

> 
> upowerd[2113]: unhandled action 'bind'
> on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1/1-4.1:1.3
> 
> upowerd[2113]: unhandled action 'bind'
> on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.1
> 
> > Check out whatever you can from the "pavucontrol" command.
> 
> The device simply isn't there.

Yes, but does pavucontrol show any devices? If so, what does it show?

> 
> And now, neither is the on-board audio device.
Perhaps your new kernel lacks the full set of kernel modules. You will have your current system modules at:
/lib/modules/$(uname -r)/kernel/

...see if there might be some other older previous "uname -r" under "/lib/modules/", and if so, list the modules there and compare to modules present in the current "uname -r". It might offer a clue as to what is missing.

> 
> What's the price of Win10 these days?
:P

> 
> Oh, for info sake:
> $ uname -a
> Linux robinson 5.4.0-42-generic #46~18.04.1-Ubuntu SMP Fri Jul 10 07:21:24
> UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
> $ cat /etc/issue
> Linux Mint 19.3 Tricia

So 5.4.0-42-generic is your new "uname -r". Perhaps the old module directory exists and you can list what modules were present. The difference could indicate what is failing.

> 
> -- 
> All operating systems suck, but Linux just sucks less
>  - Linus Torvalds
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety