On Mon, Dec 28, 2009 at 10:03:01AM +0000, Business Kid wrote: > Going on my own (unsolved) microphone problems, try this for faultfinding: > lspci -v & find your sound card device > Read alsamixer o/p - has it got the chip right? > If not, do lspci -n and get your numeric ids for the card. This is 4 hex digits > for manufacturer, & chip. My laptop for instance, has 1002:4383. standing for > ATI SB600 respectively. Alsa detection stuff returns Analog Devices 1981, or > 11d4:1981. It's plainly wrong, and it's trying to control a chip with the > levers in different places, if you're with me so odd things happen. > > then > grep -r 11d41981 /proc/asound/card0/* returns a hit when actually there > should be 10024383 In view of the fact that it was working initially, would it have changed spontaneously? I'll check it out when I get some time. Thanks -- Bob Holtzman Key ID: 8D549279 "If you think you're getting free lunch, check the price of the beer"
Attachment:
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
