[Alsa-user] USB audio device problem in ALSA 1.0.23
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
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
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
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
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
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
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
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
[Alsa-user] Help Regarding setting /etc/asound.conf
Hi, I am using a linux variant, i586-linux and have the following capture hardware device: List of CAPTURE Hardware Devices card 0: Audio [CS5535 Audio], device 0: CS5535 Audio [CS5535 Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 I will like to record from only one channel of the microphone input. When I use arecord -c1 option, it returns a high-pitched and noisy recording. I cannot figure out how to only extract 1 channel out of the 4 available channel inputs for microphones. Does anybody know how I can configure /etc/asound.conf to do that? I tried reading the documentation and use stuff like bindings, but it doesn't seem to work, giving me errors. Any help will be appreciated! Thanks, Jaedi -- 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
[Alsa-user] Problems configuring ALSA for my HDMI connection
Hello all, I recently set up a home theater PC running Ubuntu 11.04 Natty Narwhal. It is connected via HDMI to my Samsung receiver which supports 5.1 output (including PCM, Dolby Digital, and DTS). However, ALSA seems to think it is only a stereo device--sort of. If I run, for example, "speaker-test -c6", I get audio from the front left, center, and front right just fine, but audio from the rear left and rear right comes out the corresponding front channels instead. If I play a test 6-channel WAV file using aplay from the command line, I get very odd results (some channels not played at all, others on the wrong channel), whereas if I just double-click and open it using the default Ubuntu player, I get the front left/right/center fine with the rear channels on the fronts, same as speaker-test. I've spent many hours on IRC with the Pulse Audio people and haven't made any headway at all; it's not just something silly like "did you plug your speakers in?", so I'm getting very concerned at this point. I've attached the output from the alsa-info script, as well as a couple of other diagnostic results that some of the Pulse Audio people had asked for. Please let me know if anyone has any suggestions for how I can get ALSA to properly handle my HDMI output. Thanks, David alsa-info Description: Binary data amixer_c0 Description: Binary data eld Description: Binary data -- 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] Problems configuring ALSA for my HDMI connection
On Thu, Sep 22, 2011 at 07:28:37PM -0400, David O wrote: > Hello all, > > I recently set up a home theater PC running Ubuntu 11.04 Natty > Narwhal. It is connected via HDMI to my Samsung receiver which > supports 5.1 output (including PCM, Dolby Digital, and DTS). This wouldn't be a Samsung C560S, would it? I have that working just fine with also an Intel HDMI chipset. It's a different one, though. I do remember having played with pulseaudio once on my home audio system, and having things go wrong then. Did you try this without using pulseaudio at all? Just disable the daemon, and try again. I don't expect this to actually solve the problem, but it might. If that works, it's clearly pulseaudio at fault... -- The volume of a pizza of thickness a and radius z can be described by the following formula: pi zz a -- 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
