Microphone only works after toggling input source.

[3vi1]

My microphone input does not work in any program until I use KMix or Alsamixer to change the input source from "Mic" to any other value (line, cd, aux, etc.) and then back to "Mic". After that, it works fine - but the source must be toggled on each reboot.

Linux mars 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

00:0f.1 Audio device: nVidia Corporation MCP55 High Definition Audio (rev a2)
        Subsystem: ASUSTeK Computer Inc. Device 829c
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20
        Memory at efff0000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [44] Power Management version 2
        Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable-
        Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
        Kernel driver in use: HDA Intel
        Kernel modules: snd-hda-intel

[Dmik (dmik-for-maillists)]

I can confirm that this bug also presents on the Gigabyte GA-P35-S3G motherboard:

01:00.1 Audio device: ATI Technologies Inc HD48x0 audio
 Subsystem: PC Partner Limited Device aa30
 Flags: bus master, fast devsel, latency 0, IRQ 17
 Memory at f5010000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: HDA Intel
 Kernel modules: snd-hda-intel

[Dmik (dmik-for-maillists)]

I forgot to mention that this started to happen immediately after upgrading from Intrepid to Jaunty. Another unpleasant change is that the Microphone Boost control has disappeared and the Microphone record level is very low now (even if the Capture level is set to maximum) -- I suspect that Mic Boost is just turned off.

[Jeremy Foshee (jeremyfoshee)]

Hi 3vi1,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 365674

Also, if you could 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.]

[3vi1 (launchpad-net-eternaldusk)]

I no longer own the same motherboard, so asking me for further information nearly 10+ months after the initial bug report is pointless. Other people using that same chipset, like DMik, may or may not continue to have the problem - I do not know.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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