nvidi p5n32e-plus Analog Devices AD1988B soundmax microphone only works after switching to another input setting and back

Bug #593018 reported by Brian Burns
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am now using Ubuntu 10.04 LTS
I have had a strange problem since 9.10 - when I switched back to the supplied riser card that came with my mother board (Asus p5n32e-plus).
My microphone works, BUT only after I open the 'Sound Preferences' panel, and change the setting under the 'Connector' tab to another selection (any will do), then set it back to 'Microphone 1'.
Can this be fixed?
Also since since this work around works, I wondered if there is a way to make this happen automatically at every login?
Any help would be appreciated!
Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: brian 1441 F.... pulseaudio
 /dev/snd/controlC0: brian 1441 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xefff4000 irq 21'
   Mixer name : 'Analog Devices AD1988B'
   Components : 'HDA:11d4198b,104381f2,00100300'
   Controls : 49
   Simple ctrls : 28
Card1.Amixer.info:
 Card hw:1 'VOIP321'/'PHILIPS PHILIPS VOIP321 at usb-0000:02:06.0-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB0471:082f'
   Controls : 4
   Simple ctrls : 2
Date: Sat Jun 12 13:24:36 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
dmi.bios.date: 04/28/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N32-E SLI PLUS ACPI BIOS Revision 1401
dmi.board.name: P5N32-E SLI PLUS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N32-ESLIPLUSACPIBIOSRevision1401:bd04/28/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N32-ESLIPLUS:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Brian Burns (brianburnspl) wrote :
Changed in alsa-driver (Ubuntu):
status: New → Confirmed
Revision history for this message
Adrian Wilkins (adrian-wilkins) wrote :

See #776964 for guidance on fixing this (for people still on Maverick)

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.]

Changed in alsa-driver (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.