I've been trying to get AUDIO KONTROL 1 to work on my Linux laptop for several months now and today I finally made it.
A guy from the local university helped me and now (nearly) everything works.
So, here is what we did (as far as I remember):
First of all, some general requirements and information:
Operating system: I run Debian Lenny on this computer.
Kernel version: 2.6.22 or higher. We used a slightly customized 2.6.24 vanilla kernel here. However, you do not necessarily have to change the kernel configuration for being able to use AUDIO KONTROL 1.
ALSA version: 1.0.15 or higher. We used the 1.0.15 Debian packages here. So, you don't need to build ALSA from source.
Steps we took:
1. Configuring the kernel (optional)
Here I just selected the correct processor family and set the preemption model to "Low-Latency Desktop" to reduce latency.
2. Setting AUDIO KONTROL 1 as the primary soundcard
NOTE: The device only works if set as primary soundcard. We think that this may be a bug.
Open a shell, become root and open the file /etc/modprobe.d/sound with an editor of your choice, e.g.
In there you should read something like this:
debian:/home/user# cd /etc/modprobe.d/
debian:/etc/modprobe.d# vim sound
This is data concerning your internal soundcard, which is, at the moment, set as primary audio device (card 0).
alias snd-card-0 snd-x-y
alias sound-slot-0 snd-x-y
Now, you will have to add the information for AUDIO KONTROL 1 and "swap" the primary and secondary audio device.
Therefore, the file should then look approximately like this:
Save this file.
#AUDIO KONTROL 1 (primary device)
alias snd-card-0 snd-usb-caiaq
alias sound-slot-0 snd-usb-caiaq
options snd-usb-caiaq index=0
#internal card (secondary device)
alias snd-card-1 snd-x-y
alias sound-slot-1 snd-x-y
options snd-x-y index=1
3. Testing the new configuration
This command should list the two cards.
You need a WAVE file in your home directory for testing the sound cards.
To check things out, type (in normal user mode)
If you hear something now, your internal audio device (card 1) still works.
aplay -D hw:1 [yours].wav
Now, it's time to check out AUDIO KONTROL 1:
If that gives you sound, AUDIO KONTROL 1 (card 0) has been sucessfully installed as your primary audio device.
aplay -D hw:0 [yours].wav
So, now you can go on solving the next "problem": Making your programs use the soundcard of your choice.
4. Giving names to your cards (optional)
This is just something we found useful during the configuration process.
And it is probably a good thing to do if you have more than 2 cards.
As I wrote, to test a sound card via aplay, you will have to specify the device (except for the primary one).
So if you wanted to address the secondary card (card 1), you would have to type
Now imagine, you have 5 sound cards. Then it would be more comfortable to be able to simply type
because then you don't have to keep the device numbers in mind.
For this reason, open a shell and create a file called .asoundrc in your home directory.
In this file you can now specify aliases for you cards.
user@debian:~$ vim .asoundrc
Mine looks like this:
So, if I want so address my secondary/internal sound card via aplay, I simply type
device 0 #i am not really shure about devices
subdevice 0 #and subdevices, but as far as now, everything works
aplay -D internal [soundfile]
So far that's it.
What still doesn't work is the beautiful red light AUDIO KONTROL 1 normally shows.
I hope this post is useful to people who want to run this card under Linux.
If you have any problems or hints, simply post back.