The symptom is affected by two parts, one alsa-driver/linux and the other a default setting (alsa-utils *or* pulseaudio).
The latest daily builds of linux-alsa-driver-modules (from the ubuntu-audio-dev ppa) address auto-mic sensing for some HDA codecs. The Realtek ones are best supported in that regard; a few of the IDT and Sigmatel ones are, too. I can't guarantee yours is; you have to try it.
The second part is - perhaps - configurable via the alsa-utils alsactl init database. That is probably required if we wish to handle all desktop environments, not just those that use pulse. And, of course, we need to ensure that the appropriate mixer profile path sets this by default.
Note also that the easiest way to test a "default" environment is to boot from a live cd (or thumb drive) after being powered down for two or more minutes.
The symptom is affected by two parts, one alsa-driver/linux and the other a default setting (alsa-utils *or* pulseaudio).
The latest daily builds of linux-alsa- driver- modules (from the ubuntu-audio-dev ppa) address auto-mic sensing for some HDA codecs. The Realtek ones are best supported in that regard; a few of the IDT and Sigmatel ones are, too. I can't guarantee yours is; you have to try it.
The second part is - perhaps - configurable via the alsa-utils alsactl init database. That is probably required if we wish to handle all desktop environments, not just those that use pulse. And, of course, we need to ensure that the appropriate mixer profile path sets this by default.
Note also that the easiest way to test a "default" environment is to boot from a live cd (or thumb drive) after being powered down for two or more minutes.