On Fri, 2005-12-16 at 14:50 -0600, Matt Kleffner wrote: > I powered down and unplugged everything. After reconnecting everythingand turning the (desktop) computer on, the "Host Error" light on themultiface went out and the kernel log contained: > Hammerfall-DSP: wait for FIFO status <= 0 failed after 30 iterationsHammerfall-DSP: loading firmwareHammerfall-DSP: finished firmware loading > Now, when I run hdspconf and select any option (e.g. change samplingrate), I get an error for each option selected. For example, if Ichange the sampling rate to 44.1 kHz the radio button selection"jumps" back to 48 kHz. > The stdout of hdspconf looks like: > HDSPConf 1.4 - Copyright (C) 2003 Thomas Charbonnel <thomas@xxxxxxxxxx>This program comes WITH ABSOLUTELY NO WARRANTYHDSPConf is free software, see the file copying for details > Looking for HDSP cards :Card 0 : VIA 82C686A/B rev50 with ICE1232 at 0xa800, irq 9Card 1 : RME Hammerfall DSP + Multiface at 0xdd000000, irq 9Multiface found !1 Hammerfall DSP card found.Error accessing ctl interface on card hw:1Error accessing ctl interface on card hw:1Error accessing ctl interface on card hw:1 > The last message is repeated every time I attempt to change a setting,and it doesn't show up at all until I try to change a setting. If Iclose hdspconf and run > amixer -c 1 cset numid=11 2(syntax from http://www.linuxjournal.com/article/7024) > the correct (44.1 kHz) setting shows up when I reopen hdspconf.Changing the rate back to 48 kHz in hdspconf results in the sameerror, except the selection now remains fixed at 44.1 kHz. > Any thoughts on why this is happening? Is the version of HDSPConf too old? > - Matt > On 12/16/05, Paul Davis <paul@xxxxxxxxxxxxxxxxxxxxx> wrote:> try power-cycling *everything*. the computer, (including unplugging the> power cord (and battery if its a laptop), and the multiface box.>> i've run into this condition once or twice, and the only solution i have> found is a complete power cycle of everything.>>> --p i have a nasty feeling that ALSA 1.0.10 may have broken something here. this is the second report of this in a few weeks. i know its ugly and horrible and time consuming, but it would really help if you could back up to 1.0.9 and test that. --p
