I’ve spent about 3 hours on this to no avail so time to ask.
Can someone take a look at my alsa-info output? Thanks.
http://www.alsa-project.org/db/?f=4bc3b70491b81322294895481391977445c1060e
Another 4 hours in on this. What I have discovered is it is beginning to pop up elsewhere.
Basically I have a new motherboard and not well supported yet. Ubuntu forums seem to have a workaroud.
NOt sure if I can translate this into a SUSE fix but I’ll give it a shot.
It looks like you have two audio devices that use the same Driver this can cause confusion.
First try
Yast sound. try switching positions of the two devices ie make the second one default and it becomes the first one device 0 Get a test sound???
If you get a test sound but still don’t get output from programs
fist be sure you play open source format or do a switch to packman to get the proprietary codecs. Check multimedia form for details
Second install pavucontrol that will allow setting the output from any application to a output deviec
If the above does not work or you tried it all then come back for details to manually change the configs
.
I had tried all of your suggestions, but thanks for the reply.
As I observed at the Ubuntu link, it looks like the hardware is simply
too new for the present 13.2 line. My ‘fix’ which isn’t really a fix, but I needed
to move on, was to upgrade to Factory/Tumbleweed. This has sorted out the
problem. Of course now I have to learn a whole new system but it’s been awhile
since I’ve played around in factory. I like the new looks but miss the old icons.
Anyway, I’m off to tweak this release to my tastes.
-G
Well, Tumbleweed was a bust. After tinkering with it for a day, I discovered I was unable to run
VMWare Workstation which is mission critical for me. So I wiped out my root partition and reinstalled
13.2. Now, interestingly with my fresh install sound was once again working. However, after I ran my
first update to bring it in line with current patches, sound again stopped working so there is something
amiss with the latest updates. So again, I have broken sound but at least I have VMware again. Any tips for
sorting this mess out is appreciated.
You say the first update broke the sound. My suspicion is that was a massive update so it is very difficult to narrow down what in that update broke the sound.
I note the sound driver comes with a kernel update, but also possibly with pulse and alsa driver updates - so its VERY difficult to say what caused the breakage. Knowing the update was likely to break the sound, you could have tried smaller updates (ie don’t update kernel, alsa, pulse … other (?) all in one go) , testing your sound in between, so to better point a finger at the problem.
Now I looked at the previous alsa-info script output you provided and I did not read of anything amiss. I note your PC has an alc1150 and while new - I do think that should work. In the dmesg in one of the script outputs you provided I noted:
2.771572] sound hdaudioC0D0: ALC1150: SKU not ready 0x00000000
and that could suggest a problem with either the also driver or other aspect of alsa.
Given I can see no misconfiguration , likely the quickest approach is to get an alsa sound developer to look at this. The quick way to to that is to write a bug report on openSUSE-13.2 with the latest kernel (which ever version you have installed) noting it may have broke the sound for your PC’s alc1150. Why a bug report on openSUSE ? Because the packager for openSUSE sound also happens to be an alsa sound driver developer and if anyone can quickly sort this, he can.
There is guidance for writing bug reports here: openSUSE:Submitting bug reports - openSUSE Wiki . Log on to buzilla with your openSUSE forum user name and password. Attach to the bug report the script from running:
/usr/sbin/alsa-info.sh --no-upload
Do not bother referencing this forum thread as the alsa developer (open SUSE packager) will not read a forum thread. Instead ensure all salient information is in your bug report.
Check the bug report every day or so - as the packager may have questions for you. After you answer a question , clear the “NEED INFO” flag on the bug report.
I would have suggested you try a kernel update - but for all I know that may be what broke your vmware. Ensure the openSUSE packager notes you do not want to break vmware when you apply the sound fix.
Good luck.
Now I looked at the previous alsa-info script output you provided and I did not read of anything amiss. I note your PC has an alc1150 and while new - I do think that should work. In the dmesg in one of the script outputs you provided I noted:
2.771572] sound hdaudioC0D0: ALC1150: SKU not ready 0x00000000
and that could suggest a problem with either the also driver or other aspect of alsa.
Given I can see no misconfiguration , likely the quickest approach is to get an alsa sound developer to look at this. The quick way to to that is to write a bug report on openSUSE-13.2 with the latest kernel (which ever version you have installed) noting it may have broke the sound for your PC’s alc1150. Why a bug report on openSUSE ? Because the packager for openSUSE sound also happens to be an alsa sound driver developer and if anyone can quickly sort this, he can.
There is guidance for writing bug reports here: openSUSE:Submitting bug reports - openSUSE Wiki . Log on to buzilla with your openSUSE forum user name and password. Attach to the bug report the script from running:
/usr/sbin/alsa-info.sh --no-upload
Do not bother referencing this forum thread as the alsa developer (open SUSE packager) will not read a forum thread. Instead ensure all salient information is in your bug report.
Check the bug report every day or so - as the packager may have questions for you. After you answer a question , clear the “NEED INFO” flag on the bug report.
I would have suggested you try a kernel update - but for all I know that may be what broke your vmware. Ensure the openSUSE packager notes you do not want to break vmware when you apply the sound fix.
Good luck.
Okay so, I’m not sure if this will be at all helpful but I have reinstalled 13.2 and disabled all the repositories so that it is in a static ‘off the dvd’ state. Sound is working. Should I run a snapshot with alsa-inf
so that the developer can compare?
Thanks
I have uploaded both alsa-info outputs and submitted a bug report.
Many thanks.
If you go to the bug report - you will see the openSUSE sound packager (who is also an alsa sound driver developer) has replied to your bug report. Let us know if you need any help following his requests wrt tests.