Bug 1138900 - After latest 'yum update' Audio no longer works -- but can see VU meters moving (Lenovo Yoga 2)
Summary: After latest 'yum update' Audio no longer works -- but can see VU meters movi...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: alsa-lib
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jaroslav Kysela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-06 06:16 UTC by nmvega
Modified: 2015-06-29 22:24 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:24:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
alsa-info.sh --no-upload (38.67 KB, text/plain)
2014-09-06 06:16 UTC, nmvega
no flags Details

Description nmvega 2014-09-06 06:16:46 UTC
Created attachment 934947 [details]
alsa-info.sh --no-upload

Hi friends:

Attached below is some output related to this bug filing.

Info:

(1) Fedora 20 x86_64
(2) Kernel version: 3.15.10-201.fc20.x86_64
(3) Laptop Model: Lenovo Yoga 2

I know the laptop speakers are fine because I can (multi) boot into Windows 8 and they work. In fact, they have always worked on my Fedora 20 install until I performed a 'yum update' today. I don't know what was updated (I don't always look at yum output). =:)

Oddly, in the PulseAudio Volume Control (I run XFCE by the way), when I am playing a YouTube video or an MP3, I see the Left & Right VU meters moving as they are supposed to (and they ajust accordingly to my moving up & down the volume sliders). So it looks good there. And none of the channels are muted. I checked in that same PulseAudio UI as well as in the CLI based 'alsamixer'.
I also checked that the right card was selected (Built-In + Analog + Speakers
are all properly selected,... not External + HDM + Headphones).


Note that I don't have anything in /etc/modprobe.d (for example sound.conf). Things just worked, so I never needed to make adjustments there.

Here is some output that may help you (and attached is the output
of the command user@lenovo$ alsa-info.sh --no-upload):

=============================================================
user@lenovo$ aplay -l
=============================================================
**** List of PLAYBACK Hardware Devices ****
card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: PCH [HDA Intel PCH], device 0: ALC283 Analog [ALC283 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
=============================================================

=============================================================
user@lenovo$ lsmod | grep snd
=============================================================
snd_hda_codec_hdmi     47536  1 
snd_hda_codec_realtek    71717  1 
snd_hda_codec_generic    67662  1 snd_hda_codec_realtek
snd_hda_intel          30379  12 
snd_hda_controller     30139  1 snd_hda_intel
snd_hda_codec         131137  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
snd_hwdep              17650  1 snd_hda_codec
snd_seq                62266  0 
snd_seq_device         14136  1 snd_seq
snd_pcm               104333  7 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer              28778  2 snd_pcm,snd_seq
snd                    75905  31 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device
soundcore              14491  2 snd,snd_hda_codec
==============================================================

Any ideas as to what happened? I did web searches, but nothing I tried works. Again, it seems to be working, but not reaching the Speakers.

Thank you.
Noel

Comment 1 nmvega 2014-09-06 06:43:29 UTC
More information:

After shutting down Fedora, powering off the laptop, and finally booting up again, the audio came back, however the audio was very choppy
(on / off / on / off)... unusably so.

So I tried rebooting into the previous kernel (v3.15.10-200.fc20.x86_64), and the audio works again.

I guess this issue is latest kernel and/or driver and/or codec related?

Definitely booting into the latest kernel does not work.

Thank you.

Comment 2 Rex Dieter 2014-09-06 15:30:08 UTC
Did your latest 'yum update' include anything pulseaudio-related?  If not, this is more likely a alsa/driver/kernel issue.

Comment 3 Rex Dieter 2014-09-06 15:31:57 UTC
Per comment #1, likely a recent kernel/driver regression... reassigning (to alsa).

Comment 4 Fedora End Of Life 2015-05-29 12:48:23 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-06-29 22:24:20 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.