hda_intel: azx_get_response timeout, switching to polling mode -> Codec + Mixer: Conexant ID 5069 - Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) - speakers originally worked, but stopped working after installing a few applications in Ubuntu 9.04 AMD64 on Lenovo T400S (2801CTO)

My advice comes from seeing similar issues in various forums.

1) make sure alsa is up to date (which you have)
2) Add these lines to the end of /etc/modprobe.d/alsa-base(.conf)
options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=hp-m4
options snd-hda-intel enable_msi=1

For the Model you will need to consult the alsa documentation which will list all model types for your particular card.

Thank you very much for the quick and concise answer.

I would appreciate some help in order to execute 2). My knowledge is limited in these matters.

So I'd need to know how to add lines to the end of /etc/modprobe.d/alsa-base(.conf) and details on the procedure (ie. Open Terminal - Run this command - etc.)

I apologise for not being able proceed with the already provided in formation.

Hi :)

It is totally fine to keep asking questions until you nudge us into helping you sort the problem out. I don't know much about sound issues so all i can give is this guide to the linux command-line

https://help.ubuntu.com/community/UsingTheTerminal

before doing anything to the "/etc/modprobe.d/alsa-base.conf" file i would recommend backing it up like this ...

cd /etc/modprobe.d
ls
cp alsa-base.conf alsa-base.conf-010909
ls

where "ls" is a lower-case "LS" and shows a LiSt of the folders contents. It's colour coded which is a big improvement on "dir" which also works. Hopefully the 2nd "ls" will show the new file "alsa-base.conf-010909" that you have just created. If not then try putting a "sudo" in front of the "cp" command. It's better to try CoPying things like this without sudo first because sudo can mess up the permissions of things and if you don't need Superuser permissions to run a command then it's best done as a normal user

sudo cp alsa-base.conf alsa-base.conf-010909

this will ask for your normal user password, not your SuperUser/Root one and doesn't give you any stars as you type - it just quietly collects what you type without giving any indication that its heard you.

I hope this helps!
Hopefully someone a lot more knowledgeable will pop in later and help somewhat better!
Good luck and regards from
Tom :)

FYI, I had similar experience. It turned out to be hardware issue since the sound stopped working even after doing factory OS restore. It happened to 2 separate T400s'. I think Lenovo has a manufacturing issue they need to address with the T400s.

http://ubuntuforums.org/showthread.php?t=661102

http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T400s-No-Sound/m-p/153242

That first link was meant to be:

http://ubuntuforums.org/showthread.php?t=1216069&highlight=t400s

Hello,

Thank you for your interest in helping me out with this issue.

- The problem persisted after reinstalling Windows Vista professional. So I sent the machine to Lenovo and it came back fixed.
- I reinstalled Ubuntu 9.04 (the whole machine) and sound kept working.
- Somehow, it stopped working hours after, when I installed all the programs I wanted to use in the computer: VLC, VirtualBox, Picasa 3, Skype 2.1. One of those may have interferred somehow, because sound stopped working again.

I don't plan to send the machine back to Lenovo again. It looks like it's something related to the 64 bit version of Ubuntu 9.04, since both this version of the OS and the machine are pretty new, so some buggy behavior may be causing this.

Now, I decided to stay with Ubuntu 9.04 in the 64 bit architecture even though the speakers stopped working, waiting to know solutions to come in more detail. At this point, I don't want to invest a lot of time on it, so hopefully one lucky update will fix the issue. If not, I may install sometime in the future the 32 bit Ubuntu 9.04.

How about installing the 32bit version of Ubuntu alongside the 64bit version. Dual-booting between 2 different versions of Ubuntu is fine. Note that Ubuntu only really needs about 15Gb to be comfortable and can then use data and stuff from the other install. It might be worth doing as a temporary work-around? Since you already have the 64bit side setup you wouldn't need to be in a race to get the 32bit one finished. It's amazing how fast something can get done when just doing odd bits as time allows.

Good luck and regards from
Tom :)

Sounds extremely similar to my problem. However, now that sound has stopped working I found reinstalling any OS didn't resolve the issue (e.g. Ubuntu 9.04 32-bit, XP, Vista). How did Lenovo fix the problem for you? Did they replace the system board? Something funny definitely going on with those laptops. I'm having trouble seeing how Ubuntu 64-bit can permenantly kill the speakers. I didn't hear anything like the speakers being blown out.

-They repaired the system board/planar
-Updated BIOS/embedded controller
-Performed PC Doctor

That was done under Windows Vista.

The speakers were working with vista after repair.

They were also working with Ubuntu 9.04 after complete install of OS on machine.

They stopped working after I installed some apps:

- VirtualBox (biggest suspect)
- Picasa 3
- Skype

So it's something related to VirtualBox, I'd bet. Whatever it is, speakers don't work anymore. I don't think it's a Lenovo issue, but something related to the 64 bit version of the stack Ubuntu 9.04 + VirtualBox.

Hi :)

Please try working through this trouble-shooting guide
https://help.ubuntu.com/community/SoundTroubleshootingProcedure

One of the steps is to post a new question here which should grab a relevant persons attention. Launchpad doesn't handle older questions very well, sorry about this.

Good luck and regards from
Tom :)

Thank you,

Just one question:

-How do I find the exact soundcard model I have to include in /etc/modprobe.d/alsa-base(.conf)?

I don't know how to find/access to the place where this info could be. Reading other forums, I've realized I'm interested in locating in my computer "HD-Audio-Model.txt". How could I do that?

Thanks,

Hi :)

Errr, doesn't this guide help at the end here?
https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Other%20Pages
or in one of the steps? I'm a bit lost if it doesn't. Please post as a new question
https://answers.launchpad.net/ubuntu/+source/alsa-driver/+addquestion

Good luck and regards from
Tom :)

Please make a new question on "How can i find a file in Ubuntu..."

Thank you

It doesn't make sense to make more noise with a new question.

I'm just referring to this process:

######
My advice comes from seeing similar issues in various forums.

1) make sure alsa is up to date (which you have)
2) Add these lines to the end of /etc/modprobe.d/alsa-base(.conf)
options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=hp-m4
options snd-hda-intel enable_msi=1

For the Model you will need to consult the alsa documentation which will list all model types for your particular card.
#######

I'm ready to edit and save that file, and I dont know what to put instead of "hp-m4"

I have the information related to my card, but not the "equivalent" name to put in here.

My Sound card:

#######
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller
 (rev 03)
        Subsystem: Lenovo Device 20f2
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at f2920000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: HDA Intel
        Kernel modules: snd-hda-intel
######

Obviously, here I don't have the equivalent to "hp-m4" in the example above.

Would you open a new question for this? It's more work for us all.

Thanks.

Reading https://help.ubuntu.com/community/SoundTroubleshootingProcedure
...
Valid model names (that replace YOUR_MODEL) depending on the codec chip, can be found here:
here http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=blob_plain;f=Documentation/sound/alsa/ALSA-Configuration.txt
...

Hope this helps

Hi :)

Launchpad doesn't have a good way of dealing with questions over a day or 2 old. There are various bug-reports about this problem but they keep getting ignored while Launchpad developers are busy developing nice eye-candy and other stuff that doesn't help the Answers Section. While i also find it frustrating i have found that about the only work-around that works is for people to re-post questions when they reach a stage where they are unlikely to get good answers due to the way Launchpad is currently setup for the Answers Section. If you do post a new question then suddenly everyone can see the new questions whereas the old one has disappeared off the bottom of the list. You can always include the link back to this question so that people have access to the detail which will also allow your 'new' question to be very brief and less daunting to answer ;) Here's the link to this quesion
https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/81561

Many apologies for this but i am not a developer and am unable to solve the problem. All i can do is add to the existing bug-reports which get ignored anyway <shrugs>
Good luck and regards from
Tom :)

Lol, i have just noticed that you have posted a new question! Lol, thanks for that :)) I am still going through al the responses to older questions i am trying to help with ;) I haven't yet reached today's fresh problems <blushes> heheheheh
Thanks and regards from
Tom :)

Your dmesg output shows the following ALSA warning message:

[ 12.068508] ALSA /usr/src/alsa/alsa-driver-1.0.20/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:636: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x010ba000

I found a similar sound issue here:

http://ubuntuforums.org/showthread.php?t=1216069

and here:

http://fixunix.com/kernel/389335-sound-azx_get_response-timeout.html

and here:

http://readlist.com/lists/vger.kernel.org/linux-kernel/53/266248.html

"The latest snd-hda-intel driver uses MSI as default.
> > > Pass disable_msi=1 module option and see whether it works."

So please try this procedure:

1. install Ubuntu 9.04 32-bit version

2. Upgrade to ALSA version 1.0.21 in the 32-bit version of Ubuntu 9.04 by following these instructions:

http://monespaceperso.org/blog-en/2009/08/31/upgrade-alsa-1-0-21-on-ubuntu-jaunty-9-04/

3. Reboot your pc

4. Open a terminal and edit /etc/modprobe.d/alsa-base.conf as follows:

sudo gedit /etc/modprobe.d/alsa-base.conf

When the file is open, add the following 3 lines to the end of the file after "options snd-pcsp index=-2"

options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel disable_msi=1

4. Save,close and reboot into Ubuntu 9.04 32-bit version

5. !!! Retest sound. See if sound keeps working for AT LEAST a day or two before installing any new programs (like Virtualbox or Skype) that could invalidate this test. !!! If sound stops working after a few hours - WITHOUT installing any new programs - then it could still point to serious hardware issues.

Hope it helps.

Regards,

Mark

Thank you for the detailed help.

Currently on Ubuntu 9.04 32 bit and trying to update Alsa to 1.0.21

Following instructions from provided link, I get an error *just* in the same place where he gets the error, but mine is different, so his solution won't help me to successfully finish the installation.

The message I get:

#####
configure: error: required curses helper header not found
#####

Any idea on how to proceed?

Thanks again,

Please try to install...

apt-get install build-essential ncurses-dev libncurses5-dev gettext linux-headers-$(uname -r)

Hope this helps

Thanks,

That last tip allowed me to install Alsa 1.0.21.

During the install of 1.0.21 i noticed this text when running one of the processes:

WARNING!!! The mixer channels for the ALSA driver are muted by default!!!
**************************************************************************
You would use some ALSA or OSS mixer to set the appropriate volume.

After reseting Ubuntu 9.04 32 bit and opening a music video, I heard some some sound, but so low that it was like coming from headphones.

- So the sound card seems to work, but the sound is almost unnoticeable. So low that it seems to be coming out of headphones.

Anyway, the sound was there until I added your recommended last step in the process:

######
4. Open a terminal and edit /etc/modprobe.d/alsa-base.conf as follows:

sudo gedit /etc/modprobe.d/alsa-base.conf

When the file is open, add the following 3 lines to the end of the file after "options snd-pcsp index=-2"

options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel disable_msi=1

4. Save,close and reboot into Ubuntu 9.04 32-bit version
#######

After successfully updating alsa.base.conf, sound dissappeared again.

If I go to the sound icon in menu and click on preferences, one can read 2 null options to pick, which won't work:

- Playback: Null output (PulseAudio Mixer)
- Capture: Monitor of Null output (PulseAudio Mixer)

And then, on the field below the 2 devices that appear to track and control in volume control preferences, I only see "Master" as an option.

Obviously, the card didn't like our last changes in alsa-base.conf

Any hints?

Notice that sound is at least present before that, but it's barely heard, because it's so low.

I hope the explanation is concise enough.

Thanks again,

Please open a terminal and using the alsamixer (use tab and up/down arrows key) try to raise all volumes at a non 0 value.

so open a terminal and type:

alsamixer

Hope this helps

Thanks,

Opening alsamixer i see the value in Master channel is "00"

After click on tab, I am able to see all channels (Master, PCM, Mic, Mic 1) are at 100<>100, so none of them is set at 0.

Strange, because after taking out those lines from alsa-base.conf, I still hear sound, but barely noticeable, so the soundcard seems to be working now.

Somehow, I must have something muted, but not in the volume controls I see.

Any idea?

I can also add again the 3 lines to the alsa .conf file and try to raise that volume up, through when those lines are added, the channels seem to be Null, as explained before.

And I also just confirmed that adding those 3 lines to the .conf file make the sound null, and trying to open alsamixer in terminal leads to message:

###
cannot open mixer: No such file or directory
###

So I think the card is working removing these 3 lines, but somehow the sound is so low and vague it seems to come from headphones.

What do you suggest, after reading my last 2 messages?

Thanks,

Try installing gnome-alsamixer.

To install it, copy-paste the following command into the Terminal:

sudo aptitude install gnome-alsamixer

Then run gnome-alsamixer and increase the volume on all channels.

Then test the sound volume both on headphones and via the speakers.

No luck with gnome-alsamixer

The Channels Master, PCM, Mic and Mic 1 are the highest possible in "Conexant ID 5069"

I wonder if at this point I should open a new case with a subject like "sound very low in system" instead of "no sound".

Your recommendation?

Please confirm are you using VirtualBox under Windows with Ubuntu 9.04 installed on it... ?

Thank you

Right now I'm not.

I'm using a brand new Ubuntu 9.04 install, 32 bit. All clean. I didn't install any app yet, other than updating the system and installing the latest Alsa as explained by you.

Hi faircompanies,

Please make sure to try all the suggestions here:

http://ubuntuforums.org/showthread.php?t=235245

and here:

http://ubuntuforums.org/showthread.php?t=235245&page=2

Also try this procedure:

1. Open up the Volume Control (gnome-volume-control).
2. Click 'Preferences'. Enable Front, Surround, Center, LFE, Side. Click on "Close".
3. Set Headphones, Front, Surround, Center, LFE, Side to 100%. Click on "Close"

Regards,

Mark

I have dual boot Windows XP and Ubuntu 9.04 Jaunty on Lenovo T500 and T61. On both machines if I mute sound in Windows it will not work in Ubuntu. And if the sound is set low, that becomes max sound in Ubuntu. Also if headphones are plugged in when Windows shuts down only sound in Ubuntu is through headphone jack.

Hi :)

If this is still a problem then please re-post this as a new question
https://answers.launchpad.net/ubuntu/+addquestion
perhaps also at
http://www.linuxquestions.org

Launchpad can only handle most recently asked questions and often the Answers Team races through all the shortest questions first so when you re-post please keep it very brief. You can always copy&paste this link back to this question so that people can see the detail you gave here
https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/81561

When i was answering questions in here it seemed the best answers were
given when the question was posted just as americans were getting back
from work. This was weird because most of the answerers lived in Europe
or Asia at that time lol.

Anyway, good luck and regards from
Tom :)

@eddiewebb Thanks for your advice on sound. Have been struggling quite some time to get the snd-hda-intel working (my model is ALC 662 - 6stack-dig) but have tried all models registered for this codec without any success. Starting/stopping processes and sound server was ok to some extent, but finally re-booting never actually did what you hoped to expect. Sometimes it worked, for various models, sometimes no sound at all, numerous spurious responses flooding logfiles, etc.
until you mentiobned the lines above. That helped. Some were already in by default, but some werent.

Here is my result in Alsa-base.conf bottom part:
....skipping initial lines....
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Power down HDA controllers after 10 idle seconds
options snd-hda-intel position_fix=1 model=6stack-dig probe_mask=1 power_save=10 power_save_controller=N
# added from ubuntu forum @eddieweb dd 2009-09-01
options snd-hda-intel enable_msi=1
alias snd-card-0 snd-hda-intel
<EOF>

Especially the model=6stack-dig now actually works too. The kmixer shows all the options that were not there previously. And even after a few reboots still works. Totem is happy, Movieplayer too, Skype (!sic) works including microphone. Decided to drop Pulse audio in the recent past because of all the hassle, but now we are back on track again with pulse.

@eddiweb, thanks again.

@eddiewebb Thanks for your advice on sound. Have been struggling quite some time to get the snd-hda-intel working (my model is ALC 662 - 6stack-dig) but have tried all models registered for this codec without any success. Starting/stopping processes and sound server was ok to some extent, but finally re-booting never actually did what you hoped to expect. Sometimes it worked, for various models, sometimes no sound at all, numerous spurious responses flooding logfiles, etc.
until you mentiobned the lines above. That helped. Some were already in by default, but some werent.

Here is my result in Alsa-base.conf bottom part:
....skipping initial lines....
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Power down HDA controllers after 10 idle seconds
options snd-hda-intel position_fix=1 model=6stack-dig probe_mask=1 power_save=10 power_save_controller=N
# added from ubuntu forum @eddieweb dd 2009-09-01
options snd-hda-intel enable_msi=1
alias snd-card-0 snd-hda-intel
<EOF>

Especially the model=6stack-dig now actually works too. The kmixer shows all the options that were not there previously. And even after a few reboots still works. Totem is happy, Movieplayer too, Skype (!sic) works including microphone. Decided to drop Pulse audio in the recent past because of all the hassle, but now we are back on track again with pulse.

@eddiweb, thanks again.

Hi :)

Please re-post this as a new question
https://answers.launchpad.net/ubuntu/+addquestion
each sound issue is likely to be slightly different so seeking advice from old threads makes sense but probably wont give you the complete answer for your particular case.

Good luck and regards from
Tom :)

Hi :)

Have you been able to try the new Ubuntu 10.04 before it gets officially released?
http://www.ubuntulinux.org/testing/lucid/beta2
Trying it as a LiveCd or as an extra dual/multi-boot would be ideal. Developers and everyone are keen to try to iron out any problems before 10.04 gets officially released so you might find faster & more effective answers to your bug reports which would make 10.04 work better on your system for you

Thanks and regards from
Tom :)