Internal Speakers Don't shut off When Connecting Headphones
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Internal Speakers Don't shut off When Connecting Headphones
I recently bought a Lenovo u350. I'm running Ubuntu 9.10 alpha 3 (it's the only distro that would install on this new model). Mostly, everything works, but when I plug in headphones, the internal speakers keep playing. This is pretty bad when trying to watch hulu or a movie at night or listening to music in the library. Anybody have a solution?
This is a known issue with **some** motherboards and/or **some** audio devices. However, in order for someone to help diagnose your exact situation, we need to know what audio device you are using. Also, I'm going to assume you're using ALSA, but if this is not correct, please advise.
So, to know your audio device, please provide the output of lspci -vvx and copy/paste the "Audio Device" section here for us.
Also, check in /proc/asound/ for a file called codec#0 and if that file exists, use the `cat` command to dump it to a text file, and paste that file's contents in here (the first dozen or so lines should have the necessary information I'm looking for, but it won't hurt to paste the whole thing).
Oops, my mistake! The codec#0 file should be in /proc/asound/card0/codec#0 -- sorry about that. If you could post the first paragraph of that file using the method I gave earlier, I'll have a look into this a bit later this evening.
PS - how new is the laptop? Like, is it a brand-new model, or a few months+ old?
Ok, from what I can tell, there is no exact provision for the audio device in that laptop in the latest stable kernel ALSA driver, likely because the thing is very new. However, there are lots of other lenovo products that ARE supported, so I'm going to give you something(s) here to try. This comes with no guarantee that any of them will work, or if one of them DOES work, that it won't make some other aspect of the audio get weird.
There's no risk of damaging anything; if something doesn't work, just undo it or remove it.
FIRST: If you haven't yet tried running `alsaconf` as root, do try that first, following any instructions it gives you (mostly it's clicking yes or no) and when that's done, test your headphone jack. Chances are that it still will be the same, but we like to try the easiest things first
Didn't help? Read on..
I don't use SuSE and am totally unfamiliar with it's ways of configuring things, so these instructions are *general* and apply to many Linuxes but not *every* Linux. If the SuSE way is a different location for the file I'm showing you here, then you or another SuSE user will have to straighten that part out and find the right location (the modprobe.conf file might be another place where this can be done).
Hopefully on your SuSE system, you have a folder called /etc/modprobe.d or a comparable location where you put options which get passed to kernel modules, like the sound modules, when they are loaded into the kernel. On my system, it uses /etc/modprobe.d so these instructions assume that location exists on yours too.
In that folder, see if you have a file called 'sound.conf' or something like this name, something that obviously looks like it's for the sound system. If you DO, rename it to something else temporarily (and while you're at it, paste its contents here for us).
Create a new file in there, called 'sound.conf' or some name like this that you like.
Inside the file, put the following lines:
Code:
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=laptop
The bold word above can be one of: laptop, lenovo-sky, lenovo, lenovo-x200, lenovo-101e, lenovo-nb0763, lenovo-3000, or quanta
These are all the known lenovo (laptop) configurations I could find in the driver. They are in no particular order here.
So make and save this file, and delete any automatic backup file that's created by saving it.
Now, reboot and test the sound system and headphone operation and speaker operation. If it is fixed, hooray. If not, try the next of the bold options, save the file, delete any auto-backup, and reboot & try again. Repeat...
There's no guarantee here, but I hope that your machine is similar enough to one of the supported machines, that one of the existing options will work for it.
Good luck!
Sasha
Last edited by GrapefruiTgirl; 08-19-2009 at 08:43 PM.
Reason: TYPO! reload page please.
As an electronics hardware guy, I can tell you the problem. There is usually a mechanical switch in those sockets to do that. It's probably misbehaving.
As an electronics hardware guy, I can tell you the problem. There is usually a mechanical switch in those sockets to do that. It's probably misbehaving.
While the above is certainly possible, a brand new computer should not have 'misbehaving' hardware; that said though, please define 'misbehaving' in this context?
That computer has automatic jack-sensing, and using Linux/ALSA, particularly with very new machines, it doesn't always work as expected, and/or needs to be enabled (i.e. the ALSA driver needs to know that functionality exists for it to work right). Worst case, the OP will need to manually mute the speakers using Kmix or whatever mixer he/she has available, again subject to the mixer having the proper controls for the sound chip..
I've been in class all day and haven't gotten a chance to try the ideas Sasha gave me. I've tried muting the internal speakers, but alsamixer only has a PCM control that affects headphones and speakers simultaneously. The computer is about a month old, so it probably isn't the jack. I don't know if Vista (what it came with) worked with the headphones or not, because the first thing I did was format the entire drive. I should have a chance to play around with it soon.
It is a linux problem.
I had the same problem on my debian install.
Searched for weeks for a solution,no go
Then I had a crash of the HD, and installed debian testing.
Problem solved, don't know what caused it though.
My guess would be alsa
If the controls are lacking in your mixer, it's a decent sign that the device/driver is not configged right. I was missing buttons and controls too (on my desktop machine) until I passed the right option to my audio driver. Then suddenly I had a LOAD of new buttons & sliders
Best of luck,
Sasha
PS - remember to try 'alsaconf' as root first, provided SuSE has the tool. That may be enough to do it, if you haven't done it yet.
Yep, that's the one! Especially if it's the ONLY sound-ralated file in there.
If the file already contains stuff, please post it here, and back it up so you know how it WAS first..
And remember you need to reboot -- the sound module doesn't seem to like being removed while running, so the changes will take effect upon reboot.
OK. I tried all the settings you listed, and none of them worked. The file did have some stuff in it--this is what it was originally (I appended the option lines on the end).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.