Bug Description

asus 1001px laptop speaker sound is ok. But the screen microphone and the in/out jack is not functionnal. (there is only 1 sound jack with both functions ) When the jack is plugged in the speaker turn off but there is no sound in the headset.

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

I found that if you do "sudo apt-get install pavucontrol" to install the PulseAudio Volume Control, and then lower the right channel of the microphone, the internal microphone then works.

The solution from Pablo in http://www.ubuntu-es.org/node/137762 also solves the line-out issue for me too but, HOWEVER, then the internal microphone stops working even when using the PulseAudio Volume Control as described in the previous paragraph...

If I set options snd-hda-intel model=lifebook it works the output but doesn't work the microphone, if I set the model=basic it works the microphone if I plug the jack and set the type of input = line in, and works the output from the speakers but not from the headphone.
Any suggestion for any other kind of model that could make work both?

Hi,
I played around with hda-analyser and 9.10 and it seems, that the initial mixer setting is not correct. The headphone output is not connected to the sound source.
Puting this line in /etc/rc.local is a work around:
#Bugfix für EeePC 1001PX
hda-verb /dev/snd/hwC0D0 0x1a SET_CONNECT_SEL 0x0c

This sets the correct connection for headphone output.
Does someone know how to correct this in the alsa configuration files?

Resetting to incomplete per my request to microzonepl not having been answered.

Those of you affected by this issue, please review the information located in https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs.
In the future please open separate bugs for your issues and refrain from setting bug status unless you are either the original reporter or a developer working on the problem.

I have tried Pablo's link. Headphone audio works great. Speakers work fine. Internal and jack microphones don't work at all. I've tried changing that one line in /etc/modprobe.d/alsa-base.conf to several different options to no avail. A speedy fix for this would be much appreciated.

I managed to set the audio mixer to 0x0d on startup, as well as checking the widget control boxes using hda-verb and putting the proper verbs in the /etc/rc.local file, but I don't understand which verb should I use to unmute the output amp. When I manually unmute with hda-analyzer the analyze.diff file shows the output

In the audio preference, set as speakers and with balance on the left, works the headphone plugging the jack and the speakers unplugging, and of course works also the microphone.
I tried without any option in the alsa.conf file in Ubuntu, but it doesn't work.

Now the last thing to do to have the microphone working is to put all the output balance either on the left or on the right. Oddily enough the microphone doesn't work with the output balance centered. So go to System-Preferences-Sound (or whatever, I have Ubuntu in italian) and put the balance on the left.

So can use voip and messenger application (tested with skype).

To hear music of course is better to center the balance.

If you set in the output as "analog headphone" the output works with headphone and if you unplug the headphone you can hear the speakers.

Now everything works perfectly and persistently. I can use my microphone, but for some reason the volume is very very high, I guess it's because I used hda-analyzer to reset everything to the defaults, probably one of the capture channels is at 100% and the Xfce mixer hides it.

Declining the Lucid and Maverick specific nominations for now and leaving this open against the actively developed Ubuntu kernel (which happens to be Maverick at this time). Will re-open the nominations should a fix be narrowed down which we can confirm specifically resolves this issue in Lucid and Maverick and qualifies for a Stable Release Update.

I found something related to this: in my case (1001px-WHI050S), everything worked out of the box, and I *thought* the mic didn't work because of the balance issue. In fact, it works, but the mic in mono, and is converted into a stereo stream with one channel having the same values as the other, but with the polarity inverted. The result is that, when reproducing this with the mono output (the loudspeaker) both channels get mixed and therefore they cancel themselves.

The right fix for this would be to find the right register to change to make the mic a mono input, or to fix the polarity of one of the channels.

I'm using Ubuntu 10.10 with the buasaard instruction, speaker, phone and internal mic work. Also I installed pavucontrol to balance mic channel one side. Cheese does not capture audio (int. mic) and skype does not allow to change sound settings. It's a known bug between skype and pulseaudio. So I start skype with "PULSE_SERVER=192.168.0.101 skype" and after all it works!

@ #43: it's not necessary to start skype withe the pulse_server argument. Just do the test call via skype with opened pulse volumecontrol and change in tab "Aufnahme" (I think it's called "Recording" in English) during the test call from "monitor..." to "Intern analog stereo". After that skype worked here like a charm.

Back to the subject on hand (Don't really care about skype - it's the sound card that I need working)....

I have 100 of the Asus eee 1001px machines out on a pilot program at the moment with 2000 of these machines being deployed next year. I REALLY need a fix for this - the pressure is really on now as this is essentially a trial of what will become a nationwide programme.

I did try the 2.6.35-RC1 kernel have had no joy as well as updated alsa drivers.

Internal mono speaker works (good)
Plugging headphones:
- Headphones work (good)
- Internal speaker is silenced (good)
Unplugging headphones:
- Internal speaker starts sounding again (good)
Plugging microphone:
- Internal speaker is silenced, just as if the mic were a headphone (bad)
- Neither mic works (bad)
Unplugging microphone:
- Internal speaker works again (good, but it shouldn't have been silenced in the first place)

In all cases, the internal microphone never works.

FWIW, I have pulseaudio removed and purged, and I don't have any Gnome/KDE stuff running.

There appears to be two problems here:
1. I've not been able to get the microphone to work once - neither via external microphone or internal microphone.
2. Noise cancellation or something means that you have to shift the balance of the microphone essentially making it mono.

Now the question is, is anyone, anyone at all, actually working on this problem? Or are we sitting around hoping that something will change in alsa or the kernels?

So I'm at the same stage as Juan Gonzalez only I need this for 2,000 netbooks this year. If you're going to report something working, can you please provide full details? i.e. versions of applications (the kernel and alsa), what version of Ubuntu you're using etc.

If I shift the balance all the way to the left, the noise stops. All the way to right and center, noise.

Looking at the source code there was something about nomicbias which I'm hoping addresses the balance stuff though I'd have to get something from the microphone to get an idea of the balance issue.

So how do I go about getting the sound card working? By the looks of the source code, the only thing that differentiates the different models are verbs and more specifically, the vendor specific pins. HDA-Analyser is next to useless in this regard as it doesn't describe anything about what can and can't be set with with those pins.

The other thing to note: The inputs show up in sound preferences as Microphone 1, Microphone 2 and Line-In. I checked the balancing trick on each Microphone and it appears they are treated exactly the same. I'm guessing that the two microphones are actually the one stereo microphone?

The internal mic does not work from a cold boot. After I suspend to RAM and restore, it just works.

I am using Audacity to test it. Doesn't matter if I set the input to stereo or mono under "Preferences"; both seem to work, but only after a suspend-restore cycle.

If set to mono, Audacity only picks up the left audio channel; if set to stereo, picks up the same signal on both left and right channels. No noticeable noise other than the CPU fan. So, after a suspend-resume everything looks OK.

However, If I plug an external mic then, the computer believes it is a speaker and disables the internal speaker, but the internal mic still works. So, plugging an external mic does not work yet.

The internal speaker switching thing shouldn't be too much of a hassle to figure out. It's just a verb thing I think. At this stage, it's really important to try and get a microphone working (for my scenario) - I can play around with the rest once I've gotten that bit of functionality going. I'm going to play with 10.10 and see if I can replicate #57.

#58 - That's a bit more interesting. A slightly different version of Alsa which I wouldn't have thought would have made too much of a difference. It might be interesting to do a diff on the source code for that module.

I'm hoping that if I am able to replicate #57, then it might be interesting to see what the module does on wake up. Of course, that adds the complication in providing a patch and people having to compile it themselves (unless someone wants to make up a ppa for it).

I'm guessing at the very least our first 100 are 042W's (I haven't seen the new laptops yet so they could very well be a slightly different model number).

So this could very well be multiple bugs - what works on the 033S doesn't look like it's going to work on the 044S and 042W.

I'll see if I can come up with a likely patch for the 033S - though I won't be able to test so it may or may not work.

As for the other two models - I'm at a complete loss. I'm guessing someone would have already done this, but I'm going to have a go loading up the drivers with the various models and see if any of them work with a microphone. That'll at least give me somewhere to start from.

The important line seems to be the subsystem. I've asked our vendor to contact Asus about possibly getting some information on the model I've got. Can I get some more results from "lspci -v" pertaining to the audio device from those having issues?

This should enable us to get an idea of how many different revisions there appear to be for this sound card and hopefully means we'll be able to fix a range of them.

Include me on the list of people with speaker/mike woes on an Asus laptop. My machine is a K60IJ. I'm running Kubuntu 10.10 with pulseaudio installed and everything fully updated. The result of lspci -vv is:

so I'm an IRQ45 case with an SCO subsystem rather than an Asus one, according to lspci.

I have problems on both the input and output sides, but the input is worse. I cannot get the built-in mike to work at all. I've been fiddling with alsamixer, pavucontrol, etc., to no avail. I've tried muting one side, switching from mike 1 to mike 2, and several other things. Nothing seems to help.

On the output side, there's great confusion between the internal speaker and the headphone. Since I have the headphone jack connected to an external speaker system, that's the one I want to have work. I finally discovered that the necessary settings in the pulseaudio volume control are:

Paul Abrahams - can you file a separate bug report for your problems please? The solution that we come up with here might help you (though it seems kind of unlikely to me), but you're mostly just hijacking this bug report.

On the bottom of your computer, where you'd find your serial number, it'll say something along the lines of:

ASUS 1001PX-BLK042W

The 042W seems to be kind of an indication of sub-versions or revisions. I'm looking to be able to map the different models to the type of sound card they have (i.e. the different models appear to have a slightly different implementation of the sound card).

So there are all sorts of "solutions" or "work arounds" for the 1001px but it's not clear what version of the sound card these work on. So if we can get an idea of what does and doesn't work, on various revisions of the sound card, we should be able to come up with solutions.

So those people who can load up snd-hda-intel with model=fujitsu and use model=lifebook to get the microphone and headphones working respectively is probably just a matter of looking at the verbs.

Those where sleep works, is probably a case of looking at the source code to see what happens when they wake up.

And those like me, where I'm unable to confirm whether the microphone works at all (i.e. there has never been a scenario where I've had the microphone working at all). This is probably going to require figuring out if any of the vendor pins need to be used and trying to reverse engineer them or getting information out of Asus about their implementation.

So it's kind of important to figure out what models there are, which laptops they affect, and what solutions work for which models.

Juan: Given that #61 has two pci id's and yours seems to be the odd one out - can you please confirm that your pci-id (under subsystem) is a 8437?

I've started charting the issues we're seeing.

If anyone has a 1001px WHI050S - given that an earlier report shows it to work out the the box bar the balance issue - I'd really like to know if I'm on the right track in terms of the sub system pci id's.

And if anyone else can help me complete this picture:
I need:

Full model number of laptop (at the bottom of the laptop on the same sticker as the serial number)
The full output of the subsystem line from running "lspci -vv" which pertains to the Audio device.
If any prior workarounds have worked for you.
If you have tried all of the suggestions on this bug report.

And please don't reference other messages while doing this as it makes it a little awkward. IRQ's shouldn't be important here so feel free to omit that detail.

@Milos (#69): Try updating your BIOS to the latest version available from ASUS. IIRC, on this netbook, WiFi toggling via Fn+F2 is now handled in the BIOS, that's why recent kernels ignore it. This might not be relevant to the audio jack/internal mic issue, but I'm reporting here my BIOS version as well, just in case.

@Nevyn (#64): The Subsystem line shows a 8437 indeed. Here's all the info:

@Everyone else
I'm unable to flash the BIOS (as an anti-theft measure, the BIOS has been locked by the vendor on the machine I have so that if it is stolen, the image asking people to call the support line if they have received the laptop isn't removable). So can someone have a go at flashing their BIOS with the latest version (I've currently got 0904 on this laptop but it should be 1104) and confirm whether this exhibits the behaviour Juan has described:
Running linux-image-2.6.35-23, with alsa-base 1.0.23. Putting the computer to sleep and waking it up seems to make the internal microphone work. The external microphone still isn't working but this shouldn't be too hard to figure out once we've got the internal mic working (hopefully).

Can we have more details? What works? I did manage to get the internal microphone going but does external work as well? And how are the noise levels? I haven't been able to get below "jet engine" type noise.

Personally I'd like to not have to maintain a kernel if I can possibly avoid it (I've now got around 500 machines in the wild).