when i play sounds, both my internal & external speakers are running in same time.
This disprove the quality of sound, how do i shutdown the internal speaker.
Under windows when the external speaker is plugged the internal speaker is muted automatically.
Depending on your PC hardware, this could be a bug, or it could simply be the autoprobe of your PC hardware did not succeed, and you need to manually tune this.
I can possibly suggest some configuration/software changes you could try (no guarantees) if you provide more information. In the case of openSUSE-11.1, you can do that, with your PC connected to the internet, by opening a gnome-terminal or a kde konsole and typing with root permissions twice:/usr/sbin/alsa-info.shthe first time it will update the diagnostic script, and the second time that will run the diagnostic script and post the output to a web site on the Internet. It will give you the URL of the web site. Please post that URL here. Just the URL.
If not openSUSE-11.1 you will have to tell us, so we can give you a different method to run the script.
Also, please to provide additional information, copy and paste the following commands one line at a time into a gnome-terminal or a konsole and post here the output: rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound
Thank you for answering me.
I’m using opensuse 11.1
- That script told that it will send informations to:Main Page - AlsaProject I accepted.
- Then it says that new version of alsa-info is found then I install it.
- Then it tell me that the script upgraded to v8.4.56 and says “to view the ChangeLog, please visit http://www.alsa-project.org/alsa-info.sh.changelog”
Every time that I execute the script it tell me that there is new update for alsa-info.
You need to run that script with root permissions. Root permissions is like administrator permissions (or something like that) in windows.
You can do that by first typing “su” (no quotes - enter root password when prompted) and then type:
/usr/sbin/alsa-info.sh
that will update the script (you need root permissions to update software in /usr/sbin - its a FUNDAMENTAL Linux concept). Then type that a second time:
/usr/sbin/alsa-info.sh
and it should work.
It worked and said my alsa information is located at:
“http://www.alsa-project.org/db/?f=97779c27b2148a4f6a6db65f042ca4517843299f”
Great! Thanks for that.
And the output from the rest of what I requested ??
Thank you for helping me ;), those are the informations you asked for:
rpm -qa | grep alsa:
alsa-plugins-pulse-1.0.18-6.13
alsa-oss-1.0.17-1.43
alsa-oss-32bit-1.0.17-1.37
alsa-1.0.18-8.9
alsa-utils-1.0.18-6.4
alsa-plugins-1.0.18-6.13
alsa-devel-1.0.18-8.9
rpm -qa | grep pulse:
libpulse0-0.9.12-9.5
alsa-plugins-pulse-1.0.18-6.13
libpulse-browse0-0.9.12-9.5
pulseaudio-utils-0.9.12-9.5
vlc-aout-pulse-0.9.8a-12.7
pulseaudio-module-x11-0.9.12-9.5
pulseaudio-module-lirc-0.9.12-9.5
pulseaudio-esound-compat-0.9.12-9.5
libpulse-mainloop-glib0-0.9.12-9.5
pulseaudio-0.9.12-9.5
pulseaudio-module-zeroconf-0.9.12-9.5
pulseaudio-module-jack-0.9.12-9.5
libpulsecore4-0.9.12-9.5
libxine1-pulse-1.1.15-20.8
pulseaudio-module-bluetooth-0.9.12-9.5
rpm -q libasound2:
libasound2-1.0.18-8.9
uname -a:
Linux linux-9c8i 2.6.27.19-3.2-default #1 SMP 2009-02-25 15:40:44 +0100 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/modprobe.d/sound:
options snd slots=snd-hda-intel
u1Nb.R4EXrvw0MND:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
Thanks for the configuration information …
I note you stated this symptom of your problem:
Before I go and possibly recommend something silly, by external speakers do you mean you plugged some external speakers into your headphone output jack ? (or someother speaker output jack) on your laptop? or do you mean USB speakers?
By external speaker I meant speaker plugged into speaker output jack and by internal speaker I ment the one integrated in my pc CU.
Integrated in your PC CU ? Do you mean the very basic speaker that all PC’s have? Or are you referring to a laptop’s integrated speakers?
I’m referring to a laptop’s integrated speakers.
i had an identical problem with my HP laptop (dv9000), with some old version of Opensuse that i dont remember (i think 10.2). I solved simply recompiling ALSA drivers, i did not have to touch any configuration file, after recompiling it was working just fine… Not sure if that would work for you too, anyway if you cannot solve in any other way i’d recommend to try that
OK, thanks!
Try updating your alsa sound driver. You can do so by opening a terminal or a konsole, type ‘su’ (no quotes - enter root password when prompted) and then with your laptop connected to the internet, copy and paste and execute the following commands one at a time in sequence, in that terminal or konsole:
zypper ar http://download.opensuse.org/repositories/multimedia:/audio/openSUSE_11.1/ multimedia
zypper install alsa alsa-devel alsa-oss alsa-oss-32bit alsa-plugins alsa-plugins-pulse alsa-utils alsa-tools alsa-firmware libasound2
zypper rr multimedia
zypper ar http://download.opensuse.org/repositories/multimedia:/audio:/KMP/openSUSE_11.1_Update/ multimedia
zypper install alsa-driver-kmp-default
zypper rr multimedia
then when complete, restart your PC and test the functionality.
Reference is here: Alsa-update - openSUSE
I acted like you said and restarted but still the same problem.
I’ll try to be more precise; it’s not a laptop that I’m talking about but a desktop pc, my computer have an integrated speaker inside the CU, NOT a buzzer but a small weak speaker like ones on laptops.
I didn’t mentioned it previously cause I thought it can be treated by the OS as a usual laptop speaker.
If it can help you I have a HP DX2400MT.
And thank you again for assisting me
I’m not familiar with the “CU” abbreviation. I’m certain its obvious to you, but not all of us get out and look at PC types all the time. I don’t suppose you could use the non-abbreviation? :\ Anyway, can you post what your rpms are now, so I can do a quality check to ensure you did not make a mistake ? ie output of:
rpm -qa | grep alsa
rpm -q libasound2
Its also possible the autoprobe of your alc888 did not pick the correct setting. In which case you could try to manually force a model option. To do that, take a look at the HD-Audio-Models.txt file for 1.0.19 of alsa, which has a list of options:
ALC883/888
==========
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
3stack-6ch 3-jack 6-channel
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
acer-aspire Acer Aspire 9810
acer-aspire-4930g Acer Aspire 4930G
medion Medion Laptops
medion-md2 Medion MD2
targa-dig Targa/MSI
targa-2ch-dig Targs/MSI with 2-channel
laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
lenovo-101e Lenovo 101E
lenovo-nb0763 Lenovo NB0763
lenovo-ms7195-dig Lenovo MS7195
lenovo-sky Lenovo Sky
haier-w66 Haier W66
3stack-hp HP machines with 3stack (Lucknow, Samba boards)
6stack-dell Dell machines with 6stack (Inspiron 530)
mitac Mitac 8252D
clevo-m720 Clevo M720 laptop series
fujitsu-pi2515 Fujitsu AMILO Pi2515
fujitsu-xa3530 Fujitsu AMILO XA3530
3stack-6ch-intel Intel DG33* boards
auto auto-config reading BIOS (default)
You could selective try each of those, one at a time, restarting your sound driver and your mixer between each application, testing your speaker. Lets say you decide to try “3stack-hp”. To do that, change your /etc/modprobe.d/sound file to:
options snd slots=snd-hda-intel
options snd-hda-intel model=3stack-hp
# u1Nb.R4EXrvw0MND:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
restart your alsa sound driver with su -c ‘rcalsasound restart’ entering root password when prompted for a password and then restart your mixer and test your speaker.
If that does not work, then lets say you wish to try “auto” next. Simply replace “3stack-hp” in the /etc/modprobe.d/sound file with “auto”, restart your alsa sound driver (as per above), restart your mixer, and test again. Do that for each model option, to see if one might work.
With CU I just meant central unit:). Those are the informations you requested meanwhile I’ll try to apply what you suggest, I admit that I didn’t fully understood the method but I’ll try to follow it.
rpm -qa | grep alsa:
alsa-oss-32bit-1.0.17.git20080715-2.23
alsa-1.0.19.git20090304-2.1
alsa-plugins-1.0.19.git20090303-1.8
alsa-oss-1.0.17.git20080715-2.23
alsa-plugins-pulse-1.0.19.git20090303-1.8
alsa-firmware-1.0.19.git20090120-2.1
alsa-tools-1.0.19.git20090120-2.1
alsa-driver-kmp-default-1.0.19.20090306_2.6.27.19_3.2-3.1
alsa-utils-1.0.19.git20090221-1.4
alsa-devel-1.0.19.git20090304-2.1
rpm -q libasound2:
libasound2-1.0.19.git20090304-2.1
What has you puzzled? What can I explain better?
The rpms looks ok.
Sorry for waiting so long to answer.
I wanted to notice that at startup an error message appear:
“HD alc 2100 failed to start, switching to default”.
Maybe that’s the source of the problem.
I don’t think so. That error message is quite common, and it may be possible to change a configuration to have it stop.
More important, does either of these two speaker tests work?
To test your sound I recommend you try each of these sound tests (as both a regular user, and with root permissions) to see if one might work:
speaker-test -Dplug:front -c2 -l5 -twav
Note Linux is case sensitive, and “D” is not the same as “d”. To stop the above test, while the konsole/xterm has the mouse focus, press <CTRL><C> on the keyboard. Note you should check your mixer settings (kmix if using KDE, and alsamixer if using Gnome) to ensure that PCM and Master Volume are set around 95%. After basic sound is established, you can back off on your sound levels to reduce distortion. Note the test for surround sound is different.
If that test yields errors, try instead this more simple test: speaker-test -c2 -l5 -twavTry as both a regular user and with root permissions. Ideally, you should hear a lady’s voice saying ‘FRONT LEFT’,‘FRONT RIGHT’ five times.
Its not uncommon that one of those tests will work, and the other not. What is important is at least one of them works.