I’m a new opensuse (and linux)-user and I think it’s great! But now I’ve got a problem:
When I want to listen to music or to watch a film by using only the headphones, the speakers also play it.
I googled it and there were many people with the same problem but I couldn’t find an answer.
In the application browser I changed the settings of the sound controller. Here’s a photo: http://i304.photobucket.com/albums/nn175/laura_4849/Bildschirmfoto-LautstrkereglerHDAAT.png
Usually it has to work now, doesn’t it?
Is someone able to help me or does anyone of you have the same problem? And please don’t write a complicated explanation;)
(sorry for my bad English, I’m from Austria and only 14… )
Laura, typically this happens when one’s hardware is relatively new, and one needs to either custom tune the existing alsa configuration, or one needs to update one’s driver (or it simply has not been fixed yet, and one has to write a bug report on alsa/opensuse).
Please, can you run a diagnostic script? Please with your pc connected to the internet, copy and paste the following into an xterm/konsole:
wget http://home.cfl.rr.com/infofiles/tsalsa && su -c 'bash ./tsalsa'
when prompted for a password, enter the root password. When the script is complete it will pass you a URL. Post that URL here
Also, please copy and paste following one line at a time into an xterm/konsole and paste output here: rpm -qa grep alsa
rpm -qa grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound
Hi Laura, you did it perfect, but I screwed up! :rolleyes: Can you type the following “corrected” commands and post here the output? rpm -qa | grep alsa
rpm -qa | grep pulse
You have an “interim” kernel version with 2.6.25.9. OpenSUSE-11 was released with 2.6.25.5. It was updated a few times, with the latest version being 2.6.25.11. The “problem” with keeping 2.6.25.9 is if you ever wish to use a “build service” application that needs a specific kernel, they tend to build only for the initial kernel (2.6.25.5) and the latest kernel (currently 2.6.25.11).
You could try some updates to the /etc/modprobe.d/sound file. I note you have an MSI VR610 with an ATI_SB and an ALC883 hardware audio codec. The ALSA-Configuration.txt file offers a number of different “model options” for the ALC883: Ref: Linux Kernel Documentation :: sound : alsa : ALSA-Configuration.txt
857 ALC883/888
858 3stack-dig 3-jack with SPDIF I/O
859 6stack-dig 6-jack digital with SPDIF I/O
860 3stack-6ch 3-jack 6-channel
861 3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
862 6stack-dig-demo 6-jack digital for Intel demo board
863 acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
864 acer-aspire Acer Aspire 9810
865 medion Medion Laptops
866 medion-md2 Medion MD2
867 targa-dig Targa/MSI
868 targa-2ch-dig Targs/MSI with 2-channel
869 laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
870 lenovo-101e Lenovo 101E
871 lenovo-nb0763 Lenovo NB0763
872 lenovo-ms7195-dig Lenovo MS7195
873 haier-w66 Haier W66
874 6stack-hp HP machines with 6stack (Nettle boards)
875 3stack-hp HP machines with 3stack (Lucknow, Samba boards)
876 6stack-dell Dell machines with 6stack (Inspiron 530)
877 mitac Mitac 8252D
878 auto auto-config reading BIOS (default)
Hence you could try each of those model’s in turn, until you find one that works. May I suggest you start with “auto”, followed by some others. How many plugs (audio in/out jacks) on the back of your laptop? Typically there are 3 or 6.
One possible /etc/modprobe.d/sound file edit you could try is:
save the change and restart your alsa from an xterm/konsole with root permissions with: rcalsasound restart and test your headphone/speakers. If that doesn’t work, then replace “auto” with some of the other options (restarting alsa with each attempt) such as “3stack-dig”, … etc … Note typically “3stack” refers to a PC with 3 audio plugs and “6stack” refers to a PC with 6 audio plugs. I do not know how many your PC has. Sometimes model assignments associated with another brand laptop will work with your laptop. (ie maybe “acer” or “medeon”, … etc … or another will work … its a trial and error approach).
There are many ways to do this. Most users will be told of the kernel update by SuSE updater (in the lower right hand corner of their desktop) and use that to update their kernel. Other users will do an update by YaST > Software > Software management. Some will use zypper in a konsole to do the update. Others will use a different software manager, such as Smart Software Package Manager. Some will even install the new kernel and keep the old kernel, and they do that by first downloading the kernel rpmto their hard drive, and they update the kernel by rpm command: "rpm -ivh kernel-<their-kernel-version.rpm>
In all cases, before doing a kernel update, I recommend 1st backing up one’s /boot/grub/menu.lst file, … and then after the kernel update is in place, BEFORE rebooting check the new /boot/grub/menu.lst file, against the old /boot/grub/menu.lst file, compare the two, and make certain the changes make sence. And only then reboot.
)