Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ugh, I'm at a loss. I'm running Fedora Core 3 on a Compaq Presario 2585US. Here's the version:
Linux version 2.6.10-1.737_FC3 (email@example.com) (gcc version 3
.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Mon Jan 10 13:50:10 EST 2005
Now I'm trying to get ndiswrapper to work and I'm getting stuck. I downloaded ndiswrapper, the windows drivers, and I think gcc is installed. Does this mean it is:
[sketchydave@localhost ~]$ gcc
gcc: no input files
And I go to run it and I get stuck at "bash: ndiswrapper: command not found"
Here's everything from the terminal...any ideas?
[root@localhost ndiswrapper-1.0rc2]# make install
make -C driver install
make: Entering directory `/home/sketchydave/ndiswrapper-1.0rc2/driver'
make -C /lib/modules/2.6.10-1.737_FC3/build SUBDIRS=/home/sketchydave/ndiswrapper-1.0rc2/driver \
make: Entering directory `/lib/modules/2.6.10-1.737_FC3/build'
/home/sketchydave/ndiswrapper-1.0rc2/driver/Makefile:59: CONFIG_DEBUG_SPINLOCK conflicts with spinlocks used by Windows driver. There is a workaround for it inndiswrapper, but it may not work correctly. Don't complain about kernel crashesuntil CONFIG_DEBUG_SPINLOCK is disabled.
Building modules, stage 2.
make: Leaving directory `/lib/modules/2.6.10-1.737_FC3/build'
*** 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
Distribution: slamd64 2.6.12 Slackware 2.4.32 Windows XP x64 pro
I didnt have to do any of that to get my ndiswrapper driver working. I un-tared the .tar.gz file, mounted the cd with the windows drivers, then from /ndiswrapper/utils/./ndiswrapper -i *the .inf file from cd(Mine was /media/cdrom/drivers/***.inf, then had to lspci -v to find the pci number for the card and then lspci -n and match the numbers and find the pciid to bind to it will be a 0000:0000 number
hers my lspci -n:
00:00.0 Class 0600: 8086:7190 (rev 02)
00:01.0 Class 0604: 8086:7191 (rev 02)
00:0d.0 Class 0200: 8086:1229 (rev 05)
00:0e.0 Class 0300: 10de:002d (rev 15)
00:0f.0 Class 0400: 11de:6057 (rev 02)
00:10.0 Class 0401: 1274:5000
00:14.0 Class 0601: 8086:7110 (rev 02)
00:14.1 Class 0101: 8086:7111 (rev 01)
00:14.2 Class 0c03: 8086:7112 (rev 01)
00:14.3 Class 0680: 8086:7113 (rev 02)
the last one is my wireless card so I would: torm@darkside~ndiswrapper/utils/./ndiswrapper -d 0680:8086. Then all I had to do was modprobe ndiswrapper then do the if/iw config to set it up. Also you have to do the ./ndiswrapper -i and ./ndiswrapper -d from the /utils in your ndiswrapper dir.
Never did I do any type of make or make install, I believe its ready to go when you un-tar the tar.gz file.
*also just try cd to utils from the ndiswrapper dir that might fix it.
Last edited by tormented_one; 01-13-2005 at 08:28 PM.
Well i think your ndiswrapper is installed. NOw just put ure windows drivers in a folder and cd to it in terminal. Now make sure ure root and type ndiswrapper -i drivername.ini . So now the driver is loaded. Now type ndiswrapper -m . And now modprobe ndiswrapper. Now evrything should be fine. The last step is to type dhclient wlan0 and thats it. Now each time u restart ur eocmputer just in terminal type : modprobe ndiswrapper and dhclient wlan0 and the internet will work.
Thats how i got mine to work so hope it worx on ures too.
A) Are you running the ndiswrapper command as root.
B) If you su'd to root, try running 'bash -l' just incase your paths aren't setup, then run 'which ndiswrapper' to see if it is present. If not, you may need to install it.
C) You may also check if you have the wireless-tools package installed.
woohoo!!! found the right driver. For anyone who has a similar problem, you need to get the drivers from a Dell TrueMobile 1300 extract it on a PC and find the bcmwl5.inf driver. Then I emailed it to myself and loaded it (while wired) onto the linux machine. For some reason I was getting corrupt drivers from Compaq and other locations. I remember when I reinstalled Windows XP the wireless drivers were a bit of a pain to install as well. At any rate the driver works for the Broadcom BCM94306MP.
My particular problem was I kept getting "command not found" when I typed in ndiswrapper. And I do have gcc installed. I logged in as root, typed in "bash -l" as suggested and then it reconized the command. I followed one of the several ndiswrapper tutorials on the site and we have success!
wlan0: ndiswrapper ethernet device 00:90:4b:43:63:75 using driver bcmwl5
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP
ndiswrapper: driver bcmwl5 (Broadcom,11/27/2004, 184.108.40.206) added
To answer your last question, the '-l' option stands for 'login shell'.
You don't want to have paths set by .bashrc because this script is run every time you start a new terminal such as konsole. 'bash -l' will run the ~/.profile or ./.bash_login script, depending on which is present. Since root never logged in, the login script(s) never ran.
I had a thought that I thought I might add. Linux distro's have a way so simply adjust the amount of security that you want for your system. A higher level may by default not include the directorys /sbin and /usr/sbin.
I have read all your posts, sketchydave but I still do not have Internet working.
I also have the same Wireless card as you and correctly installed ndiswrapper with correct driver.
The problem is with IP (wlan0 cannot determine it) and says ACCESS POINT: UNKNOWN
Can you explain to me in more detail what you did to get IP address?