[PlanetCCRMA] HDSP - alsaconf - yes - reboot - no

Mark Knecht markknecht@attbi.com
Sun Dec 8 08:33:02 2002


Fernando,
   I'm not making much headway yet with the HDSP card. It's very strange
to me:

1) I went through numerous cold and warm reboots as per your note just
to see if I could get it to wake up. No luck.

2) alsaconf seems to recognize the card, at least well enough to build
modules.conf. When it runs it says 

"hdsp    Xilinx, Inc. Unknown device 3fc5 (rev 64)"

I don't like the unknown device part, but the hdsp part looks right, and
the modules.conf entries look at least reasonable. I can send them if
you'd like to see them.

3) When I reboot, the output of dmesg doesn't look promising:

<SNIP>

Hammerfall memory 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
usb.c: deregistering driver snd-usb-midi
usb.c: deregistering driver snd-usb-audio
[root@Godzilla root]#
<SNIP>

4) /var/log/messages doesn't look any better:

Dec  8 08:10:43 Godzilla kernel: Hammerfall memory allocator: buffers
allocated for 1 cards
Dec  8 08:10:43 Godzilla kernel: RME Hammerfall-DSP: no cards found
Dec  8 08:10:43 Godzilla insmod:
/lib/modules/2.4.19-1.ll/kernel/drivers/sound/pci/rme9652/snd-hdsp.o:
init_module: No such device
Dec  8 08:10:43 Godzilla insmod: 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
Dec  8 08:10:43 Godzilla insmod:
/lib/modules/2.4.19-1.ll/kernel/drivers/sound/pci/rme9652/snd-hdsp.o:
insmod sound-slot-0 failed
Dec  8 08:10:43 Godzilla modprobe: modprobe: Can't locate module
sound-slot-1
Dec  8 08:10:43 Godzilla modprobe: modprobe: Can't locate module
sound-service-1-0
Dec  8 08:10:43 Godzilla modprobe: modprobe: Can't locate module
sound-slot-1
Dec  8 08:10:43 Godzilla modprobe: modprobe: Can't locate module
sound-service-1-0
Dec  8 08:10:44 Godzilla kernel: Hammerfall memory allocator: buffers
allocated for 1 cards
Dec  8 08:10:44 Godzilla kernel: RME Hammerfall-DSP: no cards found
Dec  8 08:10:44 Godzilla insmod:
/lib/modules/2.4.19-1.ll/kernel/drivers/sound/pci/rme9652/snd-hdsp.o:
init_module: No such device
Dec  8 08:10:44 Godzilla insmod: 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
Dec  8 08:10:44 Godzilla insmod:
/lib/modules/2.4.19-1.ll/kernel/drivers/sound/pci/rme9652/snd-hdsp.o:
insmod sound-slot-0 failed
Dec  8 08:10:46 Godzilla modprobe: modprobe: Can't locate module
block-major-22
Dec  8 08:10:47 Godzilla modprobe: modprobe: Can't locate module
block-major-22
Dec  8 08:10:50 Godzilla gnome-name-server[1329]: starting
Dec  8 08:10:50 Godzilla gnome-name-server[1329]: name server starting
Dec  8 08:11:40 Godzilla gconfd (mark-1412): starting (version 1.0.9),
pid 1412 user 'mark'
Dec  8 08:17:13 Godzilla su(pam_unix)[1443]: session opened for user
root by mark(uid=500)
Dec  8 08:17:17 Godzilla kernel: usb.c: deregistering driver
snd-usb-midi
Dec  8 08:17:17 Godzilla kernel: usb.c: deregistering driver
snd-usb-audio
Dec  8 08:17:17 Godzilla alsasound: sound driver stop succeeded



I'm a little lost right now as to what to try. Paul Davis said something
in a mail last week about the system possibly not recognizing a PCI
Device ID and we would add that in somewhere. Could that be happening
here?

The card is definitely installed. It works in Windows and shows up in
lspci, but I think maybe the system doesn't know this is the HDSP even
though alsaconf does?:

00:0f.0 Multimedia audio controller: Xilinx, Inc.: Unknown device 3fc5
(rev 64)
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at f6000000 (32-bit, non-prefetchable) [size=64K]

I know there's a file around somewhere that defines PCI device codes.
Maybe I need to find and edit that file? 

I'm going searching. Let me know if you have ideas.

Thanks,
Mark

<SNIP>
Beware, the driver is not the latest and I think there is a problem with
the card not working after the first cold boot. A second boot will fix
things. I think there is a fix in current cvs (and the next planet ccrma
driver rpms). 

-- Fernando
<SNIP>