SlackwareThis Forum is for the discussion of Slackware 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.
There's nothng wrong with alsa. It's just a bit newer than OSS, and should get better as time goes on.............Use what you want, just remember that in the future OSS probably won't be around and you'll eventually have to use something else, anyway, which is what I was trying to point out.....but the choice is yours.
Distribution: Debian etch/lenny/sid, Fedora 7/Rawhide, CentOS 4/5, FreeBSD 6.2 and Solaris 10/Nevada
Posts: 110
Rep:
Quote:
Sounds like it would be better to try to fix the alsa problem if oss is fading out in favor of alsa....
So it would be plausible for me to install Slack, move to 2.6 and alsa should work with this "audigy" card?
Just for a test, I have loaded Fedora, Gentoo, SuSE, Knoppix & of course Slackware <----- rather be using, but Fedora is the only one that has worked with this sound card. I don't know why. I don't believe that Fedora uses alsa, I think it is still OSS. This is what happens with modules.conf in fedora:
Code:
alias eth0 3c59x
alias usb-controller usb-ohci
alias usb-controller1 ehci-hcd
alias ieee1394-controller ohci1394
alias sound-slot-0 audigy
post-install sound-slot-0 /bin/aumix-minimal -f
/etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f
/etc/.aumixrc -S >/dev/null 2>&1 || :
So I assume it is using an "audigy" driver instead of "emu10k1". What do you all think?
This is what I have in /etc/modules.conf, after running 'alsaconf' as root:
Code:
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 0.9.0 ---
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options snd major=116 cards_limit=1
options snd-emu10k1 index=0
# --- END: Generated by ALSACONF, do not edit. ---
Originally posted by Aman9090 my /etc/modules.conf is the exact same thing as what you posted above. And slack identifies it the same as well.
?
I did notice one thing in your post above with the ouput of lsmod........it show a tainted output:
Code:
Module Size Used by Tainted: P
Might be something else going on that's affecting your sound........just a thought.......
PS: Let me clarify a little.........while a tainted module does not necessarily mean a bad module, it means that it isn't open source and so there is no way of knowing for sure if there is or isn't a bug (or badly written or anything else wrong) in one of your modules.
Last edited by thegeekster; 01-01-2004 at 01:01 AM.
Originally posted by Aman9090 So how do I check what the conflict might be and how may i fix it?
Thanks for the help! I really appreciate it!
This is the point where I can't be of much help. It was just an observation I thought worth checking out.................It may help or it may lead nowhere. I still still have a long way to go learning about what makes Linux tick, and I've never had any modules problems.............yet.
What I would do is check out the linux documentation and HOWTOs (which is installed in /usr/doc with the Slack distro) and search the web (including this site) for info about the kernel and kernel conflicts. Theres also a lot of info in /usr/src/linux worth checking out as well.
So the prob was with the Audigy card........I have a PCI 512, which seems to work okay.............And now I'm looking into upgrading the kernel to 2.6...........hopefully it won't break my box too badly , but I'm sure I'll probably have some module issues to work out.....
Distribution: Debian etch/lenny/sid, Fedora 7/Rawhide, CentOS 4/5, FreeBSD 6.2 and Solaris 10/Nevada
Posts: 110
Rep:
Yeah, the audigy2 has been a pain in every distro I've tried except Fedora which uses an oss-audigy mod I think. But I love slack and didn't want to give up on it. ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.