Subject: Re: [linux-audio-user] Device for simple stereo dubbing?
From: Joseph Zitt (jzitt_AT_metatronpress.com)
Date: Fri Jun 20 2003 - 20:41:25 EEST
Clemens Ladisch wrote:
>>>"rmmod usb-uhci" and "modprobe uhci", then try to run lsusb again.
>>
>>OK, here's the output.
>
>
> No change to the "cannot get config descriptor" error, so I think this
> may be an error in your version of lsusb.
For what it's worth, I got the same error when trying to use the same
device on my laptop under Red Hat a while ago.
> Well, there are other ways to get the descriptors. Please post the
> output of "od -t x1 /proc/bus/usb/001/003" (003 is the device number).
[root_AT_localhost Documents]# od -t x1 /proc/bus/usb/001/003
0000000 12 01 00 01 00 00 00 08 82 05 06 00 10 01 01 02
0000020 00 01 09 02 9f 02 03 01 00 80 f0 09 04 00 00 00
0000040 01 01 00 00 0a 24 01 00 01 4a 00 02 01 02 0c 24
0000060 02 01 01 01 00 02 03 00 00 00 0d 24 06 02 01 02
0000100 15 01 02 00 02 00 00 09 24 03 03 04 03 00 02 00
0000120 0c 24 02 04 02 02 00 02 03 00 00 00 09 24 03 07
0000140 01 01 00 04 00 09 04 01 00 00 01 02 00 00 09 04
0000160 01 01 01 01 02 00 00 07 24 01 01 00 01 00 0b 24
0000200 02 01 01 01 08 01 44 ac 00 09 05 04 09 38 00 01
0000220 00 00 07 25 01 00 02 00 02 09 04 01 02 01 01 02
0000240 00 00 07 24 01 01 00 01 00 0b 24 02 01 02 01 08
0000260 01 44 ac 00 09 05 04 09 70 00 01 00 00 07 25 01
0000300 00 02 00 02 09 04 01 03 01 01 02 00 00 07 24 01
0000320 01 00 01 00 0b 24 02 01 01 02 10 01 44 ac 00 09
0000340 05 04 09 70 00 01 00 00 07 25 01 00 02 00 02 09
0000360 04 01 04 01 01 02 00 00 07 24 01 01 00 01 00 0b
0000400 24 02 01 02 02 10 01 44 ac 00 09 05 04 09 e0 00
0000420 01 00 00 07 25 01 00 02 00 02 09 04 01 05 01 01
0000440 02 00 00 07 24 01 01 00 01 00 0b 24 02 01 01 03
0000460 18 01 44 ac 00 09 05 04 09 a8 00 01 00 00 07 25
0000500 01 00 02 00 02 09 04 01 06 01 01 02 00 00 07 24
0000520 01 01 00 01 00 0b 24 02 01 02 03 18 01 44 ac 00
0000540 09 05 04 09 50 01 01 00 00 07 25 01 00 02 00 02
0000560 09 04 02 00 00 01 02 00 00 09 04 02 01 01 01 02
0000600 00 00 07 24 01 07 00 01 00 14 24 02 01 01 01 08
0000620 04 11 2b 00 22 56 00 44 ac 00 80 bb 00 09 05 85
0000640 05 38 00 01 00 00 07 25 01 01 02 00 00 09 04 02
0000660 02 01 01 02 00 00 07 24 01 07 00 01 00 14 24 02
0000700 01 02 01 08 04 11 2b 00 22 56 00 44 ac 00 80 bb
0000720 00 09 05 85 05 70 00 01 00 00 07 25 01 01 02 00
0000740 00 09 04 02 03 01 01 02 00 00 07 24 01 07 00 01
0000760 00 14 24 02 01 01 02 10 04 11 2b 00 22 56 00 44
0001000 ac 00 80 bb 00 09 05 85 05 70 00 01 00 00 07 25
0001020 01 01 02 00 00 09 04 02 04 01 01 02 00 00 07 24
0001040 01 07 00 01 00 14 24 02 01 02 02 10 04 11 2b 00
0001060 22 56 00 44 ac 00 80 bb 00 09 05 85 05 e0 00 01
0001100 00 00 07 25 01 01 02 00 00 09 04 02 05 01 01 02
0001120 00 00 07 24 01 07 00 01 00 14 24 02 01 01 03 18
0001140 04 11 2b 00 22 56 00 44 ac 00 80 bb 00 09 05 85
0001160 05 a8 00 01 00 00 07 25 01 01 02 00 00 09 04 02
0001200 06 01 01 02 00 00 07 24 01 07 00 01 00 14 24 02
0001220 01 02 03 18 04 11 2b 00 22 56 00 44 ac 00 80 bb
0001240 00 09 05 85 05 50 01 01 00 00 07 25 01 01 02 00
0001260 00
0001261
Wow, that was immediately informative! :-)
>>>Please try
>>>a more recent ALSA version, there have been some changes to the
>>>snd-usb-audio driver since then.
>>
>>I'm a bit hesitant to do so, since this is the most recent version
>>supplied for Mandrake. I'm downloading an alsa-driver-0.9.4-fr2 RPM for
>>i386 from rpmfind, though I'm unclear as to whether it would be better
>>to download the source RPM and build from that instead.
>
>
> There's no reason not use the binary RPM, if it works.
OK, I'm trying it, but getting into a dependency tangle, apparently over
some configuration files:
[root_AT_localhost Documents]# ls alsa
alsa-driver-0.9.4-fr2.i386.rpm alsa-tools-0.9.4.tar.bz2
alsa-lib-0.9.4-fr1.i386.rpm alsa-utils-0.9.4-fr1.i386.rpm
[root_AT_localhost Documents]# rpm -Uvh alsa*.rpm
Preparing... ###########################################
[100%]
file /usr/lib/libasound.so.2.0.0 from install of alsa-lib-0.9.4-fr1
conflicts with file from package libalsa2-0.9.0-0.14rc7.1mdk
file /usr/share/alsa/alsa.conf from install of alsa-lib-0.9.4-fr1
conflicts with file from package libalsa-data-0.9.0-0.14rc7.1mdk
file /usr/share/alsa/cards/CMI8738-MC6.conf from install of
alsa-lib-0.9.4-fr1 conflicts with file from package
libalsa-data-0.9.0-0.14rc7.1mdk
file /usr/share/alsa/cards/CS46xx.conf from install of
alsa-lib-0.9.4-fr1 conflicts with file from package
libalsa-data-0.9.0-0.14rc7.1mdk
file /usr/share/alsa/cards/EMU10K1.conf from install of
alsa-lib-0.9.4-fr1 conflicts with file from package
libalsa-data-0.9.0-0.14rc7.1mdk
file /usr/share/alsa/cards/ICE1712.conf from install of
alsa-lib-0.9.4-fr1 conflicts with file from package
libalsa-data-0.9.0-0.14rc7.1mdk
file /usr/share/alsa/cards/ICE1724.conf from install of
alsa-lib-0.9.4-fr1 conflicts with file from package
libalsa-data-0.9.0-0.14rc7.1mdk
file /usr/share/alsa/cards/VIA8233A.conf from install of
alsa-lib-0.9.4-fr1 conflicts with file from package
libalsa-data-0.9.0-0.14rc7.1mdk
[root_AT_localhost Documents]#
The latest RPM for libalsa-data that I've found is
libalsa-data-0.9.2-5mdk.i586.rpm
Trying that I get:
[root_AT_localhost Documents]# rpm -Uvh alsa*.rpm
libalsa-data-0.9.2-5mdk.i586.rpm
error: failed dependencies:
libalsa2 = 0.9.2 is needed by libalsa-data-0.9.2-5mdk
[root_AT_localhost Documents]#
This archive was generated by hypermail 2b28 : Fri Jun 20 2003 - 20:48:49 EEST