Neowin Forums > [HOW TO] Installing Wireless Networking

DjmUK

Mar 4 2005, 05:18

Introduction
I would like to thank Bliksem who helped getting me connected to the Internet.

This tutorial was written using Blkisem's help, and the help of google. This works with a variety of wireless cards, but for the sake of things I'm going to explain preciesly how I installed this using a Linksys WMP54G Wireless Network Card (V2). I know this looks like a long tutorial because it's as detailed as I can get it (because it's all extremely fresh in my mind).

My Relevant Specs & Info
- Fedora Core 3 (aka Red Hat 12)
- Kernel 2.6.10-1.760 (works with previous kernels, including *.770 and 2.6.11)
- Linksys WMP54G Wireless Network Card (Version 2)
- Username: djmuk (/home/djmuk/) <-- change this to your own login name where appropriate.

Step 1: Downloading & Saving
1.) Download ndiswrapper and the Linksys WinXP Drivers
2.) Do NOT extract anything at this point unless specified
3.) Save the ndiswrapper-[version_number].tar.gz file onto a Floppy, CD-R/RW or DVD+-R/RW (or other storage mediums)
3.) Open up the WinXP Driver's .zip file and save the 2 files (bcmwl5.sys & bcmwl5.inf) onto a Floppy, CD-R/RW or DVD+-R/RW (or other storage mediums)
4.) You should have 3 files on your Floppy, CD-R/RW or DVD+-R/RW (or other storage mediums) [ndiswrapper-1.0.tar.gz, bcmwl5.sys & bcmwl5.inf]

Step 2: Installation (Part 1/2)
1.) Extract the 3 files (ndiswrapper-[version_number].tar.gz, bcmwl5.sys and bcmwl5.inf) to /home/djmuk/
2.) Open up your terminal (Shortcut: F4 - if you're in the /home/djmuk/ folder)
3.) Type: su (super-user)
4.) Type your 'root account' password
5.) Type: tar -zxvf ndis (hit tab to auto-complete file name, and hit enter)
6.) Type: cd ndis (hit tab to auto-complete folder name, and hit enter)
7.) Type: make (hit enter)
8.) Type: make install

Step 3: Verification & Installation (Part 2/2)
1.) Type: ls -l /lib/modules/`uname -r`/misc/ (hit enter). This verifies the installation of the kernel module
2.) Type: whereis ndiswrapper loadndisdriver wlan_radio_averatec_5110hx (hit enter). This verifies the installation of user space utilities
3.) Type: /usr/sbin/ndiswrapper -i /home/djmuk/BCMWL5.INF (Case sensitive, if file: 'BCMWL5.INF' is in capitals in /home/djmuk/ then use capitals here)
4.) Type: ndiswrapper -l <-- That's the letter 'L' by the way (not the number one). This verifies the installation of the Windows driver
5.) Type: /sbin/modprobe ndiswrapper (hit enter)
6.) Type: ndiswrapper -m (hit enter)
7.) Type: /sbin/dhclient wlan0 (This activates the wireless connection - FINALLY!)

ALL DONE!

* There is no encryption being used at the moment. I haven't ventured that far yet

(but I will do when I get some sleep)

You should also note, that if you reboot your machine, you might notice there's no Internet connection.
To fix this, when you log in to the system, immediately open up the terminal and type the last command (Step 3: Part 7): (/sbin/dhclient wlan0). I'm sure there's a way to initiate this upon Start Up - but I'm still a n00b at Linux.

I hope this becomes useful for someone

markjensen

Mar 4 2005, 11:55

Excellent HOWTO on ndiswrapper!

We have been needing this for a while. Good work!

DjmUK

Mar 4 2005, 22:47

Enabling Encryption

Introduction
Alrighty then, Part 2 of this tutorial. The first part has no encryption (meaning, your Wireless Access Point has all security features disabled. Now it's time to enable them (after a few hours of research on google).

I'm going to write this tutorial based upon my own settings (feel free to change them).

My Relevant Specs & Info
- Fedora Core 3 (aka Red Hat 12)
- Kernel 2.6.10-1.760 (works with previous kernels, including *.770 and 2.6.11)
- Linksys WMP54G Wireless Network Card (Version 2)
- Linksys WAP54G Wireless-G Access Point (IP Address example used in browser: 192.168.2.2)

Step 1: Setup and Auto-Start on Reboot
1.) Copy & Paste the text below into a text editor (eg, "gedit"):

CODE

# NDIS Wrapper Configuration: Linksys WMP54G
DEVICE=wlan0
ONBOOT=yes
BOOTPROTO=dhcp
TYPE=Wireless
MODE=Managed
SSID="DjmUK_54G"
CHANNEL=11
USERCTL=yes
PEERDNS=no
KEY=xxxxxxxxx
RATE=Auto
NICK=wlan0

2.) Save the file to: /etc/sysconfig/network-scripts/ with the filename: ifcfg-wlan0.

Step 2: Editing File: ifcfg-wlan0
1.) Editing the file. Firstly open up your Access Point into a browser http://192.168.2.2 (I used my WinXP box to do this). The important settings to change (just copy the settings you see in your browser):

- SSID="DjmUK_54G"
This is the name of your wireless network which MUST match your Access Points SSID

- CHANNEL=11
Depends on your location, I use 11 because I'm in Europe

- KEY=XXXXXXXXXX
Take a look at your 'Security Settings', I'm using a 'Security Mode of WEP @ 64-bits / 10 hex digits' (because 128-bit slows down the network). Type in your key here, NOT the passphrase! the generated key. I had four to choose from, so I made sure I was broadcasting the chosen key

- RATE=Auto
You can change this to your actual bandwidth (eg, 54G), but auto is the easiest method that works just fine with me

Step 3: Network Settings and Network Restart
1.) In Fedora, go to "Start > System Settings > Network", and in the DNS Tab:

- Hostname: localhost Unless you're a web server
- Primary DNS: 192.168.1.1 Your Gateway address (your Access Point via a browser will tell you this)
- Secondary DNS:
- Tertiary DNS:
- DNS Search Path:

* I left some fields blank above because I'm not running a web server so I don't need to worry about those.

2.) Restart your network, and you have two options to do this.
-- In 'Terminal' you can type: service network restart
-- Network Configuration (Decativate device, Activate device).

3.) Now test it all. Load up any web page

ALL DONE!

The above works for me, so hopefully it will work for someone else out there and hopefully with little to no modifications.

DjmUK

Mar 5 2005, 01:09

Kernel Updates Broke My Network Connections

Introduction
Okay, this is my last article on this subject (all this Linux is a nice learning curve, and I'm still learning).

Basically, I just upgraded my kernel (via yums rpm):
From: 2.6.10-1.760
To: 2.6.10-1.770

However, on reboot the Internet was broken. But don't worry, you don't need to go through all these steps again because the hardware is installed and configured correctly.

My Relevant Specs & Info
- Fedora Core 3 (aka Red Hat 12)
- Kernel 2.6.10-1.770 <-- NEW VERSION BABY!
- Linksys WMP54G Wireless Network Card (Version 2)
- Linksys WAP54G Wireless-G Access Point

Step 1: Why Is It Broken?
1.) Because that ndiswrapper module you compiled and installed was for the previous kernel, so you're gonna' have to recompile a new one - and that's all there is to it.
2.) "Step 2: Installation (Part 1/2)" needs to be followed - but not in so much detail, so here goes.

Step 2: Recompiling
Let's say you've kept the ndiswrapper folder in your user space /home/djmuk/ (if not, then go sort it out by un-tar'ing it etc.)

01.) Load up the terminal
02.) Type: su
03.) Type: cd /home/djmuk/ndiswrapper-1.0/ Or wherever you've un-tar'ed the ndiswraper module
04.) Type: make
05.) Type: make install
06.) Type: ndiswrapper -l Note the name of the driver (in my case 'bcmwl5')
07.) Type: ndiswrapper -e bcmwl5 This removes that driver (so watch your spelling)
08.) Type: /usr/sbin/ndiswrapper -i /home/djmuk/BCMWL5.INF reinstalls the driver
09.) Type: ndiswrapper -l Verification
10.) Type: /sbin/modprobe ndiswrapper
11.) Type: ndiswrapper -m
12.) Type: /sbin/dhclient wlan0
13.) Type: service network restart

ALL DONE!

There we go, just a simple case of recompiling the ndiswrapper module for your new kernel, and reinstalling the module. All your previous settings and configurations (including encryption) are still intact.

tsukikage

Mar 19 2005, 07:00

I would like to offer another alternative to using ndiswrapper, called madwifi. I find it is much faster and more convenient especially when theres security keys involved.
It *should* work on any card that uses an atheros chipset.
This worked for me on fedora core 3 770 with a WPC55AG card:

1. get the madwifi drivers and libradies:
http://dl.atrpms.net/production/packages/f...fc3.at.i686.rpm
http://download.atrpms.net/production/pack...fc3.at.i386.rpm

2. install the rpms:
at terminal:
cd /download_location/
su
rpm -i madwifi-kmdl-2.6.10-1.770_FC3-0.9.4.12-15.rhfc3.at.i686.rpm
rpm -i madwifi-0.9.4.12-15.rhfc3.at.i386.rpm
cd /sbin
./modprobe ath_pci

3. configure your card the way you want it:
most configurations can use the built-in network config utility:
-open it up, and click to create a new device config.
-select you options for ip, dhcp, etc
-select "managed" mode
-select any othe config you need, like WEP key, if you use one.
-save
-restart "network" from applications>system settings>server settings>services

if you use a WEP key in an open system, i have found that the built in configurator has problems since it specifies "restricted" as the authentication mode, so you can do this:
-go to a terminal:
su
cd /sbin
./ifconfig ath0 up
./iwconfig ath0 key open [1] 7E0355BA7E
./dhclient ath0

you can stick all this stuff in a script or something if you want.

This config gives me fast authentication and good speed (it correctly uses 54Mb/s when available)

msg43

Mar 23 2005, 00:45

Here is a nice guide on how to get ndiswrapper working with *all* linux distros \
You must have the wireless tools installed
1: extract tar (kernel 2.4.* or lower needs ndiswrapper .12)
2: cd /path/to/ndiswrapper/source
3: make
4: su
5. make install
6. modprobe nidwrapper
7. ndiswrapper -i /path/to/win/driver
8. ndiswrapper -l [check that hardware is present]
9. iwconfig (make sure you see the card)
10. ndiswrapper -m
11. iwlist wlan0 scan (shows wireless networks (essid))
12. iwconfig wlan0 mode [network mode usually] managed
13. Then run dhcpcd wlan0
key [encription key] 48143525698
essid [network name] DLink
so you might have
iwconfig wlan0 mode managed
iwconfig wlan0 key 4812534656
iwconfig wlan0 essid DLink

How to get ndiswrapper working on startup:
There are many ways but theres nothing that exact. Different Distros have their way, but you can make a script in /etc/rc.d/rc.wlan0 and then have a some file call it
My /etc/rc.d/wlan0 looks like

CODE

#!/bin/sh
#/etc/rc.d/wlan0
echo "Starting Wireless Networking....."
modprobe ndiswrapper
sleep 1
iwconfig wlan0 mode Managed
iwconfig wlan0 essid DLink
sleep 1
dhcpcd wlan0
echo "Wireless Networking Started!"

At this time I'm working on remaking my script work better like to search for a network before it sets the essid etc...

Hope you found this useful

DjmUK

Mar 23 2005, 03:13

Didn't I already do this

Slightly more detailed and specifically for FC3, but reports show that it works on a lot of distros out there:
[HOW TO] Fedora 3: Installing Wireless Networking

Well, we now have two tutorials - if one doesn't work then the other's bound to

msg43

Mar 23 2005, 03:33

QUOTE(DjmUK @ Mar 22 2005, 22:13)

Didn't I already do this

Slightly more detailed and specifically for FC3, but reports show that it works on a lot of distros out there:
[HOW TO] Fedora 3: Installing Wireless Networking

Well, we now have two tutorials - if one doesn't work then the other's bound to

[right][snapback]585656664[/snapback][/right]

Well kinda mine short a sweet
and it tells how to load the connection at startup using a script important to gentoo, slack, arch, maybe debian

markjensen

Mar 23 2005, 14:21

Both of those procedures could be useful, and since they augment and compliment each other, let me merge them into one larger thread for people to go to when they are looking for a guide.

DjmUK

Mar 24 2005, 02:35

Good idea markjensen, 3 ways of installing wireless networking - so now there can be no problems at all, because everyone can be satisfied

rezza

Mar 24 2005, 15:38

This thread is awesome. Time to start pointing people who ask me about this on IRC and IM to it!

Great work all who wrote guides

RickSolie

Mar 26 2005, 21:02

This method works with Mandrake 10.1 (after the usual false starts and dinking around). Step 7 isn't applicable (command not available), but the Mandrake configuration utility allows you to configure and start the network connection. Thanks very much!

Hurmoth

Mar 28 2005, 21:16

Awesome guide... very easy reading and gets my wireless card working in no time

hornett

Mar 29 2005, 10:40

Thanks for the guides! Neowin's Linux forums are getting to be a great source of Linux information.

Keep up the good work

wicker_man

Mar 29 2005, 11:02

Nice guide, thanks a lot. Shame though we have to go through all this - a regular user won't be able to handle that

DjmUK

Mar 29 2005, 13:15

QUOTE(wicker_man @ Mar 29 2005, 11:02)

Nice guide, thanks a lot. Shame though we have to go through all this - a regular user won't be able to handle that

[right][snapback]585689939[/snapback][/right]

Well it's all about the 1st, 5th & 6th posts. The 2nd & 3rd are optional extras. Just follow either #1, #5 or #6 and that's all you'll need to get online (as long as basic security isn't an issue).

Jayzee

Mar 29 2005, 13:18

What about WPA encryption settings!? This guide bases on WEP encryption, which anybody can crack within 5 hours..

kjordan2001

Mar 29 2005, 13:40

QUOTE(Jayzee @ Mar 29 2005, 07:18)

What about WPA encryption settings!? This guide bases on WEP encryption, which anybody can crack within 5 hours..

[right][snapback]585690394[/snapback][/right]

Some drivers are supported by wpa-supplicant, which is configured through a separate config file.

DjmUK

Mar 29 2005, 15:40

QUOTE(Jayzee @ Mar 29 2005, 13:18)

What about WPA encryption settings!? This guide bases on WEP encryption, which anybody can crack within 5 hours..

[right][snapback]585690394[/snapback][/right]

WPA - hmm, never looked into that. I've always gone with WEP (because I know how to), but I'll have to look into WPA encryption sometime, once I've researched into 'which is more secure'.

GreenLemon

Apr 1 2005, 05:08

QUOTE(tsukikage @ Mar 19 2005, 02:00)

I would like to offer another alternative to using ndiswrapper, called madwifi. I find it is much faster and more convenient especially when theres security keys involved.
It *should* work on any card that uses an atheros chipset.
This worked for me on fedora core 3 770 with a WPC55AG card:

1. get the madwifi drivers and libradies:
http://dl.atrpms.net/production/packages/f...fc3.at.i686.rpm
http://download.atrpms.net/production/pack...fc3.at.i386.rpm

2. install the rpms:
at terminal:
cd /download_location/
su
rpm -i madwifi-kmdl-2.6.10-1.770_FC3-0.9.4.12-15.rhfc3.at.i686.rpm
rpm -i madwifi-0.9.4.12-15.rhfc3.at.i386.rpm
cd /sbin
./modprobe ath_pci

3. configure your card the way you want it:
most configurations can use the built-in network config utility:
-open it up, and click to create a new device config.
-select you options for ip, dhcp, etc
-select "managed" mode
-select any othe config you need, like WEP key, if you use one.
-save
-restart "network" from applications>system settings>server settings>services

if you use a WEP key in an open system, i have found that the built in configurator has problems since it specifies "restricted" as the authentication mode, so you can do this:
-go to a terminal:
su
cd /sbin
./ifconfig ath0 up
./iwconfig ath0 key open [1] 7E0355BA7E
./dhclient ath0

you can stick all this stuff in a script or something if you want.

This config gives me fast authentication and good speed (it correctly uses 54Mb/s when available)
[right][snapback]585637315[/snapback][/right]

Thank you so much for this. This made my wireless work flawlessly on my Toshiba laptop! GREAT JOB!

MulletRobZ

Apr 27 2005, 23:36

Thanks for the heads up. I'll give it a shot once I get the wireless networking card.

Rob2687

May 20 2005, 23:25

One thing that ive never figured out ( until recently )how to get working was WPA Supplicant with NDIS Wrapper to load automatically on boot.

Open up the interfaces file in

CODE

/etc/network/interfaces

Make sure you have these lines in there

CODE

auto wlan0
iface wlan0 inet dhcp
pre-up /usr/sbin/wpa_supplicant -Bw -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant.conf
post-down killall -q wpa_supplicant

Just thought I'd add that, would have made my life soo much freaking easier if I knew how to set that up from the start.

MulletRobZ

Jun 24 2005, 21:19

I think I figured out how to get my WLAN working, but not set for automatic startup and was setup with the native drivers instead of ndiswrapper. I noted that quite a few WLAN cards include the Linux drivers, but arc4 and/or crc32 are required. Those crypto modules can be found in /lib/modules/(your kernel version)/kernel/crypto. But if only I could find out how to get it to work for automatic startup and find a GUI WLAN monitor, I'd be all set and then, I'd be able to post a HOWTO on that.

dave164

Jun 27 2005, 01:47

Thanks alot

DKY

Jun 27 2005, 23:59

DjmUK:

I'm having a problem with Part 7 on Step 2 of the first post of this topic. I'm extremely new to Linux and have Fedora Core 4. I'm trying to get my Linux card to work on this thing. I do an lspci and come up with the following (just for the sake of having posted as much info as possible)

QUOTE

00:0a.0 Network controller: Broadcom Corporation BCM4306 802.11 b/g Wireless LAN Controller (rev03)

So I go to do this install on my nix box and get to this part

QUOTE

[root@localhost ndiswrapper-1.2]#

and type in the word 'make' to get something along the following output (I had to write it down seeing as how I have no net connection).

QUOTE

make -C driver
make [1]: Entering directory /root/Desktop/ndiswrapper-1.2/driver'
Can't find kernel sources in /lib/modules/2.6.11-1.1369_FC4/build;
give the path to kernel sources with KSRC=<path> argument to make
make[1]: *** [prereq_check] Error 1
make[1]: Leaving directory '/root/Desktop/ndiswrapper-1.2/driver'
make: ***[all]Error 2
[root@localhost ndiswrapper-1.2]#

Someone please tell me what this means? Why am I getting an error?

kjordan2001

Jun 28 2005, 08:47

QUOTE(DKY @ Jun 27 2005, 17:59)

DjmUK:

I'm having a problem with Part 7 on Step 2 of the first post of this topic. I'm extremely new to Linux and have Fedora Core 4. I'm trying to get my Linux card to work on this thing. I do an lspci and come up with the following (just for the sake of having posted as much info as possible)
So I go to do this install on my nix box and get to this part
and type in the word 'make' to get something along the following output (I had to write it down seeing as how I have no net connection).
Someone please tell me what this means? Why am I getting an error?
[right][snapback]586129713[/snapback][/right]

You need to install the sources for your kernel.

DKY

Jun 28 2005, 09:50

Okay I'm happy I got an answer. What does that mean? where do I find the sources for my kernel? I beleive I can find out what kernel I'm running by going to the /lib/Modules/ and looking at the name of that directory, right? but what are the sources?

DKY

Jun 29 2005, 23:47

Anyone?..... Please?.....

markjensen

Jun 30 2005, 00:26

I think you should be able to install the sources via yum, but there are too many hits for me to track down the one(s) that may help. None of the titles jumped out at me as being "the answer".
http://www.google.com/linux?q=fedora+4+ins...nel+sources+yum

DKY

Jun 30 2005, 22:00

Okay, I'm familiar with Windoze but not Linux. What's a source? My kernel is something like my version, right? 2.6.11-1.1369_FC4?? So, in essence I have to install a "source" for 2.6.11-1.1369_FC4, but I can't figure out what a source is or where to get it. So far all I've got is this
Source - The code that makes a program work.
But what that is saying to me is that there must be different versions of ndiswrapper and I picked the wrong one????

......PLEASE FORGIVE ME FOR BEING SO IGNORANT ABOUT THIS SUBJECT I APPOLOGIZE.....

Also, what is yum, I haven't quite googled that question yet but I've been googling the source question for a few days now to no avail.

markjensen

Jul 1 2005, 11:02

Yes, source is the code that was written to create the program (in this case, the kernel). It is written in human-readable form (generally in C), but is not machine-executable until it is compiled into 'binary' code (like a Windows .exe). And you are right in needing to download the source that matches your current kernel version. You are understanding it fine, so far.

As far as "yum" goes, it is an application that manages all of your installed packages (including the kernel). You can type "yum install celestia", and yum will search for, and install, the space simulator "Celestia". You type "yum update", and yum will check for newer versions of everything that you have on your computer. To find out more, you type "man yum" to read the 'manual' for 'yum'.

DKY

Jul 1 2005, 11:23

So, is it possible that they haven't released the proper ndiswrapper source for my FC4? Should I erase the drive and install FC3? Maybe I'd have an easier time?

markjensen

Jul 1 2005, 11:36

No... You don't need the NDISWrapper source. You need to find the kernel source, so that NDISWrapper can use it to compile what it needs to.

DKY

Jul 1 2005, 12:10

and I get that from linux themselves or do I get that on one of my four discs that I burned.

markjensen

Jul 1 2005, 12:09

Ok, did a bit of hunting, and here is what I have found:

Procedure that may be helpful: http://fedoraforum.org/forum/showthread.php?t=29434
(you probably won't want/need to rebuild your whole kernel, but the first part will install it for you) EDIT: I think that all you will want to di is the single "rpm" command as step #2.

Where your "source RPM" is located: http://download.fedora.redhat.com/pub/fedo...x/core/4/SRPMS/
Look for "kernel-2.6.11-1.1369_FC4.src.rpm"

That should get what you are needing.

DKY

Jul 1 2005, 17:24

Okay, an update: I followed your link (thank you so much for the direction, some people need their hands held) installed the src (I only used the first command '$ rpm -ivh kernel-2.6.9-1.1021_FC4.src.rpm' I don't know if I should have done the rest of it, from your post earlier it didn't seem like it.) but I was getting nokey errors. So I stumbled upon something online saying that I need to do a 'yum install kernel-devel' in order to not get a nokey error. It worked and then the src installed fine (I think) and now I'm at the ndiswrapper install at the beginning of this post again. I get to the make part and see a bunch of errors. Did I mess something up?

QUOTE

[root@localhost ndiswrapper-1.2]# make
make -C driver
make[1]: Entering directory `/home/tv/ndiswrapper-1.2/driver'
make -C /lib/modules/2.6.11-1.1369_FC4/build SUBDIRS=/home/tv/ndiswrapper-1.2/driver \
NDISWRAPPER_VERSION=1.2 \
EXTRA_VERSION= modules
/usr/src/kernels/2.6.11-1.1369_FC4-i686/scripts/gcc-version.sh: line 11: gcc: command not found
/usr/src/kernels/2.6.11-1.1369_FC4-i686/scripts/gcc-version.sh: line 12: gcc: command not found
make[2]: gcc: Command not found
make[2]: Entering directory `/usr/src/kernels/2.6.11-1.1369_FC4-i686'
CC [M] /home/tv/ndiswrapper-1.2/driver/hal.o
/bin/sh: gcc: command not found
make[3]: *** [/home/tv/ndiswrapper-1.2/driver/hal.o] Error 127
make[2]: *** [_module_/home/tv/ndiswrapper-1.2/driver] Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.11-1.1369_FC4-i686'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/tv/ndiswrapper-1.2/driver'
make: *** [all] Error 2

markjensen

Jul 1 2005, 17:38

Can you type the output of gcc -v here?

I am thinking that you don't have a compiler installed...

DKY

Jul 1 2005, 17:45

Like this?

QUOTE

[root@localhost ndiswrapper-1.2]# gcc -v
bash: gcc: command not found
[root@localhost ndiswrapper-1.2]#

markjensen

Jul 1 2005, 18:31

Yup. No compiler.

yum install gcc
I think that will be all you need. I hope so...

Blik

Jul 1 2005, 18:34

Errrrrr, doesnt yum install linux-source simply work?

edit: nevermind, i see you have the source installed now... But for future reference thats how you install your kernel source, you have a package manager, USE IT... although you were advised not to for some reason...

DKY

Jul 1 2005, 21:51

SWEET!!! now I have the compiler installed and started to do the make. I got to I think its number 4 on part 5 and realized that it says that my driver is an invalid driver and that kinda worries me. One more thing is that in the instructions it says to use all caps when pointing at the .inf file. Problem is, mine's not in all caps for some strange reason. Here's my histor below

QUOTE

[root@localhost ndiswrapper-1.2]# make
make -C driver
make[1]: Entering directory `/home/tv/ndiswrapper-1.2/driver'
make -C /lib/modules/2.6.11-1.1369_FC4/build SUBDIRS=/home/tv/ndiswrapper-1.2/driver \
NDISWRAPPER_VERSION=1.2 \
EXTRA_VERSION= modules
make[2]: Entering directory `/usr/src/kernels/2.6.11-1.1369_FC4-i686'
CC [M] /home/tv/ndiswrapper-1.2/driver/hal.o
CC [M] /home/tv/ndiswrapper-1.2/driver/iw_ndis.o
CC [M] /home/tv/ndiswrapper-1.2/driver/loader.o
/home/tv/ndiswrapper-1.2/driver/loader.c: In function ‘ndiswrapper_add_pci_device’:
/home/tv/ndiswrapper-1.2/driver/loader.c:202: warning: ignoring return value of ‘pci_set_power_state’, declared with attribute warn_unused_result
CC [M] /home/tv/ndiswrapper-1.2/driver/misc_funcs.o
CC [M] /home/tv/ndiswrapper-1.2/driver/ndis.o
CC [M] /home/tv/ndiswrapper-1.2/driver/ntoskernel.o
CC [M] /home/tv/ndiswrapper-1.2/driver/pe_linker.o
CC [M] /home/tv/ndiswrapper-1.2/driver/proc.o
CC [M] /home/tv/ndiswrapper-1.2/driver/wrapper.o
/home/tv/ndiswrapper-1.2/driver/wrapper.c: In function ‘miniport_halt’:
/home/tv/ndiswrapper-1.2/driver/wrapper.c:293: warning: ignoring return value of ‘pci_set_power_state’, declared with attribute warn_unused_result
/home/tv/ndiswrapper-1.2/driver/wrapper.c: In function ‘ndiswrapper_suspend_pci’:
/home/tv/ndiswrapper-1.2/driver/wrapper.c:737: warning: ignoring return value of ‘pci_set_power_state’, declared with attribute warn_unused_result
/home/tv/ndiswrapper-1.2/driver/wrapper.c: In function ‘ndiswrapper_resume_pci’:/home/tv/ndiswrapper-1.2/driver/wrapper.c:759: warning: ignoring return value of ‘pci_enable_device’, declared with attribute warn_unused_result
CC [M] /home/tv/ndiswrapper-1.2/driver/usb.o
CC [M] /home/tv/ndiswrapper-1.2/driver/divdi3.o
LD [M] /home/tv/ndiswrapper-1.2/driver/ndiswrapper.o
Building modules, stage 2.
MODPOST
CC /home/tv/ndiswrapper-1.2/driver/ndiswrapper.mod.o
LD [M] /home/tv/ndiswrapper-1.2/driver/ndiswrapper.ko
make[2]: Leaving directory `/usr/src/kernels/2.6.11-1.1369_FC4-i686'

*** WARNING: Kernel is compiled with 4K stack size option (CONFIG_4KSTACKS); many Windows drivers will not work with this option enabled. Disable CONFIG_4KSTACKS option, recompile and install kernel

make[1]: Leaving directory `/home/tv/ndiswrapper-1.2/driver'
make -C utils
make[1]: Entering directory `/home/tv/ndiswrapper-1.2/utils'
cc -Wall -g -DNDISWRAPPER_VERSION=\"1.2\" -c -o loadndisdriver.o loadndisdriver.c
gcc -o loadndisdriver loadndisdriver.o
make[1]: Leaving directory `/home/tv/ndiswrapper-1.2/utils'
[root@localhost ndiswrapper-1.2]# make install
make -C driver install
make[1]: Entering directory `/home/tv/ndiswrapper-1.2/driver'
make -C /lib/modules/2.6.11-1.1369_FC4/build SUBDIRS=/home/tv/ndiswrapper-1.2/driver \
NDISWRAPPER_VERSION=1.2 \
EXTRA_VERSION= modules
make[2]: Entering directory `/usr/src/kernels/2.6.11-1.1369_FC4-i686'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/kernels/2.6.11-1.1369_FC4-i686'

*** WARNING: Kernel is compiled with 4K stack size option (CONFIG_4KSTACKS); many Windows drivers will not work with this option enabled. Disable CONFIG_4KSTACKS option, recompile and install kernel

mkdir -p /lib/modules/2.6.11-1.1369_FC4/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.11-1.1369_FC4/misc
/sbin/depmod -a
make[1]: Leaving directory `/home/tv/ndiswrapper-1.2/driver'
make -C utils install
make[1]: Entering directory `/home/tv/ndiswrapper-1.2/utils'
install -D -m 755 loadndisdriver /sbin/loadndisdriver
install -D -m 755 ndiswrapper /usr/sbin/ndiswrapper
install -D -m 755 ndiswrapper-buginfo /usr/sbin/ndiswrapper-buginfo

NOTE: Windows driver configuration file format has changed since 1.0-rc2. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/home/tv/ndiswrapper-1.2/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
[root@localhost ndiswrapper-1.2]# ls -l /lib/modules/`uname -r`/misc/
total 1640
-rw-r--r-- 1 root root 1667592 Jul 1 16:50 ndiswrapper.ko
[root@localhost ndiswrapper-1.2]# whereis ndiswrapper loadndisdriver wlan_radio_averatec_5110hx
ndiswrapper: /usr/sbin/ndiswrapper /usr/share/man/man8/ndiswrapper.8
loadndisdriver: /sbin/loadndisdriver
wlan_radio_averatec_5110hx:
[root@localhost ndiswrapper-1.2]# /usr/sbin/ndiswrapper -i /home/tv/BCMWL5.INF
Installing bcmwl5
cp: cannot stat `/home/tv/BCMWL5.INF': No such file or directory
[root@localhost ndiswrapper-1.2]# /usr/sbin/ndiswrapper -i /home/tv/bcmwl5.inf
bcmwl5 is already installed. Use -e to remove it
[root@localhost ndiswrapper-1.2]# ndiswrapper -l
Installed ndis drivers:
bcmwl5 invalid driver!
[root@localhost ndiswrapper-1.2]#

DKY

Jul 2 2005, 02:21

nevermind, I figured it out. Apparently I must have typed it wrong. I removed it and then re-installed it by typing the letter 'b' and then hitting tab and typing '.inf' after it.

Xantus

Jul 23 2005, 19:52

hello i have a little trouble installing my USB wlan card with ndiswrapper 1.2 I have read about others using this usb device with ndiswrapper so it should work, but it doesn't. I have completed all steps from post #1 and #3 with out errors but when i try to reactivate the network with

QUOTE

service network restart

i get

QUOTE

determining IP address for wlan0: Failed no link present. Check cable? [FAILED]

what could be the problem? All lights are on and it starts blinking when trying to get an IP (which according to the book means that it has a valid connection and is sending/receiving data)

Quillz

Jul 29 2005, 22:50

Will this tutorial work with the D-Link DWL-122?

markjensen

Jul 29 2005, 23:59

It should. NDISWrapper uses the Windows drivers and makes them work in Linux. There may be a newer version out now than this procedure specifies. I don't have wireless, so I can't vouch.

ryanstein

Aug 1 2005, 02:55

You guys rule. I'll try this once my Ubuntu CDs come in the mail. (Shipit will send them to you free so that you have a "hard copy" that won't degrade.)

Couch Potato

Aug 20 2005, 15:58

uhm i cannot download a driver for version 2.0 and the driver for 4.0 doesn't have the file mentioned. anyone want to upload those 2 files needed?

Rob2687

Aug 21 2005, 07:17

It might be named differently, just look for the .inf and .sys file.

Couch Potato

Aug 21 2005, 09:02

Alright so only those 2 files are needed?

Thank you, let's go installing

Couch Potato

Aug 21 2005, 09:52

I get stuck on step 3 at point 4, he says the command isnt found.