Why does Alsa sometimes not find the HDSP 9652?
Wizard root # /etc/init.d/alsasound start
* Loading ALSA drivers...
* Loading: snd-seq-oss
* Loading: snd-pcm-oss
* Loading: snd-mixer-oss
* Loading: snd-via82xx
* Loading: snd-hdsp/lib/modules/2.4.20-gentoo-r9/kernel/sound/pci/rme9652/snd-hdsp.o:init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg/lib/modules/2.4.20-gentoo-r9/kernel/sound/pci/rme9652/snd-hdsp.o:
insmod /lib/m odules/2.4.20-gentoo-r9/kernel/sound/pci/rme9652/snd-hdsp.o failed /lib/modules/2.4.20-gentoo-r9/kernel/sound/pci/rme9652/snd-hdsp.o:
insmod snd-hd
sp failed
* Loading: snd-usb-audio
* Loading: snd-seq-oss
* Running card-dependent scripts
* Restoring Mixer
Levels [ ok ]
Wizard root # lspci
<SNIP>
00:0e.0 Multimedia audio controller: Xilinx Corporation RME Hammerfall DSP (rev 65)
<SNIP>
Wizard root #
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Quoted 6 lines · Mark Knecht
Wizard root #
/etc/init.d/alsasoundstart
* Loading ALSA drivers...
* Loading: snd-seq-oss
* Loading: snd-pcm-oss
* Loading: snd-mixer-oss
* Loading: snd-via82xx
Quoted 8 lines
* Loading: snd-hdsp
/lib/modules/2.4.20-gentoo-r9/kernel/sound/pci/rme9652/snd-hdsp.o:init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
You may indeed find more information in the syslog.
Probably the memory allocator has failed to load. You need to load it as early as possible after boot. Might be worth moving sound start to earlier in boot.
It might be something else, but without syslog cant help.
Justin
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Justin,
Hi. Thanks. syslog from that series of boots is attached.
Note the first boot, line 304 looks like this:
Dec 20 05:43:46 Wizard kernel: ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:807: wait for FIFO status <= 0 failed after 100 iterations Dec 20 05:43:46 Wizard kernel: RME Hammerfall-DSP: no cards found
but I didn't use sound that early in the morning, so I didn;t notice the problem. Later in the morning I finally started to kick off some work, but hdspmixer wouldn't load (line 382 or so...) and so I did a reboot. (line 414)
This time the lines above did not repeat and I get a better message:
(line 716)
Dec 20 08:22:48 Wizard kernel: ALSA
../../alsa-kernel/pci/rme9652/hdsp.c:5061: Firmware already loaded, initializing card.
If you wanted to look for other, similar, flaky aspects of Linux, my USB UPS does similar thins. Sometimes drivers load, sometimes I have to reboot to get them loaded. There is no pattern. This morning's cold boot worked jsut fine. I got both the HDSP and the UPS.
I'm not clear about how to mess with the memory allocator, but I'm not sure that's appropriate after viewing the attached file.
Thanks for your help!
Mark
Quoted 38 lines · Justin Cormack
Quoted 6 lines · Mark Knecht
Wizard root #
/etc/init.d/alsasoundstart
* Loading ALSA drivers...
* Loading: snd-seq-oss
* Loading: snd-pcm-oss
* Loading: snd-mixer-oss
* Loading: snd-via82xxQuoted 8 lines
* Loading: snd-hdsp
/lib/modules/2.4.20-gentoo-r9/kernel/sound/pci/rme9652/snd-hdsp.o:init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters, including inva
lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesgYou may indeed find more information in the syslog.
Probably the memory allocator has failed to load. You need to load it as early as possible after boot. Might be worth moving sound start to earlier in boot.
It might be something else, but without syslog cant help.
Justin
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Justin,
I'm running Alsa-1.0.0rc2. How much more up to date could I be?
Also, this is an HDSP 9652 which has the firmware on the board. Why
is a firmware loader required at all?
Possibly you're on to something I don't see yet? Maybe something is
left over from an older version and causing problems?
Let me know,
Mark
Quoted 11 lines · Justin Cormack
Quoted 9 lines · Mark Knecht
Justin,
Hi. Thanks. syslog from that series of boots is attached.Note the first boot, line 304 looks like this:
Dec 20 05:43:46 Wizard kernel: ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:807: wait for FIFO status <= 0 failed after 100 iterations Dec 20 05:43:46 Wizard kernel: RME Hammerfall-DSP: no cards found
Quoted 7 lines
ah. Update your alsa to the latest version. This is the old firmware loader bug. It is fixed now (but there is a seperate loader hdsploader that you have to run).
Justin
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Quoted 5 lines
Justin,
I'm running Alsa-1.0.0rc2. How much more up to date could I be?Also, this is an HDSP 9652 which has the firmware on the board. Why
is a firmware loader required at all?
its not. jaroslav used that phrase because the bug manifested itself most clearly when loading firmware. it was a bit more general than that however, since it affected interactions with the card in several places.
--p
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
Quoted 6 lines · Paul Davis
Quoted 5 lines
Justin,
I'm running Alsa-1.0.0rc2. How much more up to date could I be?Also, this is an HDSP 9652 which has the firmware on the board. Why
is a firmware loader required at all?
Quoted 6 lines
its not. jaroslav used that phrase because the bug manifested itself most clearly when loading firmware. it was a bit more general than that however, since it affected interactions with the card in several places.
--p
Paul,
Did I miss a response somehow? I haven't received anything on this
from Jaroslav.
Can you offer any insight into the root cause of this problem? Why
should lspci be able to see the card, but Alsa cannot start the driver? (going back tot he original post.)
Thanks,
Mark
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
RE: Why does Alsa sometimes not find the HDSP 9652? - SOLVED
In reply to Mark KnechtHi Justin,
It looks like I solved this problem in the last few days. The issue
appears to driven by how Alsa, or possibly the snd-hdsp driver specifically, attempts to discover the HDSP 9652, and the fact that my machine is moderately fast. I think this is a bug, or at least an opportunity to allow for some boot time tuning in Alsa somewhere, and I've reported it to Thomas privately.
On my machine, and Athlon XP 2600+, I use System Commander 7 to partition
the drives and to boot to DOS or Linux, and then grub to boot the Linux kernel I'm interested in. Currently SC7 has a timeout value of 20 seconds and grub has a time out value of 8 seconds.
What I've found is that if I boot the machine and do not speed up the
boot by hitting enter in either of these programs, then Alsa finds the HDSP 9652 100% of the time. However, if I boot but hit enter as early as possible in both programs then Alsa misses the HDSP 9652 100% of the time.
So, the answer is just giving the machine enough time before starting the
Alsa discovery processes.
Owing to my hardware background and use of FPGA's in other areas, the
Xilinx FPGA on the HDSP 9652 uses an outboard Flash chip to hold it's configuration code. (Sometimes called firmware here, but not really firmware.) This data is read out of the Flash chip in a fairly slow serial bitstream and takes some time. My suspicion is that by hitting the enter key twice I get to the Alsa boot stage too early, the configuration code is not loaded, and the driver cannot find the card even after 100 tries. If I don't hit enter, the configuration operation gets the extra 28 seconds and that is more than enough time to load the config code before the Alsa driver looks for the card.
I've never been comfortable with the message 'failed after 100
iterations'. To me this is not a good way to look for hardware since as machines speed up the amount of time you are giving gets shorter, so possibly Thomas will address this sometime in the future. Until then I'll just look for the smallest value I can make the boot time and still get the card to be recognized.
I hope this helps someone in the future not have this problem. Thanks for
your help.
Cheers,
Mark
Quoted 44 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Mark Knecht
Sent: Sunday, December 21, 2003 9:14 AM
To: Justin Cormack
Cc: Alsa-Devel
Subject: Re: [Alsa-devel] Why does Alsa sometimes not find the HDSP 9652?Justin,
I'm running Alsa-1.0.0rc2. How much more up to date could I be?Also, this is an HDSP 9652 which has the firmware on the board. Why
is a firmware loader required at all?Possibly you're on to something I don't see yet? Maybe something is
left over from an older version and causing problems?Let me know,
MarkQuoted 11 lines · Justin Cormack
Quoted 9 lines · Mark Knecht
Justin,
Hi. Thanks. syslog from that series of boots is attached.Note the first boot, line 304 looks like this:
Dec 20 05:43:46 Wizard kernel: ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:807: wait for FIFO status <= 0 failed after 100 iterations Dec 20 05:43:46 Wizard kernel: RME Hammerfall-DSP: no cards foundQuoted 7 lines
ah. Update your alsa to the latest version. This is the old firmware loader bug. It is fixed now (but there is a seperate loader hdsploader that you have to run).
Justin
Quoted 11 lines
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
RE: Why does Alsa sometimes not find the HDSP 9652? - SOLVED
Ah. that explains why I have never seen it - I always let my machines boot up from grub on the full timeout and most of them have pretty slow bootup processes. It is probably best to retry for 1 minute or so in module init to allow for very fast boots (after all the pci id has matched, so only broken hardware will never succeed).
Justin
Quoted 104 lines · Mark Knecht
Hi Justin,
It looks like I solved this problem in the last few days. The issue
appears to driven by how Alsa, or possibly the snd-hdsp driver specifically, attempts to discover the HDSP 9652, and the fact that my machine is moderately fast. I think this is a bug, or at least an opportunity to allow for some boot time tuning in Alsa somewhere, and I've reported it to Thomas privately.On my machine, and Athlon XP 2600+, I use System Commander 7 to partition
the drives and to boot to DOS or Linux, and then grub to boot the Linux kernel I'm interested in. Currently SC7 has a timeout value of 20 seconds and grub has a time out value of 8 seconds.What I've found is that if I boot the machine and do not speed up the
boot by hitting enter in either of these programs, then Alsa finds the HDSP 9652 100% of the time. However, if I boot but hit enter as early as possible in both programs then Alsa misses the HDSP 9652 100% of the time.So, the answer is just giving the machine enough time before starting the
Alsa discovery processes.Owing to my hardware background and use of FPGA's in other areas, the
Xilinx FPGA on the HDSP 9652 uses an outboard Flash chip to hold it's configuration code. (Sometimes called firmware here, but not really firmware.) This data is read out of the Flash chip in a fairly slow serial bitstream and takes some time. My suspicion is that by hitting the enter key twice I get to the Alsa boot stage too early, the configuration code is not loaded, and the driver cannot find the card even after 100 tries. If I don't hit enter, the configuration operation gets the extra 28 seconds and that is more than enough time to load the config code before the Alsa driver looks for the card.I've never been comfortable with the message 'failed after 100
iterations'. To me this is not a good way to look for hardware since as machines speed up the amount of time you are giving gets shorter, so possibly Thomas will address this sometime in the future. Until then I'll just look for the smallest value I can make the boot time and still get the card to be recognized.I hope this helps someone in the future not have this problem. Thanks for
your help.Cheers,
MarkQuoted 44 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Mark Knecht
Sent: Sunday, December 21, 2003 9:14 AM
To: Justin Cormack
Cc: Alsa-Devel
Subject: Re: [Alsa-devel] Why does Alsa sometimes not find the HDSP 9652?Justin,
I'm running Alsa-1.0.0rc2. How much more up to date could I be?Also, this is an HDSP 9652 which has the firmware on the board. Why
is a firmware loader required at all?Possibly you're on to something I don't see yet? Maybe something is
left over from an older version and causing problems?Let me know,
MarkQuoted 11 lines · Justin Cormack
Quoted 9 lines · Mark Knecht
Justin,
Hi. Thanks. syslog from that series of boots is attached.Note the first boot, line 304 looks like this:
Dec 20 05:43:46 Wizard kernel: ALSA ../../alsa-kernel/pci/rme9652/hdsp.c:807: wait for FIFO status <= 0 failed after 100 iterations Dec 20 05:43:46 Wizard kernel: RME Hammerfall-DSP: no cards foundQuoted 7 lines
ah. Update your alsa to the latest version. This is the old firmware loader bug. It is fixed now (but there is a seperate loader hdsploader that you have to run).
Justin
Quoted 11 lines
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Quoted 9 lines
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
RE: Why does Alsa sometimes not find the HDSP 9652? -SOLVED
Quoted 13 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Justin Cormack
Sent: Monday, December 29, 2003 10:50 AM
To: Mark Knecht
Cc: alsa list
Subject: RE: [Alsa-devel] Why does Alsa sometimes not find the HDSP 9652? -SOLVED
Quoted 8 lines
Ah. that explains why I have never seen it - I always let my machines boot up from grub on the full timeout and most of them have pretty slow bootup processes. It is probably best to retry for 1 minute or so in module init to allow for very fast boots (after all the pci id has matched, so only broken hardware will never succeed).
Justin
Sure. I was thinking that the snd-hdsp driver could also have a config option that specified how long I wanted it to wait and keep trying. If I set if for 30 seconds, then I don't need abnormally long timeouts in SC7 or grub, but if I forget and hit enter one morning early then the driver could just sit there and work for whatever amount of time I told it to.
Anyway, I think that a couple of other people have seen things like this before, so now I'll play a bit with minimum timeouts and probably end up with a reasonable boot time but still 100% functionality.
Now, if I could only get someone to pay attention to the new problems in the older Hammerfall 9636 driver...
Cheers,
Mark
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click