Ok, here are the new results. I've decided to include most of the
output as attached files. Figured it would be easier this way for most
people.
The tests were done with the cvs tree from around 14:30EST with your
test define included in the usbmixer code. Included are:
lsusb-out.txt: lsusb -vv
At Fri, 11 Oct 2002 13:39:01 -0500,
[EMAIL PROTECTED] wrote:
> > the attached patch will ignore the errors from the usb controller
> > after a mixer control is inquired. the error above shall be avoided
> > by this patch. please check the kernel messages. so we can know
> > which control is wr
On Fri, Oct 11, 2002 at 08:12:54PM +0200, Takashi Iwai wrote:
> please rebuild the alsa drivers with configure option
> "--with-debug=detect" ? this will add more verbose debug outputs
> (ususally annoying).
Small typo in the patch, nothing big just a . that should be a >
> the attached patch w
At Fri, 11 Oct 2002 13:00:23 -0500,
[EMAIL PROTECTED] wrote:
>
> On Fri, Oct 11, 2002 at 06:27:17PM +0200, Takashi Iwai wrote:
> > At Fri, 11 Oct 2002 18:02:09 +0200,
> > I wrote:
> > >
> > > hmm, could you run "alsactl store" and show the generated
> > > /etc/asound.state (only for the second c
On Fri, Oct 11, 2002 at 06:27:17PM +0200, Takashi Iwai wrote:
> At Fri, 11 Oct 2002 18:02:09 +0200,
> I wrote:
> >
> > hmm, could you run "alsactl store" and show the generated
> > /etc/asound.state (only for the second card is enough)?
> > at least we can see whether the controls are parsed prop
On Fri, Oct 11, 2002 at 06:02:09PM +0200, Takashi Iwai wrote:
> > > % aplay -Dplughw:1,0 foo.wav
> > >
> > > and for capture
> > >
> > > % arecord -Dplughw:1,0 -fcd bar.wav
> >
> > I'd love to do this, but:
> >
> > atrophy:/etc/modutils# amixer -c1
> > amixer: Mixer load error: hw:1
> > at
At Fri, 11 Oct 2002 18:02:09 +0200,
I wrote:
>
> hmm, could you run "alsactl store" and show the generated
> /etc/asound.state (only for the second card is enough)?
> at least we can see whether the controls are parsed properly.
also, please check the kernel message after running the commands
ab
At Fri, 11 Oct 2002 10:34:11 -0500,
[EMAIL PROTECTED] wrote:
>
> On Fri, Oct 11, 2002 at 05:07:25PM +0200, Takashi Iwai wrote:
> > > 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, b
On Fri, Oct 11, 2002 at 05:07:25PM +0200, Takashi Iwai wrote:
> > 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 a
Hi Mark,
At Fri, 11 Oct 2002 09:36:59 -0500,
[EMAIL PROTECTED] 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.
wh
At Fri, 11 Oct 2002 09:13:12 -0500,
[EMAIL PROTECTED] wrote:
>
> I might be a complete idiot, but when I load up the usb-audio drivers
> for my extigy out of the cvs tree, I'm not even getting the devices I
> need to test the stuff. I'm using devfs, and and hwC0D0 doesnt pop
> up.
hwCxDx is a h
I might be a complete idiot, but when I load up the usb-audio drivers
for my extigy out of the cvs tree, I'm not even getting the devices I
need to test the stuff. I'm using devfs, and and hwC0D0 doesnt pop
up.
I the same guy that once claimed that he was going to work on drivers
for the extigy.
Hi,
can anyone test the latest cvs snd-usb-audio driver with the SB
Extigy?
now the names of mixer controls on this device became more
understandable.
the mixer topology of extigy is depicted in
alsa-kernel/usb/usbmixer_maps.c. unlike other usb devices, this is a
really complicated one.
i have
13 matches
Mail list logo
