Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i did ./snddevices and it seemed working well, then tried alsamixer, but still with the same error. rebooted, tried again...nothing
anyway, i've found 'alsa.conf' - what do i do with it?
alsa.conf and alsaconf are not the same thing! I have a file alsaconf (in fact /usr/sbin/alsaconf) which I assume got run during installation and took care of, er, configuring ALSA. It's a big shell script, about 1000 lines.
Another possible cause of problems is having libraries and config files from old versions of ALSA hanging around. For example, if mandrake already uses ALSA for sound and then you compile a new version over the top of that, I can imagine there is a possibility of conflicts. Similarlly for RH if you try to install both from RPMs and source.
But if snddevices does not fix the problem, I'm clutching at straws.
Last edited by maroonbaboon; 09-28-2003 at 10:34 AM.
old alsa doesn't work - i wouldn't end up installing new one
ho DO you uninstall old alsa?!?
i had only alsa drivers, without utils (alsamixer, wich is the key to the whole thing), so i installed new everything
If it was installed from an RPM package, then there is some option like rpm -e (???) which removes everything. Otherwise I don't know a simple way. Most libraries or config files are in /usr/lib, /etc and /usr/share, so anything called alsa-something in there would probably get most of it. But that's a bit hit-or-miss.
One problem is that the big distros generally have their own way of doing things, and going outside their package systems can lead to inconsistencies. Especially for something like ALSA, which is closely tied in with the kernel.
Going back to older versions doesn't sound like a good idea.
P.S. Another source of trouble is the script which starts ALSA (in Debian this is /etc/init.d/alsa). If you decide to clobber the distro's own ALSA installation then this script will maybe also have to be changed to reflect a new disposition of ALSA components.
Last edited by maroonbaboon; 09-28-2003 at 11:04 AM.
how about i reinstall mdk without sound card driver, get new alsa packages from www.alsa.project.org and install them on a fresh os? doesn't sound bad...?
I'm still not sure if MDK uses alsa by default. I've looked at their website but it looks like you have to register to get to anything interesting.
If you just tell the installer you have no soundcard I suppose you might then be clear to install the latest version from source. Worth a try if you feel like you have exhausted other possibilities maybe. Check dmesg to make sure the system is not trying to start its own version of ALSA.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.