sound lost after kernel upgrade

I’m using KDE 4.14.9. 64 bit SuSE 13.2.

I did a kernel update today (October 25). It took a ridiculously long time to complete, and upon reboot I found that I had no sound from any sound file using any media player, or from any internet site. However, I do get the test sound (the few bars of what sounds like symphonic music) when I go into Yast.

I am completely stumped. I’ve tried re-rebooting just in case but that did not help.

What information can I supply to help you gurus find the source of my sound problem?

Thanks.
bosdad

Also just having this issue, I guess it was the kernel update, can also play the test sound in Yast but when checking the mixer controls I am missing any capture devices etc and the sound output is now showing as a dummy output?

Also 13.2 x64 bit.

Sound card is in yast as 82801JD/Do (ICH10 Family) HD audio controller.

Same as the op have lost all sounds from internet such as youtube, music players such as Amarok etc.

Adrian

Definitely to do with the Kernel, I have just gone back to Kernel Desktop 3.16.7-42-1.x86_64.rpm and have all sound back.

The update provided 3.16.7-45-1.x86_64.rpm.

Adrian

And I am having EXACTLY the same problems/issues as you describe including the dummy output. Looks as if the update was faulty. Thanks for confirming it’s not me. :o)
bosdad

No sound for me too :frowning:
However, I also have no sound in yast.
Now I have to work instead of watching youtube :frowning:

Thanks, Adrian, for this fix. I also rolled back the kernel and the audio works again. So the question now for me is when can we trust that the kernel update will be fixed and not screw us all again?
bosdad

I’m having the same problem, right down to the upgrade taking ridiculously long, except that I can’t find any test sound option in YaST. I get silence from the test sound in the System Settings app.

I have a Logitech headset in addition to the built-in Intel sound system. Normally System Settings shows both drivers, and allows me to prioritize them. Now, all I see is PulseAudio Sound Server, which I had never seen before.

I guess for the time being I should try to figure out how to revert the kernel desktop.

I suspect from your description that you’ve already done this. But just in case…
Yast > Hardware > Sound > Other (it’s in the lower right hand corner of screen) > Play test sound.
If no sound then on that “other” drop-down tab select “volume,” move the two uppermost sliders to the right and click “test.” That should get you the “symphony” test sound. Hope this helps.
bosdad

Confirm: reverting to 3.16.7-42-1.x86_64 has restored my sound.

Am Wed, 26 Oct 2016 03:36:01 GMT
schrieb bosdad <bosdad@no-mx.forums.microfocus.com>:

> So the question now for me is when can we trust that
> the kernel update will be fixed and not screw us all again?
> bosdad
>
>

Maybe contributing to bugzilla will help raising awareness to the maintainers?

Actually, there is already a report:

https://bugzilla.opensuse.org/buglist.cgi?quicksearch=3.16.7-45

AK


Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

It’s also broken my NTFS mounts for internal drives in KDE4 as well, ACL 1000 error. Reversion to previous kernel fixes all. Oh well off to bugzilla

No point.

It has been reported 3 or 4 times already, the problem has been identified and there’s even a fixed kernel available for testing.
See 1007035 – POSIX ACL support broken by kernel-desktop-3.16.7-45.

Reposting what I posted to another thread (about scanner suddenly not working) in hopes that this will contribute to others not having to do a kernel rollback:

… I’d lost sound as well. The recent update wiped out permissions, apparently. I’m a flyin’-by-the-seat-of-my-pants user, so here’re some steps for those of my ilk:

YaST->User and Group Management->(select user, then the “Edit” button)–>select “Details” tab->in the Additional Groups list, check boxes for “audio” and “lp”.->Click “OK”

You might want to log out and back in. This restored access (permissions) for my scanner and my sound card. Got everything working as before.]

You don’t need to do a “kernel rollback”.
Just select the older kernel in the boot menu (in “Advanced Options”), it should still be installed.

The fixed update should get released really soon anyway.

… I’d lost sound as well. The recent update wiped out permissions, apparently.

It broke ACL (“access control lists”) support, this means the logged in user cannot get permissions to access certain device “files”, so would need to be added to certain groups.

YaST->User and Group Management->(select user, then the “Edit” button)–>select “Details” tab->in the Additional Groups list, check boxes for “audio” and “lp”.->Click “OK”

You might want to log out and back in. This restored access (permissions) for my scanner and my sound card. Got everything working as before.]

Won’t help with mounting partitions though… :wink:

Thanks, by reverting from 3.16.7-45-desktop to 3.16.7-42-desptop the sound returned.
Good to find this information on this thread, searched already the Internet and tried several things without success.

New Kernel published:

v | kernel-default | Paket      | 3.16.7-48.1        | x86_64 | openSUSE-13.2-Update

Gr-e-a-at… I have two bootable kernels on my system: 3.16.7-45 and 3.16.7-48 – neither of those kernels allow sound output.

So, essentially, I will get no sound on Linux until another questionable set of patches comes along that /might/ fix the problem.

BTW, this is the second problem I’ve run into this week where some function was working up until I installed patches. (That one broke the ability to mount memory cards on my USB hub.) It’s nearly gotten to the point where I’m spending more time researching and fixing problems related to patches than anything else. If I wanted to spend this much time dealing with maintaining my system I could have stuck with Slackware or moved to Gentoo.

Well, better do this then.

I just installed 3.16.7-48.1-x86_64 (openSUSE-2016-1241), and I have sound. Version 3.16-7-45 is still unchecked in YaST, though.

When Software Updater notified me of something like 23 updates, I unchecked 3.16-7-45 at first, but when I saw that 3.16-7-48 was available, I rechecked it, reasoning that it was probably safer not to skip it. As it turned out, the Software Updater appears to have skipped over it anyway.

I guess we live and learn. Beware of patches even if they are coming from “reputable” sources. Crippling the sound subsystem seems like something that should have been caught during testing and fixed before foisting it on users. The last two kernel updates that I’ve seen articles about were allegedly for security flaws – who /wouldn’t/ apply those? These last two update bundles are, hands down, the flakiest I’ve seen come from Suse/OpenSUSE (and I’ve been using it since the 9.0 days.)