Hi,
We have a couple of machines that we are having problems with. Has
anyone been able to sucessfully use a Digigram VX222 with the ALSA
drivers?
What kernel should I use? Patches?
We are getting hard lockups of our system. We have turned off all power
management. It seems to be a problem with activity on either the sound
card driver and/or the NIC driver (e100). The board is an Intel
S845WD1-E.
At this point if we do not come up with a solution by next week, the
higher ups are going to make us use Win2k. Ugh.
--
Torleiv Ringer
Broadcast Systems Analyst
Minnesota Public Radio
http://www.mpr.org
hi again,
here are some revised details of my problem!
i am actually running the planetccrma kernel 2.4.20-18.1.caps
when running alsaconf i get:
[root@localhost robcanning]# /usr/sbin/alsaconf
/usr/sbin/alsaconf: line 120: modinfo: command not found
/usr/sbin/alsaconf: line 127: modinfo: command not found
/usr/sbin/alsaconf: line 135: modinfo: command not found
then it finds:
hdsp Xilinx Corporation RME Hammerfall DSP (rev 32) │ │
│ │ intel8x0 Intel Corp. 82801EB AC'97 Audio (rev
02) │ │
│ │ legacy Probe legacy ISA (non-PnP) chips
then it configures snd-hdsp and runs alsasound start at which point
things go wrong:
Loading driver...
Starting sound driver: snd-hdsp
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o: insmod
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o failed
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o: insmod snd-hdsp
failed
done
Setting default volumes...
===============================================================================
Now ALSA is ready to use.
For adjustment of volumes, use your favorite mixer.
Have a lot of fun!
more info:
03:0c.0 Multimedia audio controller: Xilinx Corporation RME Hammerfall
DSP (rev
32)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping+ SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 64
Interrupt: pin A routed to IRQ 5
Region 0: Memory at feae0000 (32-bit, non-prefetchable)
[size=64K]
[root@localhost robcanning]# dmesg
mory allocator: buffers allocated for 1 cards
RME Hammerfall-DSP: no cards found
Hammerfall memory allocator: buffers allocated for 1 cards
RME Hammerfall-DSP: no cards found
which is then repeated a number of times
thanks,
rob
I have just installed AGNULA/demudi-1.1.0 in my desktop machine (Intel
Celeron processor).
My need is to transfer two channels (that is, stereo) digitized sound
back and forth between a Tascam CR-RW2000 and a Pentium-class desktop
computer, so that the sound can be edited. The Tascam has both SP/DIF
coaxial and AES/EBU inputs and outputs.
I have no need for multi-channel operation (other than stereo), nor for
midi or routing.
Recent postings on the alsa-user mail list make me lean toward purchase
of a RME sound card, but I am confused as to which RME cards ALSA
supports. I also am confused as to whether a "multiface" or "digiface"
is required. The RME web site says that ALSA drivers are available for
the DIGI9652 and the DIGI9636; but these models are not listed on the
ALSA Sound Card Matrix web page.
Another possibility is to purchase a USB or Firewire device which
supports SP/DIF or AES/EBU input and output.
The main consideration is ALSA support: which devices (manufacturer
and model) work reliably and bug-free under ALSA?
RLH
Hi to all,
I've found a bugous beaviour in TiMidity++ version 2.11.3, shipped with
debian sid. I've alsa 1.0.1.
Starting timidity in server mode without -Os (alsa output) option:
$ timidity -iA
and than trying to connect a midi keyboard with
$ aconnect 64:0 128:0
it will freeze completly my system, I can save me from brutal reboot
only thanks to the _really_ magic sysrq key 'e'. Under X the sysrq key
'e' doesn't work.
I know that putting the -Os option is the right way but a freeze of the
system it is too much for a wrong option.
Does someone can confirm this beaviour?
Antonio.
PS Try it only in console, so you can recover with ALT+Stamp+e (at least
this works for me)
Hi,
I have Audigy2 ZS card. Alsa 1.0.2 and jack server from current
CVS are installed. Is it possible to force working on 24/96? I
have selected emu10k1 alsa driver. Is it valid selection?
Andrew
Hi to all,
I'm tryng to tune my machine to get the lower latency I can get with my
hardware and linux of course.
I have an audigy player with a debian sarge with the audio apps take
from the unstable branch. I've recompiled the 2.4.22 kernel with
capabilities, low latency, preempted patches. I've compiled the source
packages of alsa 1.0.1 and jack 0.94.
I can obtain a clean sound playing timidity thru my midi keyboard using
3 fragments each of 256 (but only if I'm root, otherwise I get "can't
set sched_setscheduler" and the sound became dirty, maybe I have to
recompile it?) which means a pretty low latency for me.
On the other side I can run jack (jackstart works fine) with a period
not less than 512, and I can't change the number of periods (neither
increase) that is 2 by default. For example:
$ jackstart -R -d alsa -d hw:0 -r 48000 -p 512 -n 1
[snip]
hw:0|hw:0|512|1|48000|0|0|nomon|swmeter|rt|32bit
control device hw:0
configuring for 48000Hz, period = 512 frames, buffer = 1 periods
Couldn't open hw:0 for 32bit samples trying 24bit instead
Couldn't open hw:0 for 24bit samples trying 16bit instead
ALSA: cannot set number of periods to 1 for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
$
The same it is if I set number of periods higher than two (and that's
strange, can be a configuration issue?)
- Is it an hardware/driver limit, can't I reach the same latency that I
have with timidity with jack?
- Is it normal having 16 bit samples with my card?
The last but not least, I have a general question about jack: if I a
stream pass twice or more times into jack (for example alsa in -> jack
rack -> ardour -> alsa out, 3 times) does the latency increases twice or
more, proportionally, or it is only related to the various apps latency?
Ok, I stop to bother anymore you with my (maybe stupid) doubts...
Thanks for the attention, every answer will be greatly apprecciated.
Ciao, Antonio
On Wed, Feb 04, 2004 at 02:56:38 +0000, rob canning wrote:
> why do i need to type /sbin/lspci rather than just lspci which won't work?
because /sbin inst in your $PATH
- Steve
Date: Wed, 4 Feb 2004 12:31:22 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
X-Originating-IP: 195.218.110.16
X-Mailer: Eircom Net CRC Webmail (http://www.eircom.net/)
Organization: Eircom Net (http://www.eircom.net/)
hi,
i am trying to get my
RME hamerfall dsp multiface (pci) working with
redhat 9 with a planetccrma kernel 2.4.21-1.11
i have downloaded the latest alsa drivers 1.0.2
and am encountering the following problem:
[root@localhost robcanning]# /sbin/modprobe snd-hdsp
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o: init_module: No
such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o: insmod
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o failed
/lib/modules/2.4.20-18.1.caps/kernel/sound/snd-hdsp.o: insmod snd-hdsp
failed
[root@localhost robcanning]# /sbin/modprobe snd-card-hdsp
modprobe: Can't locate module snd-card-hdsp
it seems like my card isn't being found but
when i put the card in kudzu popped up and recognized it
can anybody help - i'm quite new to linux
thanks for any help,
rob
www.robcanning.utvinternet.com