But based on your input, this http://www.linux-hardware-guide.com/2014-08-26-creative-sound-blaster-audigy... and this http://alsa.opensrc.org/Emu10k1 https://wiki.debian.org/snd-emu10k1%3E I think you need at least custom setup to the driver (and perhaps newer kernel version). This way the chance for the driver reporting usable setup is higher.
I've already installed alsa firmwares and the test programs the articles mentions are running fine. Everything works.
I think you have to solve this and come back. Perhaps alsamixer can resolve some of the reported features better than kmix, which does not mean that what is reported is correct.>> I see there is a lot of information on the web regarding your card. I am not an expert in alsa, but I would look first in this direction. Try at least setting up your device values properly.
I can't solve this, since i have no idea what is the problem. The drivers, firmwares are installed, the card is working, all the channels can be handled from alsamixer... And i have no idea how i can set up my device values properly, because i don't know what are they. There are no documents about what should i alias to what. deloptes deloptes@gmail.com írta:
Ló Béla wrote:
You did not provide any information about kernel or OS.
Debian 8, AMD64, 3.16
Are you not using pulse audio?
No, pulseaudio has been entirely removed from my machine.
On the alsa page there are some instruction how to configure the devices properly, so that you have consistent mapping.
Unfortunately i have no idea what kind of device numbers are exists on the Audigy Rx and if ALSA recognize it badly, then the current layout maybe only partially correct. So, i don't know what aliases should i make. As for the commands:
root@Csabi:~# uname -a Linux Csabi 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux
root@Csabi:~# lsmod | grep snd snd_emu10k1 148204 3 snd_util_mem 12747 1 snd_emu10k1 snd_hwdep 13148 1 snd_emu10k1 snd_rawmidi 27024 1 snd_emu10k1 snd_seq_device 13132 2 snd_rawmidi,snd_emu10k1 snd_ac97_codec 118711 1 snd_emu10k1 snd_pcm_oss 44798 0 snd_mixer_oss 22042 2 snd_pcm_oss snd_pcm 88662 3 snd_pcm_oss,snd_ac97_codec,snd_emu10k1 snd_timer 26668 2 snd_pcm,snd_emu10k1 snd 65338 13
snd_pcm_oss,snd_ac97_codec,snd_hwdep,snd_timer,snd_pcm,snd_rawmidi,snd_emu10k1,snd_seq_device,snd_mixer_oss
soundcore 13026 2 snd ac97_bus 12510 1 snd_ac97_codec
root@Csabi:~# amixer Result is here: http://oscomp.hu/depot/amixer.log
root@Csabi:~# amixer -c 0
Result is here: http://oscomp.hu/depot/amixer_c0.log
root@Csabi:~# amixer -c 1 Invalid card number.
It could be something in kmix, but I doubt it.
Unless, it's really that ALSA reports badly something to KMix, it's a KMix issue.
- TCH
I looked briefly in the kmix code. There are few places that could be checked, but this will require enable debugging in the code (compiling etc)
But based on your input, this http://www.linux-hardware-guide.com/2014-08-26-creative-sound-blaster-audigy... and this http://alsa.opensrc.org/Emu10k1 https://wiki.debian.org/snd-emu10k1
I think you need at least custom setup to the driver (and perhaps newer kernel version). This way the chance for the driver reporting usable setup is higher.
I think you have to solve this and come back. Perhaps alsamixer can resolve some of the reported features better than kmix, which does not mean that what is reported is correct.
I see there is a lot of information on the web regarding your card. I am not an expert in alsa, but I would look first in this direction. Try at least setting up your device values properly.
I have for example
## ALSA portion alias char-major-116 snd alias snd-card-0 snd-hda-intel alias snd-card-1 snd-usb-audio
## module options should go here options snd-hda-intel index=0 model=ref enable_msi=1 enable=0,1
regards
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting