21 Sep
2003
21 Sep
'03
4:13 p.m.
Thanks for your suggestions...
When I run "alsaconf" it finds the HDSP just fine, but when it tries to bring up
the volume, I get this message:
Starting sound driver snd-hdsp 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: init_module: No such device
/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
[FAILED]
Starting sequencer [ OK ]
Restoring sound driver settings /usr/sbin/alsactl: load_state:1121: No soundcards
found...
[FAILED]
After that an lsmod shows no snd-hdsp. Any idea what could cause this or how to go about
solving it?
Thanks,
Matt Barber
21 Sep
21 Sep
4:27 p.m.
On Sun, 2003-09-21 at 10:58, BrbrOfSvl(a)aol.com wrote:
After that an lsmod shows no snd-hdsp. Any idea what could cause this or how to go about
solving it?
Thanks,
Matt Barber
This could be caused by the hdsp driver not recognizing the firmware
revision currently loaded in your hardware.
- Mark
4:27 p.m.
I had that problem. First, no devices were created. Remember to run
./snddevices from de alsa-driver??? dierctory.
Second, the driver that comes with Red Hat was installed. I had to
remove old modules.
Third: No sound server should be running..
I found some info here> http://www.rme-audio.com/english/linux/alsa.htm
GZS
BrbrOfSvl(a)aol.com wrote:
Thanks for your suggestions...
When I run "alsaconf" it finds the HDSP just fine, but when it tries to bring
up the volume, I get this message:
Starting sound driver snd-hdsp 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: init_module: No such device
/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
[FAILED]
Starting sequencer [ OK ]
Restoring sound driver settings /usr/sbin/alsactl: load_state:1121: No soundcards
found...
[FAILED]
After that an lsmod shows no snd-hdsp. Any idea what could cause this or how to go about
solving it?
Thanks,
Matt Barber
--
This Message is sent from my Red Hat 8.0 Linux server
Machine Registration number 205692 at http://counter.li.org/
.-. Gustavo Zamorano S.
.-. | Registered Linux user number 320898
.-. | | at http://counter.li.org/
4:32 p.m.
I also found some rme drivers.
Try ./configure --help | grep rme
They are:
rme32, rme96 amd rme9652.
I think rme9652 will work.
GZS
BrbrOfSvl(a)aol.com wrote:
Thanks for your suggestions...
When I run "alsaconf" it finds the HDSP just fine, but when it tries to bring
up the volume, I get this message:
Starting sound driver snd-hdsp 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: init_module: No such device
/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
[FAILED]
Starting sequencer [ OK ]
Restoring sound driver settings /usr/sbin/alsactl: load_state:1121: No soundcards
found...
[FAILED]
After that an lsmod shows no snd-hdsp. Any idea what could cause this or how to go about
solving it?
Thanks,
Matt Barber
--
This Message is sent from my Red Hat 8.0 Linux server
Machine Registration number 205692 at http://counter.li.org/
.-. Gustavo Zamorano S.
.-. | Registered Linux user number 320898
.-. | | at http://counter.li.org/
5:46 p.m.
--- "Gustavo Zamorano S." <gzsuniq(a)cableonda.net> wrote:
I also found some rme drivers.
Try ./configure --help | grep rme
They are:
rme32, rme96 amd rme9652.
I think rme9652 will work.
These are old, OSS. They did work with the 9652 at one time, nicely in
fact with a graphical panel for clock, etc :)
For now, though, I would work on updating alsa or solving the firmware
issue (downgrade?). I am building 0.9.6/cvs rpm's based on Fernando's
.spec today and will post a link and info if I get some time.
Kevin
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
5:52 p.m.
BrbrOfSvl(a)aol.com wrote:
Thanks for your suggestions...
When I run "alsaconf" it finds the HDSP just fine, but when it tries to bring
up the volume, I get this message:
Starting sound driver snd-hdsp 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: init_module: No such device
/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
[FAILED]
Starting sequencer [ OK ]
Restoring sound driver settings /usr/sbin/alsactl: load_state:1121: No soundcards
found...
[FAILED]
After that an lsmod shows no snd-hdsp. Any idea what could cause this or how to go about
solving it?
Thanks,
Matt Barber
Could you please send the output of the dmesg command ?
Thomas
7781
days inactive
7781
days old
linux-audio-user@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
BrbrOfSvl＠aol.com -
Gustavo Zamorano S. -
kevin ernste -
Mark Knecht -
Thomas Charbonnel