Hi… I just installed OpenSUSE 11.3/KDE4 and now I have no sound from the headphone jack. I checked Kmix and everything is fine.
I do remember that in OpenSUSE 11.2 I had this similar problem which I solved by switching ON/OFF the “Independent HP” option in Kmix. The problem with 11.3 is that this option is not available in Kmix.
I will appreciate any help. Thanks.
Is there any thing in our multimedia stickie of help ?
Welcome to multimedia sub-area
I still can’t solve the problem. So what I’m trying to do is install the alsa driver from the source code.
First I removed all alsa packages from the Software Management and then I tried installing it from the source code. But when I run:
./configure --with-cards=hda-intel --with-kernel=/usr/src/linux-headers-$(uname -r)
I get the following error:
The file /lib/modules/2.6.34.7-0.3-default/source/include/linux/autoconf.h does not exist.
Please install the package with full kernel sources for your distribution
or use --with-kernel=dir option to specify another directory with kernel
sources (default is /lib/modules/2.6.34.7-0.3-default/source).
And I have installed kernel source. So what other package am I missing?
Rather than try to compile a new alsa version, there are already packaged version of the alsa sound driver as rpms, packaged by an alsa developer specifically for openSUSE-11.3.
BUT before I pass you the link as to where you can find those rpms, can you please first provide some more information, per the URL link I provided above ?
ie …
please post in this “multimedia” sub-forum, providing in your post the following information:
- provide the URLs (of a summary webpage) that are created by running the diagnostic script … by … running the script
/usr/sbin/alsa-info.sh
and select the SHARE/UPLOAD option and after the script finishes it will give you a URL to pass to the support personnel. Please post here the output URL/website-address that gives. Just the URL/website-address. You may need to run that script twice (the first time with root permissions to update in the /usr/sbin directory, and the second time to get the URL).
.
Note if for some reason that gives you no website/url/address then run it with the no-upload option:
/usr/sbin/alsa-info.sh --no-upload
and post the file /etc/alsa-info.txt it creates to Pastebin.com and press SUBMIT on that site and again post here the URL/website-address it provides.
.
… some clarification on running the script “alsa-info.sh” … when you run:
/usr/sbin/alsa-info.sh
you should get something like this (if it asks for an update, select NO):
http://thumbnails33.imagebam.com/9280/a5973e92794041.jpg](http://www.imagebam.com/image/a5973e92794041)
followed by this (select the SHARE/UPLOAD option):
http://thumbnails30.imagebam.com/9280/5e84f992794044.jpg](http://www.imagebam.com/image/5e84f992794044)
followed by this (its quickest if you simply select ‘NO’ to seeing the output - you will see it on the web page) :
http://thumbnails32.imagebam.com/9280/214da092794048.jpg](http://www.imagebam.com/image/214da092794048)
followed by this (where in RED is the URL).
http://thumbnails23.imagebam.com/9280/d9858092794051.jpg](http://www.imagebam.com/image/d9858092794051)
Just post the URL you get (similar to the RED URL in my example, but yours will be different).
Again, if you can not get that, then run this with the no upload option:
/usr/sbin/alsa-info.sh --no-upload
which will create the file /tmp/alsa-info.txt. Copy that file and paste it on Pastebin.com and press submit. That will give you a URL address. Please post that URL here.
Also provide the following:
- in a terminal, or xterm, or konsole, type: rpm -qa ‘alsa’ #and post output here
- in a terminal, or xterm, or konsole, type: rpm -qa ‘pulse’ #and post output here
- in a terminal, or xterm, or konsole, type: rpm -q libasound2 #and post output here
- in a terminal, or xterm, or konsole, type: uname -a #and post output here
- in a terminal, or xterm, or konsole, type: cat /etc/modprobe.d/50-sound.conf #and post output here
Thank you for your reply.
Here is what I get from alsa-info.sh:
http://www.alsa-project.org/db/?f=98977e306b96d3d57e3518c657867ea32351baf1
rpm -qa 'alsa’
alsa-oss-1.0.17-29.2.i586
alsa-firmware-1.0.23-1.2.noarch
alsa-plugins-1.0.23-1.9.i586
alsa-utils-1.0.23-1.8.i586
alsa-1.0.23-2.12.i586
rpm -qa 'pulse’
libxine1-pulse-1.1.18.1-1.37.i586
libpulse0-0.9.21-10.1.1.i586
libpulse-mainloop-glib0-0.9.21-10.1.1.i586
rpm -q libasound2
libasound2-1.0.23-2.12.i586
uname -a
Linux linux.site 2.6.34.7-0.3-default #1 SMP 2010-09-20 15:27:38 +0200 i686 i686 i386 GNU/Linux
cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-hda-intel
# u1Nb.ugJ7Yg4UHm7:P5KPL-CM Motherboard
alias snd-card-0 snd-hda-intel
Thanks for providing the information I requested.
Your PC’s installed rpms look fine, but your PC’s mixer is misconfigured. Note in kmix, you simply launch the mixer (kmix) by clicking on the speaker icon in the lower right corner (or run kmix directly). Go to settings > channels and then simply drag and drop from left to right to add extra controls to the mixer.
I note this misconfiguration from the diagnostic script you ran for me:
!!Amixer output
!!-------------
!!-------Mixer controls for card 0 [Intel]
**
Card hw:0 ‘Intel’/‘HDA Intel at 0xf9ffc000 irq 27’**
Mixer name : ‘VIA VT1708B 8-Ch’
Simple mixer control ‘Master Front’,0
Front Left: Playback 0 [0%] -40.25dB] [on]
Front Right: Playback 0 [0%] -40.25dB] [on]
Simple mixer control ‘PCM’,0
Front Left: Playback 0 [0%] -51.00dB]
Front Right: Playback 0 [0%] -51.00dB]
Simple mixer control ‘Independent HP’,0
Capabilities: enum
Items: ‘OFF’ ‘ON’
Item0: 'OFF’The master volume control and PCM volume controls are both at 0%, guaranteeing NO sound. You MUST move those up. Put them up to 95% until sound is established, and then back off on the settings. Also, I note there IS an ‘Independent HP’ control in your mixer.
Simply add the control as I described above.
Well, that’s not the problem:
http://www.alsa-project.org/db/?f=166f44ca3cd877dd624ea2288903891f63ae8e84
I was trying this possible solution:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/582199/comments/20
but I’m having problem running HDA Analyzer (python-gtk is already installed):
/usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning)
So what I’m trying now is to install the ALSA driver from the source but I’m having the problem mentioned above.
I don’t know if there is a way to “downgrade” the ALSA driver version, because I didn’t have this problem in OpenSUSE 11.2/KDE.
Its possible the openSUSE sound packager, who is also an alsa developer, has already fixed this ?
Try updating to the latest alsa version using this guide for openSUSE: SDB:Alsa-update - openSUSE
Please check your rpm versions for alsa BEFORE you try to update per that guide, and then check again AFTER you update per that guide. If the alsa versions did not change, then you did not update correctly. My estimate is > 50% of the users who I ask to update using that guide refuse to follow the instructions as provided, and they fail to update correctly.
Good luck.
I fallowed the guide, but I still don’t have sound from the headphones.
Before updating:
Advanced Linux Sound Architecture Driver Version 1.0.22.1.
After updating:
Advanced Linux Sound Architecture Driver Version 1.0.23-git20100929.
Compiled on Sep 28 2010 for kernel 2.6.34.7-0.3-default (SMP).
I don’t know what else to try.
That before/after does not help tell what you did. It provides only limited information (ie gives a hint as to alsa-driver-kmp-default version). But the update notes to update alsa-oss, alsa-firmware, alsa-plugins, alsa-utils, alsa, libasound2. How can one tell from that post what alsa rpms were correctly updated?
Please, can you also provdie the output of:
rpm -qa '*alsa*'
rpm -q libasound2
uname -a
cat /etc/modprobe.d/50-sound.conf
and output URL provided by running script
/usr/sbin/alsa-info.sh
… and also confirm you rebooted after the update before conducting the test.
I did every step in:
SDB:Alsa-update - openSUSE
But I had a problem with zypper install alsa-driver-kmp-default. It show me some options like downgrading the kernel and driver or not installing it. So I joined the IRC SuSE channel and asked about which option should I choose, and someone told me none. He told me to use this:
zypper ar -f -r http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.3_Update/multimedia:audio:KMP.repo && zypper ref
rather than:
zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.3/ multimedia
And after that I had no problem.
Here is the rest of the information:
alsa-info.sh
http://www.alsa-project.org/db/?f=cbc06638bb2dfc43df63c84a465767a3dd4550c6
rpm -qa 'alsa’
alsa-utils-1.0.23-1.8.i586
alsa-1.0.23-2.12.i586
alsa-firmware-1.0.23-1.2.noarch
alsa-driver-kmp-default-1.0.23.20100929_k2.6.34.7_0.3-1.1.i586
alsa-oss-1.0.17-29.2.i586
alsa-driver-unstable-kmp-default-1.0.23.20100906_k2.6.34.7_0.3-39.1.i586
alsa-plugins-1.0.23-1.9.i586
rpm -q libasound2
libasound2-1.0.23-2.12.i586
uname -a
Linux linux.site 2.6.34.7-0.3-default #1 SMP 2010-09-20 15:27:38 +0200 i686 i686 i386 GNU/Linux
cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-hda-intel
# u1Nb.ugJ7Yg4UHm7:P5KPL-CM Motherboard
alias snd-card-0 snd-hda-intel
This is what you had originally:
alsa-oss-1.0.17-29.2.i586
alsa-firmware-1.0.23-1.2.noarch
alsa-plugins-1.0.23-1.9.i586
alsa-utils-1.0.23-1.8.i586
alsa-1.0.23-2.12.i586
.........
libasound2-1.0.23-2.12.i586
and now you have:
alsa-utils-1.0.23-1.8.i586
alsa-1.0.23-2.12.i586
alsa-firmware-1.0.23-1.2.noarch
alsa-driver-kmp-default-1.0.23.20100929_k2.6.34.7_0.3-1.1.i586
alsa-oss-1.0.17-29.2.i586
alsa-driver-unstable-kmp-default-1.0.23.20100906_k2.6.34.7_0.3-39.1.i586
alsa-plugins-1.0.23-1.9.i586
…
libasound2-1.0.23-2.12.i586
… when I read the guide, and go to the repository that the web site says to update from, I note these versions:
alsa-utils-1.0.23-25.1.i586.rpm
alsa-1.0.23-69.1.i586.rpm
alsa-firmware-1.0.23-8.1.noarch.rpm
alsa-oss-1.0.17-53.1.i586.rpm
alsa-plugins-1.0.23-33.1.i586.rpm
libasound2-1.0.23-69.1.i586.rpm
… my apologies if I sound picky but you did not update per the guide. Clearly the versions of alsa, alsa-firmware, alsa-oss, and alsa-plugins, alsa-firmware, libasound2 … did not change on your PC, even though there are newer versions available and even though I asked you check to ensure the versions updated.
Plus I note installed is alsa-driver-unstable-kmp-default-1.0.23.20100906_k2.6.34.7_0.3-39.1.i586 … That should NOT be installed and that practically guarantees sound will be broken. ie things are now worse than they were before.
To recover from this, you now need to:
(1) de-install BOTH alsa-driver-unstable-kmp-default-1.0.23.20100906_k2.6.34.7_0.3-39.1.i586 and alsa-driver-kmp-default-1.0.23.20100929_k2.6.34.7_0.3-1.1.i586
(2) re-install alsa-driver-kmp-default-1.0.23.20100929_k2.6.34.7_0.3-1.1.i586
(3) update as requested in the guide: alsa, alsa-firmware, alsa-oss, alsa-plugins, alsa-utils, libasound2 … . AND MOST IMPORTANT, after you “think” you have updated those, quadruple check to ensure !! I warned before to check this, you clearly thought you updated, but you did not. The guide even gives guidance in YaST how to ENSURE you update properly!
And then reboot and test.
The problem I have is when I run:
zypper install alsa-driver-kmp-default
I get the fallowing problem:
Problem: alsa-driver-kmp-default-1.0.23.20100929_k2.6.34.0_12-1.1.i586 requires kernel(default:drivers_usb_core) = 6faa2c62dac4f41d, but this requirement cannot be provided
uninstallable providers: kernel-default-2.6.34-12.3.i586[repo-oss]
kernel-default-base-2.6.34-12.3.i586[repo-oss]
Solution 1: Following actions will be done:
downgrade of kernel-default-2.6.34.7-0.3.1.i586 to kernel-default-2.6.34-12.3.i586
downgrade of preload-kmp-default-1.1_k2.6.34.7_0.3-19.1.3.i586 to preload-kmp-default-1.1_k2.6.34.0_12-18.2.i586
Solution 2: downgrade of kernel-default-base-2.6.34.7-0.3.1.i586 to kernel-default-base-2.6.34-12.3.i586
Solution 3: do not install alsa-driver-kmp-default-1.0.23.20100929_k2.6.34.0_12-1.1.i586
Solution 4: break alsa-driver-kmp-default by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c] (c):
I didn’t know which solution to choose, so I chose number 1 but after rebooting and selecting the downgraded kernel version, I still don’t have sound.
And just in case:
alsa-info.sh
http://www.alsa-project.org/db/?f=2d624e8b63cd2e6a3f50b5d39d37d5818dc1ea2c
rpm -qa 'alsa’
alsa-utils-1.0.23-25.1.i586
alsa-1.0.23-69.1.i586
alsa-oss-1.0.17-53.1.i586
alsa-plugins-1.0.23-33.1.i586
alsa-firmware-1.0.23-8.1.noarch
alsa-driver-kmp-default-1.0.23.20100929_k2.6.34.0_12-1.1.i586
rpm -q libasound2
libasound2-1.0.23-69.1.i586
uname -a
Linux linux.site 2.6.34-12-default #1 SMP 2010-06-29 02:39:08 +0200 i686 i686 i386 GNU/Linux
cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-hda-intel
# u1Nb.ugJ7Yg4UHm7:P5KPL-CM Motherboard
alias snd-card-0 snd-hda-intel
You selected the wrong choice. You should have NOT downgraded your kernel. Instead you should have stopped, and asked, why do you get those messages? Could something have been input wrong?
The reason you obtained that error is you possibly misread ?? the guide as you have used the WRONG repository for alsa when you have the 2.6.34.7 kernel, to which the guide is very explicit as to what repository to use. There are different alsa update repositories for the 2.6.34.7 and the 2.6.34.12. Instead you did not follow the correct section of the guide, and you used the alsa repository for the 2.6.34.12 kernel, which YaST/zypper then interpreted as meaning you wanted to also downgrade your kernel version.
Rather than blindly making choices, NEXT time you encounter such a message, I recommend you ask for guidance as to what selection you should make.
Its possible this new kernel, which you have now removed, contributes to fixing your problem.
You may also consider switching ON your simple mixer control ?
Simple mixer control 'Smart 5.1',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
although that may be irrelevant. I do not know.
I can also almost guarantee, custom compiling like you wish to do, is an advanced task that you won’t be able to do, given the struggles you are having with the alsa update guide. And even IF you were able to custom compile the kernel, my view is it will not make any difference, as those rpms you are attempting to install are more cutting edge and have more fixes than are what in the alsa tarball from the alsa site.
I’m beginning to think that I can’t help, as I am unable to give guidance that is clear enough. Possibly if you write a bug report, and get help from the openSUSE sound packager (who is also an alsa sound driver developer, and who is the one who packaged those rpms that you can’t correctly install using the guide instructions) and maybe he can communicate/help better than I.
Clearly I have failed miserably in my efforts to communicate/provide guidance.
There is guidance here for writing a bug report: openSUSE:Submitting bug reports - openSUSE
Write the bug report against openSUSE-11.3 component sound and attach to the bug report the file /tmp/alsa-info.txt that you get by running:
/usr/sbin/alsa-info.sh --no-upload
There is no point in referencing this thread as the openSUSE alsa driver packager/developer will refuse to read a forum thread.
I read other people are having similar problems that I do with others Linux distributions (like Fedora) and can’t find a solution. I will still try to search the Internet for a solution, because I didn’t have this problem in OpenSUSE 11.2.
Anyway, thank you very much for your time and help.
Apologies that I am not able to help.
If you write a bug report (as I noted above) I am very confident the openSUSE packager WILL be able to help you. He is an alsa developer, and one of a small handful of people who understand the Linux sound system upsidedown and backwards, to the bit level. We are fortunate to have him on openSUSE.
So write the bug report, include the attachment I noted, and then every 2nd day check on the status of the bug report. He will almost assuredly fix this, or help you over come any misconfiguration issues (if any).
Best of luck !!
I have the same problem with openSuse 11.3/Gnome. I have tried to set up the correct configuration using alsamixer in a terminal but it keeps defaulting back to the digital audio which has no captures. Any help would be greatly appreciated.
I recommend you start a new thread of your own, and as part of your first post, provide the information requested to be provided in the multimedia stickie: Welcome to multimedia sub-area … I know in my case, without that I have no likely possiblility of helping.
Here is the URL I was given to give to you. Where you said to post this seems to be closed. I hope this helps you.
http://www.alsa-project.org/db/?f=b379a96cacaa0bab23010420a122df2757978a90
Regards,
John
I note a Codec: VIA VT1708B, and it seems a lot of such users are having problems.
But PLEASE start a new thread. I did NOT mean to add on to the ‘locked stickie’, but rather add a post into the multimedia area and use the multimedia stickie as guidance for the information to provide in your post (clearly I typed that wrong initially). Again, the information to provide in ADDITION to the script output:
please post in this “multimedia” sub-forum, providing in your post the following information:
…
Also provide the following:
- in a terminal, or xterm, or konsole, type: rpm -qa ‘alsa’ #and post output here
- in a terminal, or xterm, or konsole, type: rpm -qa ‘pulse’ #and post output here
- in a terminal, or xterm, or konsole, type: rpm -q libasound2 #and post output here
- in a terminal, or xterm, or konsole, type: uname -a #and post output here
- for openSUSE-11.2 or newer
, in a terminal, or xterm, or konsole, type: cat /etc/modprobe.d/50-sound.conf #and post output here