At Wed, 11 May 2011 07:31:37 -0700 CentOS mailing list <centos@xxxxxxxxxx> wrote:
>
> At 01:35 PM 5/7/2011, you wrote:
> >On 07/05/11 20:32, David wrote:
> > >
> > > I got two recommendations:
> > > a) Used 'alsamixer' to unmute all channels. The were, as a responder
> > > suggested, muted.
> > > b) Installed kmod-alsa from elrepo. It produced a bunch of warnings
> > > which I ignored.
> > > c) I performed lspci | grep -i audio, and got
> > >
> > > 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset
> > > High Definition Audio (rev 06)
> > > 01:00.1 Audio device: nVidia Corporation High Definition Audio
> > > Controller (rev a1)
> >
> ># lspci -n | grep '00:1b.0'
> >00:1b.0 0403: 8086:293e (rev 02)
> >
> >and take the Vendor:Device ID pairing (8086:293e in my example) and
> >search for a matching driver supporting that device:
> >
> >
> ># grep -i 8086 /lib/modules/*/modules.alias | grep -i 293e
> >/lib/modules/2.6.18-128.el5/modules.alias:alias
> >pci:v00008086d0000293Esv*sd*bc*sc*i* snd-hda-intel
> >/lib/modules/2.6.18-164.el5/modules.alias:alias
> >pci:v00008086d0000293Esv*sd*bc*sc*i* snd-hda-intel
> >/lib/modules/2.6.18-194.el5/modules.alias:alias
> >pci:v00008086d0000293Esv*sd*bc*sc*i* snd-hda-intel
> >/lib/modules/2.6.18-238.9.1.el5/modules.alias:alias
> >pci:v00008086d0000293Esv*sd*bc*sc*i* snd-hda-intel
> >/lib/modules/2.6.18-238.el5/modules.alias:alias
> >pci:v00008086d0000293Esv*sd*bc*sc*i* snd-hda-intel
> >/lib/modules/2.6.18-53.el5/modules.alias:alias
> >pci:v00008086d0000293Esv*sd*bc*sc*i* snd-hda-intel
> >/lib/modules/2.6.18-92.el5/modules.alias:alias
> >pci:v00008086d0000293Esv*sd*bc*sc*i* snd-hda-intel
> >
> >which shows me the snd-hda-intel driver present in kernel-2.6.18-53.el5
> >onwards supports my hardware.
> >
> >Now do the same for your hardware and show us the results.
> >
>
>
> I performed the tests as you indicated.
> Here's what I got...
>
> #lspci -n | grep -i '00:1b,0'
> 00:1b:0 0403: 8086:3b56 (rev06)
> #grep '8086' /lib/modules/*/modules.alias | grep -i '3b56'
>
> No output from the above
>
> The test on the other device
> #lspci -n | grep -i '01:00.1'
> 01:00.1 0403: 10de:0be2 (rev a1)
> #grep '10de' /lib/modules/*/modules.alias | grep -i '0be2'
Try:
sauron.deepsoft.com% grep -i '10de' /lib/modules/*/modules.alias | grep bc04sc03
/lib/modules/2.6.18-238.9.1.el5/modules.alias:alias pci:v000010DEd*sv*sd*bc04sc03i00* snd-hda-intel
/lib/modules/2.6.18-238.9.1.el5xen/modules.alias:alias pci:v000010DEd*sv*sd*bc04sc03i00* snd-hda-intel
It appears that *ALL* nVidia motherboard sound controllers use the
same Intel chip. The *device* ID is wildcarded. The 'bc04sc03' selects
sound devices as opposed to SATA, Network, etc. controllers. Oh, and the
alias files have the letters in uppercase and grep *by default* is case
sensitive... sauron.deepsoft.com has a nVidia-chipset motherboard and
the snd-hda-intel driver works just fine. sauron.deepsoft.com is a
desktop machine and I have a set of external powered speakers jacked
into the audio output port.
>
> No output from the above.
>
> (not lookin' good?)
Just needed a more clever set of grep expressions...
It appears that you do have the proper driver for at least one of your
sound controllers. The question remains: which one (if either) is
connected to the internal speakers...
Question: does this laptop have a headphone/speaker jack? If so, what
happens when you plug in a set of speakers or headphones in and play a
test sound?
>
> David
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
>
--
Robert Heller -- 978-544-6933 / heller@xxxxxxxxxxxx
Deepwoods Software -- http://www.deepsoft.com/
() ascii ribbon campaign -- against html e-mail
/\ www.asciiribbon.org -- against proprietary attachments
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
