A sound problem one more time.- THE SOLUTION AT LAST (PLEASE NOTE)
Nigel Henry
cave.dnb2m97pp at aliceadsl.fr
Thu Feb 14 21:13:09 UTC 2008
On Thursday 14 February 2008 18:01, Mark C. Allman wrote:
> On Wed, 2008-02-13 at 22:43 +0100, Nigel Henry wrote:
> > On Wednesday 13 February 2008 21:34, Frank Chiulli wrote:
> > > Nigel,
> > > I have a Sound Blaster Live! Value. This is an older machine. F8
> > > detected the card automatically. Unfortunately I can't tell you
> > > exactly when I got the error. I had tried lots of things to get sound
> > > to work but never did. It wasn't a big deal. Then I was looking at
> > > something else when I was the error. I figured that I would take a
> > > look at it. It seems like an easy fix. It seems pretty obvious to me
> > > what was wrong. So I corrected it. Then sound worked.
> > >
> > > Frank
> >
> > Thanks for the reply Frank. I was hoping that you would say that your
> > card was also an isa one, and would tie it in with Aarons problems.
> >
> > It's nice to see that both of you have resolved the problem, but what's
> > going on to cause these problems is beyond me.
> >
> > As you see from what I posted above, my audigy2 soundblaster was detected
> > ok, and apart from disabling pulseaudio by removing
> > alsa-plugins-pulseaudio, and adding the usual lines to /etc/modprobe.conf
> > for my usb midi keyboard that uses snd-usb-audio, the sounds are working
> > ok.
> >
> > Anyway, the fact that both you and Aaron now have sounds is the main
> > thing. Quite why you've both had problems, and me none, I've no idea.
> > That's computers for you.
> >
> > Nigel.
>
Mark says:
> When I run the "alsa-info.sh" script I see an error message when it
> tries to collect the data that says something like "no soundcard found."
> I think it's the same error that I see when I run aplay to list out
> cards:
> [mcallman at prez tmp]$ aplay -l
> aplay: device_list:205: no soundcards found...
>
> Also, when I look at the script results, I see the following at about
> line 65 (this is after I tried "model=toshiba" in modprobe.conf even
> though my laptop is a Dell XPS 1710):
> Loaded sound module option
> --------------------------
> Module: snd_hda_intel
> enable : N
> id : <NULL>
> index : 0
> model : toshiba
> position_fix : 0
> power_save : 0
> power_save_controller : Y
> probe_mask : -1
> single_cmd : N
>
> Could the "enable: N" line be the key here? For those of you that have
> sound working, what do you see listed for "enable?"
>
> If it helps, you can look at all the test results that the script
> uploaded at:
> http://pastebin.ca/903970
>
>
> -- Mark C. Allman, PMP
Hi Mark. I've sort of lost the plot a bit, but do you have your sound working
now?
I ask because the Alsa development folks are working hard on resolving
problems, particularly with the hda intel cards. Alsa driver 1.0.16 has just
been released, and I see many patches being applied to the hda intel codecs,
including your STAC9200 one.
Nigel.
More information about the fedora-list
mailing list