Rajko M. wrote:
> >
> > The lspci entry tells that your card is different:
> > 00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio
> > (rev a2)
> > Mine is MCP51.
> >
> > I just found something that might be helpful:
> >  http://www.suseforums.net/index.php?showtopic=30235

Indeed.  Thanks.  I was able to assign snd-hda-intel as the driver for
the MCP61, according to the suggestions in the forum (via YaST System
Settings), but like the person with the problem there, that alone didn't
resolve it - YaST Hardware Sound still fails to load snd-hda-intel when
I try to configure the existing sound card, or try to add a new one as
an MCP51..  Something he tried later did work, however, possibly in
addition to the earlier suggestions.  From his message:

"I installed the new versions of alsa, then did elsewheres thing with
the PCI ID, I still got complaints, but when I went to the sound section
and changed to MCP 51 (hda) it works!"

What I don't understand is the "installed the new versions of alsa"
part.  I've installed all updates that are available, supposedly, and
there was nothing about ALSA in any of them.  I don't believe he was
talking about a kernel rebuild, because an earlier message from him
stated that such would be beyond his skills.

Where can I install updates to ALSA?  Is there a patch RPG somewhere
that will update it?  Are there directions somewhere that are simple
enough for a Windows software developer to follow?

> > One idea would be to try 10.3 alpha 4. It has new kernel.

Is it possible to leave 10.2 installed and switch between them?  I
wouldn't mind trying a new kernel if there's an easy way to return to
what I now have.  It's annoying not to have sound, but everything else
is working very well indeed, and it appears that 10.3 will solve the
problem once it's released.  I can be patient for that long, if that's
the best answer.

Thanks again for all your help -- I've learned a lot in a short time!

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to