[sf-lug] Installing Void, C.E. Sign-in at SF-LUG mtg of 2017-11-05

[Ken Shaffer]

I've been waiting for the answer to Rick's critical question about seeing
if the firmware files are "not found" from the dmesg output.  The b43
driver should work with your chip, so all you should have to do is put the
firmware files into the right directory (usually /lib/firmware/b43, not
/usr/lib/firmware...).  Your chip, the 4315  used to have a special
fwcutter package with ...lpy... in its name -- don't know if the new
fwcutter package had made that unnecessary.  Any distribution which can run
the fwcutter will product the firmware files, so you can just put them on a
USB and bring them to your system.  I have even run fwcutter off a Windows
driver successfully, but a caution, fwcutter cannot handle every version of
the Windows driver.  The firmware output files look like :        18 May
20  2009 a0g0bsinitvals4.fw       158 May 20  2009 a0g0bsinitvals5.fw
   158 May 20  2009 a0g0bsinitvals9.fw      2680 May 20  2009
a0g0initvals4.fw      1840 May 20  2009 a0g0initvals5.fw
  2002 May 20  2009 a0g0initvals9.fw       158 May 20  2009
a0g1bsinitvals13.fw       158 May 20  2009 a0g1bsinitvals5.fw
   158 May 20  2009 a0g1bsinitvals9.fw      2080 May 20  2009
a0g1initvals13.fw      1840 May 20  2009 a0g1initvals5.fw
  2002 May 20  2009 a0g1initvals9.fw       158 May 20  2009
b0g0bsinitvals13.fw        18 May 20  2009 b0g0bsinitvals4.fw
   158 May 20  2009 b0g0bsinitvals5.fw       158 May 20  2009
b0g0bsinitvals9.fw      2080 May 20  2009 b0g0initvals13.fw
  2680 May 20  2009 b0g0initvals4.fw      1840 May 20  2009
b0g0initvals5.fw      2002 May 20  2009 b0g0initvals9.fw
   158 May 20  2009 lp0bsinitvals13.fw       158 May 20  2009
lp0bsinitvals14.fw       158 May 20  2009 lp0bsinitvals15.fw
  3618 May 20  2009 lp0initvals13.fw      2064 May 20  2009
lp0initvals14.fw      2052 May 20  2009 lp0initvals15.fw
   158 May 20  2009 n0absinitvals11.fw       158 May 20  2009
n0bsinitvals11.fw      2100 May 20  2009 n0initvals11.fw
  1320 May 20  2009 pcm4.fw      1320 May 20  2009 pcm5.fw     29864 May
20  2009 ucode11.fw
 32232 May 20  2009 ucode13.fw     31384 May 20  2009 ucode14.fw     30488
May 20  2009 ucode15.fw
 20176 May 20  2009 ucode4.fw     22384 May 20  2009 ucode5.fw     25160
May 20  2009 ucode9.fw

but a smaller subset may work.  The ...firmware /b43-open directory runs
with just three files:  158 Nov 17  2009 b0g0bsinitvals5.fw      976 Nov
17  2009 b0g0initvals5.fw
 9528 Nov 17  2009 ucode5.fw
The open firmware site, http://netweb.ing.unibs.it/~openfwwf/ , puts its
firmware there, which is a fallback if the .../b43 directory is absent.  I
have run with it, but I don't think your chip is supported.

Ken

On Wed, Nov 8, 2017 at 12:43 AM, Rick Moen <rick at linuxmafia.com> wrote:

> Quoting Todd Hawley (celticdm at gmail.com):
>
> > I'll try it too, once I figger out how to do that or pay someone to do it
> > for me. :)
>
> Open an access door or a case, getting access to the wireless card.
> (If it's unclear how to do this, use a search engine to search for
> information about your computer's make/model, and find out.)
>
> Now that you have the case open, remove the wireless card.  Note the
> size.  Look it up online, and determine what the form factor / size and
> the connector standard are.
>
> Then, order one of those, except better.
>
>
>
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/<br>
> Related Information <br>
> http://www.shallowsky.com/blog/<br>
> http://explainshell.com/ <br>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20171108/96776353/attachment.html>