Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 07-10-2008, 04:23 PM   #1
Registered: Jul 2008
Posts: 49

Rep: Reputation: 0
Question Slackware 12.1, stock install; Alsa 1.0.15; Audigy 2.

I have with much fiddling finally figured out how to get the analog speaker outputs to work, but I am beyond baffled on how to get the once crystal clear mic capture to work.

What I needed to do, in slack 12.0, was once I "muted" (yes unmuted, technically) the analog/digital toggle, simply capture the mic input, set it to whatever level I needed, enable mic boost, and then save.

As far as I can tell now, I also need to bring up Amix (analog mix) which effectively combines anything I had going before.

The result of which is, if I happen to be listening to streaming music, playing a game, then dare to toggle the mic on teamspeak, *all* sound is thus captured and spewed forth over.

I'm baffled now. I used to be able to have a simple stock install, (alsaconf, then no other configuration needed), set the master / mic capture sliders, toggle mic on, and be done with it.

For giggles, I tested the old Slackware 12.0 drive (always keep the previous working system), to see if there was a hardware failure I wasn't aware of, and, perfectly clear, clean separate channels, no delays with teamspeak's loopback test.

I now have a sneaking suspicion there's a quirk in a kernel module, but before I fiddle with compiles, I'll ask :

How do I separate the channels out like they used to be?
Old 07-11-2008, 08:29 PM   #2
Bruce Hill
HCL Maintainer
Registered: Jun 2003
Location: McCalla, AL
Distribution: Gentoo / Funtoo
Posts: 6,926

Rep: Reputation: 126Reputation: 126
My guess is look to udev/HAL/D-bus for screwing up more than it enhances.
Old 07-18-2008, 10:28 PM   #3
Registered: Jul 2008
Location: Berkeley, CA
Distribution: Slackware 12.1
Posts: 35

Rep: Reputation: 16
I am with you. My box with a 2.4 kernel and a Slack 10 distro had sound working
very clear, and powerful. Somehow, though the install and default kernel found
my sound card. It is somehow over modulated, and rough. I have very low volumes,
and with alsamixer or anyothers, too much slider action and the there is piercing

I have to figure out all the adjustment in ALSA to get this fixed.

Please keep us posted on how to tweak/adjust/test/correct ALSA under Slack 12.1.

Old 07-24-2008, 12:35 PM   #4
Registered: Jul 2008
Posts: 49

Original Poster
Rep: Reputation: 0

alright, I think I figured out this one out.

as a reference for the possible options, I've come up with what I believe I now need as a sound configuration file.

I use just the Audigy 2, no on-board sound - on-board was disabled in BIOS.


('touch sound' if this file isn't there yet)

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-emu10k1

# module options should go here
#	Creative Card wo/Digital out + LiveDrive	[0x3fc3/0x1fc3]
options snd-emu10k1 id="first" extin="0x3fc3" extout="0x1fc3"

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-emu10k1

# card #1
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
The "option" part seems to be when it began to run properly. The card physically does not have an IDE connector, and I'm not using the digital outputs (analog speakers) - So I made a guess that this was the correct option to use. [Note : id="first" I think is related to if the system finds a second sound card, that the one for the driver above, is loaded first, before anything else that is found. Now since, I do have on-board - although it's disabled - if I ever turn on-board back on, I want to minimize trying to figure out why the sound stops working again.]

Now, upon rebooting, a message just after the alsa state restore, said "no state is present for card first". After much googling, I gave up trying to figure out what this meant, and deleted the the file 'asound.state' within /etc then rebooted again to allow the system to recreate what it thought was the right card.

From there, set alsamixer to the sound levels below deafening, captured mic and Amix (apparently slack 12.0 did need this one selected and adjusted - but my tests after I learned that still had the same result, before the above configuration was used).

Ran startx, KDE's intro music chopped like before - began to worry it didn't work. Tested a few applications (TeamSpeak, Amarok, a few games and work-related support tools - all at the same time) and it seems to be fixed.

One day, when I have more free time, I'll see which part actually "fixed" my issue.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Sound Blaster Audigy SE on new Slackware 12.0 install salviatech99 Linux - Newbie 1 03-18-2008 03:51 AM
Weird Alsa Errors with Alsa and Audigy 2 PCMCIA??? raid517 Linux - Hardware 3 11-26-2006 07:29 AM
Alsa 1.0.4 on stock install porblem Dullin Slackware 14 05-09-2004 09:43 PM
Debian Sid - ALSA and a stock 2.6.5 kernel UrbanSlayer Debian 8 04-18-2004 09:14 PM
alsa mandrake9.1 audigy install prob primal-id Linux - Hardware 3 08-10-2003 07:40 PM

All times are GMT -5. The time now is 11:50 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration