* New azx driver: Problems in snd_mixer_load
@ 2004-12-09 18:20 Stephen Warren
2004-12-09 18:51 ` Takashi Iwai
0 siblings, 1 reply; 14+ messages in thread
From: Stephen Warren @ 2004-12-09 18:20 UTC (permalink / raw)
To: alsa-devel
Hi.
Background: We have a custom 2.6.9 kernel, to which we've back-ported
the ALSA 1.0.7 drivers, and they're all compiled in as non-modules right
now. I've installed this kernel on a machine running FC2, plus installed
the 1.0.7 version of libasound and associated config files.
On top of this, I added the latest CVS version of the azx driver into
the kernel.
Now, when I run alsamixer, I get the following error message right at
startup:
===========================
root@localhost# alsamixer
ALSA lib simple.c:950:(simple_add1) helem (MIXER,'Capture Source',0,0,0)
appears twice or more
alsamixer: function snd_mixer_load failed: Invalid argument
===========================
Does anyone have any ideas about this?
In particular, I'm a little confused about the role the files in
/usr/share/alsa play in the whole ALSA system. Do I need to import new
version of these files along with the udpated device driver?
Here's some system information:
Portions of lspci, and lspci -nv:
00:1b.0 Class 0403: Intel Corp. I/O Controller Hub Audio (rev 03)
00:1b.0 Class 0403: 8086:2668 (rev 03)
Subsystem: 8086:2668
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at feb3c000 (64-bit, non-prefetchable)
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
Capabilities: [70] #10 [0091]
root@localhost# cd /proc/asound
root@localhost# cat cards
0 [HDA ]: Azalia - ICH6 HDA
ICH6 HDA at 0xfeb3c000 irq 16
root@localhost# cd card0
root@localhost# cat codec#2
Codec: Generic 434d ID 4980
Address: 2
Vendor Id: 0x434d4980
Subsystem Id: 0x0
Revision Id: 0x90002
Default PCM: rates 0x540, bits 0x0e, types 0x1
Default Amp-In caps: N/A
Default Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Node 0x03 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x04 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x05 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x06 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x07 [Audio Output] wcaps 0x615: Stereo Digital Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
PCM: rates 0x000, bits 0x00, types 0x5
Node 0x08 [Audio Input] wcaps 0x10051b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x1e, stepsize=0x05, mute=1
Amp-In vals: 0x80 0x80
PCM: rates 0x160, bits 0x02, types 0x0
Connection: 9
0x0b 0x0c 0x0d 0x0e 0x0f 0x10 0x11 0x1f 0x20
Node 0x09 [Audio Input] wcaps 0x10051b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x1e, stepsize=0x05, mute=1
Amp-In vals: 0x80 0x80
PCM: rates 0x160, bits 0x02, types 0x0
Connection: 9
0x0b 0x0c 0x0d 0x0e 0x0f 0x10 0x11 0x1f 0x20
Node 0x0a [Audio Input] wcaps 0x100791: Stereo Digital
PCM: rates 0x160, bits 0x0e, types 0x0
Connection: 1
0x13
Node 0x0b [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01014020: Line Out at Ext Rear
Conn = 1/8, Color = Green
Pin-ctls: 0xc0
Connection: 1
0x03
Node 0x0c [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01813030: Line In at Ext Rear
Conn = 1/8, Color = Blue
Pin-ctls: 0x20
Connection: 1
0x04
Node 0x0d [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01a19040: Mic at Ext Rear
Conn = 1/8, Color = Pink
Pin-ctls: 0x20
Connection: 1
0x05
Node 0x0e [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x081033f: IN
OUT
Pin Default 0x01014021: Line Out at Ext Rear
Conn = 1/8, Color = Green
Pin-ctls: 0x20
Connection: 1
0x06
Node 0x0f [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x42214050: HP Out at Ext Front
Conn = 1/8, Color = Green
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x10 [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x42a19060: Mic at Ext Front
Conn = 1/8, Color = Pink
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x11 [Pin Complex] wcaps 0x400001: Stereo
Pincap 0x0863: IN
Pin Default 0x9933f170: CD at Int ATAPI
Conn = ATAPI, Color = Other
Pin-ctls: 0x00
Node 0x12 [Pin Complex] wcaps 0x400301: Stereo Digital
Pincap 0x0810: OUT
Pin Default 0x01450000: SPDIF Out at Ext Rear
Conn = Optical, Color = Unknown
Pin-ctls: 0x40
Connection: 1
0x07
Node 0x13 [Pin Complex] wcaps 0x400281: Stereo Digital
Pincap 0x0830: IN
OUT
Pin Default 0x01c50000: SPDIF In at Ext Rear
Conn = Optical, Color = Unknown
Pin-ctls: 0x00
Node 0x14 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x15 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x16 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x17 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x18 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x19 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1a [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1b [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1d [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1e [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1f [Pin Complex] wcaps 0x400181: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01019022: Line Out at Ext Rear
Conn = 1/8, Color = Pink
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x20 [Pin Complex] wcaps 0x400181: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01013023: Line Out at Ext Rear
Conn = 1/8, Color = Blue
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x22 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x23 [Beep Generator Widget] wcaps 0x70000c: Mono Amp-Out
Amp-Out caps: ofs=0x0f, nsteps=0x0f, stepsize=0x0b, mute=1
Amp-Out vals: 0x0f
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: New azx driver: Problems in snd_mixer_load
2004-12-09 18:20 Stephen Warren
@ 2004-12-09 18:51 ` Takashi Iwai
0 siblings, 0 replies; 14+ messages in thread
From: Takashi Iwai @ 2004-12-09 18:51 UTC (permalink / raw)
To: Stephen Warren; +Cc: alsa-devel
At Thu, 9 Dec 2004 10:20:04 -0800,
Stephen Warren wrote:
>
> Hi.
>
> Background: We have a custom 2.6.9 kernel, to which we've back-ported
> the ALSA 1.0.7 drivers, and they're all compiled in as non-modules right
> now. I've installed this kernel on a machine running FC2, plus installed
> the 1.0.7 version of libasound and associated config files.
>
> On top of this, I added the latest CVS version of the azx driver into
> the kernel.
>
> Now, when I run alsamixer, I get the following error message right at
> startup:
>
> ===========================
> root@localhost# alsamixer
> ALSA lib simple.c:950:(simple_add1) helem (MIXER,'Capture Source',0,0,0)
> appears twice or more
> alsamixer: function snd_mixer_load failed: Invalid argument
> ===========================
>
> Does anyone have any ideas about this?
Could you show the content of /etc/asound.state after "alscatl store"?
Also, try to build with --with-debug=detect
(i.e. CONFIG_SND_DEBUG_DETECT=y). This will give some more verbose info.
> In particular, I'm a little confused about the role the files in
> /usr/share/alsa play in the whole ALSA system. Do I need to import new
> version of these files along with the udpated device driver?
It'd be better if you update the driver.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
@ 2004-12-09 20:44 Stephen Warren
0 siblings, 0 replies; 14+ messages in thread
From: Stephen Warren @ 2004-12-09 20:44 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
> From: Takashi Iwai [mailto:tiwai@suse.de]
>
> At Thu, 9 Dec 2004 10:20:04 -0800,
> Stephen Warren wrote:
> >
> > ...
> > On top of this, I added the latest CVS version of the azx
> > driver into the kernel.
> >
> > Now, when I run alsamixer, I get the following error
> > message right at startup:
> >
> > ===========================
> > root@localhost# alsamixer
> > ALSA lib simple.c:950:(simple_add1) helem (MIXER,'Capture
> Source',0,0,0)
> > appears twice or more
> > alsamixer: function snd_mixer_load failed: Invalid argument
> > ===========================
>
> Could you show the content of /etc/asound.state after "alscatl store"?
> Also, try to build with --with-debug=detect
> (i.e. CONFIG_SND_DEBUG_DETECT=y). This will give some more
> verbose info.
The content of asound.state is below. I'll rebuild the kernel without
any of the ALSA drivers, and build everything from CVS to see if it's
any better...
state.HDA {
control.1 {
comment.access 'read write'
comment.type BOOLEAN
iface MIXER
name 'Capture Switch'
value.0 false
value.1 false
}
control.2 {
comment.access 'read write'
comment.type INTEGER
comment.range '0 - 30'
iface MIXER
name 'Capture Volume'
value.0 0
value.1 0
}
control.3 {
comment.access 'read write'
comment.type ENUMERATED
comment.item.0 'Input 0'
comment.item.1 Line
comment.item.2 Mic
comment.item.3 'Input 3'
comment.item.4 'Input 4'
comment.item.5 Mic
comment.item.6 CD
comment.item.7 'Input 7'
comment.item.8 'Input 8'
iface MIXER
name 'Capture Source'
value 'Input 0'
}
}
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
@ 2004-12-09 21:29 Stephen Warren
0 siblings, 0 replies; 14+ messages in thread
From: Stephen Warren @ 2004-12-09 21:29 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
> From: Takashi Iwai [mailto:tiwai@suse.de]
>
> Stephen Warren wrote:
> > On top of this, I added the latest CVS version of the azx
> > driver into the kernel.
> >
> > Now, when I run alsamixer, I get the following error
> > message right at startup:
> >
> > ===========================
> > root@localhost# alsamixer
> > ALSA lib simple.c:950:(simple_add1) helem (MIXER,'Capture
> Source',0,0,0)
> > appears twice or more
> > alsamixer: function snd_mixer_load failed: Invalid argument
> > ===========================
>
> Could you show the content of /etc/asound.state after "alscatl store"?
> Also, try to build with --with-debug=detect
> (i.e. CONFIG_SND_DEBUG_DETECT=y). This will give some more
> verbose info.
>
> > In particular, I'm a little confused about the role the files in
> > /usr/share/alsa play in the whole ALSA system. Do I need to
> > import new version of these files along with the udpated device
> > driver?
>
> It'd be better if you update the driver.
OK. I've built alsa-driver from CVS. I get this in the kernel logs when
doing "modprobe snd-azx":
ACPI: PCI interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/azx.c:356:
codec_mask = 0x4
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:488:
AUD_IN = 8
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0xb IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0xc IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0xd IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0xe IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0xf IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0x10 IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0x11 IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0x1f IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0x20 IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:518:
[Capture Source] NID=0x8, #SRC=9
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Input 0] IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Line] IDX=0x1
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Mic] IDX=0x2
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Input 3] IDX=0x3
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Input 4] IDX=0x4
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Mic] IDX=0x5
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[CD] IDX=0x6
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Input 7] IDX=0x7
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:520:
[Input 8] IDX=0x8
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 3
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0xb IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0xb
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0xb
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 4
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 5
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 6
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 3
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:217:
CONNECT: NID=0xf IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0xf IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0xf
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0xf
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 3
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:217:
CONNECT: NID=0x10 IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0x10 IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0x10
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0x10
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 7
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 3
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:217:
CONNECT: NID=0x1f IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0x1f IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0x1f
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0x1f
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:251:
AUD_OUT found 3
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:217:
CONNECT: NID=0x20 IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:201:
UNMUTE IN: NID=0x20 IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0x20
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:185:
UNMUTE OUT: NID=0x20
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:576:
[Capture Switch] NID=0x8, DIR=IN, IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:598:
[Capture Volume] NID=0x8, DIR=IN, IDX=0x0
ALSA /home/swarren/src/alsa-cvs/alsa-driver/pci/azx/hda_generic.c:217:
CONNECT: NID=0x8 IDX=0x0
If I re-run "alsactl store", I get the same content in /etc/asound.state
as before.
I didn't update any of the user-space tools. I assume that's OK?
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
@ 2004-12-09 23:26 Stephen Warren
2004-12-10 11:31 ` Takashi Iwai
0 siblings, 1 reply; 14+ messages in thread
From: Stephen Warren @ 2004-12-09 23:26 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
Stephen Warren wrote:
> On top of this, I added the latest CVS version of the azx
> driver into the kernel.
I think I've found half of the problem... I identified the codec chip on
the board, and it's a CMI9880, which isn't explicitly handled by the azx
driver, so it falls through to the default. I don't know why the default
doesn't work, but anyway...
I did find a spec for the codec - it seems to have all the relevant
information that's equivalent to the tables in patch_realktek.c, so I
guess one could create a complete driver from this. I took a look at it,
and am not quite sure how to proceed though, since I'm not remotely
familiar with the internals of HDA.
http://www.cmedia.com.tw/doc/C-Media%20CMI9880%20Datasheet%20rev%200.99C
.pdf
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: New azx driver: Problems in snd_mixer_load
2004-12-09 23:26 Stephen Warren
@ 2004-12-10 11:31 ` Takashi Iwai
2004-12-10 15:40 ` Takashi Iwai
0 siblings, 1 reply; 14+ messages in thread
From: Takashi Iwai @ 2004-12-10 11:31 UTC (permalink / raw)
To: Stephen Warren; +Cc: alsa-devel
At Thu, 9 Dec 2004 15:26:39 -0800,
Stephen Warren wrote:
>
> Stephen Warren wrote:
> > On top of this, I added the latest CVS version of the azx
> > driver into the kernel.
>
> I think I've found half of the problem... I identified the codec chip on
> the board, and it's a CMI9880, which isn't explicitly handled by the azx
> driver, so it falls through to the default. I don't know why the default
> doesn't work, but anyway...
The widget tree parser isn't perfect yet.
It was designed for ALC codec, but apparently it doesn't work well for
others.
> I did find a spec for the codec - it seems to have all the relevant
> information that's equivalent to the tables in patch_realktek.c, so I
> guess one could create a complete driver from this. I took a look at it,
> and am not quite sure how to proceed though, since I'm not remotely
> familiar with the internals of HDA.
>
> http://www.cmedia.com.tw/doc/C-Media%20CMI9880%20Datasheet%20rev%200.99C
> .pdf
Yes, I got this one yesterday, too. I'll work on it.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: New azx driver: Problems in snd_mixer_load
2004-12-10 11:31 ` Takashi Iwai
@ 2004-12-10 15:40 ` Takashi Iwai
0 siblings, 0 replies; 14+ messages in thread
From: Takashi Iwai @ 2004-12-10 15:40 UTC (permalink / raw)
To: Stephen Warren; +Cc: alsa-devel
At Fri, 10 Dec 2004 12:31:50 +0100,
I wrote:
>
> Yes, I got this one yesterday, too. I'll work on it.
Ok, now it's on CVS. Untested, as usual. Please report any
problems.
As default, the digital I/O isn't activated. You need to pass
"model=digital" module option to snd-azx.
Also, note that this codec has no playback volume controls.
Don't ask me why...
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
@ 2004-12-10 17:20 Stephen Warren
2004-12-10 17:30 ` Takashi Iwai
0 siblings, 1 reply; 14+ messages in thread
From: Stephen Warren @ 2004-12-10 17:20 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
> From: Takashi Iwai [mailto:tiwai@suse.de]
> Ok, now it's on CVS. Untested, as usual. Please report any
> problems.
Takashi,
I've installed the latest CVS drivers, CVS alsa-lib and CVS alsa-utils.
I still get the same error during alsa-lib initialization whilst running
alsamixer.
Specifically, this is caused by
alsa-lib/src/mixer/simple.c:simple_add1() being called with the
following sets of parameters, (plus others):
name="Mic", type=CTL_CAPTURE_SOURCE, value=2
then later:
name="Mic", type=CTL_CAPTURE_SOURCE, value=5
This fails at line 944:
if (simple->ctls[type].elem) {
SNDERR("helem (%s,'%s',%li,%li,%li) appears twice or more",
...
Attached is the content of /proc/asound/card0/codec#2:
Thanks for all your help.
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
[-- Attachment #2: codec2.txt --]
[-- Type: text/plain, Size: 4408 bytes --]
Codec: Generic 434d ID 4980
Address: 2
Vendor Id: 0x434d4980
Subsystem Id: 0x0
Revision Id: 0x90002
Default PCM: rates 0x540, bits 0x0e, types 0x1
Default Amp-In caps: N/A
Default Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Node 0x03 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x04 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x05 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x06 [Audio Output] wcaps 0x405: Stereo Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
Node 0x07 [Audio Output] wcaps 0x615: Stereo Digital Amp-Out
Amp-Out caps: N/A
Amp-Out vals: 0x80 0x80
PCM: rates 0x000, bits 0x00, types 0x5
Node 0x08 [Audio Input] wcaps 0x10051b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x1e, stepsize=0x05, mute=1
Amp-In vals: 0x80 0x80
PCM: rates 0x160, bits 0x02, types 0x0
Connection: 9
0x0b 0x0c 0x0d 0x0e 0x0f 0x10 0x11 0x1f 0x20
Node 0x09 [Audio Input] wcaps 0x10051b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x1e, stepsize=0x05, mute=1
Amp-In vals: 0x80 0x80
PCM: rates 0x160, bits 0x02, types 0x0
Connection: 9
0x0b 0x0c 0x0d 0x0e 0x0f 0x10 0x11 0x1f 0x20
Node 0x0a [Audio Input] wcaps 0x100791: Stereo Digital
PCM: rates 0x160, bits 0x0e, types 0x0
Connection: 1
0x13
Node 0x0b [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01014020: Line Out at Ext Rear
Conn = 1/8, Color = Green
Pin-ctls: 0xc0
Connection: 1
0x03
Node 0x0c [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01813030: Line In at Ext Rear
Conn = 1/8, Color = Blue
Pin-ctls: 0x20
Connection: 1
0x04
Node 0x0d [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01a19040: Mic at Ext Rear
Conn = 1/8, Color = Pink
Pin-ctls: 0x20
Connection: 1
0x05
Node 0x0e [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x081033f: IN
OUT
Pin Default 0x01014021: Line Out at Ext Rear
Conn = 1/8, Color = Green
Pin-ctls: 0x20
Connection: 1
0x06
Node 0x0f [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x42214050: HP Out at Ext Front
Conn = 1/8, Color = Green
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x10 [Pin Complex] wcaps 0x400581: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x42a19060: Mic at Ext Front
Conn = 1/8, Color = Pink
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x11 [Pin Complex] wcaps 0x400001: Stereo
Pincap 0x0863: IN
Pin Default 0x9933f170: CD at Int ATAPI
Conn = ATAPI, Color = Other
Pin-ctls: 0x00
Node 0x12 [Pin Complex] wcaps 0x400301: Stereo Digital
Pincap 0x0810: OUT
Pin Default 0x01450000: SPDIF Out at Ext Rear
Conn = Optical, Color = Unknown
Pin-ctls: 0x40
Connection: 1
0x07
Node 0x13 [Pin Complex] wcaps 0x400281: Stereo Digital
Pincap 0x0830: IN
OUT
Pin Default 0x01c50000: SPDIF In at Ext Rear
Conn = Optical, Color = Unknown
Pin-ctls: 0x00
Node 0x14 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x15 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x16 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x17 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x18 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x19 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1a [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1b [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1c [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1d [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1e [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x1f [Pin Complex] wcaps 0x400181: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01019022: Line Out at Ext Rear
Conn = 1/8, Color = Pink
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x20 [Pin Complex] wcaps 0x400181: Stereo
Pincap 0x0833f: IN
OUT
Pin Default 0x01013023: Line Out at Ext Rear
Conn = 1/8, Color = Blue
Pin-ctls: 0xc0
Connection: 4
0x03 0x04 0x05 0x06
Node 0x21 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x22 [Vendor Defined Widget] wcaps 0xf00000: Mono
Node 0x23 [Beep Generator Widget] wcaps 0x70000c: Mono Amp-Out
Amp-Out caps: ofs=0x0f, nsteps=0x0f, stepsize=0x0b, mute=1
Amp-Out vals: 0x0f
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: New azx driver: Problems in snd_mixer_load
2004-12-10 17:20 New azx driver: Problems in snd_mixer_load Stephen Warren
@ 2004-12-10 17:30 ` Takashi Iwai
0 siblings, 0 replies; 14+ messages in thread
From: Takashi Iwai @ 2004-12-10 17:30 UTC (permalink / raw)
To: Stephen Warren; +Cc: alsa-devel
At Fri, 10 Dec 2004 09:20:18 -0800,
Stephen Warren wrote:
>
> > From: Takashi Iwai [mailto:tiwai@suse.de]
> > Ok, now it's on CVS. Untested, as usual. Please report any
> > problems.
>
> Takashi,
>
> I've installed the latest CVS drivers, CVS alsa-lib and CVS alsa-utils.
> I still get the same error during alsa-lib initialization whilst running
> alsamixer.
The anonymous CVS tree on sourceforge isn't sync'ed often, maybe once
per day. I guess you'ure using still old version. Wait for a while
until the tree gets sync'ed.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
@ 2004-12-10 18:05 Stephen Warren
2004-12-10 18:10 ` Takashi Iwai
0 siblings, 1 reply; 14+ messages in thread
From: Stephen Warren @ 2004-12-10 18:05 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
From: Takashi Iwai [mailto:tiwai@suse.de]
> Stephen Warren wrote:
> > I've installed the latest CVS drivers, CVS alsa-lib and CVS
> > alsa-utils. I still get the same error during alsa-lib
> > initialization whilst running alsamixer.
>
> The anonymous CVS tree on sourceforge isn't sync'ed often, maybe once
> per day. I guess you'ure using still old version. Wait for a while
> until the tree gets sync'ed.
I'm on the latest code - I copied my CVS tree before updating, and then
diff'd the old and new trees. All the changes that show up in the
web-based CVS browser at the URL below are in my copy of the code:
http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-driver/pci/azx/
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: New azx driver: Problems in snd_mixer_load
2004-12-10 18:05 Stephen Warren
@ 2004-12-10 18:10 ` Takashi Iwai
0 siblings, 0 replies; 14+ messages in thread
From: Takashi Iwai @ 2004-12-10 18:10 UTC (permalink / raw)
To: Stephen Warren; +Cc: alsa-devel
At Fri, 10 Dec 2004 10:05:40 -0800,
Stephen Warren wrote:
>
> From: Takashi Iwai [mailto:tiwai@suse.de]
> > Stephen Warren wrote:
> > > I've installed the latest CVS drivers, CVS alsa-lib and CVS
> > > alsa-utils. I still get the same error during alsa-lib
> > > initialization whilst running alsamixer.
> >
> > The anonymous CVS tree on sourceforge isn't sync'ed often, maybe once
> > per day. I guess you'ure using still old version. Wait for a while
> > until the tree gets sync'ed.
>
> I'm on the latest code - I copied my CVS tree before updating, and then
> diff'd the old and new trees. All the changes that show up in the
> web-based CVS browser at the URL below are in my copy of the code:
>
> http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-driver/pci/azx/
This is still old - apparently based on the anonymous cvs tree.
The new code includes a new file, patch_cmedia.c.
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
@ 2004-12-10 22:16 Stephen Warren
2004-12-10 22:24 ` Lee Revell
0 siblings, 1 reply; 14+ messages in thread
From: Stephen Warren @ 2004-12-10 22:16 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
OK. Now I really have the latest code, and it works well for me. Weird
there's no volume control in the HW!
I have a reproducable kernel oops though.
I run alsamixer, and it gives me "columns" for:
PCM Surround Center LFE Capture Capture "Input Source" "Input Source"
As expected, I can manipulate the mute on the first 4, but not adjust
the volume value.
If I select the first "Input Source", and change the selected source, it
starts out by default as "Front Mic", then changes to "Rear Mic", then
to "CD", then if I attempt to change it once more, I get a kernel oops.
Unfortunately, I can't get ksymoops to do anything really useful - it
refuses to load symbols from /proc/kallsyms... What version should I be
used of ksymoops? The latest I can find is 2.4.10, and I also tried
2.4.9, since the kernel.org directory it's in said that was the latest
even though there was a newer version...
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
2004-12-10 22:16 Stephen Warren
@ 2004-12-10 22:24 ` Lee Revell
0 siblings, 0 replies; 14+ messages in thread
From: Lee Revell @ 2004-12-10 22:24 UTC (permalink / raw)
To: Stephen Warren; +Cc: Takashi Iwai, alsa-devel
On Fri, 2004-12-10 at 14:16 -0800, Stephen Warren wrote:
> Weird there's no volume control in the HW!
Not really, this is increasingly common. On Windows everything just
goes through the software mixer in the kernel anyway.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: New azx driver: Problems in snd_mixer_load
@ 2004-12-13 17:42 Stephen Warren
0 siblings, 0 replies; 14+ messages in thread
From: Stephen Warren @ 2004-12-13 17:42 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel
From: Stephen Warren
> OK. Now I really have the latest code, and it works well for me.
>
> I have a reproducable kernel oops though.
>
> If I select the first "Input Source", and change the selected
> source, it starts out by default as "Front Mic", then changes
> to "Rear Mic", then to "CD", then if I attempt to change it
> once more, I get a kernel oops.
I've just grabbed the latest CVS. I've confirmed it fixes this oops.
--
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2004-12-13 17:42 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-10 17:20 New azx driver: Problems in snd_mixer_load Stephen Warren
2004-12-10 17:30 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 17:42 Stephen Warren
2004-12-10 22:16 Stephen Warren
2004-12-10 22:24 ` Lee Revell
2004-12-10 18:05 Stephen Warren
2004-12-10 18:10 ` Takashi Iwai
2004-12-09 23:26 Stephen Warren
2004-12-10 11:31 ` Takashi Iwai
2004-12-10 15:40 ` Takashi Iwai
2004-12-09 21:29 Stephen Warren
2004-12-09 20:44 Stephen Warren
2004-12-09 18:20 Stephen Warren
2004-12-09 18:51 ` Takashi Iwai
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.