On Fri, 01 Feb 2008 03:30:12 -0500, Robert P. J. Day wrote: > On Fri, 1 Feb 2008, Mike -- EMAIL IGNORED wrote: > >> On Thu, 31 Jan 2008 22:58:07 -0200, Martin Marques wrote: >> >> > Mike -- EMAIL IGNORED escribió: >> >> >> >> So I did what it says, and: >> >> >> >> [root@mbrc15 driver]# which b43-fwcutter /usr/bin/b43-fwcutter >> >> [root@mbrc15 driver]# b43-fwcutter -v b43-fwcutter version 009 > > those first two commands don't seem to make much sense -- why would you > run the "which" command on b43-fwcutter only to have an extra argument > of the fully-qualified file name? i'm guessing you combined the which > command and its output on a single line, and that's really not a good > idea if you're trying to explain what you did. > > rday > -- [...] Yes, I see now that lines were inappropriately merged. I had: [root@mbrc15 driver]# which b43-fwcutter /usr/bin/b43-fwcutter [root@mbrc15 driver]# b43-fwcutter -v b43-fwcutter version 009 [root@mbrc15 driver]# b43-fwcutter -w /lib/firmware/ wl_apsta_mimo.o Sorry, the input file is either wrong or not supported by b43-fwcutter. This file has an unknown MD5sum cb8d70972b885b1f8883b943c0261a3c. [root@mbrc15 driver]# [root@mbrc15 driver]# pwd /root/broadcom/broadcom-wl-4.150.10.5/driver which I hope appears as 10 lines, as it did when I originally posted it. In any case, this is OBE, since I was using the wrong version. It is now working, but I am yet to try encryption. Mike.
