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 mor
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
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?
>>>
>>
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
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 thi
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
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
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.
Thank
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:
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 l
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
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
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=
13 matches
Mail list logo
