<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Oct 27, 2015 at 8:30 PM, stan <span dir="ltr"><<a href="mailto:stanl-fedorauser@vfemail.net" target="_blank">stanl-fedorauser@vfemail.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 27 Oct 2015 20:06:09 -0700<br>
<div><div class="h5">Dave Johansen <<a href="mailto:davejohansen@gmail.com">davejohansen@gmail.com</a>> wrote:<br>
<br>
> On Tue, Oct 27, 2015 at 8:47 AM, stan <<a href="mailto:stanl-fedorauser@vfemail.net">stanl-fedorauser@vfemail.net</a>><br>
> wrote:<br>
><br>
> > On Sun, 25 Oct 2015 20:03:18 -0700<br>
> > Dave Johansen <<a href="mailto:davejohansen@gmail.com">davejohansen@gmail.com</a>> wrote:<br>
> ><br>
> > > I recently did a clean install of F22 Mate Spin from F21 and<br>
> > > sound is no longer working. I tried the recommendations from<br>
> > > <a href="https://fedoraproject.org/wiki/How_to_debug_sound_problems" rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/How_to_debug_sound_problems</a> but<br>
> > > nothing seemed to work. Is there anything else I should try?<br>
> ><br>
> > Run aplay -lv to see if alsa found your sound devices.<br>
> ><br>
><br>
> I don't really know what to expect, but this looks fine to me:<br>
> $ aplay -lv<br>
> **** List of PLAYBACK Hardware Devices ****<br>
> card 0: Intel [HDA Intel], device 0: AD1981 Analog [AD1981 Analog]<br>
> Subdevices: 1/1<br>
> Subdevice #0: subdevice #0<br>
> card 0: Intel [HDA Intel], device 1: AD1981 Digital [AD1981 Digital]<br>
> Subdevices: 1/1<br>
> Subdevice #0: subdevice #0<br>
><br>
> Install pavucontrol and check how pulseaudio has configured those<br>
> sound<br>
> > devices. You might have defaulted to an invalid default device,<br>
> > like the hdmi on a video device. Set everything how you want it.<br>
> ><br>
><br>
> Nothing seemed out of the ordinary for this and sound still doesn't<br>
> work. Any other suggestions?<br>
<br>
</div></div>Bring up pavucontrol and remove device 0 from pulsaudio control.<br>
Should be on the last tab. Then check what happens if you try to play<br>
a .wav file with the command<br>
aplay --device=plughw:0,0 some_wav_file.wav<br>
If it plays, the problem is in the pulseaudio setup / interface with<br>
alsa, because alsa is working, so the correct driver is loaded<br>
and working.<br>
If it seems to be working, but there is no sound, check physical<br>
connections like speakers, because alsa thinks its sending sound to<br>
output.<br></blockquote><div><br></div><div>aplay doesn't error out or anything but there's no sound. It's a T60 laptop so I don't know how I can check connections.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If the command aborts, then there is a problem with the alsa driver.<br>
That seems unlikely, since aplay showed it correctly.<br>
<br>
If you have audacity installed, you can confirm the failure by<br>
importing a sound file into audacity (File->audio_import), and playing<br>
it (space bar). If the meters move, but there is no sound, then the<br>
driver is loaded and functioning, but there is a disconnect at output.<br>
<br>
If all the connections are right, it might be that the default device<br>
is device 0,1 (digital), instead of device 0,0 (analog).<br></blockquote><br></div><div class="gmail_quote">I tried device 0,1 and device 0,0 and neither worked.<br></div></div></div>