Re: testers for SB Extigy wanted

[Takashi Iwai <tiwai@suse.de>]

Hi Mark,

At Fri, 11 Oct 2002 09:36:59 -0500,
mark@undertone.org wrote:
> 
> I don't feel like spamming the list with newbie junk, but I still want
> to help as much as possible, so I'm just going to email you
> personally. If you think this stuff should still go to the list
> anyway, just say.

why not?  it contains full of useful information.

> I actually have two soundcards -- the onboard one (a cs4281) and the
> extigy. I'll just paste in all the info I can. I'm building from the
> cvs tree generically and firing it up from the included alsasound
> script. It's configured to have the cs4281 as card1 and usb-audio as
> card2 from modutils.
> 
> Here is everything syslog spits out at me when I start up alsa (the
> cant locate module stuff is obviously nothing, along with one or two
> other things, but I'll leave them in for completeness sake):
> 
> Oct 11 09:30:39 atrophy kernel: PCI: Found IRQ 10 for device 00:08.0
> Oct 11 09:30:39 atrophy kernel: usb.c: registered new driver snd-usb-audio
> Oct 11 09:30:40 atrophy kernel: ALSA ../alsa-kernel/usb/usbaudio.c:1662: 4:1:2 : unsupported format type 0

this should be harmless.  just ignored a bogus descriptor.
to be sure, could you send the output of "lsusb -v" for this device?


> Oct 11 09:30:40 atrophy kernel: ALSA ../alsa-kernel/usb/usbmixer.c:1104: cannot get min/max values for proc/ext unit

this happens sometimes.  usually it's ok.  the values will be fetched
later.

> Oct 11 09:30:40 atrophy modprobe: modprobe: Can't locate module snd-card-3
> Oct 11 09:30:40 atrophy modprobe: modprobe: Can't locate module snd-card-4
> Oct 11 09:30:40 atrophy modprobe: modprobe: Can't locate module snd-card-5
> Oct 11 09:30:40 atrophy modprobe: modprobe: Can't locate module snd-card-6
> Oct 11 09:30:40 atrophy modprobe: modprobe: Can't locate module snd-card-7

these are harmless, too.
you can avoid this by adding a module option to snd module such like

	options snd snd_cards_limit=2


> devfs looks like this:
> 
> atrophy:/dev/snd# pwd
> /dev/snd
> atrophy:/dev/snd# ls -l
> total 0
> crw-rw-rw-    1 root     root     116,   0 Dec 31  1969 controlC0
> crw-rw-rw-    1 root     root     116,  32 Dec 31  1969 controlC1
> crw-rw-rw-    1 root     root     116,  64 Dec 31  1969 controlC2
> crw-rw-rw-    1 root     root     116,  96 Dec 31  1969 controlC3
> crw-rw-rw-    1 root     root     116, 128 Dec 31  1969 controlC4
> crw-rw-rw-    1 root     root     116, 160 Dec 31  1969 controlC5
> crw-rw-rw-    1 root     root     116, 192 Dec 31  1969 controlC6
> crw-rw-rw-    1 root     root     116, 224 Dec 31  1969 controlC7
> crw-rw-rw-    1 root     root     116,   4 Dec 31  1969 hwC0D0
> crw-rw-rw-    1 root     root     116,   8 Dec 31  1969 midiC0D0
> crw-rw-rw-    1 root     root     116,  24 Dec 31  1969 pcmC0D0c
> crw-rw-rw-    1 root     root     116,  16 Dec 31  1969 pcmC0D0p
> crw-rw-rw-    1 root     root     116,  56 Dec 31  1969 pcmC1D0c
> crw-rw-rw-    1 root     root     116,  48 Dec 31  1969 pcmC1D0p
> crw-rw-rw-    1 root     root     116,   1 Dec 31  1969 seq
> crw-rw-rw-    1 root     root     116,  33 Dec 31  1969 timer

looks ok.  the pcm devices for the card1 are there (pcmC1*).

> 
> I can also load up the usb midi driver after this via modprobe:
> 
> Oct 11 09:33:28 atrophy kernel: snd-usb-midi: MIDIStreaming version 01.00
> Oct 11 09:33:28 atrophy kernel: snd-usb-midi: detected 1 output jack(s) on endpoint 7
> Oct 11 09:33:28 atrophy kernel: snd-usb-midi: detected 1 input jack(s) on endpoint 8
> Oct 11 09:33:28 atrophy kernel: devfs_register(unknown): could not append to parent, err: -17
> Oct 11 09:33:28 atrophy kernel: snd-usb-midi: endpoint 7: created 1 output and 0 input ports
> Oct 11 09:33:28 atrophy kernel: devfs_register(unknown): could not append to parent, err: -17
> Oct 11 09:33:28 atrophy kernel: devfs_register(unknown): could not append to parent, err: -17
> Oct 11 09:33:28 atrophy kernel: snd-usb-midi: endpoint 8: created 0 output and 1 input ports

looks good, too.  you have two midi ports on this device now.


> Again, I might be a complete newbie, but I'm not sure how to use
> amixer without a hw* device. It just complains. Who knows, maybe it
> might be a little refreshing to have someone not "completely
> in-the-know" help iron out interface or loading issues, heh.

so far, all looks good.

just try to start "alsamixer -c1" and unmute the switch and change the
volume as you like.
you can play via hw:1,0 pcm (you might need to use plughw:1,0
instead), for example,

	% aplay -Dplughw:1,0 foo.wav

and for capture

	% arecord -Dplughw:1,0 -fcd bar.wav

and /dev/dsp1 is the OSS device for Extigy (available only if you load
snd-pcm-oss module).

if the above doesn't work (or even if it works), please send me the
output of /proc/asound/card1/stream* files. 
this contains the supported formats on the device.


to the MIDI devices, you can access either via ALSA sequencer or via
a rawmidi device file /dev/snd/midiC1D0 (or midiC1D1), which is
equivalent with OSS midi device, /dev/midi01 (or amidi01).

but please note that here MIDI means not the MIDI wavetable playback.
apparently Extigy has _no_ wavetable function at all.
they are connectors to external MIDI devices.


and finally, if the above works properly, please check what mixer
element corresponds to which role (as i asked in my original post).
you can see the mixer topology and each mixer element in
usbmixer_maps.c.


thanks,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf