Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Hi i already buy the sound blaster 5.1 for the creative t5900 but now the problem is this
alsamixer: function snd_ctl_open failed for default: No such device
Why?
To have sound you need modules for your soundcard loaded in your system.
Issue "/sbin/lspci" and check "lsmod" to see if you have the proper modules
loaded for the soundcard your system detected. Probably emu10k1 for yours.
Yeah i did that the audio card is good and i can listen the music but i can't set the volum, infact the central sub doesn't play, this is my really problem.
It doesn't look like you have all the modules loaded for the card.
I'm in America and my computer with a emu10k1 card is in China.
However, you can check at ALSA and use that line they've got for
loading modules. I have 5.1 speakers and the modules listed on
that site and all 6 speakers work fine.
These are the modules I have on a box I just built here with only
the onboard VIA soundchip:
Forget re-compiling the kernel because soundcore is already compiled. If was not compiled, then loaded up the snd-emu10k1 module will not work. You may need to compile and install ALSA libraries if you have not done so. Also clear out ~/.asoundrc and /etc/asound.conf.
Have you tried to insert the mdoules into the kernel? As root issue:
modprobe snd-emu10k1;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss
If that works, don't read further and enjoy your sound. If not ...
There is no need to recompile ALSA for Slack with your 2.6.x.y kernel.
Support was already there in Slackware. You should have these pkgs:
Code:
bruce@silas:/backup/slackware/slackbuilds/keytouch/build$ ls /var/log/packages/*alsa*
/var/log/packages/alsa-driver-1.0.9b_2.4.31-i486-1 /var/log/packages/alsa-oss-1.0.9-i486-1
/var/log/packages/alsa-lib-1.0.9-i486-1 /var/log/packages/alsa-utils-1.0.9a-i486-2
from a Slackware -current system. That is in mine, which was installed
with Slackware -current from Sept. 26, and the only thing added since
then was Thunderbird-1.0.7. Those ALSA packages were also in 10.2,
having been updated after 10.1 was released; so if you've run Slack
current for a while, you already had them.
If you've recompiled ALSA you may have messed up your Slackware
packages. Please tell us what you did, as your last post isn't very clear.
If you recompiled ALSA, I would get those 4 ALSA packages I listed
above and reinstall them ... either from a Slackware-10.2 CD or d/l
them from Slackware or an official mirror.
Check if you have those other modules in your kernel, and if you do,
reinstall those ALSA packages from Slackware.
I have the module in the kernel, i yet ricompiled alsa with the new reletion of this, i put on my slackware the tgz of alsa. I really don't know why i have this problem... but i need to alsa for set the speaker suond, with emutool, now i'm recompiling the kernel with static modules, i'hope that i can do that.
Have you tried to insert the mdoules into the kernel? As root issue:
modprobe snd-emu10k1;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss
If that works, don't read further and enjoy your sound. If not ...
There is no need to recompile ALSA for Slack with your 2.6.x.y kernel.
Support was already there in Slackware. You should have these pkgs:
Code:
bruce@silas:/backup/slackware/slackbuilds/keytouch/build$ ls /var/log/packages/*alsa*
/var/log/packages/alsa-driver-1.0.9b_2.4.31-i486-1 /var/log/packages/alsa-oss-1.0.9-i486-1
/var/log/packages/alsa-lib-1.0.9-i486-1 /var/log/packages/alsa-utils-1.0.9a-i486-2
from a Slackware -current system. That is in mine, which was installed
with Slackware -current from Sept. 26, and the only thing added since
then was Thunderbird-1.0.7. Those ALSA packages were also in 10.2,
having been updated after 10.1 was released; so if you've run Slack
current for a while, you already had them.
If you've recompiled ALSA you may have messed up your Slackware
packages. Please tell us what you did, as your last post isn't very clear.
If you recompiled ALSA, I would get those 4 ALSA packages I listed
above and reinstall them ... either from a Slackware-10.2 CD or d/l
them from Slackware or an official mirror.
Check if you have those other modules in your kernel, and if you do,
reinstall those ALSA packages from Slackware.
Wrong, any distribution that you use will not have /etc/asound.conf or ~/.asoundrc. Any smart person should have common sense if they do not see a required file, create it. Also you do not need to recompile the kernel for ALSA. The only thing that ALSA requires is sound support in the kernel which is already selected. OSS and ALSA in the kernel does not need to be selected in the kernel. The kernel uses old versions of OSS and ALSA, so it useless to compile both in the process of compiling the kernel. Though sound support has to be enabled (soundcore if set as a module) in the kernel for either OSS and ALSA to work which is already compiled.
When I was using Slackware, I removed Slackware's ALSA package and installed ALSA manually (./configure && make && make install && depmod).
Like said earlier the message:
Quote:
alsamixer: function snd_ctl_open failed for default: No such device
Means you do not have default in either /etc/asound.conf or ~/.asoundrc. Either /etc/asound.conf or ~/.asoundrc could have incorrect syntax, so you may want to rename the files or make them blank. Also the ALSA library may not match the driver version. The reason to not use ALSA that comes from the kernel shows this well. Use ALSA drivers, libraries, and utilities from alsa-project.org. Also the ALSA library is sensitive to CFLAG and CCFLAG options, so keep the options to a bare minimum.
A second look at the module list shows that two sound modules emu10k1 and snd-emu10k1 is loaded. You will not get any sound because both modules are conflicting with each other. The second module should not ever get loaded because it will come to an error and this error stops it from loading. I think hotplug forces emu10k1 module to load. You can place emu10k1 in /etc/hotplug/blacklist. Next time you reboot, hotplug will not load emu10k1.
I found the soluzion, when there is alsamixer i can't start emutool or if i use emutool i can't use alsamixer. I succeeded the lateral speaker, but i'm not able to set the central speaker :? I used:
neo@Neo:~$emu-dspmgr -o
Outputs:
Front L
Front R
Digital L
Digital R
Digital Center
Digital LFE
Phones L
Phones R
Rear L
Rear R
ADC Rec L
ADC Rec R
Mic Rec
out6r
out7l
out7r
out8l
Analog Center
Analog LFE
out9r
out10l
out10r
out11l
out11r
out12l
out12r
out13l
out13r
out14l
out14r
out15l
out15r
This one of input
Code:
neo@Neo:~$emu-dspmgr -i
Inputs:
Pcm L
Pcm R
fx2
fx3
Pcm1 L
Pcm1 R
fx6
fx7
fx8
fx9
fx10
fx11
fx12
fx13
fx14
fx15
Analog L
Analog R
CD-Spdif L
CD-Spdif R
in2l
in2r
Opt. Spdif L
Opt. Spdif R
Line2/Mic2 L
Line2/Mic2 R
RCA Spdif L
RCA Spdif R
RCA Aux L
RCA Aux R
in7l
in7r
I tried to use
Code:
neo@Neo:~$emu-dspmgr -a"Analog Center
Error: Bad patch or gpr name
neo@Neo:~$emu-dspmgr -a"Digital Center"
Error: Bad route specified
You did not say that you want digital ouput. All you said you can not get sound working. I never use emutools when I was using Creative Labs Soundblaster LIVE!. Also I think they are only for OSS modules (drivers). ALSA has plenty documentation for the card on how to output digital through the orange or center/subwoofer connector. Either use alsamixer and use the tools that ALSA provides or use OSS and use emutools. Try `alsamixer -V all`to get a more detail view of mixer controls that amixer lists. All channels does work, but you have to specify alsa and surround51 to output 6 channels. Though if the source media has 2 channels information, it will output 2 channels.
I now use either Audiotrak Prodigy 7.1 and Turtle Beach Santa Cruz. Creative Labs Soundblaster LIVE! and up color the sound, so they are crap.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.