From: frankgaetano@collegeclub.com
To: MarkKnecht <mknecht@controlnet.com>, frankgaetano@collegeclub.com
Cc: Alsa-Devel <Alsa-Devel@lists.sourceforge.net>
Subject: Re: RE: Hammerfall DSP System Problems
Date: Tue, 10 Jun 2003 13:50:07 -0400 (EDT) [thread overview]
Message-ID: <4732869.1055267407970.JavaMail.java@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 4727 bytes --]
I recompiled a new kernel 2.4.19 with the latency patch and preemptive
kernel patch. I still got the same unresolved symbol, so I loaded the
modules that it was giving errors for individually. Like this:
/sbin/modprobe snd-rawmidi
/sbin/modprobe snd-hammerfall-mem
/sbin/modprobe snd-hwdep
/sbin/modprobe snd-hdsp
After I issue the last command I get the following errors:
/lib/modules/2.4.19/kernel/sound/pci/rme9652/snd-hdsp.o: init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
I know that I have the latest firmware. However, I am using the
lastest version of ALSA 0.9.4 from the ftp site. I also tried the
lastest CVS and I get the same error. When I check the hdsp.c it has
the code for my firmware version 0x0b.
What is the status of this driver on the newest firmware? I am sorry
if I am asking questions that have already been answered.
I am okay with C programming if you need more help. The main thing is
I don't understand the status of the driver with the newest firmware
and what do I use the hdsploader for, or how. The documentation I have
found for the setup of this card doesn't mention this program.
Someone please help or direct me were I can get it.
Thanks,
Frank
Mark Knecht <mknecht@controlnet.com> wrote:
>Hi Frank,
>
> I'm an HDSP 9652 non-user for many of the same reasons. A couple of
>
>comments below.
>
>Mark
>
>
>>
>
>>
>
>> Hello,
>
>> I recently purchased a Hammerfall DSP system to use on Windows and
>
>> especially LINUX for use on Ardour. I have the multiface system. I
>
>> must say I am confused on the support of the newest version of this
>
>> pci card (I know that I have firmware version 11). I downloaded the
>
>> current CVS on alsa-dev and compiled it fine. However when I run
>
>> modprobe I get the following error:
>
>>
>
>> /sbin/modprobe snd-hdsp
>
>> /lib/modules/2.4.18-3/kernel/sound/pci/rme9652/snd-hdsp.o:
>
>> init_module: No such device
>
>
>[MWK] This is sometimes caused by a mismatch between between the
firmware
>
>revision in your card/box and those firmware revisions that the
driver knows
>
>about. Run lspci to see what your card has, and read through the
driver code
>
>to see what the driver knows about.
>
>
>NOTE TO DEVELOPERS - Can't you make this message "init_module: No
such
>
>device" more descriptive, such as "init_module: Checked for devices
with PCI
>
>Device ID's XXX, firmware revisions AA, BB, CC, DD & EE - No devices
found"?
>
>Many people, including me, don't know how to read source code and
can't give
>
>you as much direct information. Just a thought.
>
>
>
>
>> Hint: insmod errors can be caused by incorrect module parameters,
>
>> including invalid IO or IRQ parameters
>
>> /lib/modules/2.4.18-3/kernel/sound/pci/rme9652/snd-hdsp.o: insmod
>
>> /lib/modules/2.4.18-3/kernel/sound/pci/rme9652/snd-hdsp.o failed
>
>> /lib/modules/2.4.18-3/kernel/sound/pci/rme9652/snd-hdsp.o: insmod
>
>> snd-hdsp failed
>
>>
>
>> Then when I just offer the command insmod snd-hdsp I get the
>
>> following:
>
>>
>
>> /sbin/insmod snd-hdsp
>
>> Using /lib/modules/2.4.18-3/kernel/sound/pci/rme9652/snd-hdsp.o
>
>> /lib/modules/2.4.18-3/kernel/sound/pci/rme9652/snd-hdsp.o:
unresolved
>
>> symbol snd_hammerfall_get_buffer_R5bab1fdf
>
>> /lib/modules/2.4.18-3/kernel/sound/pci/rme9652/snd-hdsp.o:
unresolved
>
>> symbol snd_rawmidi_receive_R1e37534c
>
>
>[MWK] I have seen these sorts of errors when:
>
>
>1) The kernel source code that the driver was compiled against is not
the
>
>same as the kernel that's running. For instanace, you have a standard
>
>distribution kernel and a custom kernel from kernel.org. If you are
running
>
>the standard kernel, but the Alsa driver was compiled with
/usr/src/linux
>
>pointing at the custom kernel, then problems ensue.
>
>
>2) The C compiler used to compile Alsa does not match the compiler
used to
>
>compile the kernel.
>
>
><SNIP>
>
>>
>
>> When I run hdsploader it completes but says nothing like this:
>
>>
>
>> hdsploader - firmware loader for RME Hammerfall DSP cards
>
>> Looking for HDSP + Multiface or Digiface cards :
>
>>
>
>
>[MWK] Again, this strikes me that Alsa does not understand your
firmware
>
>revision since it isn't even finding a card.
>
>
>Good luck!!
>
>
>
>
>
--------------------------------------------------------------------------
Looking for a roommate? Let CollegeClub.com help you out!
<http://navisite.collegeclub.com/channels/college/>
CollegeClub.com makes college life even better.
next reply other threads:[~2003-06-10 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 17:50 frankgaetano [this message]
2003-06-10 18:06 ` RE: Hammerfall DSP System Problems Mark Knecht
2003-06-10 18:33 ` Paul Davis
2003-06-12 5:13 ` Jesse Chappell
2003-06-12 8:29 ` Jesse Chappell
2003-06-12 11:28 ` Jaakko Prättälä
[not found] ` <1055414777.1404.6.camel@tpdrh.niptron.com>
2003-06-22 14:57 ` Jesse Chappell
2003-06-22 19:36 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4732869.1055267407970.JavaMail.java@localhost \
--to=frankgaetano@collegeclub.com \
--cc=Alsa-Devel@lists.sourceforge.net \
--cc=mknecht@controlnet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.