Just installed 12.1 with Gnome. Everything is good exept sound.
When headphones are connected there is sound from them, it’s bit low, but it is there. But when I unplug them, there is no sound whatsoever.
Forgot to say, that I tested 12.1 from milestone5 onwards all the way to GM. This problem occured also in milestones. Because I was mainly interested in testing gnome 3.2, it wasn’t my main conserns. I tried to fix it then, but with no success. BUT somewhere during the beta-RC phase, this was fixed all by itself, I had set all the settings back to default when I got fed up with trying. I’m absolutely positive, that today I did all the things I did then and more.
From the diagnostic script I note a 64-bit openSUSE-12.1 with the 3.1.1-1-desktop kernel running on a ESPRIMO Mobile V6515 v.1.21 Fujitsu-Siemens laptop with 1.0.24.2 alsa utilities and 1.0.24 alsa driver. Your hardware has an ALC268 hardware audio codec.
Sound should be working from the speakers.
You could try forcing different alsa configurations upon boot to see if one of them work. The list of alsa model options (to force the configuration) are in the HD-Audio-Models.txt file that is on every openSUSE PC, and for the ALC268 in this subset of the list:
ALC267/268
==========
quanta-il1 Quanta IL1 mini-notebook
3stack 3-stack model
toshiba Toshiba A205
acer Acer laptops
acer-dmic Acer laptops with digital-mic
acer-aspire Acer Aspire One
dell Dell OEM laptops (Vostro 1200)
zepto Zepto laptops
test for testing/debugging purpose, almost all controls can
adjusted. Appearing only when compiled with
$CONFIG_SND_DEBUG=y
auto auto-config reading BIOS (default)
To force one of those options (say ‘3stack’) you add the following line to the START of the /etc/modprobe.d/50-sound.conf file:
options snd-hda-intel model=3stack
save the change, reboot and test. Do that for EACH option in that list, replacing ‘3stack’ with another option. ONLY test one at a time.
Now, that guidance is in the SDB:Audio troubleshooting - openSUSE guide you state you followed, but my guess is you simply skimmed by the portion, and did not understand what it was trying to explain to you to try.
Also - a question. I note a nVidia chipset for your sound. The graphic driver can on rare occasions impact the sound driver. What nVidia graphic driver are you using ?
You quess wrong.
I tested all of those. But there was a difference. I did not reboot, only did as is directed in the troubleshooting guide and commanded rcalsasound restart between changes. (and of course tested the sound) Should I test again with reboot?
I’m using nvidia proprietary driver from the nvidia repo. GPU is GeForce 8200M G.
Its difficult to guess EXACTLY what one tries when one does not provide specifics. I have read dozens of posts of users who stated they followed the troubleshooting guide, when in fact it was far from it. In fact, I venture 95% of users who say they follow it, did NOT. So I’m just going by the percentages.
Since you state you followed the troubleshoot guide, did you update your alsa like the guide suggests? To confirm you followed like you noted, please show me (so I can do a quality check) by providing the output of:
rpm -qa '*alsa*'
rpm -q libasound2
Apolgies, I know you stated I guessed wrong, but when I think back to the 95% … well, … I have to ask.
No, running ‘rcalsasound restart’ is sufficient IF you also run kmix (for kde) or alsamixer (for gnome). Also I recommend you tune your audio with the application ‘pulseaudio volume control’ (pavucontrol) , as pulse audio can add complications.
OK,
… but … I note:
That is not in the troubleshooting guide, but some other guide. It could mean you have kernel modules that are incompatible with your user space alsa apps, which could be contributing to this problem. ie by updating the kernel, you could have made this worse, and for that I can not help troubleshoot. You are on your own with a kernel that is not from the OSS or UPDATE repository.
It was the first thing that came to my mind. Before I red the troubleshooting guide. But then I couldn’t find a newer opensuse rpm’s for alsa. Then when I red the troubleshooting guide, I checked if there has been any changes affecting ALC268 and couldn’t find any. So I decided to forget it then, because I thought updating would be troublesome. Now I doublechecked and found that I was in error. there is newer version, I had just misred 12.1, when it was 121. I’ll try this next.
Yes, I had with me alsamixer, pavucontrol and YaST’s audio settings.
That was the last thing I did. After I had tested all the models. (but before alsa-test). Now I have to donwgrade before Iäll try anything else.
Hmmm … I note you grabbed the factory alsa-driver-kmp-desktop. If it were me, I would not have installed that, but I would have only installed the ‘user space’ alsa apps.
Anyway, my recommendation now is you write a bug report and get the attention of the SuSE-GmbH packager for sound (where the SuSE-GmbH sound packager is also an alsa driver developer). There is guidance here for that: openSUSE:Submitting bug reports - openSUSE and you can use your openSUSE forum username and password when logging on to bugzilla. Do not bother referencing a forum thread in that bug report, as the SuSE-GmbH packager will not read a forum thread. The bug report needs to be inclusive of all salient information. Be certain to attach to the bug report the file “alsa-info.txt” that you get by running
/sbin/alsa-info.sh --no-upload
Then monitor the bug report, checking on it every 2 to 3 days. The SuSE-GmbH packager will ask you questions and possible provide updates for you to try. Be certain to CLEAR the ‘NEED INFO’ flag when you reply to their questions on the bug report.
My experience is the SuSE-GmbH packager is VERY GOOD at solving sound problems.
Good Luck.
… edit - be certain your speaker cabling is correct . Apologies for that suggestion, but it had to be made.
I actully did something, I would not normally do. I reinstalled whole system. And hey, it worked! \o/
Installing has always been bit troublesome with this computer. Mainly because install wants to use nouveau, and nouveau doens’t work well with this GPU. Easiest solution for all my install problems I have found this far has been setting acpi=off. Now I installed without it, and it was a hell, but finally everything is good.
If you had paid attention, you would have noticed that this we are talking about a laptop lol!. For obvious reasons, I have not tampered with my speaker cabling…
First I am glad to read this is working now. Congratulations.
BUT not having a CAUSE and EFFECT would worry me if I were you. And if it were me, with functioning sound, I would document this configuration with the diagnostic script, and screen prints of my pavucontrol and mixer settings, so that if sound stopped, I would have a baseline to go back to.