SigmaTel STAC9205: Headphone Jack Not Working

Hi, thanks for your interest in reporting bugs!

Some additional information would be helpful in tracking down the problem. What version of Ubuntu are you running?

Also, could you download this file: http://alsa-project.org/alsa-info.sh and open up a terminal? Then navigate to the folder where you saved alsa-info.sh and run it in the terminal by typing:
bash alsa-info.sh
And then paste the URL in a comment here? Thanks!

I am using 8.10. The URL for the outcome is here: http://www.alsa-project.org/db/?f=d1988cc510d9eabb3f89eb4fed4179454e9ddae9

Again, many thanks.

I am currently experiencing the exact same problem with my Gateway T-1628 laptop. After looking around various forums it seems that this bug is being experienced by all users using any Gateway T-Series laptop. I am currently using Ubuntu 8.10, however this problem was previously non-existent in 8.04. The codec these laptops use is: SigmaTel STAC9205. Hope that information helps.

Here is my alsa info:
http://www.alsa-project.org/db/?f=b0d82d1aaaeb7822e68b816d7baa4d5a4eaa61ef

Thanks in advance

I have the same problem on the Gateway T-6386

I submitted this bug already: https://bugs.launchpad.net/ubuntu/+bug/325567

Yup, me too. Gateway T-6836.

http://www.alsa-project.org/db/?f=2512cd7649c23f5067eb6f773f2c646147f0e298

The same thing is happening with the microphone jack, too. If I plug in a mic before I boot, it'll work (but extremely quietly...), but if I unplug it and plug it back in, it doesn't work at all.
This is really frustrating. I've been reading other posts about people who are trying to get Skype working... why does Ubuntu have such trouble with sound?

I too am looking for a solution to this. It was working in intrepid (when I used an old kernel) but now in jaunty beta, the old kernel is causing other problems (no cpu scaling, etc.) and now a proper solution is more important.

In response to bgilbert I am not convinced this problem effects all T-series. I remember months ago trying a solution that worked for another T and not my T-6836.

What can I do to help diagnose this?

Same exact issue on my Gateway 6850FX with the SigmaTel STAC9205.

I've tried clean installs of 8.10 and 9.04 with no luck. I got it to work downgrading kernel with 8.10, but to many other issues to deal with.

Also tried compiling Alsa from source on 8.10 using a script from the Ubuntu Forums.

Will try to post Alsa output when booted in Ubuntu.

Same issue on t-1625 with STAC9205. I'm wondering how many kernels/alsa versions it takes to get this right, I'd really like to install 9.04.

I agree with both of you, and thank you: it does seem to be a STAC9205 problem. The Dell D830 is also effected by the same bug (also STAC9205), maybe looking for workarounds with that model will help ours?

Anyway, I am going to mark that bug as a duplicate and then change the title of our bug. Also, please change "This bug doesn't affect me" near the top of this page. I think the more attention this bug gets the better.

Running Jaunty 9.04 on a Gateway 6850FX with STAC9205 sound. Here is my ALSA info finally: http://www.alsa-project.org/db/?f=378423b82cae5f07ba960950ca595c5e6a4f9cbe

I have the same issue with the headphone jack with Jaunty Beta on a Gateway T 6836, the headphone jack worked on intrepid if the headphones were plugged before the booting, but now in Jaunty it doesn't work any more.

psychelf: So is everything working completely (speakers/headphones etc.)?

Sorry forgot to include that in that post. The headphone/external speaker jack is still not working on 8.10 or 9.04 (Jaunty).

The problem seem to be fixed in ALSA 1.019. Now I use the pachtend alsa-driver 1.0.19 from linuxant on my Ubuntu 8.10 and it works fine, with kernel 2.6.27-9 and 2.6.27-11. All problems are solved for me! I have also tested the version 1.0.18 from linuxant, but this version doesn't work.

My system is a Dell D830 with STAC9205.

Can you walk us through what you did? I assume you just installed the deb from http://www.linuxant.com/alsa-driver/ I'm actually trying that now.

Also, if you could run this: http://www.alsa-project.org/alsa-info.sh and respond with the output, it would help a lot. Thank you!

Okay, I can report back that on 8.04 and kernel 2.6.28-11, installing that deb file did not change anything. Still no sound from headphones.

After installing the deb on Ubuntu 8.10 and kernel 2.6.27-11, I am sad to say that there was a change for the worse. I now can no longer hear anything through the headphones even when I have them plugged in on startup.

Does anyone know how to undo what this treacherous linuxtant patch has done?

1. Driver from linuxant
I need the alsa-driver-linuxant not primary to fix the issues with the kernel driver but to use the
build in hsf-modem. So the easiest way to install the driver is to run the installscript from
http://www.linuxant.com/drivers/hsf/downloads-installer.php.

Is also possible to install the deb from
http://www.linuxant.com/alsa-driver/.
It did this to.

The informatin you whished is saved on
http://www.alsa-project.org/db/?f=90a96ab10c887c418e6f3532f746472af986aec5

I think, it should be also possible to use the original driver from the ALSA project and build the
drive direct from source. The fixes are probably not made from linuxant. I only use this package,
because I need my hsf modem and linuxant build in an alsa-patch for the modem driver.

And it was important to remove options for the alsa driver in the /etc/modprobe.d/alsa-base. No
“options snd-hda-intel model=ref” or “options snd-hda-intel model=dell-m44” are possible. In
both case the sound through the headphones is missing.

I am having the same problem on a Gateway t-1625 laptop/STAC9205 running the Jaunty Release Candidate. The output of the alsa-info script is attached. I've been working on it at the ubuntu forums as well, but so far I'm not having any luck: http://ubuntuforums.org/showthread.php?p=7117161#post7117161 If this would work, jaunty would be perfect for me, unfortunately, this is a pretty major bug for me personally.

I tried the linuxant driver, and still have no sound in my headphones. I also removed the line "options snd-hda-intel model=dell-m44" from my /etc/modprobe.d/alsa-base.conf file. Still nothing. Is L Schmiedl the only person who has gotten the headphone jack to work?

FYI,,,,Found this bug on alsa: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4343

Some additional information:

1.
I don't have pulseaudio installed.

2.
I use my dell d830 in conjunction with a docking station from dell. And so
I have two headphone jacks in my system. One is build in the notebook and
one is build in the docking station.
Maybe it is important, but I never had problem with the headphone jacks in
the docking station. This jack is married with the IEC958 switch in the alsa-
mixer. And it is not possible to control this headphone jacks with the master
control in the alsa-mixer.

3.
Since the update from kernel 2.6.26-9 to 2.6.26-11 the internal headphone
jacks seems to work a little bit. I got sound through the headphone but the
driver is not really clean.
Some devices now are missing in the alsa-mixer and the master control has
a own live. It is not possibly to decrease the sound level. If I to the this, the
sound increase like from ghost hand.

4.
For both kernels, 2.6.26-9 and 2.6.26-11, I can solve the problem with the alsa
driver 1.0.19 but not with 1.0.18 (both from linuxant). Furthermore the older
kernel 2.6.24 (from Ubuntu 8.04) works without problems on Ubutu 8.10. And
this kernel work fine with alsa-driver 1.017 (from linuxant) to.

I think the problem is contained in a change from alsa 1.0.17 to 1.0.18. And
I can remember to read an entry in a change look from alsa project about a
change in a initialization sequence of the stac92xx. Unfortunately I can't find
this entry again.
Maybe the analog ports of the stac92xx are note used in the same manner on a
dell notebook as on a gateway notebook. And maybe a chance in alsa 1.019 only
fix issues in a configuration of stac92xx like in a dell systems.

Is there any other information that I can provide that might help with this? I'd like to help fix this, but I'm not sure that I have the necessary knowledge to do so. I will gladly test possible fixes if asked.

i have the same problem nos soun on the headphones

http://www.alsa-project.org/db/?f=6680f490f1371744a023a7119eea1dc6717d776e

I can confirm this issue on the Gateway T-6828, both under ALSA 1.0.18rc3 (Jaunty) and ALSA 1.0.19. I can also confirm that downgrading to ALSA 1.0.16 and kernel 2.6.24-22-generic *worked in the past*--I can't say now, as I haven't tried with Jaunty.

Output of alsa-info.sh is here: http://www.alsa-project.org/db/?f=4d8a44c9570c78c302e5b91002294756c5d4ffa6

(Also, I think something might be wrong with the alsa-info.sh script. Everytime I ran it, it erased itself, thinking it had a new version, until I removed the update function calls.)

This is an issue that has persisted for four kernel updates and three ALSA updates. It causes significant impairment of sound in Ubuntu for what seems to be almost an entire line of laptops, if posts in the forum are to be believed. By virtue of its antiquity and ubiquity, it should be given a bit higher priority than 'undecided', if at all possible.

This affects me too, with a Geteway T series.

I am using Kubuntu 9.04 AMD64.
Alsa-info.sh here: http://www.alsa-project.org/db/?f=4260b0c68d3b8fb8cd84e6ea59a945b957808a7d

I can confirm this bug on my Gateway T-1628. I've been dealing with this bug from Ubuntu 8.10 .. but now the headphones are not working .. in any way. I'm upgraded from Ubuntu 9.04, replacing /etc/pulse/* config files with the newest, and the /etc/modprobe.d/* ... too.
Also, I've tried all the mode options listed in the Alsa-configuration list . for the STAC9205 ..., but any of them worked for me..
Here I left the alsa-info.sh : http://www.alsa-project.org/db/?f=9a7fd05d6e5ae80c78aaa5658902a9d9e6b6d0ad.

Thanks

I also have the problem with a Gateway T1625. I tried a fix I saw somewhere about using package 'alsamixer-jack', but it did not work. I am dual booting, so I can go to Vista if I have to to listen. BUT, this is the last problem left on my Ubuntu install. (The first was multiple driver installation on my wlan). Soooo, if this is fixed, I have effectively replaced my vista install for 99% of my daily usage. I would love that.

This is an important update.

My laptop (a Gateway T-series (Turion 64x2)) have start to get output signal from the jack, right now I am using my externals speakers, but the internal speakers don't get muted, but at least thats less problems to deal with.

What I did I think is not useful, because I cant make the problem come back again, to be able to confirm the workaround, but I will post it anyway.

1)Open Kmix
2)Select configure channels
3)Add everything
4)I unmute a muted control called “Analog Loopback”
5)Done!

The system got freeze for 2 seconds and then the speakers sounds, the problem as I mention before, is that now even with the control muted, the speakers sounds.

If anyone need some information about my laptop just ask.

PS: Now a problem from 8.10 has been corrected, a problem that wont let you change in real-time from internal speakers → external speakers and vice versa.

I can confirm having the same issue with headphone jacks on Ubuntu 9.04 Jaunty Jackalope, 32 bits.

When headphones are plugged in, the speakers are muted but no sound comes from the headphones.

My laptop has the following features:
Gatewat T-1625
AMD Turion 64 X2 TL-60
SigmaTel STAC9205 codec

Alsa-info.sh here:
http://www.alsa-project.org/db/?f=9dc9d90e42726deac65af83da2a398cee5bfadfc

Is there any other helpful info that should be provided ??

Confirmed on Gateway T-1625 with 9.04 - 32 bits.

Hi guys!
 I've made my headphones work :). I've found the solution in this thread:
  http://ubuntuforums.org/showthread.php?p=6589810#post6589810

 Download the script and run with the options "-di"

   sudo ./AlsaUpgrade-1.0.x-rev-1.17.sh -di

 Then reboot, and everything works !!

 Basically the script, download the last version of alsa (1.0.20) and then compile it.

 I can cofirm that this bug is solved with that version of alsa, and is working in:
  Gateway T-1625
  Ubuntu 9.04 - 64 bit

Cheers and I hope this work for you! :)

P.S: I wondering why ubuntu not update the alsa version to 1.0.20 ?

This solved the issue for me as well! Thanks a million Andrix....this bug has plagued me far too long.

I see the headphone option now, but it's still not working. And my keyboard
volume keys seem to be changing PCM, instead of Speaker, even after changing
the preferences...

Looks like a vast improvement at least.

On Fri, May 22, 2009 at 3:51 PM, Andrix <email address hidden> wrote:

> Hi guys!
> I've made my headphones work :). I've found the solution in this thread:
> http://ubuntuforums.org/showthread.php?p=6589810#post6589810
>
> Download the script and run with the options "-di"
>
> sudo ./AlsaUpgrade-1.0.x-rev-1.17.sh -di
>
> Then reboot, and everything works !!
>
> Basically the script, download the last version of alsa (1.0.20) and then
> compile it.
>
> I can cofirm that this bug is solved with that version of alsa, and is
> working in:
> Gateway T-1625
> Ubuntu 9.04 - 64 bit
>
> Cheers and I hope this work for you! :)
>
> P.S: I wondering why ubuntu not update the alsa version to 1.0.20 ?
>
> --
> SigmaTel STAC9205: Headphone Jack Not Working
> https://bugs.launchpad.net/bugs/306755
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ALSA driver: New
> Status in “linux” source package in Ubuntu: Confirmed
>
> Bug description:
> The headphone jack does not work on the Gateway T-6836. When headphones
> are plugged in, the speakers are muted but no sound comes from the
> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA
> 1.0.16.
>
> This is a Regression and should be marked as such (I don't know how). The
> original description follows:
>
> My headphone jack works perfectly fine upon turning the computer on or
> restarting it if the headphones are already in it. If I take the headphones
> out and put them back in, it stops working. If they are not in when I turn
> the computer on, and then I put them in, it doesn't work. If they are
> working and then I put the computer into hibernate, they stop working when I
> wake it up. If the volume is muted when I turn the computer on, the sound
> does not work even if I unmute it. If I log out and then back in, it does
> not fix it
>

Oh, fixed the volume keys problem. Apparently it's a separate setting from
the volume applet selection.

On Fri, May 22, 2009 at 7:07 PM, Thomas <email address hidden> wrote:

> I see the headphone option now, but it's still not working. And my keyboard
> volume keys seem to be changing PCM, instead of Speaker, even after changing
> the preferences...
>
> Looks like a vast improvement at least.
>
>
> On Fri, May 22, 2009 at 3:51 PM, Andrix <email address hidden> wrote:
>
>> Hi guys!
>> I've made my headphones work :). I've found the solution in this thread:
>> http://ubuntuforums.org/showthread.php?p=6589810#post6589810
>>
>> Download the script and run with the options "-di"
>>
>> sudo ./AlsaUpgrade-1.0.x-rev-1.17.sh -di
>>
>> Then reboot, and everything works !!
>>
>> Basically the script, download the last version of alsa (1.0.20) and then
>> compile it.
>>
>> I can cofirm that this bug is solved with that version of alsa, and is
>> working in:
>> Gateway T-1625
>> Ubuntu 9.04 - 64 bit
>>
>> Cheers and I hope this work for you! :)
>>
>> P.S: I wondering why ubuntu not update the alsa version to 1.0.20 ?
>>
>> --
>> SigmaTel STAC9205: Headphone Jack Not Working
>> https://bugs.launchpad.net/bugs/306755
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in ALSA driver: New
>> Status in “linux” source package in Ubuntu: Confirmed
>>
>> Bug description:
>> The headphone jack does not work on the Gateway T-6836. When headphones
>> are plugged in, the speakers are muted but no sound comes from the
>> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA
>> 1.0.16.
>>
>> This is a Regression and should be marked as such (I don't know how). The
>> original description follows:
>>
>> My headphone jack works perfectly fine upon turning the computer on or
>> restarting it if the headphones are already in it. If I take the headphones
>> out and put them back in, it stops working. If they are not in when I turn
>> the computer on, and then I put them in, it doesn't work. If they are
>> working and then I put the computer into hibernate, they stop working when I
>> wake it up. If the volume is muted when I turn the computer on, the sound
>> does not work even if I unmute it. If I log out and then back in, it does
>> not fix it
>>
>
>

This fix does not work on the T-6828, regrettably.

As a correction to my previous post, this -does- work on the T-6828. The issue with mine was that it required a line to be appended to /etc/modprobe.d/alsa-base.conf, and the computer restarted:

options snd-hda-intel enable_msi=0 model=eapd

O happy day!

It 's really great hear that that *workaround* work for almost every of you! I think we must comment on some threads in ubuntuforums to spread the news to all the people who has this problem with the Sigmatel. I'm an old linux user that I can hack some stuffs to get things done, but for the new users it's very unpleasant to plug him/her headphone and doesn't work, so we must spread the solution :).

Also, I think Ubuntu must include the alsa-*.1.0.20 packages as soon as possible.

Cheers,
 Andrés

That does it! I wonder what that technically does, though...
Hooray for fixing problems that should have been fixed a long time ago! Now
let's all sit back and hope that the next release candidate won't break it
again.

On Sat, May 23, 2009 at 5:30 AM, Rob Yurkowski <email address hidden> wrote:

> As a correction to my previous post, this -does- work on the T-6828. The
> issue with mine was that it required a line to be appended to
> /etc/modprobe.d/alsa-base.conf, and the computer restarted:
>
> options snd-hda-intel enable_msi=0 model=eapd
>
> O happy day!
>
> --
> SigmaTel STAC9205: Headphone Jack Not Working
> https://bugs.launchpad.net/bugs/306755
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ALSA driver: New
> Status in “linux” source package in Ubuntu: Confirmed
>
> Bug description:
> The headphone jack does not work on the Gateway T-6836. When headphones
> are plugged in, the speakers are muted but no sound comes from the
> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA
> 1.0.16.
>
> This is a Regression and should be marked as such (I don't know how). The
> original description follows:
>
> My headphone jack works perfectly fine upon turning the computer on or
> restarting it if the headphones are already in it. If I take the headphones
> out and put them back in, it stops working. If they are not in when I turn
> the computer on, and then I put them in, it doesn't work. If they are
> working and then I put the computer into hibernate, they stop working when I
> wake it up. If the volume is muted when I turn the computer on, the sound
> does not work even if I unmute it. If I log out and then back in, it does
> not fix it
>

Well, this fixed the headphone jack problem however trouble is nowhere away from my T-1625. Is it only me or are you guys also having problems with getting simultaneous audio out of different sources? Besides, my Flash player is not able to produce any sound anymore. Any ideas?

I have the same problem with Flash, no sound. I went through all the different mixers available, and all the 'option' settings for playback in the Alsa Mixer, to no avail.

For now, the music playback will soothe me while I code, but since I watch a lot of dance videos on youtube, I would love to have flash player back.

I will try the snapshot later today and see what happens.

I installed the snapshot (-snap instead of -di), and it works beautifully for me--both flash and multiplexed sound.

We can confirm that this works on the:

T-1625
T-6828

Pending confirmation from the T-6838 crowd, and that -snap works for everyone else, I'll close the bug as 'resolved'.

I'm T-6836, and it works for me with the addition of the following line in
/etc/modprobe.d/alsa-base.conf:
options snd-hda-intel enable_msi=0 model=eapd

--Thomas

On Sun, May 24, 2009 at 12:26 AM, Rob Yurkowski <email address hidden> wrote:

> I installed the snapshot (-snap instead of -di), and it works
> beautifully for me--both flash and multiplexed sound.
>
> We can confirm that this works on the:
>
> T-1625
> T-6828
>
> Pending confirmation from the T-6838 crowd, and that -snap works for
> everyone else, I'll close the bug as 'resolved'.
>
> --
> SigmaTel STAC9205: Headphone Jack Not Working
> https://bugs.launchpad.net/bugs/306755
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ALSA driver: New
> Status in “linux” source package in Ubuntu: Confirmed
>
> Bug description:
> The headphone jack does not work on the Gateway T-6836. When headphones
> are plugged in, the speakers are muted but no sound comes from the
> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA
> 1.0.16.
>
> This is a Regression and should be marked as such (I don't know how). The
> original description follows:
>
> My headphone jack works perfectly fine upon turning the computer on or
> restarting it if the headphones are already in it. If I take the headphones
> out and put them back in, it stops working. If they are not in when I turn
> the computer on, and then I put them in, it doesn't work. If they are
> working and then I put the computer into hibernate, they stop working when I
> wake it up. If the volume is muted when I turn the computer on, the sound
> does not work even if I unmute it. If I log out and then back in, it does
> not fix it
>

Rob,
 it's possible to notify the ubuntu alsa package mantainer to promote the alsa-*1.0.20 or greater to an upgrade of alsa for jaunty, or for karmic ?

I don't think saying anything will help. I know that there are some hard feelings about the rate that ALSA gets pushed into the repos, but keep in mind that 1.0.17 was released when we were affected. While it's true that subsequent upgrades of ALSA usually make the entire world better, I'm sure there are a plethora of other bugs that will be caused by 1.0.20, and most of them will have to be resolved before it's pushed into the main repos. That's one of the disadvantages of Ubuntu: it has to cater to the largest base of all distros, and so you can both be left waiting or left behind.

It might also be an issue of time; I urge anyone and everyone interested in keeping the Ubuntu repos up-to-date to look into becoming a MOTU (https://wiki.ubuntu.com/MOTU), so that others might be able to spend more time on Jaunty-main.

That said, I can all but guarantee that it'll be hitting the karmic-proposed repo (it might be too late to make the freeze, but given that it's only late May, I doubt it). It'll make Jaunty, eventually, but we're still at 1.0.18 right now.

In summary, progress will come, just slowly. The important thing is that we have a fix.

Using a t-1625 gateway, the -snap did not fix the flash problem. Additional notes, once the flash player has played, if I stop rhythmBox (my usual player), I cannot get it to play anymore. Even if I shut it down and restart it, it won't play - the play button depresses, and then it stops and the progress bar does not advance.

The last thing left to try is the configuration options. I will try them and then feed all this back to the Alsa folks.

If I just didn't want to play flash . . . . . it would be like I had no problems ;-)

Well, I would have to say that the original bug is fixed. The extra line :
     options snd-hda-intel enable_msi=0 model=eapd
didn't fix anything related to rhythmbox being stopped by playing flash first. But THE HEADPHONES NOW WORK, which is the original bug.
.
On a more positive note, the alsaPlayer works fine with flash playing at the same time, before or after. So I guess I'll just switch to the AlsaPlayer. I'll probably talk to the RhythmBox folks eventually.

I was able to fix multiplexed sound problem by changing everything to PulseAudio Sound Server in System>Preferences>Sound. I use Exaile (and I love and recommend it) as a media player and works fine.
The wierd thing is, Flash works in Opera browser but not in Firefox. Apparently it has something to do with FF configuration but I don't know what it is.

Found another side effect of fixing this bug, mplayer now only plays in some kind of "frame every 2 seconds" mode. Totally unusable. This is playing quicktime movies. So, I guess I will continue to use windows for some things. If I wasn't unemployed, or a better programmer, I'd offer some help.

Not exactly sure why these settings are now necessary, or if they got changed by the udate script, but the mplayer problem is now fixed, YeeeeeHaaaaaaw. I used this - https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/221488/comments/7

I've noticed that too, but I mistakenly thought it was related to the flash
problem, because I only ever use Mplayer as an embedded player in Firefox.

On Sun, May 24, 2009 at 8:17 PM, gearond <email address hidden> wrote:

> Found another side effect of fixing this bug, mplayer now only plays in
> some kind of "frame every 2 seconds" mode. Totally unusable. This is
> playing quicktime movies. So, I guess I will continue to use windows for
> some things. If I wasn't unemployed, or a better programmer, I'd offer
> some help.
>
> --
> SigmaTel STAC9205: Headphone Jack Not Working
> https://bugs.launchpad.net/bugs/306755
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ALSA driver: New
> Status in “linux” source package in Ubuntu: Confirmed
>
> Bug description:
> The headphone jack does not work on the Gateway T-6836. When headphones
> are plugged in, the speakers are muted but no sound comes from the
> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA
> 1.0.16.
>
> This is a Regression and should be marked as such (I don't know how). The
> original description follows:
>
> My headphone jack works perfectly fine upon turning the computer on or
> restarting it if the headphones are already in it. If I take the headphones
> out and put them back in, it stops working. If they are not in when I turn
> the computer on, and then I put them in, it doesn't work. If they are
> working and then I put the computer into hibernate, they stop working when I
> wake it up. If the volume is muted when I turn the computer on, the sound
> does not work even if I unmute it. If I log out and then back in, it does
> not fix it
>

Bingo. That does it.

On Sun, May 24, 2009 at 8:37 PM, gearond <email address hidden> wrote:

> Not exactly sure why these settings are now necessary, or if they got
> changed by the udate script, but the mplayer problem is now fixed,
> YeeeeeHaaaaaaw. I used this -
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/221488/comments/7
>
> --
> SigmaTel STAC9205: Headphone Jack Not Working
> https://bugs.launchpad.net/bugs/306755
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ALSA driver: New
> Status in “linux” source package in Ubuntu: Confirmed
>
> Bug description:
> The headphone jack does not work on the Gateway T-6836. When headphones
> are plugged in, the speakers are muted but no sound comes from the
> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA
> 1.0.16.
>
> This is a Regression and should be marked as such (I don't know how). The
> original description follows:
>
> My headphone jack works perfectly fine upon turning the computer on or
> restarting it if the headphones are already in it. If I take the headphones
> out and put them back in, it stops working. If they are not in when I turn
> the computer on, and then I put them in, it doesn't work. If they are
> working and then I put the computer into hibernate, they stop working when I
> wake it up. If the volume is muted when I turn the computer on, the sound
> does not work even if I unmute it. If I log out and then back in, it does
> not fix it
>

Is anyone else having trouble with runaway CPU usage after upgrading ALSA?
Now and then my fan will start going full-speed, and my processors are fully
loaded, but I can't find a pattern to it. And it's only started recently.

--Thomas

On Sun, May 24, 2009 at 9:01 PM, Thomas <email address hidden> wrote:

> Bingo. That does it.
>
>
> On Sun, May 24, 2009 at 8:37 PM, gearond <email address hidden> wrote:
>
>> Not exactly sure why these settings are now necessary, or if they got
>> changed by the udate script, but the mplayer problem is now fixed,
>> YeeeeeHaaaaaaw. I used this -
>>
>> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/221488/comments/7
>>
>> --
>> SigmaTel STAC9205: Headphone Jack Not Working
>> https://bugs.launchpad.net/bugs/306755
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in ALSA driver: New
>> Status in “linux” source package in Ubuntu: Confirmed
>>
>> Bug description:
>> The headphone jack does not work on the Gateway T-6836. When headphones
>> are plugged in, the speakers are muted but no sound comes from the
>> headphones. It is fixed by downgrading to kernel 2.6.24-22-generic and ALSA
>> 1.0.16.
>>
>> This is a Regression and should be marked as such (I don't know how). The
>> original description follows:
>>
>> My headphone jack works perfectly fine upon turning the computer on or
>> restarting it if the headphones are already in it. If I take the headphones
>> out and put them back in, it stops working. If they are not in when I turn
>> the computer on, and then I put them in, it doesn't work. If they are
>> working and then I put the computer into hibernate, they stop working when I
>> wake it up. If the volume is muted when I turn the computer on, the sound
>> does not work even if I unmute it. If I log out and then back in, it does
>> not fix it
>>
>
>

Not to that degree.

In windbloze, with winamp, exact same machine, playing MP3s uses about 3-6 %of the CPU.
This is with a DSP module engaged that changes tempo rate without changing pitch. THAT is, with tempo change to zero, not really doing anything.

Using Alsa on Ubuntu it uses about 18-20% CPU.
Pretty bad actually. I don't use any extra filters on the linux version.

 But it doesn't seem to affect much of what I do, since it's browsing,mail, music, and simple web programming that I do.

Running Jaunty 9.04 on Gateway 6850FX laptop and ran ALSA upgrade script with -di option as -snap would not work for some reason. Also added "options snd-hda-intel enable_msi=0 model=eapd". Headphone jack is now working. Hopefully it will stay working. :) Here is ALSA info after upgrade and jack working: http://www.alsa-project.org/db/?f=57e45f43cc7f508384d17126bcfb3cfff44e75f6 . Thanks to those who found this fix!

I'm running Jaunty 9.04 64 bit on Gateway T-6836. I've had the "headphone not working" problem since installation. I have tried the suggestions posted here, to no avail. Simply for clarification, what I was able to gather from the instructions posted here, I am supposed to open a terminal and enter:

     sudo /AlsaUpgrade-1.0.x-rev-1.17.sh -di

Doing so merely sends back the message:

     sudo: /AlsaUpgrade-1.0.x-rev-1.17.sh: command not found

I have also tried the next suggestion:

     sudo /AlsaUpgrade-1.0.x-rev-1.17.sh -snap

Still nothing.
The next suggestion I was able to decipher from these cryptic forum postings was that I had to enter this into terminal:

    /etc/modprobe.d/alsa-base.conf
    options snd-hda-intel enable_msi=0 model=eapd

Which returned this:

     command not found

Obviously, I am missing something here. Would anyone be able to break this down as though they were explaining it to a child? An exact step-for-step set of instructions, with no knowledge being assumed would be spectacular. Thanks everyone.

infinitree,

    in the command you posted above you are missing the "dot" before the "/", you have to enter:

          sudo ./AlsaUpgrade-1.0.x-rev-1.17.sh -di (Note the dot before the slash)
    or
          sudo sh AlsaUpgrade-1.0.x-rev-1.17.sh -di

  about the other suggestion you don't have to execute in a terminal, you have to edit the file /etc/modprobe.d/alsa-base.conf in any text editor in linux, for example:

           sudo gedit /etc/modprobe.d/alsa-base.conf (you will edit the file alsa-base.conf with Gedit editor)

after you open the file with the any editor you choose, you can *try* adding this line to the end of the file

   options snd-hda-intel enable_msi=0 model=eapd

I recommend you that first try upgrading Alsa with the first script, if you can't make it work, then try to add the second line.

I hope that you can make it work.

Cheers,
 Andres

Thank you very much, Andres, for your speedy response.

1. The terminal command:

          sudo ./AlsaUpgrade-1.0.x-rev-1.17.sh -di

     Elicits this response:

          sudo: ./AlsaUpgrade-1.0.x-rev-1.17.sh: command not found

2. This terminal command:

          sudo sh AlsaUpgrade-1.0.x-rev-1.17.sh -di

     Gets this response:

          sh: Can't open AlsaUpgrade-1.0.x-rev-1.17.sh

3. I have edited alsa-base.conf as you instructed, then saved the file.

4. I then restarted my system.

Unfortunately, there has been no change. I know that my headphone jack works, as it works just fine in Windows.

Again, thank you Andres, and anyone else for any help you are able to give.

infinitree,

You missed either the point that you have to download the script file you are trying to execute or you didn't think that you have to extrart the actual script file from the archive you've downloaded. Your shell (most probably the bash) can't find the file you are trying to run. So, as posted above, goto to this

http://ubuntuforums.org/showthread.php?p=6589810#post6589810

thread and download the file named AlsaUpgrade-1.0.x-rev-1.17.tar. This is an archive file (.tar) just like .zip files. After you download, double click it and extract its contents to your desktop (drag'n'drop works). Then, in the terminal, cd to your desktop by typing cd ~/Desktop and try to run the script again.

I know these stuff look very complicated at first. Switching from the Windows, it is very difficult to figure out what all these commands do and how do they work. My advise to you is using the manual pages for the commands you don't know about. For example, executing the command "man sudo" will bring you a nice documentation of the command "sudo". These manual pages are available for virtually every command. Similarly, try "man sh" and you will get to know what "sh" does. Man pages will be your second friend after the Google. I hope this helps you getting your front jack working.

And, welcome to the Linux world. We are (at least myself) very glad you decided (or forced) to switch.

agonified,

You were right about me not knowing about the script to download. I was able to download the script, extract it, and run it. My sound, I can happily say, is now working! Very exciting.

Also, thank you for the advice on the "man" command. This will come in quite handy as I will no doubt run into further walls sometime in the future. That's half the fun about learning something new. I should have switched to Linux a long time ago.

Anyway, thanks to everyone for their help.

With the the script and the adding T.F.'s line its now working for my T-6836 though I did notice sound doesn't play out of my right speaker with out the head phones, but I always use head phones so no big deal thanks for fixes

I used to have this problem with my Gateway T6834c laptop with Ubuntu 9.04. Now I seem to have solved the issue with my own homebrewed patch (in the attachment). I've sent this patch to the ALSA developers mail-list and got accepted by Takashi Iwai.

The problem, as far as I can tell, is related to EAPD (external amplifier power down), and can be diagnosed with this command (please adjust the card and codec numbers in the command if necessary)

$ head -n 20 /proc/asound/card0/codec#0
Codec: SigmaTel STAC9205
Address: 0
Function Id: 0x1
Vendor Id: 0x838476a0
Subsystem Id: 0x107b0560
Revision Id: 0x100204
No Modem Function Group found
Default PCM:
    rates [0x7e0]: 44100 48000 88200 96000 176400 192000
    bits [0xe]: 16 20 24
    formats [0x1]: PCM
Default Amp-In caps: ofs=0x00, nsteps=0x0f, stepsize=0x05, mute=0
Default Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x02, mute=1
GPIO: io=5, o=0, i=0, unsolicited=1, wake=1
  IO[0]: enable=1, dir=1, wake=0, sticky=0, data=1, unsol=0 ---- note this line
  IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Analog Loopback: 0x00

Note the line IO[0] in the GPIO section, in STAC9502, this GPIO pin coincides with EAPD pin.
(see this pdf datasheet from manufacturer: http://www.idt.com/products/getDoc.cfm?docID=18693776)
And if you have the data=0 while your headphone is plugged-in, then the external amplifier is powered down,
which effectively mute your headphone.

This problem is already solved in the latest alsa-driver 1.0.20 for Gateway T1616, a special "eapd" model is
introduced to make sure that EAPD is always on (data=1). So if you can diagnose the same problem as above,
just try to force the kernel to use the "eapd" model. There are two ways to do that

1. the quick way, update to latest alsa-driver, and append this line to /etc/modprobe.d/alsa-base.conf
     options snd-hda-intel model=eapd position_fix=1
2. the once-for-all-and-everybody way, tell the kernel to probe for your Gateway audio chip and adjust to "eapd" model
   once the kernel knows how to do the job, no conf file tweaking will be necessary.
   that's what I did in my patch. add this line into the model probing code of the sigmatel STAC9205 driver
       SND_PCI_QUIRK(0x107b, 0x0560, "Gateway T6834c", STAC_9205_EAPD),
    the two numbers 0x107b and 0x0560 are from the "Subsystem Id" line from "/proc/asound/card0/codec#0"

I'm trying to write a "bigger" patch that supports more STAC9205 Gateway models, so please give me your
subsystem id and gateway model number if you diagnose the same problem on your system and you haven't
submitted these info above.

Thanks!

Resolved in Karmic & Lucid.