Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have an Analog Devices 1881A on board sound chip on a Sony Vaio PCV-RX560. Mandrake 9.0 has recognized it and Kmix indicates that it knows that the card exists and all channels are unmuted. Mandrakes Hardware detection also shows that the card exists and lists all attributes and related driver (right off hand I don't recall which it is but will update this when I get home tonight.) However, I am unable to get any sound. If I use the KDE sound server configuration utility and choose the ALSA driver I am greeted with the following error: device: default can't be opened for playback (No such file or directory). When using AutoDetect it seems to be happy for awhile and then I get some sort of sound server fatal error: cpu overload, aborting; error. Last night I accidentally bumped the mic and heard the sound through the speakers so I know that at least that portion is working. I thought perhaps the mic was using up the resources so I muted it in Kmix and went as far as unplugging it, but still no sound can be heard. I have had all versions of Mandrake on this machine since 7.2 and haven't had any sound. I'm starting to get a bit frustrated with this Sony.
QUESTION: Is there something simple that I am overlooking? Or should I abandon this on board sound card for a real PCI card that is truly compatible? If I do go with a real PCI sound card, which cards are recommended?
I haven't tried disabling Kmix yet. However, there was some sort of error message in dmesg. Right off the top of my head I don't recall the error. As soon as I get a chance I'll copy that message to you. Maybe you or someone else has seen it before.