Wireless Help

[Rick Stevens]

On Tue, 2005-12-27 at 10:47 -0800, Rick Stevens wrote:
> On Mon, 2005-12-26 at 12:11 -0700, brad.mugleston at comcast.net wrote: 
> > Merry Day after Christmas - hope everyone had a good holiday.
> > 
> > Now down to business - To catch everyone up.
> > 
> > Wanted to upgrade my notebook to FC4 from FC2.  The upgrade
> > didn't work so I formated and did a fresh install of FC4.
> > 
> > As it has a wireless card I needed to install NdisWrapper (or I
> > think I do) to get it running, note I did find a sys file on the
> > Linksys web site for this card and it said it was for FC3 - if
> > this would work without NdisWrapper can someone direct me as to
> > how to install it?
> > 
> > Back to NdisWrapper - it needs the source code for the current
> > kernel - in the past I've just downloaded it as an RPM and
> > followed the instructions.  This time strangeness happened.
> > 
> > The instructions say to link the source to the module directory
> > with the following command
> > 
> > ln -s /usr/src/linux-<kernel-version> /lib/modules/VERSION/build
> > 
> > I did that replacing "linux-<kernel-version>" and "VERSION"
> > with the proper (I believe) wording and got the error that the
> > link was already there. Asuming that it was from the source
> > install I tried to go on with the NdisWrapper install and got the
> > error that the link was to the wrong version (which looking at
> > it, it was - how that happened I have no idea).
> > 
> > I deleted the link and tried to redo it and get an error -
> > any suggestions on how to procede.  I'm thinking the instructions
> > are for an older version of FC.
> 
> Hi, Brad.
> 
> ndiswrapper uses the Windows drivers (the .inf and .sys files), so
> any reference to a ".sys" file that's appropriate for FC3 is kinda
> misleading--the .sys file is the Windows driver.
> 
> Now, as to kernel source code.  Make sure you do a "yum install
> kernel-devel".  This will install the kernel headers and such needed to
> build most drivers.  NOTE: This is NOT the kernel source code.  For
> that, you need to do a bit more (details later).

<el snippo!>

I've added a document that describes all the stuff I described in the
previous post to the RHIL website:

	http://www.rhil.net/docs/kernelbuild-26.html

Have a looksee if you wish.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-   Never test for an error condition you don't know how to handle.  -
----------------------------------------------------------------------