[PlanetCCRMA] Still stuck with Hammerfall HDSP.....

Ludo Max ludo.max@uconn.edu
Mon Dec 8 14:24:01 2003


> -----Original Message-----
> From: Fernando Pablo Lopez-Lezcano
> Sent: Thursday, December 04, 2003 1:49 PM
> Subject: Re: [PlanetCCRMA] Still stuck with Hammerfall HDSP.....
>
> > I installed kernel-2.4.23-1.ll.rh90.ccrma and the ALSA drivers
> > post 1.0.0rc1 [...]
> > I re-ran the alsaconf script and it automatically detected the
> > HDSP. I let it
> > modify the modules file and then deleted all lines with oss
> > from that file. Then I typed /etc/rc.d/init.d/alsasound start
> > and got a message that the alsa drivers were already running
> > BUT also an error...
> > ALSA driver already running
> > Starting sound driver snd-hdsp
> > /lib/modules/2.4.22-6.ll.rh90/kernel/sound/snd-hdsp.o: 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
> > init_module: No such device
> > /lib/modules/2.4.22-6.ll.rh90/kernel/sound/snd-hdsp.o: insmod
> > /lib/modules/2.4.22-6.ll.rh90/kernel/sound/snd-hdsp.o failed
> > /lib/modules/2.4.22-6.ll.rh90/kernel/sound/snd-hdsp.o: insmod
> > snd-hdsp failed
> >                                                            [FAILED]
>
> What happens if you do a "/etc/rc.d/init.d/alsasound stop" and then
> restart the driver? Does the driver get unloaded when you stop?


When I did that at the time, it did indicate that it was stopping the
driver. That was only once though. Now I am unable to replicate the "ALSA
driver already running" message. When I do a cold start and then do
/etc/rc.d/init.d/alsasound start, I am back to getting what I got before any
driver updates:

Starting sound driver snd-hdsp
/lib/modules/2.4.22-6.ll.rh90/kernel/sound/snd-hdsp.o: init_module: No such
device
/lib/modules/2.4.22-6.ll.rh90/kernel/sound/snd-hdsp.o: insmod
/lib/modules/2.4.22-6.ll.rh90/kernel/sound/snd-hdsp.o failed
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.22-6.ll.rh90/kernel/sound/snd-hdsp.o: insmod snd-hdsp
failed
                                                  [FAILED]

In other words, I get absolutely nothing (and therefore every day looks more
like the right time to give up quickly on the Linux experiment and stick
with Windows....)

During booting the text messages already indicated a failure related to the
sound. The text scrolls too quickly to read it but one can see that it says
to be looking for an RME Hammerfall but that no card is found

> Check
> the loaded modules at that point to see if there is anything else there
> that is sound related (/sbin/lsmod).

Here is what I get when doing /sbin/lsmod

[root@d68h203 lspmc]# /sbin/lsmod
Module                  Size  Used by    Not tainted
soundcore               6660   0  (autoclean)
i830                   75840  12
agpgart                51352  11  (autoclean)
parport_pc             19172   1  (autoclean)
lp                      9028   0  (autoclean)
parport                37792   1  (autoclean) [parport_pc lp]
autofs                 13620   0  (autoclean) (unused)
e100                   57988   1
ipt_REJECT              4344   6  (autoclean)
iptable_filter          2412   1  (autoclean)
ip_tables              15776   2  [ipt_REJECT iptable_filter]
sg                     37772   0  (autoclean)
sr_mod                 18168   4  (autoclean)
ide-scsi               12240   2
scsi_mod              109684   3  [sg sr_mod ide-scsi]
ide-cd                 36128   0
cdrom                  33984   0  [sr_mod ide-cd]
keybdev                 2976   0  (unused)
mousedev                5620   1
hid                    24708   0  (unused)
input                   5856   0  [keybdev mousedev hid]
usb-uhci               27372   0  (unused)
ehci-hcd               20840   0  (unused)
usbcore                80448   1  [hid usb-uhci ehci-hcd]
ext3                   73444   2
jbd                    54228   2  [ext3]


Anything suspicious, please let me know....
Any other suggestions, please let me know....
Any thoughts on other dumb things that I could be doing wrong, no matter how
simple?

Thanks in advance,

Ludo