View previous topic :: View next topic |
Author |
Message |
LoTeK Apprentice
Joined: 26 Jul 2012 Posts: 270
|
Posted: Sun May 19, 2013 11:43 am Post subject: EMU-0404 PCIe with alsa -> no sound |
|
|
hi,
I'm trying to set up my EMU-0404 PCIe soundcard, but I get no sound.
the system recognizes the card:
output of lspci -vv -s 08:04.0:
Code: |
08:04.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
Subsystem: Creative Labs Device 4005
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (500ns min, 5000ns max)
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at a000 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: snd_emu10k1
Kernel modules: snd_emu10k1 |
I've installed alsa-firmware and set the card as the default card:
cat /etc/modprobe.d/alsa.conf:
Code: |
# Alsa kernel modules' configuration file.
# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore
##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
## ALSA portion
## alias snd-card-0 snd-interwave
## alias snd-card-1 snd-ens1371
## OSS/Free portion
## alias sound-slot-0 snd-card-0
## alias sound-slot-1 snd-card-1
##
# OSS/Free portion - 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
## OSS/Free portion - card #2
## alias sound-service-1-0 snd-mixer-oss
## alias sound-service-1-3 snd-pcm-oss
## alias sound-service-1-12 snd-pcm-oss
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
# Set this to the correct number of cards.
options snd cards_limit=1
options snd slots=snd_emu10k1,snd_hda_intel
options snd_emu10k1 index=0
options snd_hda_intel index=1 |
I think the problem is the configuration of alsa?! If I run "alsaconf" I get the message that none of my cards is supported, but I get this message with the onboard soundcard too and even so I had sound.
output of aplay -l:
http://bpaste.net/show/100081/
when I run:
Code: | aplay /usr/share/sounds/alsa/Noise.wav |
I get:
Code: | ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
aplay: main:696: audio open error: No such file or directory |
and:
Code: | speaker-test -t sine -f 440 -c 2 |
produces:
Code: | speaker-test 1.0.26
Playback device is default
Stream parameters are 48000Hz, S16_LE, 2 channels
Sine wave rate is 440.0000Hz
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Playback open error: -2,No such file or directory |
_________________ "I want to see gamma rays! I want to hear X-rays! Do you see the absurdity of what I am? I can't even express these things properly because I have to conceptualize complex ideas in this stupid limiting spoken language!" |
|
Back to top |
|
|
xaviermiller Bodhisattva
Joined: 23 Jul 2004 Posts: 8708 Location: ~Brussels - Belgique
|
|
Back to top |
|
|
LoTeK Apprentice
Joined: 26 Jul 2012 Posts: 270
|
Posted: Sun May 19, 2013 8:10 pm Post subject: |
|
|
well that sucks..!!
I've read that the PCI card is supported, for example: http://forums.fedoraforum.org/showthread.php?t=245159
I've tried to follow the instructions from your link, but while trying to configure the alsa-drivers with:
Code: | ./configure --with-cards=emu10k1 --with-sequencer=yes |
I get:
Code: | checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory... /usr/src/alsa/alsa-driver-1.0.25
checking cross compile...
checking for directory with ALSA kernel sources... /usr/src/alsa/alsa-driver-1.0.25/alsa-kernel
checking for directory with kernel source... /lib/modules/3.8.6-hardened/source
checking for directory with kernel build... /lib/modules/3.8.6-hardened/build
checking for kernel linux/version.h ... no
The file /lib/modules/3.8.6-hardened/source/include/INCLUDE_VERSION_H does not exist.
Please install the package with full kernel sources for your distribution
or use --with-kernel=dir option to specify another directory with kernel
sources (default is /lib/modules/3.8.6-hardened/source). |
Do you think I should try it with pulseaudio? _________________ "I want to see gamma rays! I want to hear X-rays! Do you see the absurdity of what I am? I can't even express these things properly because I have to conceptualize complex ideas in this stupid limiting spoken language!" |
|
Back to top |
|
|
wcg Guru
Joined: 06 Jan 2009 Posts: 588
|
Posted: Mon May 20, 2013 12:45 pm Post subject: |
|
|
In your aplay -l output, there is no device 1, only devices 0,2, and 3.
This is the problem? It does look like the kernel driver is not recognizing
something or misnumbering devices that it does recognize.
I only have an onboard hda-intel sound device at the moment to compare
with, but in aplay -l output it shows devices 0 and 1. device 0 is analog playback
and device 1 is digital playback.
The error message looks more like what one would see with a
misconfigured /etc/asound.conf or ~/.asoundrc, but I am no expert
on alsa setup, so that is only an impression from reading lots of alsa
problem reports.
(People still use the kernel's OSS support? I disabled it in the kernel
.config months ago, no negative side-effects with hda-intel or the
ice1724 driver. The only things that use alsa on my system are mplayer,
firefox, and alsa-utils tools like alsamixer and aplay.) _________________ TIA |
|
Back to top |
|
|
LoTeK Apprentice
Joined: 26 Jul 2012 Posts: 270
|
Posted: Mon May 20, 2013 3:12 pm Post subject: |
|
|
I think device 1 is the onboard-soundcard that I've disabled in the BIOS, because I've read one has to do that.
Quote: | The only things that use alsa on my system are mplayer,
firefox, and alsa-utils tools like alsamixer and aplay.) |
same on my system. the OSS support is enabled by default and I haven't heard that one should disable it. _________________ "I want to see gamma rays! I want to hear X-rays! Do you see the absurdity of what I am? I can't even express these things properly because I have to conceptualize complex ideas in this stupid limiting spoken language!" |
|
Back to top |
|
|
wcg Guru
Joined: 06 Jan 2009 Posts: 588
|
Posted: Wed May 22, 2013 5:37 am Post subject: |
|
|
I disabled OSS in the kernel .config when I was trying to figure
out some alsa problem with a few pci soundcards. (It did not
make any difference, but the soundcards eventually worked
without it, so I left it disabled.)
I do not know if alsa would assign "device 1" to onboard sound
disabled in BIOS. How would it even know it is there?
(You probably don't have an /etc/asound.conf or ~/.asoundrc,
either, I guess, so alsa would be using a default configuration.)
The fact that your soundcard actually appears in aplay -l
output is a good sign, though. The kernel finds it, alsa knows
it is there. It should be possible to find out what slave device
it is trying to open and failing. (It is just that when I have seen
messages like that in people's problem reports, an asound.conf
or .asoundrc file was always actually redirecting the output
through what alsa calls a "slave device".) _________________ TIA |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|