problems with hdsp

problems with hdsp

[David E. Storey]

Folks,

I'm running alsa-driver v0.9.3a under Linux v2.4.21-rc2 with kernel
preemption, low-latency, acpi-20030424, capabilities, soundcore-2.4.20
and rtc-2.4.16 patches. (Jack still has NUMEROUS xruns under virtually
no load whatsoever using the intel8x0 driver... while alsaplayer and
xmms-alsa hardly skip a beat while pounding the CPU with kernel
compiles, but since this isn't the jack mailing list...)

I tried compiling the hdsp driver and it tells me:

(root@scorpius root)# modprobe snd-hdsp
/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o: unresolved
symbol snd_hwdep_new
/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o: insmod
/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o failed
/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o: insmod
snd-hdsp failed

it seems simple to fix, but my knowledge of alsa isn't intimate... yet.
It was compiled via:

./configure --with-pcmcia=kernel --with-cards=intel8x0,hdsp

I've kind-of gotten it to work in the past, but I had to rev down the
firmware, which I'm really hoping I won't have to do soon. (Since the
latest windoze drivers required upgraded firmware and that's been the
only way I can do any kind of multi-track recording... due to jack's
issues, ardour is fairly useless to me for anything other than
mixdowns.)

If this issue has already been hashed out, I apologize. The web archives
of this list start about five days ago.

Also, I've read in numerous places that it's a really BAD idea to "bond"
multiple sound cards together using one's .asoundrc file since they're
not synchronized. Is that still the case if, say, I synced the word
clock among multiple multifaces? Would anything change in the .asoundrc
file?

d!



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

Re: problems with hdsp

[Paul Davis]

>I tried compiling the hdsp driver and it tells me:
>
>(root@scorpius root)# modprobe snd-hdsp
>/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o: unresolved
>symbol snd_hwdep_new
>/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o: insmod
>/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o failed
>/lib/modules/2.4.21-rc2/kernel/sound/pci/rme9652/snd-hdsp.o: insmod
>snd-hdsp failed
>
>it seems simple to fix, but my knowledge of alsa isn't intimate... yet.
>It was compiled via:

this was fixed in CVS a few days ago. the hwdep module (which is now
used by the hdsp driver) wasn't declared as a dependency for the hdsp
driver. 

there are other (non-hdsp-related) issues ALSA CVS current, but i
believe they won't affect you on a single CPU system.

>I've kind-of gotten it to work in the past, but I had to rev down the
>firmware, which I'm really hoping I won't have to do soon. (Since the

that's correct. there is no reason to do this with the current driver.

>Also, I've read in numerous places that it's a really BAD idea to "bond"
>multiple sound cards together using one's .asoundrc file since they're
>not synchronized. Is that still the case if, say, I synced the word
>clock among multiple multifaces? Would anything change in the .asoundrc
>file?

this should work. jeremy hall has been doing this, and i believe that
with the recent changes (the ones causing the ALSA CVS current
problems i referred to above), it is now working for him.

--p


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com