On Apr 9, 2010, at 3:33 AM, Tom Chadwin wrote: > So, I think my last conclusion was in error. The box which has the firware > in /lib/firmware is the one which I manually added the firware to in 0.6.x. > Is it possible for it to have persisted across the 0.7 upgrade?
Tom, If you manually added the zaptel-fw-vpmadt032.bin to /lib/firmware then it would persist across versions since it resides on the unionfs overlay of the base image /lib/firmware directory. In this directory... http://downloads.digium.com/pub/telephony/firmware/releases/ There is a much newer version: http://downloads.digium.com/pub/telephony/firmware/releases/dahdi-fwload-vpmadt032-1.22.0.tar.gz It looks quite different from the .bin file, though... Tom, what does: $ lsmod | grep dahdi_vpmadt032_loader show? If nothing, perhaps "dahdi_vpmadt032_loader" should be added to DAHDIMODS ? Someone with more (any :-) ) experience using this card will have to chime in, I'm just guessing. I don't want Tom to do anything to keep his remote box from booting. Lonnie ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
