No sound on openSUSE 12.3 since the upgrade on snd-hda-intel

English Hardware
#1

Hello yesterday i upgraded the distro from 12.2 to 12.3… all works ok except sound…

I have realtek ALC662 rev1

I found this material but its obsolete SDB:Intel-HDA sound problems - openSUSE

The problem its that everything seems to work ok… i have pulse audio with the volume ok, if i put the control volume in pulse audio i get the moving bars ( saying that soundcard is playing) but i cant hear anything, also the alsamixer gui i have the volume ok and seems it works ok but i cant hear anything… And yes i have the speakers turn on and the cable works ok… as i can hear from my smartphone. A similar problem i have to face off with different kernels ( some kernels work, some others not)… but now i cant use another kernel…
the last kernel i have tested and being working these past days was 3.4.11…

Any help would be apreciated: all the data you need taken from the last version of START

http://www.alsa-project.org/db/?f=f28eed59e600aefd4667a1f9144f1e22e867c984

#2

You could try adding your user to the “audio” group:

usermod -a -G audio $USER

[FONT=Verdana](do that as root and replace $USER with your username)
[/FONT]
You could also try to disable and then again enable pulseaudio in YaST.
This can be done in Hardware->Sound, click on the button on the lower right labelled “Other…” and select “Pulseaudio configuration…”

Note that you would need to logout and login for those changes to take effect.

#3

Thanks for your response.

I ve reinstalled all alsa* packages, installed kernel source and added user to audio group. Ive also disabled pulseaudio as said.

Ive logoout and reboot the system.

Seems some progress, now appears in kmix hd nvidia ( before it showed analogic standard output, without specifying the type). I ve all the volume ok,and when i reboot i could hear some sounds and hums from the speakers. But still no luck. I cant hear anything. I ve connected the speakers to my smartphone again, and they are on and working ok, with good volume.

The bad news before when i was playing a mp3 for example in kmix i could see a bar with the volumeter of the file ( ex: kplayer or vlc playing sound). Now i cant, it says nothing plays audio.

Need another plan lol!.

#4

This seems to be a problem for many distributions, probably only for systems with dual sound systems. Install pavucontrol, there you can select the correct sound devices.

#5

I note a 32-bit openSUSE-12.3 on a Gigabyte M61PME-52 (F2 firmware) with v.1.0.26 of alsa (and the 3.7.10.1-1-desktop kernel) where hardware has an ALC662 hardware audio codec, with the snd_hda_intel and snd_usb_audio alsa kernel modules loaded. Pulse was running in the script output you provided, but if you have since removed pulse audio then you can stop reading this post now as I suspect I won’t be of much help in a non-standard openSUSE configuration.

I note this from the script:



!!Aplay/Arecord output
!!--------------------

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 1: ALC662 rev1 Digital [ALC662 rev1 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ARECORD

**** List of CAPTURE Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 2: ALC662 rev1 Analog [ALC662 rev1 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: U0x46d0x9a4 [USB Device 0x46d:0x9a4], device 0: USB Audio [USB Audio]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

Indicating two devices for audio (consistent with the loaded kernel modules). Likely one is your motherboard (snd_hda_intel) and the other the webcam (snd_usb_audio). I can see that your playback device(s) for sound are hw:0,0 (analog) and hw:0,1 (digital). I note for recording your devices are hw:0,0 and hw:0,2 (motherboard) and hw:1,0 (webcam mic I speculate).

The mixer settings look ok for analog playback.

Some dmesg entries of interest include:


!!ALSA/HDA dmesg
!!--------------

   19.910370] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 23
   19.910378] hda_intel: Disabling MSI
   19.910405] snd_hda_intel 0000:00:05.0: setting latency timer to 64
   19.918075] ALSA hda_intel.c:1642 Enable delay in RIRB handling
--
   21.024919] USB Video Class driver (1.1.1)
   21.069029] ALSA patch_realtek.c:1241 SKU: Nid=0x1d sku_cfg=0x4005c603
   21.069034] ALSA patch_realtek.c:1243 SKU: port_connectivity=0x1
   21.069036] ALSA patch_realtek.c:1244 SKU: enable_pcbeep=0x0
   21.069038] ALSA patch_realtek.c:1245 SKU: check_sum=0x00000005
   21.069039] ALSA patch_realtek.c:1246 SKU: customization=0x000000c6
   21.069041] ALSA patch_realtek.c:1247 SKU: external_amp=0x0
   21.069042] ALSA patch_realtek.c:1248 SKU: platform_type=0x0
   21.069044] ALSA patch_realtek.c:1249 SKU: swap=0x1
   21.069045] ALSA patch_realtek.c:1250 SKU: override=0x1
   21.069050] ALSA hda_auto_parser.c:318 autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
   21.069052] ALSA hda_auto_parser.c:322    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
   21.069054] ALSA hda_auto_parser.c:326    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
   21.069056] ALSA hda_auto_parser.c:327    mono: mono_out=0x0
   21.069057] ALSA hda_auto_parser.c:330    dig-out=0x1e/0x0
   21.069059] ALSA hda_auto_parser.c:331    inputs:
   21.069061] ALSA hda_auto_parser.c:335      Rear Mic=0x18
   21.069063] ALSA hda_auto_parser.c:335      Front Mic=0x19
   21.069064] ALSA hda_auto_parser.c:335      Line=0x1a
--
   21.193491]  sdc: sdc1
   21.195050] ALSA patch_realtek.c:1304 realtek: No valid SSID, checking pincfg 0x4005c603 for NID 0x1d
   21.195055] ALSA patch_realtek.c:1320 realtek: Enabling init ASM_ID=0xc603 CODEC_ID=10ec0662
   21.196477] sd 4:0:0:0: [sdc] Asking for cache data failed
--
   21.196486] sd 4:0:0:0: [sdc] Attached SCSI disk
   21.201081] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:05.0/input/input6
   21.433235] input: HDA NVidia Line as /devices/pci0000:00/0000:00:05.0/sound/card0/input7
   21.433420] input: HDA NVidia Front Mic as /devices/pci0000:00/0000:00:05.0/sound/card0/input8
   21.433567] input: HDA NVidia Rear Mic as /devices/pci0000:00/0000:00:05.0/sound/card0/input9
   21.433706] input: HDA NVidia Front Headphone as /devices/pci0000:00/0000:00:05.0/sound/card0/input10
   21.433840] input: HDA NVidia Line Out as /devices/pci0000:00/0000:00:05.0/sound/card0/input11
   22.147090] ALSA clock.c:237 3:3:1: cannot get freq at ep 0x86
   22.147260] ALSA mixer.c:887 5:2: cannot get min/max values for control 2 (id 5)
   22.147528] ALSA mixer.c:887 5:2: cannot get min/max values for control 2 (id 5)
   22.147632] usbcore: registered new interface driver snd-usb-audio
--
   25.507235] ALSA mixer.c:834 set volume quirk for QuickCam E3500

Assume pulse audio has not been messed up by any remove/re-install or disable/enable efforts, my recommendation is the same as that of hank_se which is to install ‘pavucontrol’ and look at using that to tune your audio. There are more detailed / fundamental tests we can try - but lets go for something basic first. I have some suggestions in this blog entry on using ‘pavucontrol’ : https://forums.opensuse.org/blogs/oldcpu/pulseaudio-basics-opensuse-pavucontrol-96/

If that does not work, we can try some more basic commands, and also look at apply soming some Hda-Audio-Models.txt file options for the ALC662 (one at a time) to alsa startup (where that file is located under /usr/src/linux-3.7.10-1.1/Documentation/sound/alsa/).

#6

That’s a function of pulseaudio.
If you want to have that, you should enable pulseaudio again. (I did suggest this anyway :wink: )
Who knows, maybe it works now?
If not, you could try pavucontrol then, as somebody else suggested…

#7

In chat support they told me that pulse audio is somewhat a sado mazo thing jejejje. I still think its module problem with kernel.I have two kernels because whe i updated some times i found that the new kernel couldnt recognize the sound card. Without configuring anything just booting with other kernel and sound worked perfect. Now when i upgraded, i have to delete my kernels ( both of them with audio working, the last one was 3.4.11…). The only kernel in 12.3 is 3.7.10…which seems that doesnt work…

Now i have disabled pulse audio as told before…

My phonon: http://i.imgur.com/Yy6OTm8.jpg

My kmix: http://i.imgur.com/O750TUL.jpg
Here it shows the name of the sound card hd nvidia and lots of channels, with pulse audio it only appeared one master channe and Analog Standard output ( in phonon the same, with pulse audio i had an BOBA output disabled and a Analog Standard Output as only device).

Kmix showing nothing playing audio… as i was playing a song: http://i.imgur.com/q6ICwUt.jpg

I cant use pavucontrol as i have my pulse audio now disabled, here is the data from START ( this report as root):

http://www.alsa-project.org/db/?f=6573c90e7b3f551840936070253e80c26cf18cab

Any ideas would be apreciated…i have reinstalled now all pulse* packages but still disabled.

Before the mate told me to disable pulse audio, i remember that pavucontrol was ok… with sound in the card and volumeter moving but i still couldnt hear anything…was a some kind of virtual sound jejejjejjelol!

Im expecting orders and ideas…

Thanks for you collaboration.

#8

That’s normal. That’s how pulseaudio works.

Kmix showing nothing playing audio… as i was playing a song: http://i.imgur.com/q6ICwUt.jpg

As I said before, this is only available when pulseaudio is enabled!

I cant use pavucontrol as i have my pulse audio now disabled, here is the data from START ( this report as root):

http://www.alsa-project.org/db/?f=6573c90e7b3f551840936070253e80c26cf18cab

Any ideas would be apreciated…i have reinstalled now all pulse* packages but still disabled.

Before the mate told me to disable pulse audio, i remember that pavucontrol was ok… with sound in the card and volumeter moving but i still couldnt hear anything…was a some kind of virtual sound jejejjejjelol!

Well, I suggested you should try to enable pulseaudio again. Maybe it works then.
And try to play around with pavucontrol then:

Do you have sound in YaST->Sound, when you select “Test Sound” on the “Other” button?

#9

irc chat is very much a volunteer thing, and some of the users there do not like pulse and have also never taken the time to learn it. I would take that with a grain of salt (lots and lots of salt). It can sometimes depend on one’s hardware, but having typed that I have pulse enabled on six PCs each with completely different audio hardware, and it works fine.

#10

Right now i was following the instructions of the first mate, its not worth to mix ideas …

Now i cant hear test sound in YAst -> Sound -> Others

http://wstaw.org/m/2013/04/26/plasma-desktopSh2582.png

Now im going to re-activate pulse audio in yast → Sound → Configure Pulse Audio…

With a song playing… i get ( i havent reboot the system or logout, still cant hear anything):

http://wstaw.org/m/2013/04/26/plasma-desktopUn2582.png

and

http://wstaw.org/m/2013/04/26/plasma-desktopzi2582.png

My new start ( remember activated pulseaudio in yast and viewing pavucontrol seems that works ok, havent reboot or logout session)
http://www.alsa-project.org/db/?f=faff3a617e271c579c451fcb127169d7daf7062f

Thanks again for you help…

#11

Well, i havent pick a chat helper looking in his/her curriculum vitae jejjeje I suppose that he had the best intention to help…

I have more information to share:

Ive entered in phonon ( system settings -> multimedia -> phonon) and i found this:

http://wstaw.org/m/2013/04/26/plasma-desktopOh2582.png

and when i want to change the configuration…when i clic on apply it gets stuck on grey colour…

http://wstaw.org/m/2013/04/26/plasma-desktopZu2582.png

When i left and enter again i find the first configuration, with my webcam as sound card.

I also forget to mention that problem is system related and not kde, as i have entered in gnome and the same happens.

#12

Thats easy fixed with Yast > Hardware > Sound …

If you decide to re-enable pulse audio (with all the supporting rpms that you may have removed (?)), then repost the output URL from the " /usr/sbin/alsa-info.sh" script and I can look at the configuration. Again, if you decide to re-enable pulse … etc … don’t forget to try ‘pavucontrol’ as many have recommended.

If you decide NOT to re-enable pulse, then someone else who is not a pulse fan will have to chime in. My experience in this thou, is those who do not like pulse don’t provide much support to other users with ‘audio problems’ other than to say they don’t like pulse and rave/go on a tangent about their dislike for pulse (which is not overly helpful IMHO).

#13

Updated: i have reinstalled all pulse*packages, enabled pulse audio in yast → sound, logout, reboot and still cant hear nothing… I think my system makes a mess with my webcam as sound card in phonon.

Pavucontrol seems everything to work ok:

My phonon ( system settings -> multimedia -> phonon):
http://wstaw.org/m/2013/04/27/plasma-desktopqC2602.png

This is the problem i think:
http://wstaw.org/m/2013/04/27/plasma-desktopCG2602.png

It uses webcam as default sound card, when i want to change, i clic apply and gets stuck. When i exit and go back to phonon it always appears this.

I try to put:
http://wstaw.org/m/2013/04/27/plasma-desktopxH2602.png
But as said before and you can watch, gets stuck when i clic on apply. So changes dont take effect.

Pavucontrol seems as said before everything ok:
http://wstaw.org/m/2013/04/27/plasma-desktopAE2602.png

http://wstaw.org/m/2013/04/27/plasma-desktopfU2602.png

http://wstaw.org/m/2013/04/27/plasma-desktopPq2602.png

Last my yast sound:
http://wstaw.org/m/2013/04/27/plasma-desktopov2602.png
http://wstaw.org/m/2013/04/27/plasma-desktopEB2602.png

My kmix:
http://wstaw.org/m/2013/04/27/plasma-desktopog2602.png

http://wstaw.org/m/2013/04/27/plasma-desktopNz2602.png

My START:
http://www.alsa-project.org/db/?f=35e449b9b7099b163dfc8b3640a0c4b0ce119ea8

I still think its a bug of kernel and modules…

Thanks in advance…

#14

It doesn’t get “stuck” when you press the “Apply” button…
That’s just the way KDE works:
When you change something in a settings dialog, the “Apply” button gets enabled.
If you press “Apply” the settings get applied and the “Apply” button gets disabled again, because there are now no changed settings anymore to apply.

Please click on the “OK” button to save the settings and close the window.

But if the settings are not remembered then there’s something wrong somewhere. (maybe kernel module or pulseaudio?)

Anyway, your problem sounds very much like this:
https://bugs.launchpad.net/ubuntu/+source/phonon/+bug/769274

Or maybe this could help: (from http://forum.kde.org/viewtopic.php?f=15&t=98726)

Eventually the problem was pulseaudio. I had to force pulseaudio to use analog output by issuing
pacmd set-card-profile output:analog-stereo+input:analog-stereo

Or you could try to upgrade your kernel, see here for how you would do that:
https://forums.opensuse.org/blogs/jdmcdaniel3/opensuse-installing-new-linux-kernel-versions-134/

#15

Likely there is a bug, but that does not mean we can not get this to work.

What is your test for sound ?

Have you tried commands such as:

prepare a .wav file (called 'somefile.wav fro example) and send in a terminal the command:


aplay -vv somefile.wav

or


aplay -D hw:0,0 -vv somefile.wav

or


aplay -D hw:0,1 -vv somefile.wav

or for example for 5.1 surround sound:


speaker-test -Dplug:surround51 -c6 -twav

or


speaker-test -Dplug:surround51 -c2 -twav

or


speaker-test -Dplug:default -c6 -twav

… and as I noted there are model options we can have forced upon the boot of the alsa sound driver.

#16

Pavucontrol is a gtk app for PulseAudio, and you say everything works (excellent news). However, KDE’s Phonon/KMix support for PulseAudio doesn’t appear to work for your sound device, but it should really work without pavucontrol.

That makes me think it is firstly a failure of the KDE support, and a problem for openSUSE to take onboard via a bug report supplied by you if you are able to do that. Then openSUSE are best placed to decide whether it is a problem for KDE, ALSA driver, or Kernel, and to refer it upstream.