[PlanetCCRMA] Can't load HDSP firmware on F-17

Fernando Lopez-Lezcano nando at ccrma.Stanford.EDU
Sat Aug 25 22:29:04 PDT 2012


On 08/25/2012 07:30 PM, Janina Sajka wrote:
> Fernando Lopez-Lezcano writes:
>> Aha, you don't need to run hdsploader explicitly. The kernel will
>> trigger the firmware load so it is very likely that the card is
>> working. What do you see in the logs if you reload the module as
>> before. Or even better, remove the module, power cycle the multiface
>> box (so the firmware goes away), the load the module and see what
>> you get in /var/log/messages.
>
> I get a series of messages like the following:
>
> Aug 25 21:16:43 concerto pulseaudio[10080]: [pulseaudio] module.c:
> Failed to load module "module-alsa-card" (argument: "device_id="4"
> name="pci-0000_04_00.0" card_name="alsa_card.pci-0000_04_00.0"
> namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
> deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
> initialization failed.
> Aug 25 21:16:43 concerto pulseaudio[10080]: [pulseaudio]
> module-alsa-card.c: Failed to find a working profile.
> Aug 25 21:16:43 concerto pulseaudio[10080]: [pulseaudio] module.c:
> Failed to load module "module-alsa-card" (argument: "device_id="4"
> name="pci-0000_04_00.0" card_name="alsa_card.pci-0000_04_00.0"
> namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
> deferred_volume=yes card_properties="module-udev-detect.discovered=1""):
> initialization failed.
> Aug 25 21:16:43 concerto pulseaudio[10080]: [pulseaudio]
> module-udev-detect.c: Tried to configure
> /devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/sound/card4
> (alsa_card.pci-0000_04_00.0) more often than 5 times in 10s
>
> So, not sure how to interpret this. Of course, I don't want pulseaudio
> doing anything with my Multiface. Is it possible to restrict it by
> device? Or just by application a la pasuspender?

This is not (should not) be relevant to the hammerfall working. You 
should be seeing messages that deal with the snd_hdsp module loading and 
then the firmware loading (all automatic).

> I'm trying to figure out whether I can live with pulse. The
> Orca/Speech-Dispatcher/GNOME-Desktop environment claims to prefer pulse.
> meanwhile, my console TTS won't run with it.

Ah, sorry, I don't know much about those, I pretty much use only jack.

>And, I'm aiming at jackd
> for the Multiface, once I can play and record through it. Not sure how I
> should think about all of that, so any sage advice on this aspect also
> much appreciated.

What happens if you do:

jackd -d alsa -d hw:4

(assuming hw:4 is still the hammerfall).

-- Fernando



More information about the PlanetCCRMA mailing list