29 Jul
2006
29 Jul
'06
12:26 p.m.
Hi all,
Does anyone know what the requirements are to get the high
definition audio controller in an NVidia chipset working? lspci says
this:
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
Currently I'm running 2.6.17-gentoo-r4 with :
alsa-tools-1.0.11
alsa-utils-1.0.11
A few emails and forum posts I found from last January suggested it
works but I don't see it listed in the Alsa sound card database.
Anyone know about this before I subscribe to the alsa-devel list again?
Thanks,
Mark
29 Jul
29 Jul
12:40 p.m.
Mark Knecht wrote:
Does anyone know what the requirements are to get
the high
definition audio controller in an NVidia chipset working? lspci says
this:
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio
(rev a2)
You should just be able to use the snd-hda-intel module. Just like AC97,
it's an Intel standard that everyone else has adopted.
later,
Steve
12:47 p.m.
On 7/29/06, Stephen Hassard <steve(a)hassard.net> wrote:
Mark Knecht wrote:
Steve,
Thanks. I'll give it a try. However alsaconf did not discover it.
Does that mean alsaconf needs a PCI ID update or something like that?
Thanks again for the help.
Cheers,
Mark
Does anyone know what the requirements are to
get the high
definition audio controller in an NVidia chipset working? lspci says
this:
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio
(rev a2)
You should just be able to use the snd-hda-intel module. Just like AC97,
it's an Intel standard that everyone else has adopted.
later,
Steve
3:20 p.m.
On 7/29/06, Mark Knecht <markknecht(a)gmail.com> wrote:
On 7/29/06, Stephen Hassard <steve(a)hassard.net>
wrote:
Steve,
OK, so it turns out that alsaconf doesn't find cards until the
driver is built for the card. Since I didn't know the NVidia device
used the Intel driver then alsaconf couldn't configure for it until I
rebuilt the kernel and included that device as a module. The Intel
driver installs and alsamixer now comes up fine.
The machine is not near speakers so I cannot test sound yet, but
I'm curious about the controls I see in alsamixer. Comparing with
other on-board sound chips I do not see a Master volume control and I
do not see a PCM control. The only control that looks interesting is
'Front'. Is that the master volume for this type of sound chip?
Again, thanks for the help. Seems it will likely work when I get
the build finished up and get it moved. Still have ndiswrapper &
wireless config to go.
Cheers,
Mark
Mark Knecht wrote:
Steve,
Thanks. I'll give it a try. However alsaconf did not discover it.
Does that mean alsaconf needs a PCI ID update or something like that?
Thanks again for the help.
Cheers,
Mark
Does anyone know what the requirements are to
get the high
definition audio controller in an NVidia chipset working? lspci says
this:
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio
(rev a2)
You should just be able to use the snd-hda-intel module. Just like AC97,
it's an Intel standard that everyone else has adopted.
later,
Steve
31 Jul
31 Jul
5:23 a.m.
Mark Knecht wrote:
I'm curious about the controls I see in alsamixer.
Comparing with
other on-board sound chips I do not see a Master volume control and I
do not see a PCM control.
What codec do you have? (see /proc/asound/cards)?
The HDA driver is continually updated. If your board isn't yet known,
it's possible that you have to add the 'model' option to the driver,
and/or to update the driver.
HTH
Clemens
12:43 p.m.
On 7/31/06, Clemens Ladisch <clemens(a)ladisch.de> wrote:
Mark Knecht wrote:
Hi Clemens,
Thanks for responding. I *think* this was my problem. It seemed
that alsaconf didn't find the card until I actually built the driver.
That was a bit of a Catch-22 since I didn't know what driver to build,
etc. Anyway, after building the driver based on Stephen's input
alsaconf found the card, it's installed and mostly working. The only
app I'm having trouble with so far is MythTV which says it is
controlling PCM but doesn't actually control PCM on this card. IT
works fine on all my non-HDA systems. That may be a MythTV problem, or
maybe it's a driver problem we could look at since it will take months
to get the MythTV people to pay any attention to a problem like this!
;-)
Let me know what other information would be of interest.
Cheers,
Mark
Sector9 ~ # cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.11rc4 (Wed Mar 22
10:27:24 2006 UTC).
Sector9 ~ #
Sector9 ~ # cat /proc/asound/cards
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfe024000 irq 16
Sector9 ~ #
Sector9 ~ # lspci
<SNIP>
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
Sector9 ~ # lspci -x
<SNIP>
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00: de 10 6c 02 06 00 b0 00 a2 00 03 04 00 00 80 00
10: 00 40 02 fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 3c 10 3e 2a
30: 00 00 00 00 44 00 00 00 00 00 00 00 0a 02 02 05
Sector9 ~ # eix -Ic alsa-
[I] media-libs/alsa-lib (1.0.11): Advanced Linux Sound Architecture Library
[I] media-libs/alsa-oss (1.0.11): Advanced Linux Sound Architecture
OSS compatibility layer.
[I] media-sound/alsa-headers (1.0.11): Header files for Advanced Linux
Sound Architecture kernel modules
[I] media-sound/alsa-tools (1.0.11): Advanced Linux Sound Architecture tools
[I] media-sound/alsa-utils (1.0.11): Advanced Linux Sound Architecture
Utils (alsactl, alsamixer, etc.)
Found 5 matches
Sector9 ~ #
Sector9 ~ # uname -a
Linux Sector9 2.6.17-gentoo-r4 #1 PREEMPT Sat Jul 29 09:49:32 PDT 2006
i686 AMD Sempron(tm) Processor 3200+ GNU/Linux
Sector9 ~ #
Sector9 ~ # cat /etc/modules.d/alsa
# Alsa 0.9.X kernel modules' configuration file.
# $Header: /var/cvsroot/gentoo-x86/media-sound/alsa-utils/files/alsa-modules.conf-rc,v
1.5 2006/06/13 10:18:25 uberlord Exp $
# ALSA portion
# OSS/Free portion
##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `modules-update' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
## ALSA portion
## alias snd-card-0 snd-interwave
## alias snd-card-1 snd-ens1371
## OSS/Free portion
## alias sound-slot-0 snd-card-0
## alias sound-slot-1 snd-card-1
##
# OSS/Free portion - card #1
## OSS/Free portion - card #2
## alias sound-service-1-0 snd-mixer-oss
## alias sound-service-1-3 snd-pcm-oss
## alias sound-service-1-12 snd-pcm-oss
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
# Set this to the correct number of cards.
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.11 ---
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
# --- END: Generated by ALSACONF, do not edit. ---
Sector9 ~ #
I'm curious about the controls I see in
alsamixer. Comparing with
other on-board sound chips I do not see a Master volume control and I
do not see a PCM control.
What codec do you have? (see /proc/asound/cards)?
The HDA driver is continually updated. If your board isn't yet known,
it's possible that you have to add the 'model' option to the driver,
and/or to update the driver.
HTH
Clemens
9:44 p.m.
On Mon, 2006-07-31 at 07:43 -0700, Mark Knecht wrote:
Thanks for responding. I *think* this was my problem.
It seemed
that alsaconf didn't find the card until I actually built the driver.
Why are you even using alsaconf for a PCI device? It's only needed for
old ISA stuff. hotplug/udev/whatever should automagically load the
right driver for a PCI card on boot.
Lee
10:08 p.m.
On 7/31/06, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Mon, 2006-07-31 at 07:43 -0700, Mark Knecht wrote:
Lee,
Sometimes I don't get where you are coming from with these strong
statements...
There was no driver to be loaded since I hadn't built any drivers
when I built the kernel. As I said earlier, I didn't *know* what
driver to build. It's a new machine. I didn't recognize the hardware.
I didn't know what to do so I thought alsaconf would help me. There
was no indication for a new user of this NVidia hardware that the
NVidia HDA had anything at all to do with the Intel HDA. You might
think I'm stupid. I suppose I am. Sorry. It just wasn't clear to me
and I don't think it would be any clearer to most purely user types.
We reside in a lower place my friend.
So, as I said earlier, it was my thought that alsaconf, which does
configure PCI devices quite fine thank you, would look at the PCI
device ID, build a new modprobe.conf entry, and in doing that it would
tell me what driver to build, albeit a bit indirectly. Unfortunately
it didn't work that way *until* I built the driver. At that point
alsaconf built modprobe.conf just fine.
Anyway, I disagree that on a machine that has absolutely no audio
drivers built that anything is going to load a driver automagically.
Built I'm a stupid guitar player do what the F do I know.
- Mark
Thanks for responding. I *think* this was my
problem. It seemed
that alsaconf didn't find the card until I actually built the driver.
Why are you even using alsaconf for a PCI device? It's only needed for
old ISA stuff. hotplug/udev/whatever should automagically load the
right driver for a PCI card on boot.
Lee
10:25 p.m.
On Mon, 2006-07-31 at 17:08 -0700, Mark Knecht wrote:
On 7/31/06, Lee Revell <rlrevell(a)joe-job.com>
wrote:
Sorry, I just got back into town and was going through 1000s of emails,
and rattled that off too quickly. I did not mean to be rude but
obviously I was. Apologies.
Lee
On Mon, 2006-07-31 at 07:43 -0700, Mark Knecht
wrote:
Lee,
Sometimes I don't get where you are coming from with these strong
statements...
Thanks for responding. I *think* this was my
problem. It seemed
that alsaconf didn't find the card until I actually built the driver.
Why are you even using alsaconf for a PCI device? It's only needed for
old ISA stuff. hotplug/udev/whatever should automagically load the
right driver for a PCI card on boot.
Lee There was no driver to be loaded since I hadn't
built any drivers
when I built the kernel. As I said earlier, I didn't *know* what
driver to build. It's a new machine. I didn't recognize the hardware.
I didn't know what to do so I thought alsaconf would help me. There
was no indication for a new user of this NVidia hardware that the
NVidia HDA had anything at all to do with the Intel HDA. You might
think I'm stupid. I suppose I am. Sorry. It just wasn't clear to me
and I don't think it would be any clearer to most purely user types.
We reside in a lower place my friend.
So, as I said earlier, it was my thought that alsaconf, which does
configure PCI devices quite fine thank you, would look at the PCI
device ID, build a new modprobe.conf entry, and in doing that it would
tell me what driver to build, albeit a bit indirectly. Unfortunately
it didn't work that way *until* I built the driver. At that point
alsaconf built modprobe.conf just fine.
Anyway, I disagree that on a machine that has absolutely no audio
drivers built that anything is going to load a driver automagically.
Built I'm a stupid guitar player do what the F do I know.
- Mark
10:29 p.m.
On 7/31/06, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Mon, 2006-07-31 at 17:08 -0700, Mark Knecht wrote:
Happily accepted. Thanks.
- Mark
On 7/31/06, Lee Revell
<rlrevell(a)joe-job.com> wrote:
Sorry, I just got back into town and was going through 1000s of emails,
and rattled that off too quickly. I did not mean to be rude but
obviously I was. Apologies.
Lee On Mon, 2006-07-31 at 07:43 -0700, Mark Knecht
wrote:
Lee,
Sometimes I don't get where you are coming from with these strong
statements...
Thanks for responding. I *think* this was my
problem. It seemed
that alsaconf didn't find the card until I actually built the driver.
Why are you even using alsaconf for a PCI device? It's only needed for
old ISA stuff. hotplug/udev/whatever should automagically load the
right driver for a PCI card on boot.
Lee
10:58 p.m.
On Mon, 2006-07-31 at 17:29 -0700, Mark Knecht wrote:
On 7/31/06, Lee Revell <rlrevell(a)joe-job.com>
wrote:
No problem.
For future reference, I think you could have built and installed the
driver, then restarted udev (/etc/init.d/udev restart on my system) and
it would have loaded the correct driver.
Lee
On Mon, 2006-07-31 at 17:08 -0700, Mark Knecht
wrote:
Happily accepted. Thanks. On 7/31/06, Lee Revell
<rlrevell(a)joe-job.com> wrote:
Sorry, I just got back into town and was going through 1000s of emails,
and rattled that off too quickly. I did not mean to be rude but
obviously I was. Apologies.
Lee On Mon, 2006-07-31 at 07:43 -0700, Mark Knecht
wrote:
> Thanks for responding. I *think* this was my problem. It seemed
> that alsaconf didn't find the card until I actually built the driver.
Why are you even using alsaconf for a PCI device? It's only needed for
old ISA stuff. hotplug/udev/whatever should automagically load the
right driver for a PCI card on boot.
Lee
Lee,
Sometimes I don't get where you are coming from with these strong
statements...
11:12 p.m.
On 7/31/06, Lee Revell <rlrevell(a)joe-job.com> wrote:
On Mon, 2006-07-31 at 17:29 -0700, Mark Knecht wrote:
Lee,
OK, I'll play along. I'm a new user setting up a new machine. I
don't know what driver to build. How do I find out without resorting
to joining lists or doing long, boring web searches. I looked at the
alsa-project.org sound card lists didn't show it. It only listed the
intel8x0 driver which was all I built before I started writing emails.
Next, what do you mean by 'built and installed the driver'? Since
nothing tells me to use the Intel HDA driver the only way I think this
logic holds up is if I build every single driver offered by the kernel
and hope for the best. I'm sure you're not really suggesting that
path...
And alsaconf worked just fine, but only once the driver was built.
My original thought, which seemed innocent enough, was that alsaconf
understood all the PCI IDs and then determined what driver to put in
modprobe.conf from that. Apparently not.
Cheers,
Mark
On 7/31/06, Lee Revell
<rlrevell(a)joe-job.com> wrote:
No problem.
For future reference, I think you could have built and installed the
driver, then restarted udev (/etc/init.d/udev restart on my system) and
it would have loaded the correct driver.
Lee On Mon, 2006-07-31 at 17:08 -0700, Mark Knecht
wrote:
Happily accepted. Thanks. On 7/31/06, Lee Revell
<rlrevell(a)joe-job.com> wrote:
> On Mon, 2006-07-31 at 07:43 -0700, Mark Knecht wrote:
> > Thanks for responding. I *think* this was my problem. It seemed
> > that alsaconf didn't find the card until I actually built the driver.
>
> Why are you even using alsaconf for a PCI device? It's only needed for
> old ISA stuff. hotplug/udev/whatever should automagically load the
> right driver for a PCI card on boot.
>
> Lee
Lee,
Sometimes I don't get where you are coming from with these strong
statements...
Sorry, I just got back into town and was going through 1000s of emails,
and rattled that off too quickly. I did not mean to be rude but
obviously I was. Apologies.
Lee
1 Aug
1 Aug
1:47 a.m.
On Mon, 2006-07-31 at 18:12 -0700, Mark Knecht wrote:
Lee,
OK, I'll play along. I'm a new user setting up a new machine. I
don't know what driver to build. How do I find out without resorting
to joining lists or doing long, boring web searches. I looked at the
alsa-project.org sound card lists didn't show it. It only listed the
intel8x0 driver which was all I built before I started writing emails.
Next, what do you mean by 'built and installed the driver'? Since
nothing tells me to use the Intel HDA driver the only way I think this
logic holds up is if I build every single driver offered by the kernel
and hope for the best. I'm sure you're not really suggesting that
path...
And alsaconf worked just fine, but only once the driver was built.
My original thought, which seemed innocent enough, was that alsaconf
understood all the PCI IDs and then determined what driver to put in
modprobe.conf from that. Apparently not.
You're right, it doesn't help with choosing the driver to compile. I
was just referring to alsaconf which chooses the driver to load. It
assumes that they are all present, as would be the case if a distro
kernel was used.
Lee
10 a.m.
Mark Knecht wrote:
OK, I'll play along. I'm a new user setting
up a new machine. I
don't know what driver to build. How do I find out without resorting
to joining lists or doing long, boring web searches. I looked at the
alsa-project.org sound card lists didn't show it. It only listed the
intel8x0 driver which was all I built before I started writing emails.
--with-cards=all
That oughta do it. :)
And alsaconf worked just fine, but only once the
driver was built.
My original thought, which seemed innocent enough, was that alsaconf
understood all the PCI IDs and then determined what driver to put in
modprobe.conf from that. Apparently not.
Indeed. I got bit by this one recently. I was surprised when alsaconf
didn't report the existence of my PCI128. lspci could see it, but not
alsaconf, *until* I built and installed the ens1371 driver. So the
--with-cards=all option really is the best way to go for anyone who
doesn't know for sure what hardware is in their system or which driver
they need for the hardware.
Best,
dp
11:24 a.m.
Dave Phillips wrote:
Indeed. I got bit by this one recently. I was
surprised when alsaconf
didn't report the existence of my PCI128.
I think all that alsaconf does is try to load each available
driver until one works. So if you don't have the driver, it
can't try and load it in the 1st place.
--
paul w
31 Jul
31 Jul
9:45 p.m.
On Mon, 2006-07-31 at 07:43 -0700, Mark Knecht wrote:
The only
app I'm having trouble with so far is MythTV which says it is
controlling PCM but doesn't actually control PCM on this card. IT
works fine on all my non-HDA systems. That may be a MythTV problem, or
maybe it's a driver problem we could look at since it will take months
to get the MythTV people to pay any attention to a problem like this!
Does the PCM volume control in alsamixer work properly? If so it's a
MythTV bug.
Lee
6742
days inactive
6745
days old
linux-audio-user@lists.linuxaudio.org
15 comments
6 participants
participants (6)
-
Clemens Ladisch -
Dave Phillips -
Lee Revell -
Mark Knecht -
paul wisehart -
Stephen Hassard