Re: [linux-audio-user] alsa setup debug (was: jackd -d alsa -d hw:0 -p512 / problem to start)
27 Oct
2003
27 Oct
'03
9:44 a.m.
this sounds
like what happens when alsa is not running properly.
I do the following tests: arecord (meanwhile in other xterm play some
mp3), and then when I do aplay, file.tests contains a portion of this
mp3 recorded [I suppose] using alsa.
But you're right, alsa say 'failed' when start and all seems to go bad,
27 Oct
27 Oct
10:49 a.m.
New subject: [linux-audio-user] alsa setup debug (was: jackd -d alsa -d hw:0 -p512 / problem to start)
On Mon, Oct 27, 2003 at 04:58:33PM +0100, Tim Orford wrote:
i'm assuming you mean the alsa init script.
did you look in the logs (eg /var/log/syslog) for why it failed?
mmm... no.
maybe you could tell us what distro and software
versions you are
Debian [unstable]
Package: alsa [alsa-base 0.9.6-5 ]
Package: jackd
Versions:
0.75.0-2(/var/lib/apt/lists/http.us.debian.org_debian_dists_unstable_main_binary-i386_Packages)(/var/lib/dpkg/status)
lspci -v
00:0e.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
Subsystem: Unknown device 4942:4c4c
Flags: bus master, slow devsel, latency 96, IRQ 5
I/O ports at 1480 [size=64]
[this Montego soundcard doesn't work under my Debian box]
00:10.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02)
Subsystem: Voyetra Technologies Montego
Flags: bus master, medium devsel, latency 64, IRQ 9
Memory at f4000000 (32-bit, non-prefetchable)
[size=128K]
I/O ports at 14f8 [size=8]
I/O ports at 14f0 [size=8]
Capabilities: [dc] Power
Management version 1
lsmod
Module Size Used by
Not tainted
3c59x 27600 1
lp 6432 0 (autoclean)
snd-seq-midi 4064 0 (autoclean) (unused)
snd-seq-oss 29632 0 (unused)
snd-seq-midi-event 3296 0 [snd-seq-midi snd-seq-oss]
snd-seq 36816 2 [snd-seq-midi snd-seq-oss
snd-seq-midi-event]
snd-pcm-oss 39556 0
snd-mixer-oss 13592 0 [snd-pcm-oss]
snd-ens1370 8580 0
snd-pcm 60804 0 [snd-pcm-oss snd-ens1370]
snd-timer 14468 0 [snd-seq snd-pcm]
snd-page-alloc 6292 0 [snd-ens1370 snd-pcm]
snd-rawmidi 13408 0 [snd-seq-midi snd-ens1370]
snd-seq-device 4288 0 [snd-seq-midi snd-seq-oss snd-seq
snd-rawmidi]
snd-ak4531-codec 4888 0 [snd-ens1370]
snd 28964 0 [snd-seq-midi snd-seq-oss
snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-ens1370
snd-pcm snd-timer snd-rawmidi snd-seq-device snd-ak4531-codec]
soundcore 3844 8 [snd]
service alsa status
(or whatever it is on your distro)
[I don't know how to do that, my init
script say that. In fact is the
first time I'm trying to use alsa]
Usage: /etc/init.d/alsa
{start|stop|restart|reload|force-stop|force-restart|force-reload}
cat /var/log/syslog | grep -i alsa
(for the last boot)
# cat /var/log/syslog |grep -i alsa
#
[nothing, except grep -i alsa /var/log/boot]
/var/log/boot:Tue Oct 21 10:03:21 2003: Starting ALSA (version 0.9.6): ens1370.
/var/log/boot:Tue Oct 21 10:03:24 2003: Restoring ALSA mixer settings... failed
/var/log/boot.0:Thu Oct 16 14:24:13 2003: Starting ALSA (version 0.9.6):
warning, no drivers defined in /etc/modules.conf failed
But I have this lines in /etc/modules.conf
### update-modules: start processing /etc/modutils/alsa
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-ens1370
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
also read the documentation for your card on
http://www.alsa-project.org
I readed yet
and the quicktoots:
http://www.djcj.org/LAU/quicktoots/
I'm reading now ;-)
the archives for the alsa-user list might also be
instructive...
Thanks a lot for your help Tim.
Felix
--
Félix Cuello
felix(a)qodiga.com
--
Time will end all my troubles, but I don't always approve of Time's methods.
28 Oct
28 Oct
2:16 p.m.
New subject: [linux-audio-user] alsa setup debug (was: jackd -d alsa -d hw:0 -p512 / problem to start)
On Mon, Oct 27, 2003 at 11:47:39AM -0300, felix.news(a)qodiga.com wrote:
looks ok.
to use jack you only need "snd", "snd-pcm" and
"snd-ens1370"
ok, no problem. Module info is more useful anyway.
Debian [unstable]
Package: alsa [alsa-base 0.9.6-5 ]
Package: jackd
Versions:
0.75.0-2(/var/lib/apt/lists/http.us.debian.org_debian_dists_unstable_main_binary-i386_Packages)(/var/lib/dpkg/status)
As you trimmed the output we dont know what other hardware could be causing
problems, but still, it looks ok.
so which card are you trying to use? the ensoniq i guess.
lspci -v
00:0e.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
Subsystem: Unknown device 4942:4c4c
Flags: bus master, slow devsel, latency 96, IRQ 5
I/O ports at 1480 [size=64]
[this Montego soundcard doesn't work under my Debian box]
00:10.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02)
Subsystem: Voyetra Technologies Montego
Flags: bus master, medium devsel, latency 64, IRQ 9
Memory at f4000000 (32-bit, non-prefetchable)
[size=128K]
I/O ports at 14f8 [size=8]
I/O ports at 14f0 [size=8]
Capabilities: [dc] Power
Management version 1 lsmod
Module Size Used
by Not tainted
3c59x 27600 1
lp 6432 0 (autoclean)
snd-seq-midi 4064 0 (autoclean) (unused)
snd-seq-oss 29632 0 (unused)
snd-seq-midi-event 3296 0 [snd-seq-midi snd-seq-oss]
snd-seq 36816 2 [snd-seq-midi snd-seq-oss
snd-seq-midi-event]
snd-pcm-oss 39556 0
snd-mixer-oss 13592 0 [snd-pcm-oss]
snd-ens1370 8580 0
snd-pcm 60804 0 [snd-pcm-oss snd-ens1370]
snd-timer 14468 0 [snd-seq snd-pcm]
snd-page-alloc 6292 0 [snd-ens1370 snd-pcm]
snd-rawmidi 13408 0 [snd-seq-midi snd-ens1370]
snd-seq-device 4288 0 [snd-seq-midi snd-seq-oss snd-seq
snd-rawmidi]
snd-ak4531-codec 4888 0 [snd-ens1370]
snd 28964 0 [snd-seq-midi snd-seq-oss
snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-ens1370
snd-pcm snd-timer snd-rawmidi snd-seq-device snd-ak4531-codec]
soundcore 3844 8 [snd] service alsa
status
(or whatever it is on your distro)
[I don't know how to do that, my init
script say that. In fact is the
first time I'm trying to use alsa]
Usage: /etc/init.d/alsa
{start|stop|restart|reload|force-stop|force-restart|force-reload} # cat /var/log/syslog |grep -i alsa
#
[nothing, except grep -i alsa /var/log/boot]
/var/log/boot:Tue Oct 21 10:03:21 2003: Starting ALSA (version 0.9.6): ens1370.
/var/log/boot:Tue Oct 21 10:03:24 2003: Restoring ALSA mixer settings... failed
looks probably ok.
probably you havnt saved your mixer settings?
they live in /etc/asound.state (or your home dir)
you might want to create one using the alsactl program as root.
(i dont know why disributions dont do this as part of the alsa installation)
/var/log/boot.0:Thu Oct 16 14:24:13 2003: Starting
ALSA (version 0.9.6):
warning, no drivers defined in /etc/modules.conf failed
er, isnt this from last week? :-)
But I have this lines in /etc/modules.conf
### update-modules: start processing /etc/modutils/alsa
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-ens1370
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
ok.
all looks ok.
one further check: look in /proc/asound/cards
there should be just one card "card0"
# arecord -f cd > file.test
Recording WAVE 'stdout' : Signed 16 bit Little Endian, Rate 44100 Hz,
Stereo
Aborted by signal Interrupt...
i originally thought this was an error but i guess it is just
you hitting Ctl-C.
it looks like alsa is not the problem, but before moving onto jack
maybe it would be wise to check recording from the soundcard input
rather than stdin.
jack:
how often are the xruns? or are they too fast to count?
pls post the first few lines of jack output.
you are running everything as root arnt you?
is the kernel compiled with low-latency and preemtible options?
maybe dont start with ardour as its undergoing rapid development
atm. Better to imo use eg 'alsaplayer -o jack'. Also use one of
the jack control guis such as qjackconnect or qjackctl to check
jackd has 2 input ports and 2 output ports.
cheers!
--
Tim Orford
30 Oct
30 Oct
8:54 a.m.
New subject: [linux-audio-user] alsa setup debug (was: jackd -d alsa -d hw:0 -p512 / problem to start)
On Tue, Oct 28, 2003 at 09:29:25PM +0100, Tim Orford wrote:
Sorry... I suppose the output could be too long to post here.
Yes. I don't know how to say in english but I'll try :-) -> the power
company leave the city (this day) without power for political reasons.
[because power companies wants to grow up their taxes]
Yes. I hitted Ctl-C because I don't know how to stop arecord :-)
> lspci -v
As you trimmed the output we dont know what other hardware could be causing
problems, but still, it looks ok. so which card are you trying to use? the ensoniq i
guess.
Yes!. Because I compiled vortex drivers without success.
looks ok.
to use jack you only need "snd", "snd-pcm" and
"snd-ens1370"
Ok.
looks probably ok.
probably you havnt saved your mixer settings?
they live in /etc/asound.state (or your home dir)
you might want to create one using the alsactl program as root.
(i dont know why disributions dont do this as part of the alsa installation)
# ll /etc/asound.state
-rw-r--r-- 1 root root 6381 Sep 14 18:20 /etc/asound.state
now is here :-)
/var/log/boot.0:Thu Oct 16 14:24:13 2003: Starting ALSA (version 0.9.6):
warning, no drivers defined in /etc/modules.conf failed
er, isnt this from last week? :-) all looks ok.
oh no! :-)... I expected an error
or something wrong... :-))
one further check: look in /proc/asound/cards
there should be just one card "card0"
# cat /proc/asound/cards
0 [AudioPCI ]: ENS1370 - Ensoniq AudioPCI
Ensoniq AudioPCI ENS1370 at 0x1480, irq 5
and
# ll -d /proc/asound/card?
dr-xr-xr-x 5 root root 0 Oct 30 09:38 /proc/asound/card0/
-r--r--r-- 1 root root 0 Oct 30 09:38 /proc/asound/cards
# arecord -f cd
> file.test
Recording WAVE 'stdout' : Signed 16 bit Little Endian, Rate 44100 Hz,
Stereo
Aborted by signal Interrupt...
i originally thought this was an error but i guess it is just
you hitting Ctl-C. it looks like alsa is not the problem, but before
moving onto jack
maybe it would be wise to check recording from the soundcard input
rather than stdin.
Ok... I'll take a look of arecord documentation, because arecord throw
the data to stdout.
jack:
how often are the xruns? or are they too fast to count?
Intinite times or using
your words: 'too fast to count'.
pls post the first few lines of jack output.
# jackd -d alsa -d hw:0 -p512 |head -n 6
JACK compiled with System V SHM support
loading driver ..
open
starting engine
**** alsa_pcm: xrun of at least 0.060 msecs
**** alsa_pcm: xrun of at least 4.512 msecs
**** alsa_pcm: xrun of at least 0.033 msecs
**** alsa_pcm: xrun of at least 3.397 msecs
**** alsa_pcm: xrun of at least 0.051 msecs
**** alsa_pcm: xrun of at least 2.852 msecs
**** alsa_pcm: xrun of at least 0.034 msecs
**** alsa_pcm: xrun of at least 0.019 msecs
**** alsa_pcm: xrun of at least 0.215 msecs
**** alsa_pcm: xrun of at least 0.033 msecs
**** alsa_pcm: xrun of at least 0.052 msecs
you are running everything as root arnt you?
Yes.
is the kernel compiled with low-latency and preemtible
options?
The kernel is only compiled with low-latency because I can't find
preemptible patch for kernel 2.4.22.
# cat /proc/sys/kernel/lowlatency
1
#
maybe dont start with ardour as its undergoing rapid
development
atm. Better to imo use eg 'alsaplayer -o jack'. Also use one of
the jack control guis such as qjackconnect or qjackctl to check
jackd has 2 input ports and 2 output ports.
Without running jackd I tried to do that:
# jackrec -f pepe -d 4 0
cannot connect to jack server
cannot connect to default JACK server
jack server not running?
#
but running jackd [with a lot of xruns output in the other console]
I get this error:
# jackrec -f pepe -d 4 0
cannot connect input port jackrec:input1 to 0
# jackrec -f pepe -d 4 1
cannot connect input port jackrec:input1 to 1
# jackrec -f pepe -d 4 2
cannot connect input port jackrec:input1 to 2
[I changed port by hand... because I don't have qjackconnect or
qjackctl, I'll investigate why]
cheers!
--
Tim Orford
Thanks a lot for your help Tim.
Felix
--
Félix Cuello
felix(a)qodiga.com
--
Las gentes que nunca se preocupan por sus antepasados jamás mirarán hacia la
posteridad.
-- Edmund Burke. (1729-1797) Político y escritor británico.
12:08 p.m.
New subject: [linux-audio-user] alsa setup debug (was: jackd -d alsa -d hw:0 -p512 / problem to start)
so which card
are you trying to use? the ensoniq i guess.
Yes!. Because I compiled vortex drivers without success. > > /var/log/boot.0:Thu Oct 16 14:24:13 2003:
Starting ALSA (version 0.9.6):
so alsa init sript runs without errors now...?
Yes. I don't know how to say in english but
I'll try :-) -> the power
company leave the city (this day) without power for political reasons.
[because power companies wants to grow up their taxes]
wow!
Aborted by signal Interrupt...
i originally thought this was an error but i guess it is just
you hitting Ctl-C. it looks like
alsa is not the problem, but before moving onto jack
maybe it would be wise to check recording from the soundcard input
rather than stdin.
Ok... I'll take a look of arecord documentation, because arecord throw
the data to stdout. jack:
how often are the xruns? or are they too fast to count?
Intinite times or using
your words: 'too fast to count'. pls post the first few lines of jack output.
# jackd -d alsa -d hw:0 -p512 |head -n 6
JACK compiled with System V SHM support
loading driver ..
open
starting engine
**** alsa_pcm: xrun of at least 0.060 msecs The kernel is only compiled with low-latency because I
can't find
preemptible patch for kernel 2.4.22.
maybe its standard?
does your kernel compile ".config" file have "CONFIG_PREEMPT=y"?
maybe dont
start with ardour as its undergoing rapid development
atm. Better to imo use eg 'alsaplayer -o jack'. Also use one of
the jack control guis such as qjackconnect or qjackctl to check
jackd has 2 input ports and 2 output ports.
Without running jackd I tried to do that:
# jackrec -f pepe -d 4 0
cannot connect to jack server
cannot connect to default JACK server
jack server not running? #
but running jackd [with a lot of xruns output in the other console]
I get this error:
# jackrec -f pepe -d 4 0
cannot connect input port jackrec:input1 to 0
# jackrec -f pepe -d 4 1
cannot connect input port jackrec:input1 to 1
# jackrec -f pepe -d 4 2
cannot connect input port jackrec:input1 to 2
[I changed port by hand... because I don't have qjackconnect or
qjackctl, I'll investigate why]
http://qjackctl.sourceforge.net
http://www.suse.de/~mana/jack.html
but i suspect none of these will work with your 'infinite' xruns :-)
Las gentes que nunca se preocupan por sus antepasados
jamás mirarán hacia la
posteridad.
-- Edmund Burke. (1729-1797) Político y escritor británico.
"The more deeply we penetrate into the labyrinth of art, the further we
find ourselves from those ends for which we entered it." Burke (A Vindication
of Natural Society, 1756.)
i hope that doesnt apply in this case! :-)
--
Tim Orford
2:58 p.m.
New subject: [linux-audio-user] alsa setup debug (was: jackd -d alsa -d hw:0 -p512 / problem to start)
On Thu, 30 Oct 2003 19:19:31 +0100
Tim Orford <tim(a)orford.org> wrote:
unfortunately, head is not showing some output from jack.
you are missing this line:
creating alsa driver ... hw:0|hw:0|4096|2|48000|nomon|swmeter|rt
this is useful cos it shows how jack is actually running.
This particular line is sent to stderr, instead of stdout (which is what head would be
reading from). I'd suggest the following:
jackd -v -d alsa -d hw:0 -p 512 1> jackstdout 2> jackerrout
Let it run for half a second, and then kill it with Ctrl-c. Both files (jackstdout and
jackerrout) should contain more detailed information about what's going on.
|)
|)enji
pls post the first few lines of jack output.
# jackd -d alsa -d hw:0 -p512 |head -n 6
JACK compiled with System V SHM support
loading driver ..
open
starting engine
**** alsa_pcm: xrun of at least 0.060 msecs
7491
days inactive
7494
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Benjamin Flaming -
felix.news＠qodiga.com -
Tim Orford