SlackwareThis Forum is for the discussion of Slackware 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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It's rather strange; Slack's never been at odds with any of my hardware before, and none of my bios settings have changed (on-board sound is off). I've already tried the usual suspects: volume levels, etc, but I don't really know where to start looking beyond that.
Here's the output from lsmod and lspci, as suggested by other threads on the subject:
I think I might be onto something already; I just don't know what to do about it.
Alsaconf doesn't return any errors, it tells me Alsa is ready to go, and nothing changes.
However, when I run alsamixer to play with the volume instead of kmix (which always crashes at the moment), the card and chip starts up trying to mix by default is my tv card (Brooktree Bt878). So it's obviously interfering in some manner.
Originally posted by egag ah...you've got also " snd-bt87x " loaded
maybe try to unload it ( rmmod snd-bt87x ) and see if it works then...
I unloaded snd-bt87x, and now alsamixer doesn't fire up at all: "alsamixer: function snd_ctl_open failed for default: No such device"
Originally posted by egag btw.:how do you normally set up sound from your tv-card ?
i have mine with a cable connected to an input of the mobo-sound.
Physically, there's an external jumper between the two cards. I've actually never gotten the thing to function correctly since Mandrake 8.0, so I've basically ignored it since then. Until this point it's never been a problem.
you could try to add the module to /etc/hotplug/blacklist ,
so it won't be loaded at boot.
after that, a reboot is the most simple way to look if all works.
( i guess at boot the bt-module is used by the kernel as your first sound device )