[Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Sean M. Pappalardo - D.J. Pegasus 
Hello.

I am testing a new USB audio interface called the Ebox44 by Electrix. 
It's based on a TUSB3200A chip. But when I plug it in, dmesg shows:

[  133.992032] usb 3-1: new full speed USB device using ohci_hcd and 
address 2
[  134.235928] usb 3-1: New USB device found, idVendor=200c, idProduct=1018
[  134.235935] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=4
[  134.235939] usb 3-1: Product: Ebox44
[  134.235942] usb 3-1: Manufacturer: ELECTRIX
[  134.235945] usb 3-1: SerialNumber: 20101128
[  134.236181] usb 3-1: configuration #1 chosen from 1 choice
[  137.792271] usbaudio: unit 2 not found!
[  137.792337] snd-usb-audio: probe of 3-1:1.0 failed with error -5
[  137.792403] usbcore: registered new interface driver snd-usb-audio

...and aplay -l does not list the device at all.

I'm using Linux kernel 2.6.32-5-686 and also tested on 2.6.39 and 3.0.0 
with the same exact results. I also tried:
- editing /etc/modprobe.d/alsa-base.conf: (rebooting after each change)
- changing options snd-usb-audio index= to 0
- commenting out the snd-usb-audio index line
- adding snd-intel8x0=-2 and 0 (the driver for my on-board sound card)
- modprobe -r snd_intel8x0 before plugging in the device
- editing /etc/modprobe.d/aliases.conf and adding aliases for 
snd-usb-audio to snd-card-0 and snd-intel8x0 to snd-card-1

Nothing helped. I got the same kernel error and the card is missing in 
aplay -l every time.

What else can I try?

Thank you very much for your time.

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist
http://www.mixxx.org/

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Nick Lidakis 
On Thu, Sep 22, 2011 at 02:53:32PM +0200, Sean M. Pappalardo - D.J. Pegasus 
wrote:
> Hello.
> 
> I am testing a new USB audio interface called the Ebox44 by Electrix. 
> It's based on a TUSB3200A chip. But when I plug it in, dmesg shows:
> 
> [  133.992032] usb 3-1: new full speed USB device using ohci_hcd and 
> address 2
> [  134.235928] usb 3-1: New USB device found, idVendor=200c, idProduct=1018
> [  134.235935] usb 3-1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=4
> [  134.235939] usb 3-1: Product: Ebox44
> [  134.235942] usb 3-1: Manufacturer: ELECTRIX
> [  134.235945] usb 3-1: SerialNumber: 20101128
> [  134.236181] usb 3-1: configuration #1 chosen from 1 choice
> [  137.792271] usbaudio: unit 2 not found!
> [  137.792337] snd-usb-audio: probe of 3-1:1.0 failed with error -5
> [  137.792403] usbcore: registered new interface driver snd-usb-audio


Looking at their web page (http://www.electrixpro.com/ebox44.html) it seems
as if you need to use drivers for Windows or Mac. Lookis like it's not USB
Audio Class 1 or 2 compliant.

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Daniel Mack 
On Thu, Sep 22, 2011 at 2:53 PM, Sean M. Pappalardo - D.J. Pegasus
 wrote:
> I am testing a new USB audio interface called the Ebox44 by Electrix.
> It's based on a TUSB3200A chip. But when I plug it in, dmesg shows:
>
> [  133.992032] usb 3-1: new full speed USB device using ohci_hcd and
> address 2
> [  134.235928] usb 3-1: New USB device found, idVendor=200c, idProduct=1018
> [  134.235935] usb 3-1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=4
> [  134.235939] usb 3-1: Product: Ebox44
> [  134.235942] usb 3-1: Manufacturer: ELECTRIX
> [  134.235945] usb 3-1: SerialNumber: 20101128
> [  134.236181] usb 3-1: configuration #1 chosen from 1 choice
> [  137.792271] usbaudio: unit 2 not found!
> [  137.792337] snd-usb-audio: probe of 3-1:1.0 failed with error -5
> [  137.792403] usbcore: registered new interface driver snd-usb-audio
>
> ...and aplay -l does not list the device at all.
>
> I'm using Linux kernel 2.6.32-5-686 and also tested on 2.6.39 and 3.0.0
> with the same exact results. I also tried:
> - editing /etc/modprobe.d/alsa-base.conf: (rebooting after each change)
>        - changing options snd-usb-audio index= to 0
>        - commenting out the snd-usb-audio index line
>        - adding snd-intel8x0=-2 and 0 (the driver for my on-board sound card)
> - modprobe -r snd_intel8x0 before plugging in the device
> - editing /etc/modprobe.d/aliases.conf and adding aliases for
> snd-usb-audio to snd-card-0 and snd-intel8x0 to snd-card-1
>
> Nothing helped. I got the same kernel error and the card is missing in
> aplay -l every time.
>
> What else can I try?

Can you send the output of "lsusb -v"?



Daniel

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Daniel Mack 
On Thu, Sep 22, 2011 at 4:05 PM, Sean M. Pappalardo - D.J. Pegasus
 wrote:
> Hello again.
>
> On 09/22/2011 03:59 PM, Daniel Mack wrote:
>>
>> Can you send the output of "lsusb -v"?
>
> Sure, here you go. The last line is a lie...the device draws power only from
> the USB bus.

And there are more lies in the descriptor set, as it references a
baSourceID "2" which is not defined. So the driver is perfectly right
which its complaint.

You can probably hack your way around this with something like the
following patch.

diff --git a/sound/usb/mixer.c b/sound/usb/mixer.c
index cdd19d7..ca17a35 100644
--- a/sound/usb/mixer.c
+++ b/sound/usb/mixer.c
@@ -1876,6 +1876,9 @@ static int parse_audio_unit(struct mixer_build
*state, int unitid)
if (test_and_set_bit(unitid, state->unitbitmap))
return 0; /* the unit already visited */

+   if (state->chip->usb_id == USB_ID(0x200c, 0x1018) && unitid == 2)
+   return 0;
+
p1 = find_audio_control_unit(state, unitid);
if (!p1) {
snd_printk(KERN_ERR "usbaudio: unit %d not found!\n", unitid);

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Daniel Mack 
On Thu, Sep 22, 2011 at 3:58 PM, Nick Lidakis  wrote:
> On Thu, Sep 22, 2011 at 02:53:32PM +0200, Sean M. Pappalardo - D.J. Pegasus 
> wrote:
>> Hello.
>>
>> I am testing a new USB audio interface called the Ebox44 by Electrix.
>> It's based on a TUSB3200A chip. But when I plug it in, dmesg shows:
>>
>> [  133.992032] usb 3-1: new full speed USB device using ohci_hcd and
>> address 2
>> [  134.235928] usb 3-1: New USB device found, idVendor=200c, idProduct=1018
>> [  134.235935] usb 3-1: New USB device strings: Mfr=1, Product=2,
>> SerialNumber=4
>> [  134.235939] usb 3-1: Product: Ebox44
>> [  134.235942] usb 3-1: Manufacturer: ELECTRIX
>> [  134.235945] usb 3-1: SerialNumber: 20101128
>> [  134.236181] usb 3-1: configuration #1 chosen from 1 choice
>> [  137.792271] usbaudio: unit 2 not found!
>> [  137.792337] snd-usb-audio: probe of 3-1:1.0 failed with error -5
>> [  137.792403] usbcore: registered new interface driver snd-usb-audio
>
>
> Looking at their web page (http://www.electrixpro.com/ebox44.html) it seems
> as if you need to use drivers for Windows or Mac. Lookis like it's not USB
> Audio Class 1 or 2 compliant.

Windows never had a working generic USB audio implementation, and it
still doesn't. Hence sound card vendors are in the unforunate
situation that they have to roll their own Windows support anyway and
reinvent the wheel over and over again. And in that process, most
vendors don't care about real class compliancy and ship what ever
works for them. It's really sad how a useful standard is beaten to
death by crappy OS implementations.


Daniel

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Sean M. Pappalardo - D.J. Pegasus 


On 09/22/2011 04:23 PM, Daniel Mack wrote:
> And there are more lies in the descriptor set, as it references a
> baSourceID "2" which is not defined. So the driver is perfectly right
> which its complaint.

So the right way to fix it is to tell the manufacturer? I am in contact 
with them.

Thanks for your time.

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Daniel Mack 
On Thu, Sep 22, 2011 at 4:29 PM, Sean M. Pappalardo - D.J. Pegasus
 wrote:
>
>
> On 09/22/2011 04:23 PM, Daniel Mack wrote:
>>
>> And there are more lies in the descriptor set, as it references a
>> baSourceID "2" which is not defined. So the driver is perfectly right
>> which its complaint.
>
> So the right way to fix it is to tell the manufacturer? I am in contact with
> them.

No, this is pointless, as it would involve changing the firmware of
all devices. The only solution is to contribute to the thousands of
quirk mechanisms the driver already ships with and add yet another one
for this device. Did you try my patch?



Daniel

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-22 Thread Sean M. Pappalardo - D.J. Pegasus 
Hello again.

On 09/22/2011 03:59 PM, Daniel Mack wrote:
> Can you send the output of "lsusb -v"?

Sure, here you go. The last line is a lie...the device draws power only 
from the USB bus.

Bus 003 Device 002: ID 200c:1018
Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass0 (Defined at Interface level)
   bDeviceSubClass 0
   bDeviceProtocol 0
   bMaxPacketSize0 8
   idVendor   0x200c
   idProduct  0x1018
   bcdDevice0.03
   iManufacturer   1 ELECTRIX
   iProduct2 Ebox44
   iSerial 4 20101128
   bNumConfigurations  1
   Configuration Descriptor:
 bLength 9
 bDescriptorType 2
 wTotalLength  248
 bNumInterfaces  3
 bConfigurationValue 1
 iConfiguration  0
 bmAttributes 0x40
   (Missing must-be-set bit!)
   Self Powered
 MaxPower0mA
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   0
   bNumEndpoints   0
   bInterfaceClass 1 Audio
   bInterfaceSubClass  1 Control Device
   bInterfaceProtocol  0
   iInterface  0
   AudioControl Interface Descriptor:
 bLength10
 bDescriptorType36
 bDescriptorSubtype  1 (HEADER)
 bcdADC   1.00
 wTotalLength  142
 bInCollection   2
 baInterfaceNr( 0)   1
 baInterfaceNr( 1)   2
   AudioControl Interface Descriptor:
 bLength12
 bDescriptorType36
 bDescriptorSubtype  2 (INPUT_TERMINAL)
 bTerminalID 5
 wTerminalType  0x0101 USB Streaming
 bAssocTerminal  0
 bNrChannels 2
 wChannelConfig 0x0003
   Left Front (L)
   Right Front (R)
 iChannelNames   0
 iTerminal   0
   AudioControl Interface Descriptor:
 bLength12
 bDescriptorType36
 bDescriptorSubtype  2 (INPUT_TERMINAL)
 bTerminalID 3
 wTerminalType  0x0302 Headphones
 bAssocTerminal  0
 bNrChannels 2
 wChannelConfig 0x0003
   Left Front (L)
   Right Front (R)
 iChannelNames   0
 iTerminal   0
   AudioControl Interface Descriptor:
 bLength10
 bDescriptorType36
 bDescriptorSubtype  6 (FEATURE_UNIT)
 bUnitID 4
 bSourceID   3
 bControlSize1
 bmaControls( 0)  0x01
   Mute
 bmaControls( 1)  0x02
   Volume
 bmaControls( 2)  0x02
   Volume
 iFeature0
   AudioControl Interface Descriptor:
 bLength15
 bDescriptorType36
 bDescriptorSubtype  4 (MIXER_UNIT)
 bUnitID 6
 bNrInPins   3
 baSourceID( 0)  5
 baSourceID( 1)  4
 baSourceID( 2)  2
 bNrChannels 2
 wChannelConfig 0x0003
   Left Front (L)
   Right Front (R)
 iChannelNames   0
 bmControls 0x00
 iMixer  0
 junk at descriptor end: 00
   AudioControl Interface Descriptor:
 bLength10
 bDescriptorType36
 bDescriptorSubtype  6 (FEATURE_UNIT)
 bUnitID 7
 bSourceID   6
 bControlSize1
 bmaControls( 0)  0x01
   Mute
 bmaControls( 1)  0x02
   Volume
 bmaControls( 2)  0x02
   Volume
 iFeature0
   AudioControl Interface Descriptor:
 bLength 9
 bDescriptorType36
 bDescriptorSubtype  3 (OUTPUT_TERMINAL)
 bTerminalID 8
 wTerminalType  0x0301 Speaker
 bAssocTerminal  0
 bSourceID   7
 iTerminal   0
   AudioControl Interface Descriptor:
 bLength12
 bDescriptorType36
 bDescriptorSubtype  2 (INPUT_TERMINAL)
 bTerminalID 9
 wTerminalType  0x0603 Line Connector
 bAssocTerminal  1
 bNrChannels 2
 wChannelConfig 0x0003
   Left Front (L)
   Right Front (R)
 iChannelNames   0
 iTerminal

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2011-09-23 Thread Sean M. Pappalardo - D.J. Pegasus 


On 09/22/2011 04:33 PM, Daniel Mack wrote:
> contribute to the thousands of
> quirk mechanisms the driver already ships with and add yet another one
> for this device. Did you try my patch?

I did but got a CPU lockup when I plugged the device in. :S I'll see 
what the mfgr says since I don't think they've started shipping yet.

Thanks so much for your time!

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2012-01-16 Thread Sean M. Pappalardo - D.J. Pegasus 



On 09/22/2011 06:40 PM, Daniel Mack wrote:

The only solution is to contribute to the thousands of
quirk mechanisms the driver already ships with and add yet another one
for this device. Did you try my patch?


Not yet. I'm reading up on how to build ALSA now.


I would recommend to just build a recent kernel from the sources. All
the ALSA code is included in the tree there ...


OK, I finally got around to this using the 3.2 kernel source and I get 
the same problem:
Jan 16 17:50:53 8440p kernel: [   66.547352] usb 1-1.4.1: new full-speed 
USB device number 8 using ehci_hcd
Jan 16 17:50:53 8440p kernel: [   66.658712] usb 1-1.4.1: New USB device 
found, idVendor=200c, idProduct=1018
Jan 16 17:50:53 8440p kernel: [   66.658718] usb 1-1.4.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=4

Jan 16 17:50:53 8440p kernel: [   66.658722] usb 1-1.4.1: Product: Ebox44
Jan 16 17:50:53 8440p kernel: [   66.658726] usb 1-1.4.1: Manufacturer: 
ELECTRIX
Jan 16 17:50:53 8440p kernel: [   66.658729] usb 1-1.4.1: SerialNumber: 
20101128
Jan 16 17:50:58 8440p kernel: [   70.857346] snd-usb-audio: probe of 
1-1.4.1:1.0 failed with error -5
Jan 16 17:50:58 8440p kernel: [   70.857382] usbcore: registered new 
interface driver snd-usb-audio


and it doesn't show up in aplay -l. Let me know if you need more 
information.


Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2012-01-16 Thread Bill Unruh 
On Mon, 16 Jan 2012, Sean M. Pappalardo - D.J. Pegasus wrote:

>
>
> On 09/22/2011 06:40 PM, Daniel Mack wrote:
 The only solution is to contribute to the thousands of
 quirk mechanisms the driver already ships with and add yet another one
 for this device. Did you try my patch?
>>> 
>>> Not yet. I'm reading up on how to build ALSA now.
>> 
>> I would recommend to just build a recent kernel from the sources. All
>> the ALSA code is included in the tree there ...
>
> OK, I finally got around to this using the 3.2 kernel source and I get the 
> same problem:
> Jan 16 17:50:53 8440p kernel: [   66.547352] usb 1-1.4.1: new full-speed USB 
> device number 8 using ehci_hcd
> Jan 16 17:50:53 8440p kernel: [   66.658712] usb 1-1.4.1: New USB device 
> found, idVendor=200c, idProduct=1018
> Jan 16 17:50:53 8440p kernel: [   66.658718] usb 1-1.4.1: New USB device 
> strings: Mfr=1, Product=2, SerialNumber=4
> Jan 16 17:50:53 8440p kernel: [   66.658722] usb 1-1.4.1: Product: Ebox44
> Jan 16 17:50:53 8440p kernel: [   66.658726] usb 1-1.4.1: Manufacturer: 
> ELECTRIX
> Jan 16 17:50:53 8440p kernel: [   66.658729] usb 1-1.4.1: SerialNumber: 
> 20101128
> Jan 16 17:50:58 8440p kernel: [   70.857346] snd-usb-audio: probe of 
> 1-1.4.1:1.0 failed with error -5
> Jan 16 17:50:58 8440p kernel: [   70.857382] usbcore: registered new 
> interface driver snd-usb-audio
>
> and it doesn't show up in aplay -l. Let me know if you need more information.

Some usb cards require firmware to be loaded onto the card before it can work
as a sound card. Is that true of this card?

--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2012-01-16 Thread Sean M. Pappalardo - D.J. Pegasus 



On 01/16/2012 06:23 PM, Bill Unruh wrote:

Some usb cards require firmware to be loaded onto the card before it can
work
as a sound card. Is that true of this card?


It is not. If you look at the thread from September of last year 
(http://sourceforge.net/mailarchive/message.php?msg_id=28125705) you'll 
see that it reports a number of incorrect things in the lsusb output, 
causing the driver to reject it.


The manufacturer is going to do a new batch that do work correctly 
out-of-the-box in Linux, but they've already started shipping and 
selling these so a quirk will now be needed.


Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] USB audio device problem in ALSA 1.0.23

2012-02-08 Thread Sean M. Pappalardo - D.J. Pegasus 

Hello again.

On 09/22/2011 04:23 PM, Daniel Mack wrote:

You can probably hack your way around this with something like the
following patch.


I'm now running kernel 3.2.1 and tried the patch you gave but it didn't 
seem to help. I'm an ALSA newb but I've CC'ed Mark Hills (of xwax) who 
knows more about it. If you'd be so kind as to let us know more 
specifically what we should do, we would be very grateful.


FWIW, the manufacturer just sent me another device with supposedly fixed 
firmware, but I still get the following when I plug it in:


[54784.896722] usb 1-1.4.1: new full-speed USB device number 9 using 
ehci_hcd
[54785.006671] usb 1-1.4.1: New USB device found, idVendor=200c, 
idProduct=1018
[54785.006677] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=4

[54785.006681] usb 1-1.4.1: Product: Ebox44
[54785.006684] usb 1-1.4.1: Manufacturer: ELECTRIX
[54785.006686] usb 1-1.4.1: SerialNumber: 20101128
[54788.989330] usbaudio: unit 2 not found!
[54788.989375] snd-usb-audio: probe of 1-1.4.1:1.0 failed with error -5

Seems the new firmware didn't fix all of the issues. Here's the lsusb diff:

--- old.ebox2012-02-08 11:27:34.0 +0100
+++ new.ebox2012-02-08 11:26:09.0 +0100
@@ -1,4 +1,4 @@
-Bus 001 Device 010: ID 200c:1018
+Bus 001 Device 009: ID 200c:1018
 Device Descriptor:
 bLength18
 bDescriptorType 1
@@ -9,7 +9,7 @@
 bMaxPacketSize0 8
 idVendor   0x200c
 idProduct  0x1018
-bcdDevice0.03
+bcdDevice0.04
 iManufacturer   1 ELECTRIX
 iProduct2 Ebox44
 iSerial 4 20101128
@@ -21,8 +21,7 @@
 bNumInterfaces  3
 bConfigurationValue 1
 iConfiguration  0
-bmAttributes 0x40
-(Missing must-be-set bit!)
+bmAttributes 0xc0
 Self Powered
 MaxPower0mA
 Interface Descriptor:


I will continue working with the manufacturer, but at this point, I 
would like to get a quirk into ALSA anyway since a number of people have 
these things and want to use them in Linux. (And they're not 
field-flashable.)


Thank you all very much for your time!

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"
Mixxx Developer - Controller Specialist



smime.p7s
Description: S/MIME Cryptographic Signature
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user