EMU-0202 seems to be broken again. Ssound card input fails.
Diagnostics:
alsamixer fails with
"cannot load mixer controls: Invalid argument"
I get this when I turn it on in dmesg:
Code:
[ 583.562286] usb 1-1.4: new high speed USB device using ehci_hcd and address 9
[ 583.662878] 9:1:1: endpoint lacks sample rate attribute bit, cannot set.
[ 583.663247] 9:1:2: endpoint lacks sample rate attribute bit, cannot set.
[ 583.663617] 9:1:3: endpoint lacks sample rate attribute bit, cannot set.
[ 583.663993] 9:1:4: endpoint lacks sample rate attribute bit, cannot set.
[ 583.664830] 9:1:5: endpoint lacks sample rate attribute bit, cannot set.
[ 583.665253] 9:1:6: endpoint lacks sample rate attribute bit, cannot set.
[ 583.665618] 9:1:7: endpoint lacks sample rate attribute bit, cannot set.
[ 583.666089] 9:1:8: endpoint lacks sample rate attribute bit, cannot set.
[ 583.666492] 9:1:9: endpoint lacks sample rate attribute bit, cannot set.
[ 583.666869] 9:1:10: endpoint lacks sample rate attribute bit, cannot set.
[ 583.667242] 9:1:11: endpoint lacks sample rate attribute bit, cannot set.
[ 583.667994] 9:2:1: endpoint lacks sample rate attribute bit, cannot set.
[ 583.668364] 9:2:2: endpoint lacks sample rate attribute bit, cannot set.
[ 583.668742] 9:2:3: endpoint lacks sample rate attribute bit, cannot set.
[ 583.669112] 9:2:4: endpoint lacks sample rate attribute bit, cannot set.
[ 583.669611] 9:2:5: endpoint lacks sample rate attribute bit, cannot set.
[ 583.669986] 9:2:6: endpoint lacks sample rate attribute bit, cannot set.
[ 583.670499] 9:2:7: endpoint lacks sample rate attribute bit, cannot set.
[ 583.670861] 9:2:8: endpoint lacks sample rate attribute bit, cannot set.
[ 583.671369] 9:2:9: endpoint lacks sample rate attribute bit, cannot set.
[ 583.671859] 9:2:10: endpoint lacks sample rate attribute bit, cannot set.
[ 583.672233] 9:2:11: endpoint lacks sample rate attribute bit, cannot set.
[ 583.695621] 9:1:1: endpoint lacks sample rate attribute bit, cannot set.
Eventually I'll get (here with 10 instead of 9, since I've repeated the test)
Code:
[ 784.732753] 10:2:1: usb_set_interface failed
[ 789.726801] 10:2:1: usb_set_interface failed
[ 794.720885] 10:2:1: usb_set_interface failed
[ 799.715979] 10:2:1: usb_set_interface failed
[ 804.709091] 10:2:1: usb_set_interface failed
[ 809.786982] 10:2:1: usb_set_interface failed
[ 814.780645] 10:2:1: usb_set_interface failed
[ 819.775501] 10:2:1: usb_set_interface failed
[ 824.768466] 10:2:1: usb_set_interface failed
[ 829.762546] 10:2:1: usb_set_interface failed
[ 835.880334] 10:2:1: usb_set_interface failed
[ 840.873402] 10:2:1: usb_set_interface failed
[ 845.867485] 10:2:1: usb_set_interface failed
[ 850.861581] 10:2:1: usb_set_interface failed
I'm on 2.6.35-26-generic-pae build from Ubuntu Maverick 10.10.
I wonder if this change is somehow related, either in that it has, or perhaps hasn't, happened.
The Audio Class v2 support code in 2.6.35 added checks for the
bInterfaceProtocol field. However, there are devices (usually those
detected by vendor-specific quirks) that do not have one of the
predefined values in this field, which made the driver reject them.
To fix this regression, restore the old behaviour, i.e., assume that
a device with an unknown bInterfaceProtocol field (other than
UAC_VERSION_2) has more or less UAC-v1-compatible descriptors.
http://amailbox.org/mailarchive/linu...0/9/18/4621391
Bookmarks