[SOLVED] Sound stopped working after update to Jessie

goumba · 12-07-2013, 07:13 AM

My sound suddenly stopped working after a recent update, running Jessie. I've found a bunch of such threads, none of which have worked for me.

Code:

00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)

I tried both with GNOME 3s volume control, alsamixer and pavucontrol, and nothing shows muted.

widget · 12-08-2013, 12:27 AM

Quote:

Originally Posted by goumba

My sound suddenly stopped working after a recent update, running Jessie. I've found a bunch of such threads, none of which have worked for me.

Code:

00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)

I tried both with GNOME 3s volume control, alsamixer and pavucontrol, and nothing shows muted.

A bit of information on your hardware would be a great thing.

CPU and video card would be good.

What is the complete output of;

Code:

lspci

Is all sound affected or just some? Internet video sound? Stored music files? Stored video files?

What sort of output device are you using? Internal computer speaker, usb speakers, rca type plug in speakers, something else?

aus9 · 12-08-2013, 01:47 AM

http://www.linuxquestions.org/questi...-a-4175459926/

goumba · 12-08-2013, 05:34 AM

No sound whatsoever.

Quote:

Originally Posted by goumba

I tried both with GNOME 3s volume control, alsamixer and pavucontrol, and nothing shows muted.

I'll add to that that all volume levels are at maximum.

Quote:

Originally Posted by widget

A bit of information on your hardware would be a great thing.
CPU and video card would be good.

I didn't think that video or cpu (core i3, ivy bridge) would be revelvant. I did however neglect to specify this is a laptop, so internal speakers.

Code:

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Device 0153 (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 4 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
02:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Atheros Communications Inc. AR8162 Fast Ethernet (rev 10)

widget · 12-08-2013, 02:44 PM

Thanks.

I asked about the video card/controller because I recently installed a new card on my desktop and it supports hdmi. Some times when I reboot the video card is set as my default sound controller instead of my audio card. When this happens I get no sound because I am not using hdmi and I have no speakers in my monitor so it wouldn't help if I were.

The command;

Code:

aplay -l

will give you the details of your sound controller(s).

The command;

Code:

cat /proc/asound/cards

should give you all detected sound devices on your system. I doubt this is your problem but you might feel better if you run it.

In my case the out put is;

Code:

tom@jessie:~$ cat /proc/asound/cards
 0 [Audigy         ]: Audigy - SB Audigy 1 ES [SB0160]
                      SB Audigy 1 ES [SB0160] (rev.3, serial:0x521102) at 0xcce0, irq 16
 1 [Generic        ]: HDA-Intel - HD-Audio Generic
                      HD-Audio Generic at 0xfe9dc000 irq 44

Yes it is an ancient sound card. Works great. That output will give me sound by default. Sometimes rebooting reverses the number of the devices however and so it is defaulting to the other controller which is in the ATI 6450 video card.

As this is a Dell computer I do not have access to irq settings in bios (stupid setup).

I can however create a ~/.asoundrc with this content;

Code:

pcm.!default {
    type hw
    card 0
}
ctl.!default {
    type hw           
    card 0
}

and change that 0 to 1 if need be and things are then fixed if I simply drop and then reload what ever application has no sound.

I only go through all this because you did not say if you have hdmi support and I am not familiar with your video controller. Many laptops do support hdmi.

It is possible that, if yours does support hdmi, that your recent upgraded packages change the sound capabilities to make using hdmi easier and thus causing this problem for you.

aus9 · 12-08-2013, 06:00 PM

ok how about a screenshot of your alsamixer output controls by running alsamixer
and uploading the image somewhere, I use tinypic.com
then link to it pls

Now you mention pavucontrol, which means you may have pulseadio running
so if you run alsamixer and see only one control-----PA is running so don't screenshot instead run this command

Code:

alsamixer -c0

2) you are aware that you can go into pavucontrol and mute your speakers multiple ways and set volumes too low?

goumba · 12-10-2013, 08:35 AM

Quote:

Originally Posted by widget

It is possible that, if yours does support hdmi, that your recent upgraded packages change the sound capabilities to make using hdmi easier and thus causing this problem for you.

You know, I hadn't even considered the HDMI audio having anything to do with this. I'll play with your solution when I get home.

Quote:

Originally Posted by aus9

you are aware that you can go into pavucontrol and mute your speakers multiple ways and set volumes too low?

Yeah, and I played with all of them(well, those that were presented to me), even turned the mute controls on, then off again to cycle and be sure. All volume controls are up.

aus9 · 12-10-2013, 07:26 PM

sorry in reply 6 I meant if you see only pulseaudio (one) control in the alsamixer command
then

take a screenshot of

Code:

alsamixer -c0

2) I noticed you did not reply to all of widget's sugestions. Do you have a laptop with hdmi output connector and do you want to use it?

if so the aplay -l is important

3) in the screenshot I am interested to see if you have auto mute mode enabled
---if you spot it right arrow to it, and press the up or down arrows to show disabled then save the setting with

Code:

sudo alsactl store

but I still want to see that screenshot.

4) also you may have a auto mute type config for pulseaudio so this link explains how to fix

http://askubuntu.com/questions/19120...ting-when-idle

b) but I also suggest you copy the files from /etc/pulse to your home folder so you can edit without root powers
log out then login to see the result
---otherwise you have to kill pulseaudio then change the config then restart the daemon
-----IMHO messier

goumba · 12-11-2013, 09:50 AM

widget seems to be on to something, which I missed before. alsamixer is indicating it is using the HDMI device, thank you widget (serves me right for not looking at everything).

Code:

**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 2: VT1802 HP [VT1802 HP]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
anthony@serenity:~$

However, using his suggestion, and even changing the ID numbers has no result. No matter what ID I use in .asoundrc, alsamixer shows "PatherPoint HDMI"

widget · 12-11-2013, 03:57 PM

In alsamixer try hitting F6 to be able to select the device.

I like the alsamixergui package for a gui mixer. Also allows you to choose a device.

Both require the .asoundrc file to work.

Only application for sound I have found that doesn't is the DeadBeef music player which has its own device selection function. That always works.

It took me several days after installing this current video card to get this figured out. Sometimes the thing just works and others the numerical designation changes on bootup. I think it is weird.

aus9 · 12-11-2013, 05:29 PM

ok you are confirming you have hdmi as default and you want analog

but widget's asoundrc won't work as you need to go into device level

before we do, always try a simple thing first

delete any /home/anthony/.asoundrc

log out and log in....not a full reboot

open pavucontrol and pull down and select the one of the analog devices in the last tab called configuration
http://i1140.photobucket.com/albums/...Screenshot.png

also check all other tabs to ensure volumes are ok - not muted now that you have a new device

image is example only showing hdmi showing

test speakers then log out and log in......did you need to do the same to get sound

If all good then full reboot and if all good say so and mark as solved

##########################

only if bad read on

you need a different .asoundrc if above PA configs failed for you

Quote:

pcm.!default {
type hw
card 0
device 0
}

log out then log in

run pavucontroll and re-check firstly the config tab is showing the analog device----full reboot if not
secondly all mixer controls are set up

log out then log in.....re-check then full reboot
---if all good mark as solved

say which method you needed

##################
if both methods did not work say so

good luck

goumba · 12-11-2013, 05:56 PM

Well, I finally got it to work. It was actually an accident. I had prepared a post listing modules loaded along with output from uname (3.11), when it occurred to me to see if there was a newer kernel, and indeed 3.12-exp1 was in experimental. Installed 3.12, rebooted and now I have sound.

The only thing is, now I think I'll have to keep an eye on the kernel, as IIRC packages from experimental do not upgrade automatically, even if the main repo has a newer version.

Thank you anyway for your help.

aus9 · 12-11-2013, 08:47 PM

no problem can you now mark this post as solved

If interested I am on debian sid and use a third party kernel from

http://liquorix.net/

my latest is

Code:

uname -a
Linux box 3.12-4.dmz.1-liquorix-686 #1 ZEN SMP PREEMPT Mon Dec 9 21:27:40 UTC 2013 i686 GNU/Linux

but I don't update every day either and yes there are 64 bits for those with > 3B RAM

rokytnji · 12-11-2013, 08:55 PM

Ran into this and fixed it

http://steamcommunity.com/app/24420/...9691155218006/

http://www.mariusv.com/cannot-open-alsamixer/

a while back. My thread on breaking stuff while partying.

http://antix.freeforums.org/post31277.html

This was back in Oct but my fix has been working fine since then through a 200 watt per channel pioneer amplifier.
Just posting the info since you say you fixed it already. I don't use pulse audio. Just alsa.

aus9 · 12-11-2013, 10:46 PM

rokytnji----yes its off topic to OP

I have never been drunk or made mistakes----grins like a sheep

since you have liquorix kernel why not try smxi to do your updates?

http://smxi.org/site/about.htm#smxi

2) I looked at your links

I guess the aquaria link is steam related as I do not have /etc/openal folder

b) I am on debian sid so of course already at 1.0.27.2-1