LinuxQuestions.org
Support LQ: Use code LQCO20 and save 20% on CrossOver Office
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
LinkBack Search this Thread
Old 10-06-2005, 09:12 AM   #1
DarkNeo
Member
 
Registered: Aug 2005
Location: Rome
Distribution: Slackware 10.2 && Debian Sarge
Posts: 49

Rep: Reputation: 15
Alsa && Sound blaster 5.1


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?
 
Old 10-06-2005, 09:36 AM   #2
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 121Reputation: 121
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.
 
Old 10-06-2005, 09:57 AM   #3
DarkNeo
Member
 
Registered: Aug 2005
Location: Rome
Distribution: Slackware 10.2 && Debian Sarge
Posts: 49

Original Poster
Rep: Reputation: 15
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.
Code:
neo@Neo:~$lsmod
Module                  Size  Used by
nvidia               3917052  12 
lp                      9028  0 
ohci_hcd               32644  0 
parport_pc             24836  1 
parport                31816  2 lp,parport_pc
amd64_agp              10184  1 
shpchp                 96740  0 
pci_hotplug             9796  1 shpchp
ohci1394               31412  0 
ieee1394               87864  1 ohci1394
snd_emu10k1           120164  0 
snd_rawmidi            20896  1 snd_emu10k1
snd_ac97_codec         83196  1 snd_emu10k1
snd_util_mem            3776  1 snd_emu10k1
snd_hwdep               7456  1 snd_emu10k1
uhci_hcd               31564  0 
ehci_hcd               42504  0 
i2c_viapro              8272  0 
i2c_core               18960  1 i2c_viapro
evdev                   7232  0 
emu10k1                74052  1 
sound                  71148  1 emu10k1
ac97_codec             17932  1 emu10k1
ide_scsi               14340  0 
ov511                  81504  0 
usbcore               118268  5 ohci_hcd,uhci_hcd,ehci_hcd,ov511
videodev                6976  1 ov511
agpgart                29256  2 nvidia,amd64_agp
 
Old 10-06-2005, 10:24 AM   #4
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 121Reputation: 121
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:
Code:
bruce@silas:~$ lsmod
Module                  Size  Used by
snd_pcm_oss            47008  0 
snd_mixer_oss          16960  1 snd_pcm_oss
sk98lin               169248  0 
ath_pci                69852  0 
ath_rate_sample        14536  1 ath_pci
wlan                  128988  3 ath_pci,ath_rate_sample
ath_hal               146512  3 ath_pci,ath_rate_sample
uhci_hcd               30352  0 
ehci_hcd               30216  0 
i2c_viapro              6736  0 
i2c_core               16976  1 i2c_viapro
snd_via82xx            22688  1 
snd_ac97_codec         81788  1 snd_via82xx
snd_pcm                78984  4 snd_pcm_oss,snd_via82xx,snd_ac97_codec
snd_timer              20356  1 snd_pcm
snd_page_alloc          8456  2 snd_via82xx,snd_pcm
snd_mpu401_uart         5824  1 snd_via82xx
snd_rawmidi            19168  1 snd_mpu401_uart
snd                    44900  9 snd_pcm_oss,snd_mixer_oss,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi
soundcore               7008  1 snd
 
Old 10-06-2005, 01:26 PM   #5
DarkNeo
Member
 
Registered: Aug 2005
Location: Rome
Distribution: Slackware 10.2 && Debian Sarge
Posts: 49

Original Poster
Rep: Reputation: 15
nothing i recompiled all alsa but i can't start alsamixer i'll be crazy

Last edited by DarkNeo; 10-06-2005 at 03:06 PM.
 
Old 10-06-2005, 03:09 PM   #6
DarkNeo
Member
 
Registered: Aug 2005
Location: Rome
Distribution: Slackware 10.2 && Debian Sarge
Posts: 49

Original Poster
Rep: Reputation: 15
However in my kernel .config i put that
Code:
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_VERBOSE_PRINTK=y
CONFIG_SND_DEBUG=y
CONFIG_SND_DEBUG_MEMORY=y
CONFIG_SND_DEBUG_DETECT=y
 
Old 10-06-2005, 09:52 PM   #7
Electro
Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
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.
 
Old 10-06-2005, 10:28 PM   #8
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: Tupelo, MS
Distribution: Gentoo
Posts: 6,926

Rep: Reputation: 121Reputation: 121
Per Electro's post, Slackware doesn't have the .asoundrc file unless you
create it; nor does it have /etc/asound.conf.

You have the modules you need (even more than you need) listed, but
do you also have these for your specific soundcard?
Code:
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
<snip, snip>
CONFIG_SND_EMU10K1=m
From your previous posts I think so.

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.
 
Old 10-07-2005, 09:56 AM   #9
DarkNeo
Member
 
Registered: Aug 2005
Location: Rome
Distribution: Slackware 10.2 && Debian Sarge
Posts: 49

Original Poster
Rep: Reputation: 15
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.
 
Old 10-08-2005, 12:25 AM   #10
Electro
Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
Quote:
Originally posted by Chinaman
Per Electro's post, Slackware doesn't have the .asoundrc file unless you
create it; nor does it have /etc/asound.conf.

You have the modules you need (even more than you need) listed, but
do you also have these for your specific soundcard?
Code:
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
<snip, snip>
CONFIG_SND_EMU10K1=m
From your previous posts I think so.

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.
 
Old 10-09-2005, 02:51 PM   #11
DarkNeo
Member
 
Registered: Aug 2005
Location: Rome
Distribution: Slackware 10.2 && Debian Sarge
Posts: 49

Original Poster
Rep: Reputation: 15
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:
Code:
neo@Neo:~$emu-dspmgr -a"Pcm L:Rear L"
emu-dspmgr -v"Pcm L:Rear L" -mpcm_l
emu-dspmgr -p"Routing" -c"Vol Pcm L:Rear L" -sffffff
emu-dspmgr -a"Pcm R:Rear R"
emu-dspmgr -v"Pcm R:Rear R" -mpcm_l
emu-dspmgr -p"Routing" -c"Vol Pcm R:Rear R" -sffffff
This is the list of output device that i can use
Code:
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
 
Old 10-09-2005, 05:43 PM   #12
Electro
Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
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.
 
Old 10-09-2005, 05:56 PM   #13
DarkNeo
Member
 
Registered: Aug 2005
Location: Rome
Distribution: Slackware 10.2 && Debian Sarge
Posts: 49

Original Poster
Rep: Reputation: 15
Sorry but i forgot to write emu-dspmgr -d for the digital audio, if i do alsamixer -V all
Code:
neo@Neo:~$amixer
amixer: Mixer attach default error: No such device
 
  


Reply


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Japanese canna won't work : Warning: &#12363;&#12394;&#28450;&#23383;&#22793;&am OrganicOrange84 Debian 3 06-30-2005 02:28 PM
Ph&#7909;c h&#7891;i d&#7919; li&#7879;u b&#7883; m&#7845;t???, c&#7913; pollsite General 1 06-27-2005 12:39 PM
Fedora & Sound Blaster one.sick.tzim Linux - Hardware 12 03-09-2005 12:05 AM
Creative Blaster Audigy LS & ALSA problems otchie1 Slackware 10 12-19-2004 03:01 AM
Sound Blaster Live Value & Slack8.0 milos Linux - Hardware 1 05-05-2002 09:56 PM


All times are GMT -5. The time now is 06:44 AM.

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