PDA

View Full Version : HOWTO: Dell Inspiron E1505 Wireless (Broadcom 1390 WLAN)



Pages : [1] 2 3 4 5 6 7

paperdiesel
November 10th, 2006, 09:33 PM
This HOWTO describes how to get Wifi working on your Dell Inspiron E1505/6400 laptop using Ndiswrapper. This applies if you have the Broadcom "Dell Wireless 1390 WLAN MiniCard", which as far as I know, is the cheaper, low-end version that Dell currently offers in this laptop. This HOWTO has been tested and works with both 32 bit and 64 bit ubuntu, and uses the exact same method for both. It is VERY IMPORTANT that you read every part of this how-to and follow the steps EXACTLY as they're written. Many users have trouble because they only read the code sections and ignore my directions to change to the proper directories. Again, PLEASE BE SURE YOU ARE IN THE PROPER DIRECTORY WHEN EXECUTING THESE COMMANDS. This will save you a lot of trouble and will make the installation go a lot smoother.

This HOWTO supports:
Gutsy Gibbon 7.10
Feisty Fawn 7.04
Edgy Eft 6.10
Dapper Drake 6.06



STEP 1: CLEAN YOUR SYSTEM

IMPORTANT NOTE ABOUT CLEANING YOUR SYSTEM:

One of the most common reasons why many people can't get their wireless working is because their system is in a state of chaos. If you have made ANY previous attempts to get your wireless working -- either using fwcutter, ndiswrapper, or the bcm43xx drivers -- this how-to will most likely not work UNTIL you reverse your previous changes. In many cases, it is much easier to simply reinstall ubuntu and come straight to this how-to. Alternatively, you can manually clean your system of the previous attempts, as outlined in various posts throughout this thread. But BE WARNED: If you have done ANY previous work on your wireless, there is almost no chance that this how-to will work unless you clean your system.

If you have a fresh install of Ubuntu, you need to remove any and all versions of Ndiswrapper that come installed by default on your system:



sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5
sudo apt-get remove ndiswrapper-utils

Don't worry if you get errors about not being able to find or remove these -- we're just making sure they're not present before we get started.



STEP 2: GET NEEDED PACKAGES

We'll need to install compiling tools (don't panic when you read that, just bear with me), the latest kernel headers, and then the source code for the latest ndiswrapper (seriously, don't panic. This will be very simple), and the wireless drivers from Dell.com.



sudo apt-get update
sudo apt-get install build-essential
sudo apt-get install linux-headers-`uname -r`
wget http://ftp.us.dell.com/network/R151517.EXE

NOTE: The characters around `uname -r` are BACK TICS, NOT apostrophes. A back tic is usually located at the top left of your keyboard, to the left of the 1 key. The command WILL NOT WORK if you use apostrophes. Just copy/paste the commands from this how-to in to your terminal to avoid making typos.

At this point, you need to go to the ndiswrapper sourceforge site and get the latest version of the Ndiswrapper program.



wget http://superb-east.dl.sourceforge.net/sourceforge/ndiswrapper/ndiswrapper-1.51.tar.gz

If that wget doesn't work, just go here: http://sourceforge.net/project/showfiles.php?group_id=93482

Uncompress the ndiswrapper source (in my example, the file name is ndiswrapper-1.51.tar.gz):



tar -xzvf ndiswrapper-1.51.tar.gz

Finally, we need to blacklist the broken and useless bcm43xx firmware drivers that try to load in a default ubuntu install:



sudo echo blacklist bcm43xx >> /etc/modprobe.d/blacklist

NOTE: If the above command gives you a permission denied error, try this code instead:



sudo -s
echo blacklist bcm43xx >> /etc/modprobe.d/blacklist
exit

YOU MUST REBOOT NOW!



STEP 3: COMPILE PROGRAM

Now we'll complile the Ndiswrapper program. In a terminal, go to the directory where you extracted ndiswrapper and execute the following:



cd YOUR-NDISWRAPPER-DIRECTORY
sudo make uninstall

IMPORTANT: Do the above command multiple times. You can stop when you get the message that says something about no files or directories found. This usually means running the command 2 or 3 times, but not more than about a dozen.



sudo make distclean
sudo make
sudo make install



STEP 4: INSTALL DRIVERS

If that worked, then you now have Ndiswrapper installed. Now we need to install the drivers. In a terminal, go to the directory where you have the R151517.EXE file:



unzip -a R151517.EXE

Now change directories to the DRIVER directory that was just extracted.



cd YOUR-DRIVER-DIRECTORY
sudo ndiswrapper -i bcmwl5.inf
sudo ndiswrapper -l

you should see a message that says driver present, hardware detected



sudo ndiswrapper -m
sudo modprobe ndiswrapper
sudo echo ndiswrapper >> /etc/modules

NOTE: If the above echo command gives you a permission denied error, try this code instead:



sudo -s
echo ndiswrapper >> /etc/modules
exit

Some users have reported the need to reboot here.



STEP 5: TEST WIRELESS

Your wifi light on your laptop should be illuminated, and you're all set! Try running this to see if your wireless card is functioning properly:



sudo iwlist scanning

Even if it doesn't detect any wireless networks in range, it will still tell you if linux is recognizing your wireless card properly. If you'd like a better way to scan for wireless networks, I'd suggest installing/using network-manager or wifi-radar.


TO ALL WHO REQUEST HELP:

1) Please indicate:

your laptop model
ubuntu version
your lspci output
the relevant rows from /var/log/syslog
the relevant rows from dmesg
any unexpected output when following the steps in the how-to


2) If your wireless card is being recognized by the system, but you simply cannot connect to your desired wireless network, please understand that your issue is beyond the scope of this how-to, due largely to the fact that such issues are very complicated and often have absolutely nothing to do with the way you got ubuntu to recognize your wireless card. That said, I will do what I can to help. My first suggestion will always be to turn off all encryption first to see if you can at least connect to an open network.

NOTES:

- Dell driver version updated to R151517.EXE on 30 March 2007
- Ndiswrapper version updated to 1.51 on 7 January 2008
- If you are using a Dell laptop that's NOT model E1505, you need to go to Dell.com and search for the drivers that correspond to your specific model. Use those instead.

varunbhalerao
November 13th, 2006, 01:41 AM
Great ! thats a nice, easy how-to - and works perfectly. I needed to manually put an ESSID from the last command into the the config of the wireless card (system->administration->networking) - it wouldnt auto-detect networks there. If all need to do it, you might want to add it in the how-to !

Zaffe
November 16th, 2006, 01:29 AM
Ty for this, working fine now

rodealmeida
November 16th, 2006, 08:00 PM
Thank You. U save me. I was using windows because i couldn't set up my wireless connection. Now it's working fine and it was very easy to configure. Thanks :-D

sudipta_cht
November 20th, 2006, 10:54 AM
God bless you!

arthur_kalm
November 21st, 2006, 04:56 AM
I get the same result as before, no wireless. The light doesn't come up and the scan is empty. I can't connect to any networks. This is really annoying because wireless was working PERFECTLY under Dapper. I'm really _really_ disappointed with Edgy. Nothing seems to work (wireless, XGL/Beryl, suspend and hibernate). I'm going to mess around with it for a while but I might just go back to Dapper.

loismustdie
November 21st, 2006, 05:38 AM
i have a problem, and i'm new to linux in general, so i apologize ahead of time for not completely understanding the answers if that happens.

when i go to blacklist the bcm drivers, it says permission is denied. what do i do to get around that? i'm using sudo, and i've already typed in the only password i know of. what's going on?

loismustdie
November 21st, 2006, 06:34 AM
so nevermind on that, i logged in as root and fixed the problem. the next thing is that i'm actually having trouble with an earlier step.

sudo apt-get install linux-headers-`uname -r`

this command gets me the following reply:

Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package linux-headers-uname -r

again, i'm completely new to linux and don't know what i'm doing wrong. anyone?

ILoveLily
November 21st, 2006, 07:15 AM
i have a problem, and i'm new to linux in general, so i apologize ahead of time for not completely understanding the answers if that happens.

when i go to blacklist the bcm drivers, it says permission is denied. what do i do to get around that? i'm using sudo, and i've already typed in the only password i know of. what's going on?

Open a new terminal and do "sudo -s" and then try the same code without the sudo.


so nevermind on that, i logged in as root and fixed the problem. the next thing is that i'm actually having trouble with an earlier step.

sudo apt-get install linux-headers-`uname -r`

this command gets me the following reply:

Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package linux-headers-uname -r

again, i'm completely new to linux and don't know what i'm doing wrong. anyone?

see where it says "uname"? that;s where you enter the linux headers version number. first type "sudo apt-get install linux-headers" and it will give you a selection and then choose the version replaced with "uname"






However, I am having problems installing the driver. It is giving me the error with something like "code at line 167". Any ideas?

loismustdie
November 21st, 2006, 04:48 PM
i'm getting the same line 167 message now.

and it's showing that i've got like three drivers installed somehow. how can i remove specific drivers for the device?



and thank you very much for the previous answer. that was extremely helpful.

paperdiesel
November 21st, 2006, 05:23 PM
If you followed the steps from the very beginning, then there's no way you should have three drivers installed. I would recommend starting over. Go to the directory where you extracted the ndiswrapper tarball and do this:



sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5

Then do this at least three or four times:



sudo make uninstall

Finally, reinstall the program:



sudo make
sudo make install

Then pick back up with the howto.

eq235
November 22nd, 2006, 12:17 AM
Thanks for posting. Very nice, clear guide. There is one more step I would mention. To get the driver to load automatically when you boot, insert "ndiswrapper" into /etc/modules. In terminal, type

sudo nano /etc/modules

-then add 'ndiswrapper' to it (no quotes). then press ctrl-O to save it.

Then it will load automatically for you on each boot *instead of having to load it manually each time).

ILoveLily
November 22nd, 2006, 05:05 AM
Right thanks for the automatic load on start up. But as Loismustdie, and I said something is wrong with the code on line 167. or something.

loismustdie: do you have a compaq by any chance?

paperdiesel
November 22nd, 2006, 07:32 PM
Ok, hold up. I don't mean to be pedantic or anything, but if you're not using a Dell Inspiron E1505/6400, then this is probably not the HOW-TO for you. This how-to is written for Dell Inspiron Notebooks only, using Dell's proprietary wireless drivers. ](*,)

If you're not using a Dell, you are of course free to try the methods here -- and I'll do my best to help you out. But please don't respond to the poll saying this how-to doesn't work if you're not actually using the equipment for which this how-to was written.

ILoveLily
November 22nd, 2006, 09:10 PM
i realise that, but when i do a lspci. it comes up with this wireless card. i'm not that dumb.

paperdiesel
November 22nd, 2006, 11:55 PM
I never said you were dumb. In fact, I admire anyone willing to try to get a non-native wireless card to work under linux.

The problem with you using this how-to is that you're going to be using Dell's drivers, which are specifically designed to work on DELL laptops. Even if you have the same chipset (Broadcom), that's no guarantee that the entire NIC is the same (bus interface, memory management, etc), nor is it any indication whether or not DELL drivers will work on your NON-DELL laptop. I would suggest you go to the ndiswrapper list (http://ndiswrapper.sourceforge.net/mediawiki/index.php/List) page to find out more about support with your laptop manufacturer and wireless drivers.

If you're getting an error when trying to load Dell wireless drivers on your non-Dell laptop, then there's not much I can do to help.

Skyline.R34
November 23rd, 2006, 12:17 AM
Hi.. I followed this guide.. but my wireless still doesnt seem to work.. the wifi light on the laptop is blinking like bad tho.. lol.. the only way i can get on the net is by plugging in the Ethernet cable which kinda beats the purpose of me trying to set up the wireless lol...

i ran that last command and it listed a whole bunch of data.. tho i cant even tell if the thing is working or not.. lol

typing sudo ndiswrapper -l shows

installed drivers:
bcmwl5 driver installed (alternative driver: bcm43xx)


and yea i'm using Inspiron E1505 hehe...

any ideas ?

loismustdie
November 23rd, 2006, 12:44 AM
so i just used -r to remove all the drivers and then reinstalled the correct one. when in did that, it showed the following:

derrick@derrick-laptop:~/DRIVER$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5 ...
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2

then i did the ndiswrapper -l command and got:

derrick@derrick-laptop:~/DRIVER$ sudo ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4324) present (alternate driver: bcm43xx)

but i've still got nothing. the wireless light doesn't come on. nothing.

any suggestions? i'm not quite sure what to do.

paperdiesel
November 23rd, 2006, 01:31 AM
so i just used -r to remove all the drivers and then reinstalled the correct one. when in did that, it showed the following:

derrick@derrick-laptop:~/DRIVER$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5 ...
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2

then i did the ndiswrapper -l command and got:

derrick@derrick-laptop:~/DRIVER$ sudo ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4324) present (alternate driver: bcm43xx)

but i've still got nothing. the wireless light doesn't come on. nothing.

any suggestions? i'm not quite sure what to do.

So far so good. ASSUMING you've followed all of the previous steps in the guide, without errors, then execute this:



sudo modprobe ndiswrapper

And that should do it. Try the iwlist command to see if you're up.

loismustdie
November 23rd, 2006, 02:02 AM
when i do the modprobe command, nothing happens. is there supposed to be some sort of message?

and when i do the iwlist command, i get the following:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.


and thanks for the help so far.

paperdiesel
November 23rd, 2006, 04:16 PM
when i do the modprobe command, nothing happens. is there supposed to be some sort of message?

and when i do the iwlist command, i get the following:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.


and thanks for the help so far.

Basically, you need to start all the way over. Let's try this again:



sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5
sudo apt-get remove ndiswrapper-utils

Now go to the directory where you downloaded and installed ndiswrapper from sourceforge, and do this MULTIPLE TIMES:



sudo make uninstall

When you start seeing the same output over and over, REBOOT NOW.

Now do this in the ndiswrapper directory:



sudo make
sudo make install

Now go to the DRIVERS directory where you extracted the dell drivers (you ARE using a Dell Inspiron E1505, right??):



sudo ndiswrapper -i bcmwl5.inf
sudo ndiswrapper -l
sudo modprobe ndiswrapper
sudo iwlist scanning

That should get you going.

ILoveLily
November 24th, 2006, 04:36 AM
I never said you were dumb. In fact, I admire anyone willing to try to get a non-native wireless card to work under linux.

The problem with you using this how-to is that you're going to be using Dell's drivers, which are specifically designed to work on DELL laptops. Even if you have the same chipset (Broadcom), that's no guarantee that the entire NIC is the same (bus interface, memory management, etc), nor is it any indication whether or not DELL drivers will work on your NON-DELL laptop. I would suggest you go to the ndiswrapper list (http://ndiswrapper.sourceforge.net/mediawiki/index.php/List) page to find out more about support with your laptop manufacturer and wireless drivers.

If you're getting an error when trying to load Dell wireless drivers on your non-Dell laptop, then there's not much I can do to help.

Well, it's odd because it literally says Dell 1390 WLAN. And I used the driver you provided (the R213123123123213213.EXE) one on Arch Linux. It's up and running beautifully. That's so weird.

arthur_kalm
November 26th, 2006, 01:00 AM
Hmm I followed the guide but I get no scan results... this is very strange because there are several wireless networks around my area. I guess I'll go back to Dapper :P

pyros
November 26th, 2006, 08:27 AM
hmm. Ok, so this is my first odyssey with ndiswrapper.

Just for the record: I am not trying this on a model 1505, but 1501; the card is the same, dell (broadcom) 1390; the windows driver downloads from the dell site are the same; there are three unsecured and one secured access point available in my area; I was referred to this thread by another 1501 owner, who successfully followed your guide;

I, however, have not been so lucky.

everything goes swimmingly, until I run sudo iwlist scanning. I get a message for each interface that they don't support scanning. I've tried this with the driver that is listed in the tutorial, as well as the updated driver that was released on the 15th with the same results. I've included the output (after running sudo make uninstall and rebooting) from my last run in the hopes that what I'm doing wrong will be obvious to others.





username@hostname:~$ cd ndiswrapper-1.28/
username@hostname:~/ndiswrapper-1.28$ sudo make
Password:
make -C driver
make[1]: Entering directory `/home/username/ndiswrapper-1.28/driver'
make -C /lib/modules/2.6.17-10-generic/build SUBDIRS=/home/username/ndiswrapper-1.28/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-10-generic'
LD /home/username/ndiswrapper-1.28/driver/built-in.o
CC [M] /home/username/ndiswrapper-1.28/driver/crt.o
CC [M] /home/username/ndiswrapper-1.28/driver/hal.o
CC [M] /home/username/ndiswrapper-1.28/driver/iw_ndis.o
CC [M] /home/username/ndiswrapper-1.28/driver/loader.o
CC [M] /home/username/ndiswrapper-1.28/driver/ndis.o
CC [M] /home/username/ndiswrapper-1.28/driver/ntoskernel.o
CC [M] /home/username/ndiswrapper-1.28/driver/ntoskernel_io.o
CC [M] /home/username/ndiswrapper-1.28/driver/pe_linker.o
CC [M] /home/username/ndiswrapper-1.28/driver/pnp.o
CC [M] /home/username/ndiswrapper-1.28/driver/proc.o
CC [M] /home/username/ndiswrapper-1.28/driver/rtl.o
CC [M] /home/username/ndiswrapper-1.28/driver/wrapmem.o
CC [M] /home/username/ndiswrapper-1.28/driver/wrapndis.o
CC [M] /home/username/ndiswrapper-1.28/driver/wrapper.o
CC [M] /home/username/ndiswrapper-1.28/driver/usb.o
CC [M] /home/username/ndiswrapper-1.28/driver/divdi3.o
LD [M] /home/username/ndiswrapper-1.28/driver/ndiswrapper.o
Building modules, stage 2.
MODPOST
CC /home/username/ndiswrapper-1.28/driver/ndiswrapper.mod.o
LD [M] /home/username/ndiswrapper-1.28/driver/ndiswrapper.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-10-generic'
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/driver'
make -C utils
make[1]: Entering directory `/home/username/ndiswrapper-1.28/utils'
gcc -g -Wall -I../driver -o loadndisdriver loadndisdriver.c
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/utils'
username@hostname:~/ndiswrapper-1.28$ sudo make install
make -C driver install
make[1]: Entering directory `/home/username/ndiswrapper-1.28/driver'
make -C /lib/modules/2.6.17-10-generic/build SUBDIRS=/home/username/ndiswrapper-1.28/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-10-generic'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-10-generic'
echo /lib/modules/2.6.17-10-generic/misc
/lib/modules/2.6.17-10-generic/misc
mkdir -p /lib/modules/2.6.17-10-generic/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.17-10-generic/misc
/sbin/depmod -a 2.6.17-10-generic -b /
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/driver'
make -C utils install
make[1]: Entering directory `/home/username/ndiswrapper-1.28/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.5. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
install -m 644 loadndisdriver.8 /usr/share/man/man8
username@hostname:~/ndiswrapper-1.28$ cd ../DRIVER/
username@hostname:~/DRIVER$ ls
bcm43xx64.cat bcm43xx.cat bcmwl564.sys bcmwl5.inf bcmwl5.sys
username@hostname:~/DRIVER$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5 ...
username@hostname:~/DRIVER$ ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4328) present
username@hostname:~/DRIVER$ sudo modprobe ndiswrapper
username@hostname:~/DRIVER$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning : No such device

sit0 Interface doesn't support scanning.

username@hostname:~/DRIVER$


Thanks for the guide and any help you can give.

paperdiesel
November 26th, 2006, 07:16 PM
hmm. Ok, so this is my first odyssey with ndiswrapper.

Just for the record: I am not trying this on a model 1505, but 1501; the card is the same, dell (broadcom) 1390; the windows driver downloads from the dell site are the same; there are three unsecured and one secured access point available in my area; I was referred to this thread by another 1501 owner, who successfully followed your guide;

I, however, have not been so lucky.

everything goes swimmingly, until I run sudo iwlist scanning. I get a message for each interface that they don't support scanning. I've tried this with the driver that is listed in the tutorial, as well as the updated driver that was released on the 15th with the same results. I've included the output (after running sudo make uninstall and rebooting) from my last run in the hopes that what I'm doing wrong will be obvious to others.





username@hostname:~$ cd ndiswrapper-1.28/
username@hostname:~/ndiswrapper-1.28$ sudo make
Password:
make -C driver
make[1]: Entering directory `/home/username/ndiswrapper-1.28/driver'
make -C /lib/modules/2.6.17-10-generic/build SUBDIRS=/home/username/ndiswrapper-1.28/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-10-generic'
LD /home/username/ndiswrapper-1.28/driver/built-in.o
CC [M] /home/username/ndiswrapper-1.28/driver/crt.o
CC [M] /home/username/ndiswrapper-1.28/driver/hal.o
CC [M] /home/username/ndiswrapper-1.28/driver/iw_ndis.o
CC [M] /home/username/ndiswrapper-1.28/driver/loader.o
CC [M] /home/username/ndiswrapper-1.28/driver/ndis.o
CC [M] /home/username/ndiswrapper-1.28/driver/ntoskernel.o
CC [M] /home/username/ndiswrapper-1.28/driver/ntoskernel_io.o
CC [M] /home/username/ndiswrapper-1.28/driver/pe_linker.o
CC [M] /home/username/ndiswrapper-1.28/driver/pnp.o
CC [M] /home/username/ndiswrapper-1.28/driver/proc.o
CC [M] /home/username/ndiswrapper-1.28/driver/rtl.o
CC [M] /home/username/ndiswrapper-1.28/driver/wrapmem.o
CC [M] /home/username/ndiswrapper-1.28/driver/wrapndis.o
CC [M] /home/username/ndiswrapper-1.28/driver/wrapper.o
CC [M] /home/username/ndiswrapper-1.28/driver/usb.o
CC [M] /home/username/ndiswrapper-1.28/driver/divdi3.o
LD [M] /home/username/ndiswrapper-1.28/driver/ndiswrapper.o
Building modules, stage 2.
MODPOST
CC /home/username/ndiswrapper-1.28/driver/ndiswrapper.mod.o
LD [M] /home/username/ndiswrapper-1.28/driver/ndiswrapper.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-10-generic'
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/driver'
make -C utils
make[1]: Entering directory `/home/username/ndiswrapper-1.28/utils'
gcc -g -Wall -I../driver -o loadndisdriver loadndisdriver.c
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/utils'
username@hostname:~/ndiswrapper-1.28$ sudo make install
make -C driver install
make[1]: Entering directory `/home/username/ndiswrapper-1.28/driver'
make -C /lib/modules/2.6.17-10-generic/build SUBDIRS=/home/username/ndiswrapper-1.28/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-10-generic'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-10-generic'
echo /lib/modules/2.6.17-10-generic/misc
/lib/modules/2.6.17-10-generic/misc
mkdir -p /lib/modules/2.6.17-10-generic/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.17-10-generic/misc
/sbin/depmod -a 2.6.17-10-generic -b /
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/driver'
make -C utils install
make[1]: Entering directory `/home/username/ndiswrapper-1.28/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.5. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/home/username/ndiswrapper-1.28/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
install -m 644 loadndisdriver.8 /usr/share/man/man8
username@hostname:~/ndiswrapper-1.28$ cd ../DRIVER/
username@hostname:~/DRIVER$ ls
bcm43xx64.cat bcm43xx.cat bcmwl564.sys bcmwl5.inf bcmwl5.sys
username@hostname:~/DRIVER$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5 ...
username@hostname:~/DRIVER$ ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4328) present
username@hostname:~/DRIVER$ sudo modprobe ndiswrapper
username@hostname:~/DRIVER$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning : No such device

sit0 Interface doesn't support scanning.

username@hostname:~/DRIVER$


Thanks for the guide and any help you can give.

Finally... someone who is polite! And you even provided error output. I'm happy to help. Let's start here:

Reboot your machine. Once it's up, then go to a terminal and type:



sudo modprobe ndiswrapper
sudo iwlist scanning
dmesg
cat /var/log/syslog

Give me all of the console output and ONLY the relevant rows from your log files (dmesg and /var/log/syslog). Let's see what's up.

cab1024
November 27th, 2006, 03:05 AM
Hello, I just got an Inspiron e1505 but can't get WiFi to work.

Everything seems to work fine until the end of Step 4. When I enter this command:
sudo modprobe ndiswrapper

Nothing happens.

Here's what I have:

chuck@chuck-laptop:~/DRIVER$ sudo ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4324) present (alternate driver: bcm43xx)
chuck@chuck-laptop:~/DRIVER$ sudo modprobe ndiswrapper
chuck@chuck-laptop:~/DRIVER$

The WiFi light does not come on and the test step 5 gives me the following errors:

chuck@chuck-laptop:~/DRIVER$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning : No such device

sit0 Interface doesn't support scanning.


Any advice? I'm stuck in XP having moved from Mac unless this starts working.

pyros
November 27th, 2006, 04:45 PM
After woring in tech support for a few years, you have a whole differnt perspective of those who do it for free.

I have tried to include any relevant entries, and tried to err on the side of caution, so I'm sure I've included things that weren't.

with the sudo'd comands:


username@hostname:~$ sudo modprobe ndiswrapper
password:
username@hostname:~$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning : No such device

sit0 Interface doesn't support scanning.

username@hostname:~$


dmesg:


[17179875.236000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
[17179998.856000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.


syslog


Nov 27 09:40:40 hostname kernel: [17179604.164000] ieee80211_crypt: registered algorithm 'NULL'
Nov 27 09:40:40 hostname kernel: [17179604.172000] ieee80211: 802.11 data/management/control stack, git-1.1.13
Nov 27 09:40:40 hostname kernel: [17179604.172000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
Nov 27 09:40:57 hostname NetworkManager: <information>^Istarting...
Nov 27 09:40:57 hostname firmware_helper[4352]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:40:57 hostname kernel: [17179624.668000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:41:01 hostname NetworkManager: <information>^Ieth1: Device is fully-supported using driver 'bcm43xx'.
Nov 27 09:41:01 hostname NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Nov 27 09:41:01 hostname firmware_helper[4506]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:41:01 hostname kernel: [17179628.404000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:41:01 hostname NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Nov 27 09:41:01 hostname NetworkManager: <information>^INow managing wireless (802.11) device 'eth1'.
Nov 27 09:41:01 hostname NetworkManager: <information>^IDeactivating device eth1.
Nov 27 09:41:04 hostname NetworkManager: <information>^Ieth0: Device is fully-supported using driver 'b44'.
Nov 27 09:41:04 hostname NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Nov 27 09:41:04 hostname NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Nov 27 09:41:04 hostname NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Nov 27 09:41:04 hostname NetworkManager: <information>^IDeactivating device eth0.
Nov 27 09:41:04 hostname dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Nov 27 09:41:04 hostname NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link.
Nov 27 09:41:04 hostname NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Nov 27 09:41:04 hostname dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Nov 27 09:41:04 hostname NetworkManager: <information>^IWill activate connection 'eth0'.
Nov 27 09:41:04 hostname NetworkManager: <information>^IDevice eth0 activation scheduled...
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) started...
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Nov 27 09:41:04 hostname NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Nov 27 09:41:04 hostname NetworkManager: <information>^IUpdating allowed wireless network lists.
Nov 27 09:41:04 hostname NetworkManager: <WARNING>^I nm_dbus_get_networks_cb (): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..
Nov 27 09:41:05 hostname NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Nov 27 09:41:05 hostname NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Nov 27 09:41:05 hostname NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0
Nov 27 09:41:05 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:41:06 hostname NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0
Nov 27 09:41:07 hostname dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Nov 27 09:41:07 hostname dhclient: DHCPACK from 192.168.2.1
Nov 27 09:41:07 hostname NetworkManager: <information>^IDHCP daemon state is now 4 (reboot) for interface eth0
Nov 27 09:41:07 hostname NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Nov 27 09:41:07 hostname NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) started...
Nov 27 09:41:07 hostname dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Nov 27 09:41:07 hostname dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Nov 27 09:41:07 hostname dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Nov 27 09:41:07 hostname dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Nov 27 09:41:07 hostname NetworkManager: <information>^IRetrieved the following IP4 configuration from the DHCP daemon:
Nov 27 09:41:07 hostname NetworkManager: <information>^I address 192.168.2.9
Nov 27 09:41:07 hostname NetworkManager: <information>^I netmask 255.255.255.0
Nov 27 09:41:07 hostname NetworkManager: <information>^I broadcast 192.168.2.255
Nov 27 09:41:07 hostname NetworkManager: <information>^I gateway 192.168.2.1
Nov 27 09:41:07 hostname NetworkManager: <information>^I nameserver 192.168.2.1
Nov 27 09:41:07 hostname NetworkManager: <information>^I nameserver 65.32.5.75
Nov 27 09:41:07 hostname NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Nov 27 09:41:07 hostname NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Nov 27 09:41:07 hostname NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Nov 27 09:41:07 hostname dhclient: bound to 192.168.2.9 -- renewal in 34066 seconds.
Nov 27 09:41:08 hostname NetworkManager: <information>^IDHCP returned name servers but system has disabled dynamic modification!
Nov 27 09:41:08 hostname NetworkManager: <information>^IActivation (eth0) successful, device activated.
Nov 27 09:41:08 hostname NetworkManager: <information>^IActivation (eth0) Finish handler scheduled.
Nov 27 09:41:08 hostname NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Nov 27 09:41:08 hostname ntpdate[4765]: step time server 82.211.81.145 offset 0.000605 sec
Nov 27 09:41:18 hostname kernel: [17179645.776000] eth0: no IPv6 routers present
Nov 27 09:41:25 hostname firmware_helper[4792]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:41:25 hostname kernel: [17179652.328000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:41:30 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:41:50 hostname kernel: [17179676.896000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:41:50 hostname firmware_helper[4802]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:41:54 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:42:14 hostname firmware_helper[4814]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:42:14 hostname kernel: [17179701.536000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:42:19 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:42:20 hostname kernel: [17179707.264000] ndiswrapper version 1.28 loaded (preempt=no,smp=yes)
Nov 27 09:42:20 hostname kernel: [17179707.396000] usbcore: registered new driver ndiswrapper
Nov 27 09:42:39 hostname firmware_helper[4857]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:42:39 hostname kernel: [17179726.172000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:42:43 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:43:03 hostname firmware_helper[4871]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:43:03 hostname kernel: [17179750.708000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:43:08 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:45:08 hostname firmware_helper[4925]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:45:08 hostname kernel: [17179875.236000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:45:12 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:47:12 hostname firmware_helper[4990]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:47:12 hostname kernel: [17179998.856000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:47:15 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device

paperdiesel
November 27th, 2006, 05:59 PM
Hello, I just got an Inspiron e1505 but can't get WiFi to work.

Everything seems to work fine until the end of Step 4. When I enter this command:
sudo modprobe ndiswrapper

Nothing happens.

Here's what I have:

chuck@chuck-laptop:~/DRIVER$ sudo ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4324) present (alternate driver: bcm43xx)
chuck@chuck-laptop:~/DRIVER$ sudo modprobe ndiswrapper
chuck@chuck-laptop:~/DRIVER$

The WiFi light does not come on and the test step 5 gives me the following errors:

chuck@chuck-laptop:~/DRIVER$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

eth1 Interface doesn't support scanning : No such device

sit0 Interface doesn't support scanning.


Any advice? I'm stuck in XP having moved from Mac unless this starts working.

Cab,

Try this:

Reboot your machine. BEFORE it starts loading linux, go in to your BIOS setup. Scroll down to the entry that says Wireless. You'll see a section that says something about the Wifi / bluetooth hotkey. Try setting that so that the wifi is always on, and the hotkey is disabled.

I'm wondering if you're set up correctly, but the wifi hotkey is defaulting to off. Switch that BIOS setting and report back.

paperdiesel
November 27th, 2006, 06:04 PM
dmesg:


[17179875.236000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
[17179998.856000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.


syslog


Nov 27 09:41:18 hostname kernel: [17179645.776000] eth0: no IPv6 routers present
Nov 27 09:41:25 hostname firmware_helper[4792]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:41:25 hostname kernel: [17179652.328000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:41:30 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:41:50 hostname kernel: [17179676.896000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:41:50 hostname firmware_helper[4802]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:41:54 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:42:14 hostname firmware_helper[4814]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:42:14 hostname kernel: [17179701.536000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:42:19 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:42:20 hostname kernel: [17179707.264000] ndiswrapper version 1.28 loaded (preempt=no,smp=yes)
Nov 27 09:42:20 hostname kernel: [17179707.396000] usbcore: registered new driver ndiswrapper
Nov 27 09:42:39 hostname firmware_helper[4857]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:42:39 hostname kernel: [17179726.172000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:42:43 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:43:03 hostname firmware_helper[4871]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:43:03 hostname kernel: [17179750.708000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:43:08 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:45:08 hostname firmware_helper[4925]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:45:08 hostname kernel: [17179875.236000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:45:12 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device
Nov 27 09:47:12 hostname firmware_helper[4990]: main: error loading '/lib/firmware/bcm43xx_microcode5.fw' for device '/class/firmware/0000:05:00.0' with driver 'bcm43xx'
Nov 27 09:47:12 hostname kernel: [17179998.856000] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Nov 27 09:47:15 hostname NetworkManager: <WARNING>^I nm_device_802_11_wireless_scan (): could not trigger wireless scan on device eth1: No such device


Pyros,

First, go in to your BIOS and set your wireless hotkey to always on / key disabled (see my previous post to Cab). If that still doesn't do the trick, I would look in your /etc/modprobe.d/blacklist file and make sure that you have the line
blacklist bcm43xx in there without anything before or after it on that same line. It looks to me like your system is trying to load the broken and useless bcm43xx drivers that come default with ubuntu.

arthur_kalm
November 27th, 2006, 10:55 PM
It worked!!! How do I take back my vote? :p

It seems that even though I don't get scan results (very strange), I can still connect to networks...

I thought it didn't work because iwlist scan gives me no scan results. Why is this?

pyros
November 27th, 2006, 11:12 PM
So, I'm posting this over my wifi connection. hoorah. I disabled the button, but the problem was in the blacklist file. Not sure how I screwed that one up the line was missing altogether. Maybe I missed an error... maybe I shouldn't wait until 4am before trying to work on my computer. Anyway, Thank you Paperdiesel, you are my hero.

paperdiesel
November 28th, 2006, 12:50 AM
It worked!!! How do I take back my vote? :p

It seems that even though I don't get scan results (very strange), I can still connect to networks...

I thought it didn't work because iwlist scan gives me no scan results. Why is this?

Nice! Glad to hear that it worked. Sometimes that iwlist command will not report back about any networks in range -- I just put it in there so that you can see that your wireless card is visible to linux, nothing more.

If you want a better way to scan for wireless networks, I recommend network manager or wifi-radar.

paperdiesel
November 28th, 2006, 12:53 AM
So, I'm posting this over my wifi connection. hoorah. I disabled the button, but the problem was in the blacklist file. Not sure how I screwed that one up the line was missing altogether. Maybe I missed an error... maybe I shouldn't wait until 4am before trying to work on my computer. Anyway, Thank you Paperdiesel, you are my hero.

Congrats! I'm glad it was an easy fix. Coffee is your friend :).

humphry
November 28th, 2006, 01:52 AM
Hi! Thanks for this tutorial, it all worked well. There's only one issue... I don't know how to actually connect to a wireless network. I've got my card up and working and iwlist gives me 4 networks to connect to, but what do I do after that? I've tried system>administration>networking and input the ESSID, but that didn't seem to work...

At the top toolbar, there's the icon for network connection that says it's set on eth0, but don't I want eth1?

As you can tell, I'm new to Linux. Thanks for all your help!

Also, if you could help point me towards some graphics card drivers for my Intel 945GM chipset... I can't get the correct resolution.

Thanks!

Nigel Jacob
November 28th, 2006, 07:13 AM
Hi,

I'm glad that so many people have had good luck in getting their wifi cards
up and running. I've been having the same problem that has been described previously on my 1501. I can get through the outlined steps and they all seem to do the right thing. However, it still doesn't work.

When I try to restart the network services by doing a

'sudo /etc/init.d/networking restart'

I get the following:
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth1.
There is already a pid file /var/run/dhclient.eth2.pid with pid 5798864

This suggested to me that I need to add an entry in /etc/modules, like:

alias eth1 ndiswrapper

...but that didn't help either.

The output from dmesg is nothing but a bunch of:

[ 820.631542] unexpected IRQ trap at vector b0

since I had to use irqpolling to get Kubuntu to recognize my HDD. The same thing goes for my /var/log/syslog output.

Any ideas?

Thanks,
Nigel.

paperdiesel
November 28th, 2006, 02:41 PM
Hi! Thanks for this tutorial, it all worked well. There's only one issue... I don't know how to actually connect to a wireless network. I've got my card up and working and iwlist gives me 4 networks to connect to, but what do I do after that? I've tried system>administration>networking and input the ESSID, but that didn't seem to work...

At the top toolbar, there's the icon for network connection that says it's set on eth0, but don't I want eth1?

Yes, you want to select eth1 (or wlan0, or whatever the wireless card is). Are you trying to connect to a network with encryption? What are you putting in the fields in system -> admin -> networking?


Also, if you could help point me towards some graphics card drivers for my Intel 945GM chipset... I can't get the correct resolution.

Thanks!

Easy, in a terminal type:



sudo apt-get install 915resolution

Then reboot.

humphry
November 28th, 2006, 07:20 PM
Thanks to all, my wireless now works well!

Threbus5
November 29th, 2006, 01:12 AM
I get the same result as before, no wireless. The light doesn't come up and the scan is empty. I can't connect to any networks. This is really annoying because wireless was working PERFECTLY under Dapper. I'm really _really_ disappointed with Edgy. Nothing seems to work (wireless, XGL/Beryl, suspend and hibernate). I'm going to mess around with it for a while but I might just go back to Dapper.
I experienced a similar problem.
Recommend two things - first temporariliy disable network and notebook encryption and see if the notebook connectes to the wireless access point/wireless router (verify via ping not by notebook card LEDs). If the notebook can ping the router in the clear the problem may be a "key issue". I corrected that key issue by re-enabling encryption and changing the network & notebook wireless key. (For an unknown reason I am unable to re-use a wireless key after upgrading or reinstalling Ubuntu.)
Good luck.

nwnyc
November 29th, 2006, 05:51 AM
hi,
i'm trying to drop xp for good. i've got everything i want except wireless. i make it fine until the next to last command:

sudo ndiswrapper -l

i'm getting this error:

bcmwl5 invalid driver!

not sure why this is happening. any ideas? i'd greatly appreciate it. i double checked my system, i definitely have the 1390.

my machine:
dell inspiron e1505
intel core 2 duo
Broadcom 1390 WLAN

paperdiesel
November 29th, 2006, 05:55 PM
hi,
i'm trying to drop xp for good. i've got everything i want except wireless. i make it fine until the next to last command:

sudo ndiswrapper -l

i'm getting this error:

bcmwl5 invalid driver!

not sure why this is happening. any ideas? i'd greatly appreciate it. i double checked my system, i definitely have the 1390.

my machine:
dell inspiron e1505
intel core 2 duo
Broadcom 1390 WLAN

Make sure you downloaded the drivers from dell.com. And make sure you unzipped the driver using unzip -a. Finally, make sure that you execute that ndiswrapper -i bcmwl5.inf from WITHIN the DRIVERS directory where you extracted the dell driver.

Can you show me the output from the console? Also, please include the relevant logs from /var/logs/syslog.

Before you do anything, though, you need to remove the "invalid" driver from ndiswrapper with
sudo ndiswrapper -e bcmwl5

optimarcus_prime
November 29th, 2006, 06:39 PM
First of all, I'd like to say that this guide has been incredibly helpful. Before the guide I was completely lost in this wireless world, but I'm now very close. However, I have but one problem left.

I am using a Dell Inspiron E1505 with the same card that you state in the title. I've gone through all the steps and everything is working beautifully. I've got iwlist scanning working, and it is showing me the networks on my college campus. The problem that I'm having now is that I am unable to connect to the networks. Clearly the wireless card is working because I can scan and see it, but I am completely in the dark as far as how to set Ubuntu to wireless.

Is there a program I need to download? I've tried using NetworkManager Applet 0.6.3, as well as KWiFiManager. I may even have the right tools, but I don't know how to use them. Thank you in advance for any help.


-marcus

paperdiesel
November 29th, 2006, 07:03 PM
First of all, I'd like to say that this guide has been incredibly helpful. Before the guide I was completely lost in this wireless world, but I'm now very close. However, I have but one problem left.

I am using a Dell Inspiron E1505 with the same card that you state in the title. I've gone through all the steps and everything is working beautifully. I've got iwlist scanning working, and it is showing me the networks on my college campus. The problem that I'm having now is that I am unable to connect to the networks. Clearly the wireless card is working because I can scan and see it, but I am completely in the dark as far as how to set Ubuntu to wireless.

Is there a program I need to download? I've tried using NetworkManager Applet 0.6.3, as well as KWiFiManager. I may even have the right tools, but I don't know how to use them. Thank you in advance for any help.


-marcus

Ok, hold up. You're saying you followed the steps succesfully, ubuntu is succesfully recognizing your wireless card, and you can succesfully scan for networks in range? If so, I really hope you voted for the "this worked on my laptop" option in the poll :cool:.

It sounds like you just can't plug in the right values to connect to your college wifi network. Please give more detail. What, exactly, is not working? What have you tried? Screenshots and console output are always helpful.

optimarcus_prime
November 29th, 2006, 08:09 PM
No problem. When I'm in an area that I know has WiFi access, I type in:

sudo iwlist scanning
...and I get the following messages:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:E0:63:82:F6:08
ESSID:"conncollwireless"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:23/100 Signal level:-81 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:16:46:AA:1B:60
ESSID:"conncollwireless"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:54/100 Signal level:-61 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
This is while connected to an Ethernet cable, if that helps you at all (gotta access the forum somehow;) ). I know that there are two conncollwireless's, but the one that I want is the second, 802.11g, signal.

My network settings [System > Admin > Networking > Wireless connection Properties] looks like this:
http://sibbles.com/settings.png

Also, my Network Connection [located on a panel] looks like this:
http://sibbles.com/eth1settings.png

Sorry if my description of the problem isn't as verbose as it should be. I am fairly new to the whole Linux idea, so I'm not sure what you need. Thanks again for any help.

-marcus

paperdiesel
November 29th, 2006, 10:25 PM
Marcus,

I notice in that iwlist scanning command, both of those wireless networks are encrypted. However, in your network setup, you do not have any network key entered. Have you tried finding out what that network key is and entering it in the text box?

optimarcus_prime
November 29th, 2006, 11:32 PM
The way our campus network works [as far as windows machines go] is that the key is supposed to be automatically given to you, and then you enter your college username and password for the network. Unfortunately, there it no option for either of those things on any of the settings I can find.

-marcus

paperdiesel
November 30th, 2006, 01:05 AM
Hm.. well.. I'm not sure what to tell you. As far as I know, ubuntu (and perhaps linux in general) only supports WEP and WPA encryption. If your college uses a form of either, then there has to be a way to pass the proper settings.

My advice is to go to your college's IT center and tell them you have a linux box and need the wireless key. Being a college, they're probably a lot more open and friendly to students of F/OSS operating systems such as ubuntu. I bet they have a set of wireless keys they use for their own tech help purposes, and might let you in on one.

Regardless, you should talk to them and find out how the wireless key is passed (from a techie perspective, not the noob-friendly wireless guide you're given as a student).

Good luck, and let me know if I can do any more to help.

nwnyc
November 30th, 2006, 04:05 AM
Before you do anything, though, you need to remove the "invalid" driver from ndiswrapper with
sudo ndiswrapper -e bcmwl5

This seemed to be the problem. After that, all I had to do was disable the wireless hotkeys in the bios like some previous posters. Thanks so much!

jlapier
November 30th, 2006, 04:28 AM
another Inspiron 1501 here - not having much luck - here's as far as I get for good news - all the steps up to:

$ ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4328) present

modprobe ndiswrapper seemed to work, but I don't know:

k$ modinfo ndiswrapper
filename: /lib/modules/2.6.17-10-generic/misc/ndiswrapper.ko
author: ndiswrapper team <ndiswrapper-general@lists.sourceforge.net>
description: NDIS wrapper driver
version: 1.30
license: GPL
vermagic: 2.6.17-10-generic SMP mod_unload gcc-4.1
depends: usbcore
srcversion: 171308422A0E67F3FC0AA61
parm: hangcheck_interval:The interval, in seconds, for checking if driver is hung. (default: 0) (int)
parm: debug:debug level (int)
parm: proc_gid:The gid of the files created in /proc (default: 0). (int)
parm: proc_uid:The uid of the files created in /proc (default: 0). (int)
parm: if_name:Network interface name or template (default: wlan%d) (charp)

also this doesn't work:


$ iwlist scanning
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

I don't even know what sit0 is (modem maybe?) - I know eth1 is my wired connection (and of course lo is loopback) so I did ifconfig and get:



eth1 Link encap:Ethernet HWaddr 00:15:C5:C5:EA:F7
inet addr:172.16.0.108 Bcast:172.16.255.255 Mask:255.255.0.0
inet6 addr: fe80::215:c5ff:fec5:eaf7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:43294 errors:0 dropped:0 overruns:0 frame:0
TX packets:23565 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:62411525 (59.5 MiB) TX bytes:1875686 (1.7 MiB)
Interrupt:66

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

So I'm not seeing any wifi interfaces there. Also when I go to the Networking control panel in Gnome I only see the wired net connection and a disabled modem connection. Am I missing something? This is a really fresh install (just got this laptop today and blew away the Windows partition before I even loaded it).

Any help is greatly appreciated!

- Jason

jlapier
November 30th, 2006, 04:38 AM
ok, I thought I'd tried everything, but I guess not - I did this:



ndiswrapper -ma
ndiswrapper -mi
ndiswrapper -m

I don't know if that's the right order or if you even need to do all of those - but it creates the alias for you to map wlan0 to ndiswrapper (Nigel, I noticed you were having a similar issue, so maybe give this a try?)

After a reboot, the wifi light was on - I'm on it right now!

- Jason

paperdiesel
November 30th, 2006, 06:32 PM
D'oh! You're right, Jason. I forgot to add in the ndiswrapper -m command. Fixed. Thanks!

Nigel Jacob
December 1st, 2006, 05:51 AM
Thanks for the suggestion! I gave that a try, but no dice. I took a look at /var/log/syslog and the kernel is still throwing a bunch of:

Nov 30 23:37:45 wongo-dev kernel: [ 302.146417] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.148509] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.150438] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.152419] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.155088] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.156522] unexpected IRQ trap at vector 30

...I think that this may be the problem. As I mentioned previously I had to add "acpi=force irqpoll" to the boot params to get Edgy to recognize my HDD. Maybe this irq polling is messing-up the kernel's ability to talk to the 1390 Broadcom chip? I'm guessing here.

This is making me really cranky.

pyros
December 1st, 2006, 12:39 PM
My 1501 gives those same messages, but I was able to get wifi up and running without doing anything extra.

paperdiesel
December 1st, 2006, 06:08 PM
Thanks for the suggestion! I gave that a try, but no dice. I took a look at /var/log/syslog and the kernel is still throwing a bunch of:

Nov 30 23:37:45 wongo-dev kernel: [ 302.146417] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.148509] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.150438] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.152419] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.155088] unexpected IRQ trap at vector 30
Nov 30 23:37:45 wongo-dev kernel: [ 302.156522] unexpected IRQ trap at vector 30

...I think that this may be the problem. As I mentioned previously I had to add "acpi=force irqpoll" to the boot params to get Edgy to recognize my HDD. Maybe this irq polling is messing-up the kernel's ability to talk to the 1390 Broadcom chip? I'm guessing here.

This is making me really cranky.

What's your dmesg output? Also, you might try this for your boot options and see if you have more success:


noapic nolapic irqpoll

surajit
December 1st, 2006, 06:52 PM
Everything worked smoothly.
Thanks a ton!!!

Nigel Jacob
December 2nd, 2006, 04:33 AM
Excellent! Those boot params worked! The broadcom driver seems to be loaded at bootup. However the wifi light still doesn't come on and I can't seem to scan for networks correctly. Needless to say, I can't attach to any local wireless networks. My MacBook is sitting beside me and it can see the networks (which are wide open) so I know they are up.

I can see the following in the dmesg output:

ADDRCONF(NETDEV_UP): eth1: link is not ready

...where eth1 is indeed my wifi interface. Is this message significant?

Thanks!

Nigel Jacob
December 2nd, 2006, 03:20 PM
It works!...but I'm not sure why. This morning I did a 'sudo iwlist scanning' then the wifi light came on and it just worked!

Thanks for a ll the helpful suggestions!

Cheers,
Nigel.

paperdiesel
December 2nd, 2006, 04:32 PM
It works!...but I'm not sure why. This morning I did a 'sudo iwlist scanning' then the wifi light came on and it just worked!

Thanks for a ll the helpful suggestions!

Cheers,
Nigel.

I think you needed to toggle your WiFi hotkey. See my post earlier in this thread about setting your laptop's wifi to "always on, hotkey disabled" in the BIOS.

Glad it's working!

ender8282
December 8th, 2006, 01:07 AM
I am having problems. I get through the howto without any problems until the ==sudo ndiswrapper -l== step. At that point I get the message:
==
installed drivers:
bcmwl5 invalid driver!
==
I have gone through the bios and set the wlan so that it is always on.
thanks for any help.

wool
December 8th, 2006, 03:06 AM
did anyone made their inspiron 1501 (Dell Wireless 1490) work on this method already? Replaced the R115321.EXE with R140747.EXE or is it wrong to replace it?


dave@dave-laptop:~$ sudo iwlist scanning
Password:
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 No scan results
sit0 Interface doesn't support scanning.

dave@dave-laptop:~$ sudo ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4328) present

I already tried disbling the wireless hotkey on bios and
check wireless is enabled. Ran the "ndiswrapper -m" also.
how do you capture the logs?

paperdiesel
December 8th, 2006, 04:46 AM
I am having problems. I get through the howto without any problems until the ==sudo ndiswrapper -l== step. At that point I get the message:
==
installed drivers:
bcmwl5 invalid driver!
==
I have gone through the bios and set the wlan so that it is always on.
thanks for any help.

Ender,

You need to make sure that you run the "sudo ndiswrapper -i bcmwl5.inf" command from WITHIN the DRIVERS directory where you extracted the wireless drivers. If you run that command from any other directory, you'll get the problem you're seeing now. So to back out, first do this:
sudo ndiswrapper -e bcmwl5 Once that's done, go to the DRIVERS directory where you extracted the driver from Dell.com, and pick back up with the how-to with
sudo ndiswrapper -i bcmwl5.inf etc etc.

paperdiesel
December 8th, 2006, 04:47 AM
did anyone made their inspiron 1501 (Dell Wireless 1490) work on this method already? Replaced the R115321.EXE with R140747.EXE or is it wrong to replace it?


dave@dave-laptop:~$ sudo iwlist scanning
Password:
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 No scan results
sit0 Interface doesn't support scanning.

dave@dave-laptop:~$ sudo ndiswrapper -l
installed drivers:
bcmwl5 driver installed, hardware (14E4:4328) present

I already tried disbling the wireless hotkey on bios and
check wireless is enabled. Ran the "ndiswrapper -m" also.
how do you capture the logs?

It looks like it's working, dude. Linux is recognizing your wireless card. If you know you're in range of a wireless network, try manually entering the ESSID and see if it connects.

peacekpr
December 8th, 2006, 04:51 AM
My hardware: Dell Inspiron 1501 Turion X2 w/ 1490 card.
My software: Ubuntu Edgy (6.10) AMD64

I have wifi working after much tinkering. This is how I did it...

I followed paperdiesel's Steps 1 through 3 word-for-word. At Step 4, I obtained Dell's 64-bit proprietary driver R140747.EXE. This is the only thing in his steps that I changed since I'm running Ubuntu Edgy for AMD64. Naturally, Ubuntu informed me of this at bootup (disabled the splash since it bugs me). That was the tip-off. So anyone out there with a 1390 or 1490 wireless card on a Dell and using a 64-bit release of Linux, this driver is the one you want.

I did have to deviate from the last step ("iwlist scanning"). I had to reboot before my card would work. I also disabled the Wireless Hotkey in the BIOS. Once I rebooted, no more 64-bit issues, the Wifi light illuminates, and I am now cookin' with gas. Thanks paperdiesel for your tutorial. I can now vote "It worked for me."


EDIT:
paperdiesel, I recommend renaming the thread to include the Dell 1501 and the 1490 card (and even 64-bit). You may want to update your first posting to account for the additional capability since that first post gets higher visibility than my little post on page 7. Thanks again for the help.
END EDIT

Regards,
Jason

wool
December 8th, 2006, 07:34 AM
I made the driver worked but i cannot connect to any network.

The wifi was disabled on the Windows then I enabled it but first i have enable the hotkey in the bios then disable it before goin back to Edgy Amd64

I can "sudo iwlist scanning" but cant connect on our own secured network (i can connect by windows MCE) or open networks. I think I need to be moving to other forums

I can not get an IP address from the Wifi Router and even tried using static? Maybe i have corrupted my network configuration and stuff so should reinstall my edgy amd64 or you suggest to try dapper amd64 or i386?

ender8282
December 8th, 2006, 10:40 PM
Ender,

You need to make sure that you run the "sudo ndiswrapper -i bcmwl5.inf" command from WITHIN the DRIVERS directory where you extracted the wireless drivers. If you run that command from any other directory, you'll get the problem you're seeing now. So to back out, first do this:
sudo ndiswrapper -e bcmwl5 Once that's done, go to the DRIVERS directory where you extracted the driver from Dell.com, and pick back up with the how-to with
sudo ndiswrapper -i bcmwl5.inf etc etc.

Thanks for the advice. I have been running the install command from inside of the DRIVER dir. It appears to install. It gives the message:


jhubbard@jhubbard-laptop:~/tmp/DRIVER$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5 ...
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
...
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
jhubbard@jhubbard-laptop:~/tmp/DRIVER$ sudo ndiswrapper -l
installed drivers:
bcmwl5 invalid driver!

I still get the same invalid driver when i try to ?load?.
Any other advice.
Thanks.
-John

heathman001
December 9th, 2006, 08:51 AM
This worked for my Inspiron 1501 with a dell 1490 wlan card (broadcom bcm4311)

paperdiesel
December 9th, 2006, 05:06 PM
I still get the same invalid driver when i try to ?load?.
Any other advice.
Thanks.
-John

What Dell laptop model are you using? Which wireless card is inside your Dell?

BlueN1nja
December 9th, 2006, 09:46 PM
My hardware: Dell Inspiron 1501 Turion X2 w/ 1490 card.
My software: Ubuntu Edgy (6.10) AMD64

I have wifi working after much tinkering. This is how I did it...

I followed paperdiesel's Steps 1 through 3 word-for-word. At Step 4, I obtained Dell's 64-bit proprietary driver R140747.EXE. This is the only thing in his steps that I changed since I'm running Ubuntu Edgy for AMD64. Naturally, Ubuntu informed me of this at bootup (disabled the splash since it bugs me). That was the tip-off. So anyone out there with a 1390 or 1490 wireless card on a Dell and using a 64-bit release of Linux, this driver is the one you want.

I did have to deviate from the last step ("iwlist scanning"). I had to reboot before my card would work. I also disabled the Wireless Hotkey in the BIOS. Once I rebooted, no more 64-bit issues, the Wifi light illuminates, and I am now cookin' with gas. Thanks paperdiesel for your tutorial. I can now vote "It worked for me."


EDIT:
paperdiesel, I recommend renaming the thread to include the Dell 1501 and the 1490 card (and even 64-bit). You may want to update your first posting to account for the additional capability since that first post gets higher visibility than my little post on page 7. Thanks again for the help.
END EDIT

Regards,
Jason

I wasn't able to get it working with PD's tutorial on my Inspiron 1501. Happened to see this, and it started working.

Thanks!

ender8282
December 10th, 2006, 05:22 AM
What Dell laptop model are you using? Which wireless card is inside your Dell?

I have a Dell Inspiron E1505. According to windows (where my wireless card works) I have a Dell Wireless 1390WLAN Mini-Card. (it uses a Broadcom Driver)
Under windows I am using the bcmwl5.inf driver.
I have tried using the drier downloaded from dell as well as the driver from my windows install. In both cases it is bcmwl5.inf. And I believe that they are the same file.
Again thanks for any help.
-john

paperdiesel
December 10th, 2006, 03:40 PM
I have a Dell Inspiron E1505. According to windows (where my wireless card works) I have a Dell Wireless 1390WLAN Mini-Card. (it uses a Broadcom Driver)
Under windows I am using the bcmwl5.inf driver.
I have tried using the drier downloaded from dell as well as the driver from my windows install. In both cases it is bcmwl5.inf. And I believe that they are the same file.
Again thanks for any help.
-john

Hm... give me your dmesg and the relevant rows from /var/log/syslog when you install the driver.

towel
December 11th, 2006, 04:36 AM
I was getting the following error:

eth1 Interface doesn't support scanning.

I used the code posted earlier by Jason to fix it.

ndiswrapper -ma
ndiswrapper -mi
ndiswrapper -m


Yay for wireless! This is my first day with Ubuntu and I'm pretty happy!

Thank you so much!

expatrick
December 14th, 2006, 01:57 AM
Dear paperdiesel - thanks for getting me down from the ledge. I've been trying to get this to work all day. mad props to you. happy holidays. xoxoxo

ender8282
December 14th, 2006, 08:58 PM
Hm... give me your dmesg and the relevant rows from /var/log/syslog when you install the driver.

I ran a
grep ndiswrapper /var/log/syslog
grep ndiswrapper /var/log/dmesg
I edited out the duplicates (I have run the commands many times.)
The output was...

dmesg:[17179597.024000] ndiswrapper version 1.29 loaded (preempt=no,smp=no)
dmesg:[17179597.076000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
dmesg:[17179597.080000] usbcore: registered new driver ndiswrapper
syslog:Dec 10 13:55:17 jhubbard-laptop kernel: [17179597.024000] ndiswrapper version 1.29 loaded (preempt=no,smp=no)
syslog:Dec 10 13:55:17 jhubbard-laptop kernel: [17179597.076000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
syslog:Dec 10 13:55:17 jhubbard-laptop kernel: [17179597.080000] usbcore: registered new driver ndiswrapper
Is there any way that I can get more messages to be written to the sys log? It tells me to see error messages in the sys log but there are no messages with real information.
Thanks for all of the help.
-john

pearlygate
December 15th, 2006, 05:35 AM
I think my wireless is working now because when I type sudo iwlist scanning I got several hits.
Thank you very much.
I do have but one question though.

In windows, I can look up available network and choose which one to connect. Is there a tool to do that in ubuntu?
Network manager seems to require me to type my network name.

paperdiesel
December 16th, 2006, 03:50 AM
I ran a
grep ndiswrapper /var/log/syslog
grep ndiswrapper /var/log/dmesg
I edited out the duplicates (I have run the commands many times.)
The output was...

dmesg:[17179597.024000] ndiswrapper version 1.29 loaded (preempt=no,smp=no)
dmesg:[17179597.076000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
dmesg:[17179597.080000] usbcore: registered new driver ndiswrapper
syslog:Dec 10 13:55:17 jhubbard-laptop kernel: [17179597.024000] ndiswrapper version 1.29 loaded (preempt=no,smp=no)
syslog:Dec 10 13:55:17 jhubbard-laptop kernel: [17179597.076000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
syslog:Dec 10 13:55:17 jhubbard-laptop kernel: [17179597.080000] usbcore: registered new driver ndiswrapper
Is there any way that I can get more messages to be written to the sys log? It tells me to see error messages in the sys log but there are no messages with real information.
Thanks for all of the help.
-john

Do a
grep loadndisdriver /var/log/syslog and let me know what it says.

paperdiesel
December 16th, 2006, 03:55 AM
I think my wireless is working now because when I type sudo iwlist scanning I got several hits.
Thank you very much.
I do have but one question though.

In windows, I can look up available network and choose which one to connect. Is there a tool to do that in ubuntu?
Network manager seems to require me to type my network name.

Network-manager works fine for that. You just need to comment-out all of the references to your wireless card in /etc/network/interfaces, as it says in the network-manager docs 8).

peacekpr
December 16th, 2006, 01:33 PM
In windows, I can look up available network and choose which one to connect. Is there a tool to do that in ubuntu?

There is another tool that you can use if you run into problems with paperdiesel's method. I use the tool "wifi-radar" and I like it. See http://wifi-radar.systemimager.org/.

Good luck!

pearlygate
December 16th, 2006, 06:02 PM
Network-manager works fine for that. You just need to comment-out all of the references to your wireless card in /etc/network/interfaces, as it says in the network-manager docs 8).

I went there but everything has already been commented out. hmm here's what I got inside interfaces
auto lo
iface lo inet loopback


iface eth0 inet dhcp


iface eth1 inet dhcp
wireless-essid airseas

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Paperdiesel, can you teach me how to connect to the server that I want to?

pearlygate
December 16th, 2006, 07:34 PM
There is another tool that you can use if you run into problems with paperdiesel's method. I use the tool "wifi-radar" and I like it. See http://wifi-radar.systemimager.org/.

Good luck!

I downloaded wifi radar, found some networks. However it can't connect to any network I got error message: Could not obtain IP address.

Weird?

Stephen47
December 17th, 2006, 12:57 AM
I ran sudo make uninstall and got this message:
make: *** No rule to make target `uninstall'. Stop.
what does this mean?
Also I tried to install 915 resolution and get this message:
steve@steve-laptop:~$ sudo apt-get install 915resolution
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package 915resolution

Stephen47
December 17th, 2006, 01:38 AM
I just started from the top when I get to the step to run sudo echo blacklist bcm43xx >> /etc/modprobe.d/blacklist I get this:
bash: /etc/modprobe.d/blacklist: Permission denied
why? this is becoming very frustrating

michael@redsofa
December 17th, 2006, 02:16 AM
I just started from the top when I get to the step to run sudo echo blacklist bcm43xx >> /etc/modprobe.d/blacklist I get this:
bash: /etc/modprobe.d/blacklist: Permission denied


Step 1: open a new terminal
Step 2:

sudo -s
Step 3:
sudo echo blacklist bcm43xx >> /etc/modprobe.d/blacklist
Step 4:

gedit /etc/modprobe.d/blacklist
must be a line "blacklist bcm43xx"

michael@redsofa
December 17th, 2006, 02:57 AM
Now i work on this wlan thing almost one week and it seems it was wasted time.
Sure, i can see my three Access Points around me, so i think my Wireless card is alive and well. But neither Network-Manager nor wifi-radar couldn't help me to establish a wireless connection.
Anyway, this Howto helps me a lot, so thank you, paperdiesel, for that.
Is there a equal HowTo can help me to bring it to an successful end?


"sudo iwlist scanning" shows me


lo Interface doesn't support scanning.

eth1 Scan completed :
Cell 01 - Address: 00:09:5B:DA:FD:D6
ESSID:"sofa"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:92/100 Signal level:-37 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 02 - Address: 00:14:6C:15:A3:FE
ESSID:"gate"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:53/100 Signal level:-62 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
Cell 03 - Address: 00:C0:02:FB:24:4A
ESSID:"garden"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.427 GHz (Channel 4)
Quality:70/100 Signal level:-51 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.


Even i set one of this Access Points in a open, unsecured modus, nothing happens.
Can i fix this without a tool, just by edit a config file?

Stephen47
December 17th, 2006, 03:15 AM
thanks that worked but after I rebooted and went to the next step I entered: sudo make uninstall and I got this back:make: *** No rule to make target `uninstall'. Stop.
I am in the right directory

ender8282
December 17th, 2006, 03:27 AM
Do a
grep loadndisdriver /var/log/syslog and let me know what it says.


jhubbard@jhubbard-laptop:~$ grep loadndisdriver /var/log/syslog
Dec 7 16:23:35 jhubbard-laptop kernel: [17179597.232000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 7 16:49:55 jhubbard-laptop kernel: [17179597.808000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 8 14:29:59 jhubbard-laptop kernel: [17179604.164000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 9 19:02:21 jhubbard-laptop kernel: [17179604.020000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 9 19:16:51 jhubbard-laptop kernel: [17179597.068000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 9 21:11:30 jhubbard-laptop kernel: [17179596.500000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 10 13:55:17 jhubbard-laptop kernel: [17179597.076000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 11 08:57:15 jhubbard-laptop kernel: [17179597.596000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 14 12:42:03 jhubbard-laptop kernel: [17179604.372000] ndiswrapper (load_wrap_driver:119): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'
Dec 16 19:13:04 jhubbard-laptop kernel:
All of those messages appeared when I tried to boot my machine up. The log messages from loadndisdriver seem to be missing.

hookem10
December 18th, 2006, 03:03 AM
Hi.
I believe that i have followed all of your steps up to 5.
When i run sudo ndiswrapper -i bcmwl5.inf it says driver installed.
But when i do the test wireless nothing comes up, it says lo, eth0, and the one that begins with an s all don't support scanning.
I'm confused, i think the driver is present but it's not working. The wirless light isn't illuminated either.

rowanparker
December 18th, 2006, 12:56 PM
Hello,
I have installed Edgy on my mates Dell Inspiron 640m (with Broadcom 1390 Wireless Card inside). And it all flies through untill I get this:

:~$ sudo ndiswrapper -m
adding "alias wlan0 ndiswrapper" to /etc/modprobe.d/ndiswrapper ...
couldn't add module alias: at /usr/sbin/ndiswrapper line 717
All help is welcome, it did take me a while to pursuade him to let me install it but he wont be able to keep it on without internet.

Please help, thank you, Rowan.

Stephen47
December 18th, 2006, 06:10 PM
All questions and no answers

hookem10
December 19th, 2006, 03:48 AM
I have done all of the steps and they seem to work correctly until

sudo ndiswrapper -l
its displays:
bcmwl: invalid driver
bcmwl5: driver installed
device (14E4:4311) present (alternate driver:bcm43xx)
driver: invalid driver
wireless: invalid driver


any idea what's wrong?

rowanparker
December 19th, 2006, 11:17 AM
I have done all of the steps and they seem to work correctly until

sudo ndiswrapper -l
its displays:
bcmwl: invalid driver
bcmwl5: driver installed
device (14E4:4311) present (alternate driver:bcm43xx)
driver: invalid driver
wireless: invalid driver


any idea what's wrong?
Did you get any errors earlier?

hookem10
December 19th, 2006, 09:39 PM
no nothing that i remember. ill try it all over and see what i get.

Stephen47
December 19th, 2006, 09:51 PM
I need a response to post #83

hookem10
December 19th, 2006, 10:24 PM
i honestly don't really know what happened, but i am posting this in ubuntu!!!!!
time to vote for this working.

Stephen47
December 19th, 2006, 11:06 PM
well it hasn't worked for me yet

paperdiesel
December 22nd, 2006, 11:30 AM
Now i work on this wlan thing almost one week and it seems it was wasted time.
Sure, i can see my three Access Points around me, so i think my Wireless card is alive and well. But neither Network-Manager nor wifi-radar couldn't help me to establish a wireless connection.
Anyway, this Howto helps me a lot, so thank you, paperdiesel, for that.
Is there a equal HowTo can help me to bring it to an successful end?


"sudo iwlist scanning" shows me

Even i set one of this Access Points in a open, unsecured modus, nothing happens.
Can i fix this without a tool, just by edit a config file?

This applies to everyone who wants to try network-manager or wifi-radar to connect to networks:

To use network-manager or wifi-radar, you need to comment-out all of the lines in /etc/network/interfaces that correspond to your network devices. For example, your /etc/network/interfaces file should look something like this:


auto lo
iface lo inet loopback

#iface eth0 inet dhcp

#iface eth1 inet dhcp
#wireless-essid airseas

#auto eth2
#iface eth2 inet dhcp

#auto ath0
#iface ath0 inet dhcp

#auto wlan0
#iface wlan0 inet dhcp

Note that the # character comments-out the line. Once you've edited and saved your changes, you need to reboot.

paperdiesel
December 22nd, 2006, 11:33 AM
thanks that worked but after I rebooted and went to the next step I entered: sudo make uninstall and I got this back:make: *** No rule to make target `uninstall'. Stop.
I am in the right directory

Which directory are you in when you run that uninstall command?

paperdiesel
December 22nd, 2006, 11:34 AM
Hello,
I have installed Edgy on my mates Dell Inspiron 640m (with Broadcom 1390 Wireless Card inside). And it all flies through untill I get this:

:~$ sudo ndiswrapper -m
adding "alias wlan0 ndiswrapper" to /etc/modprobe.d/ndiswrapper ...
couldn't add module alias: at /usr/sbin/ndiswrapper line 717
All help is welcome, it did take me a while to pursuade him to let me install it but he wont be able to keep it on without internet.

Please help, thank you, Rowan.

You can try manually adding the line "alias wlan0 ndiswrapper" to the file /etc.modprobe.d/ndiswrapper and see if it works. You'll need to edit it in sudo mode.

rowanparker
December 22nd, 2006, 12:14 PM
You can try manually adding the line "alias wlan0 ndiswrapper" to the file /etc.modprobe.d/ndiswrapper and see if it works. You'll need to edit it in sudo mode.
It was already there, even though it said it failed.

And this shows nothing:
sudo modprobe ndiswrapper.

Thanks paperdiesel.

Any ideas?

paperdiesel
December 22nd, 2006, 06:59 PM
It was already there, even though it said it failed.

And this shows nothing:
sudo modprobe ndiswrapper.

Thanks paperdiesel.

Any ideas?

Well when you execute that command, if it worked properly, it SHOULDN'T show anything. Give me your dmesg and /var/log/syslog after you run the modprobe command. And what dell / wireless card are you using? Also, did you set your wifi hotkey to disabled / always on in your BIOS (see previous posts in this thread)?

rowanparker
December 22nd, 2006, 07:07 PM
Yeah, I've set that in the BIOS.

It's my friends laptop so I'll get back to you after next time I see him, thank you.


The laptop is a Dell Inspiron m640 (maybe?) with Broadcom 1390 wireless card.

rowanparker
December 23rd, 2006, 12:21 AM
I have run the command sudo modprobe ndiswrapper and I couldn't find anything in syslog or dmesg that related to wireless but I'll attach them anyway.

And sorry, no text files can be uploaded over 19.5k so I split them.

Stephen47
December 23rd, 2006, 02:06 AM
I am in my home directory.

paperdiesel
December 23rd, 2006, 02:55 AM
I am in my home directory.

Well then you are not in the correct directory. You need to run the uninstall command from inside the directory where you extracted ndiswrapper (the program, not the driver).

ender8282
December 23rd, 2006, 03:44 AM
I am still at a loss for how to get my wireless working. I have not been able to get any more messages posted when I try to load the drivers.
I have tried re-downloading all of the packages and re-running all of the commands. I have the WiFi light on and I set the bios to always have wireless enabled. I am unsure if this means anything but when I run the command

lspci
I get a list and I wanted to know if there was any relevance to the line

0b:00.0 Network controller: Broadcom Corporation Unknown device 4311 (rev 01)
I think that that is my wireless card. Is it an unknown device because I have not installed the driver or for some other reason?
If any one has any ideas or suggestions they would be appreciated.
thanks
John

paperdiesel
December 23rd, 2006, 07:09 AM
I am still at a loss for how to get my wireless working. I have not been able to get any more messages posted when I try to load the drivers.
I have tried re-downloading all of the packages and re-running all of the commands. I have the WiFi light on and I set the bios to always have wireless enabled. I am unsure if this means anything but when I run the command

lspci
I get a list and I wanted to know if there was any relevance to the line

0b:00.0 Network controller: Broadcom Corporation Unknown device 4311 (rev 01)
I think that that is my wireless card. Is it an unknown device because I have not installed the driver or for some other reason?
If any one has any ideas or suggestions they would be appreciated.
thanks
John

Ender, that lspci output is normal. Even after your wireless is working properly, you'll get that same output (I see the exact same thing on my laptop).

What model dell are you using again?

Also, start all the way over (remember to uninstall first). When you get to the part where you do the sudo ndiswrapper -i bcmwl5.inf, post the dmesg and /var/log/syslog output.

rowanparker
December 23rd, 2006, 11:12 AM
Paperdiesel, you had a chance to look at the text files I uploaded.
Or shall I just try starting from scratch or something?

Thanks, Rowan.

Stephen47
December 23rd, 2006, 03:09 PM
Well then you are not in the correct directory. You need to run the uninstall command from inside the directory where you extracted ndiswrapper (the program, not the driver).
Which is my home directory.

paperdiesel
December 23rd, 2006, 04:26 PM
Which is my home directory.

No, it's not. If you extracted that ndiswrapper tarball in your home directory, then tar creates another directory and puts all the files in there. The directory usually looks something like ndiswrapper-1.28/. In your case, it would look similar to /home/stephen/ndiswrapper-1.28/.

paperdiesel
December 23rd, 2006, 04:31 PM
Paperdiesel, you had a chance to look at the text files I uploaded.
Or shall I just try starting from scratch or something?

Thanks, Rowan.

Hey Rowan,

Ok, I did some digging around on dell.com for the 640m. Unsurprisingly, the 640m/E1405 uses a different set of drivers than the E1505 for which I wrote this how-to. So I suggest you start all the way over (make sure you uninstall the drivers AND ndiswrapper -- see earlier posts in this thread for instructions), then reboot. Then when you get to the driver install part, you can try the version for your specific model, link provided below:

R140747.EXE (http://ftp.us.dell.com/network/R140747.EXE)

Man... Dell should pay me for this crap.

rowanparker
December 23rd, 2006, 04:36 PM
Hey Rowan,

I looked at them. As far as I can tell, they don't mention anything about ndiswrapper or your wireless card, which is weird. I would go back and triple check to make sure that the blacklist line is in your blaklists file, that the wifi hotkey is set to always on / key disabled. Are you using an E1505? If it's an E1501, you could try using the other drivers that are mentioned in the how-to.
Thanks, I will double check. No wait, tripple check :D

The dell is a E1405.

I have just checked the dell site and the driver download (for XP) is the same for both the E1505 as the E1405.

paperdiesel
December 23rd, 2006, 04:56 PM
Thanks, I will double check. No wait, tripple check :D

The dell is a E1405.

I have just checked the dell site and the driver download (for XP) is the same for both the E1505 as the E1405.

Actually, no. I just updated the how-to to reflect the latest version of the drivers and ndiswrapper. If you were trying it with the old wireless drivers (115132.EXE or something like that), then I suggest you try it with the new ones. And grab the new ndiswrapper as well.

rowanparker
December 23rd, 2006, 05:24 PM
Actually, no. I just updated the how-to to reflect the latest version of the drivers and ndiswrapper. If you were trying it with the old wireless drivers (115132.EXE or something like that), then I suggest you try it with the new ones. And grab the new ndiswrapper as well.
Ok, I'll try again with the latest versions, thank you.

Stephen47
December 24th, 2006, 01:13 AM
No, it's not. If you extracted that ndiswrapper tarball in your home directory, then tar creates another directory and puts all the files in there. The directory usually looks something like ndiswrapper-1.28/. In your case, it would look similar to /home/stephen/ndiswrapper-1.28/.

So how do I find it? I did a file search in all the directories listed and they all showde no files found.
When I look in my home folder I see the file now it is ndiswrapper -l.32 but how do I open a terminal in that directory? I tried "cd /home/steve/ndiswrapper-l.32" and get a "nosuch directory or files found" message.

paperdiesel
December 24th, 2006, 07:16 AM
So how do I find it? I did a file search in all the directories listed and they all showde no files found.
When I look in my home folder I see the file now it is ndiswrapper -l.32 but how do I open a terminal in that directory? I tried "cd /home/steve/ndiswrapper-l.32" and get a "nosuch directory or files found" message.

Stephen,

If you open a terminal, it usually puts you in your home directory. From there, you should be able to cd in to the ndiswrapper directory, whatever it's called. You can even just type the first few letters of the desired directory and hit the TAB button, which will auto-complete for you.

Unfortunately, we're talking about the basics of linux here, and there are probably better tutorials than this wireless how-to that walk you through command line usage, syntax, etc. I'm not sure how much help I can be at this point.

Stephen47
December 25th, 2006, 01:34 PM
Well Merry Christmas to you too, pal

paperdiesel
December 25th, 2006, 10:21 PM
Well Merry Christmas to you too, pal

Stephen, I think you need to go back and re-read my posts to you in this thread. I've been nothing but polite and helpful to you. You on the other hand have been rude, demanding, and complaintive. I realize that you're probably still struggling with your wireless issues, and I wish it were going better for you. But your total lack of common courtesy or appreciation has blacklisted you in my book. Good luck elsewhere, pal.

shom
December 28th, 2006, 09:59 AM
how do i find which device is installed in my dell?:confused:

paperdiesel
December 28th, 2006, 09:02 PM
how do i find which device is installed in my dell?:confused:

Open a terminal and type "lspci" without the quotes. It should tell you what kind of card you have. You can also find more information by typing "dmesg" without the quotes, or looking at the logfile in /var/log/syslog.

coverman
December 28th, 2006, 10:40 PM
Thanks for the guide paperdiesel. It got me a long way but there are still some issues:

Status now is that I can scan the environment for WLAN's, but I cannot connect to my own. So the good thing is that the WiFi is up and running.

Installed wifi-radar but when I click the application from the menu nothing happens; it just won't start. I installed network-manager but this program does not appear in my KDE menu. Don't know how to start it from commandline. I did try to comment out all the entries in /etc/network/interfaces and rebooted as you pointed out, but no luck there either.
In my interfaces file there is an entry for my wireless-essid and wireless-key under the eth1 part. I'm stuck here to make use of my WLAN.

Another thing that worries me a bit is that it seems I have two drivers active:
The output for sudo ndiswrapper -l gives me:

bcmwl5 : driver installed
device (14E4:4311:1028:0007) present (alternate driver: bcm43xx)
device (14E4:4311) present (alternate driver: bcm43xx)

(I recall that sudo ndiswrapper -i bcmwl5.inf allready gave me feedback that the driver was already loaded/present. Although I exactly followed your steps in removing old ndiswrapper and driver files, I think my attempts one month ago with the old driver and ndiswrapper still left some traces on my system).

Thanks for any help to get me going.

londoh
December 29th, 2006, 03:28 AM
Also I tried to install 915 resolution and get this message:
steve@steve-laptop:~$ sudo apt-get install 915resolution
Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package 915resolution

Stephen47 - did you find out why 915 res couldnt be found? I have the same errro message and my 1280 x 800 laptop screen looks pretty naff in 1024 x 768. any pointers will be appreciated
thnx

l.

Stephen47
December 29th, 2006, 11:17 AM
sorry, paperdeisel has banned me from this thread

paperdiesel
December 29th, 2006, 05:35 PM
Thanks for the guide paperdiesel. It got me a long way but there are still some issues:

Status now is that I can scan the environment for WLAN's, but I cannot connect to my own. So the good thing is that the WiFi is up and running.

Installed wifi-radar but when I click the application from the menu nothing happens; it just won't start. I installed network-manager but this program does not appear in my KDE menu. Don't know how to start it from commandline. I did try to comment out all the entries in /etc/network/interfaces and rebooted as you pointed out, but no luck there either.
In my interfaces file there is an entry for my wireless-essid and wireless-key under the eth1 part. I'm stuck here to make use of my WLAN.

Another thing that worries me a bit is that it seems I have two drivers active:
The output for sudo ndiswrapper -l gives me:

bcmwl5 : driver installed
device (14E4:4311:1028:0007) present (alternate driver: bcm43xx)
device (14E4:4311) present (alternate driver: bcm43xx)

(I recall that sudo ndiswrapper -i bcmwl5.inf allready gave me feedback that the driver was already loaded/present. Although I exactly followed your steps in removing old ndiswrapper and driver files, I think my attempts one month ago with the old driver and ndiswrapper still left some traces on my system).

Thanks for any help to get me going.

Coverman,

There are a couple of things you can try. If you'd like to see if you can connect using your current setup, then I'd recommend manually editing your /etc/network/interfaces file. Sometimes you have to change the wireless-key line a little bit. For example, if your wifi network is wep secured with an open key, your line in the interfaces file would look like
wireless-key open [password] where [password] is your key. Or, if that doesn't work, put the open part AFTER the password. Give those a shot. Keep in mind that in the interfaces file, the password must start with s: if it's in ascii form, or not if it's in hex form.

Alternatively, you could totally back out and wipe your system of any ndiswrapper modules. Do this
sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5
sudo ndiswrapper -e bcmwl5
sudo apt-get remove ndiwrapper-utils
The second ndiswrapper -e might give you an error, but do it anyway. Then in a terminal go to the directory where you extracted the ndiswrapper PROGRAM, and do
sudo make uninstall
sudo make uninstall
sudo make uninstall
sudo make uninstall

That should pretty well wipe it clean. Then pick back up with the how-to, paying careful attention not to do the wrong commands twice, NO TYPOS when doing the ndiswrapper -i bcmwl5.inf command, etc.

paperdiesel
December 29th, 2006, 05:38 PM
Stephen47 - did you find out why 915 res couldnt be found? I have the same errro message and my 1280 x 800 laptop screen looks pretty naff in 1024 x 768. any pointers will be appreciated
thnx

l.

Londoh,

The command is
sudo apt-get install 915resolution If it's saying it can't be found, then you need to make sure that you have the right repository enabled in your sources list. The easiest way to go about this is to go here http://packages.ubuntu.com/dapper/x11/915resolution and enable the repository that owns it. Or just download it right off that page and install it with
sudo dpkg -i [packagename] where [packagename] is the name of the downloaded package.

paperdiesel
December 29th, 2006, 05:41 PM
sorry, paperdeisel has banned me from this thread

Stephen, I did not ban you from anything. I'm not a moderator -- I have no ban powers. I simply responded to your snide remark by saying I wasn't willing to help you anymore.

Stephen47
December 30th, 2006, 02:14 AM
I didn't consider them snide

HodKling
December 30th, 2006, 06:52 PM
Thanks this post has helped alot, but.... everytime I boot my Dell Inspiron 1705 I have to go to a terminal windows and type modprobe ndiswrapper. Im a newbie so I would appreciate help. I cant seem to figure out how to get this to happen on its own at boot.

UPDATE:
Thanks to eq235 on his post. Once I took the time to read through this post I found the solution. Edit /etc/modules and add ndiswrapper and save.

Thanks

lbrigman
December 31st, 2006, 08:18 AM
Is this HowTo done because the fw-cutter/bcm42xx native drivers don't work
on a laptop or is it just seemed simpler this way (which it my no means simple as
it will break on any of the kernel updates) ?

paperdiesel
January 2nd, 2007, 12:23 AM
Is this HowTo done because the fw-cutter/bcm42xx native drivers don't work
on a laptop or is it just seemed simpler this way (which it my no means simple as
it will break on any of the kernel updates) ?

It's done because the fw-cutter method doesn't work with the 1390 on the E1505. It's true that if you update your kernel, you'll have to compile a new version of the ndiswrapper program to match your new kernel. But that takes all of ten seconds, and is much simpler than going out and buying a new wireless card.

HarrisonHopkins
January 2nd, 2007, 03:14 AM
Ok, I just installed Kubuntu 6.06 Dapper Drake. Whenever I try "sudo apt-get install build-essential", I get a "E: couldn't find package build-essential." Is it because my laptop wasn't connected to internet when I installed Kubuntu?

EDIT: Nevermind, I found out how to get it to work. Had to uncomment the repositories in the sources list.

Grin
January 3rd, 2007, 10:43 PM
Thank you so much paperdiesel, ive go an inspiron 1501 and to make work my card ive just changed the driver R140747 by the R140745 but at the end the message was bcmwl5 invalid driver so i tried sudo ndiswrapper -e bcmwl5 and then sudo ndiswrapper -i bcmwl5.inf. Afterthat the wireless card was working perfectly

Grin
January 4th, 2007, 01:47 AM
Well, everything was working but with the reboot my wireless interface doesn't appear so i need to do modprobe ndsiwrapper again.
What happens? it seems that i'm the only one who has this problem. Must i do anything to make the process automatic?Thanks

Tanvir
January 5th, 2007, 04:10 AM
Thanks a lot. the wireless is working now :)

davetrainer
January 6th, 2007, 01:59 AM
I have gotten my wireless card recognized, and I can scan nearby networks, but I can not get an ip address from DHCP unless I first explicitly set the ssid in the networking panel, then do


sudo ifdown eth1
sudo ifup eth1

I want to simply select the SSID to associate with from network-manager or wifi-radar. when i do lspci, I get this:


05:00.0 Network controller: Broadcom Corporation Unknown device 4311 (rev 01)

can anyone help??

paperdiesel
January 6th, 2007, 09:22 AM
I have gotten my wireless card recognized, and I can scan nearby networks, but I can not get an ip address from DHCP unless I first explicitly set the ssid in the networking panel, then do


sudo ifdown eth1
sudo ifup eth1

I want to simply select the SSID to associate with from network-manager or wifi-radar. when i do lspci, I get this:


05:00.0 Network controller: Broadcom Corporation Unknown device 4311 (rev 01)

can anyone help??

That lspci output is normal -- everyone gets that with Dells. If you want to use network-manager, you need to comment-out the lines in your /etc/network/interfaces files that correspond with your wireless card, then reboot. The nm docs go in to more detail.

You didn't vote in the poll, did you?

cgons
January 9th, 2007, 04:27 PM
what's up guys??????? new to site and new to linux in general....i've followed these directions for 3 days missing some steps, getting some error messages, basically trying to learn how to operate in linux...anyway i think at this point my file folder is pretty unorginized and i may need to just start over...i erased what i thought was the dell driver unzipped into my home folder.....was i supposed to leave the folder called DRIVER??? was that there when i first installed ubuntu?? im sorry i just don't know whats going on..

i think where it all went wrong was on step 2 after ''sudo apt-get install build essentials" it says cannot find file....i wish i could post screenshots of the termial but i don't know how to yet...i don't even know how to write the code...just to give you an idea of where i'm at in all this

my thoughts

sudo apt-get install linux-headers-`uname -r`

now i know that `uname1 is to be replaced by some header version that i have no idea what it is or where it is, but what about -r is that included or what...

i know this thread has been going on for awhile now but can somebody please help me get through this...i need to be babied through it..literally......any and all help is greatly appreciated

<chris

cgons
January 10th, 2007, 03:04 PM
ok well i realized that i needed to learn alittle about linux first so i did a little reading.....i can be more specific about whats going on now...so let me give this another shot...

i have a 1501 from dell with the 1490 wireless card

i reinstalled ubuntu with the boot parameters "noapic nolapic irqpoll"

i changed the bios setting to wireless "always on" hot key "disabled"

this is as far as i am right now because i ran into a problem...

when i used the command "sudo apt-get update" i realized im not connected to the internet. i am connected through a wire. before i reinstalled ubuntu the computer recongized my connection but now it doesn't any idea why??

paperdiesel
January 10th, 2007, 06:43 PM
ok well i realized that i needed to learn alittle about linux first so i did a little reading.....i can be more specific about whats going on now...so let me give this another shot...

i have a 1501 from dell with the 1490 wireless card

i reinstalled ubuntu with the boot parameters "noapic nolapic irqpoll"

i changed the bios setting to wireless "always on" hot key "disabled"

this is as far as i am right now because i ran into a problem...

when i used the command "sudo apt-get update" i realized im not connected to the internet. i am connected through a wire. before i reinstalled ubuntu the computer recongized my connection but now it doesn't any idea why??

No idea why, man. From the terminal, you can try a "sudo ifup eth0" to see if that works. Or try pinging your router to see if you have any connectivity at all. Did you look in system -> administration -> networking to make sure the wired connection is active?

cgons
January 11th, 2007, 03:18 PM
i got the internet to work it was the hotkey disabled....when i switched to enable it came back on.....anyway....so i partitioned my harddrive lastnight for a dual boot so i have xp installed to use wireless until i figure out how to get it runing in ubuntu......anyway so after a clean reinstall....i believe as of now this is the only problem im going to have i was ....but who knows

sudo apt-get update - downloads a whole bunch of updates
sudo apt-get build essential - E: Invalid operation build essentials

do i continue without this step?
what do i do with all the updates i downloaded, install all of them?

sudo apt-get install linux-header-`uname -r`

how exactly do i input this command into the CLI

i believe that should do it..................thanks for all your help

paperdiesel
January 11th, 2007, 07:32 PM
i got the internet to work it was the hotkey disabled....when i switched to enable it came back on.....anyway....so i partitioned my harddrive lastnight for a dual boot so i have xp installed to use wireless until i figure out how to get it runing in ubuntu......anyway so after a clean reinstall....i believe as of now this is the only problem im going to have i was ....but who knows

sudo apt-get update - downloads a whole bunch of updates
sudo apt-get build essential - E: Invalid operation build essentials

do i continue without this step?
what do i do with all the updates i downloaded, install all of them?

sudo apt-get install linux-header-`uname -r`

how exactly do i input this command into the CLI

i believe that should do it..................thanks for all your help

Read the guide a bit more carefully :). It's
sudo apt-get install build-essential. If that doesn't work, you need to edit your sources list to make sure you have all of the repositories enabled.

the uname-r works fine if you copy/paste from the how-to to the terminal. Those back-tics tell the system to execute the command uname -r inside your command string. Just copy/paste it will be fine.

You don't have to do anything with the updates -- they download and install themselves.

cgons
January 12th, 2007, 12:27 AM
yup that did it..i can't believe that was all because of a missed word....lol...anyway i'm all setup now thanks for the help....in a way i'm glad this happened..i learned some new tricks.....

chris

brotherajnin
January 13th, 2007, 11:24 PM
Help!!! I followed the steps on the first page to the point where I enter:

sudo ndiswrapper -l

and get:

Installed ndis drivers:
bcmwl5 driver present, hardware present

So good so far? And then I try sudo ndiswrapper -m and get:

modprobe config already contains alias directive

And then sudo modprobe ndiswrapper returns nothing... my wireless does not come on. I have tried modifying the BIOS settings... any suggestions? I've been trying to get this for a while now... thanks.

Hinde01
January 14th, 2007, 07:44 AM
Basically a new linux user here. I followed this howto and I was glad to see that my light lit up and when I used the iwlist command I saw my network:


eth1 Scan completed :
Cell 01 - Address: 00:06:25:F3:67:C9
ESSID:"Family_Room"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:59/100 Signal level:-58 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0


Tried to use the gui tools in the system pulldown and set the network icon in the top left of my screen to eth1 but I don't get any signal strength. I set the ethernet connection to disabled and enabled the wireless connection. I even took off wep (know I should be using wpa, but some family members devices don't have wpa) to see if that would help. No dice. I appreciate any help you guys can give, and please try to be explicit as possible.

paperdiesel
January 15th, 2007, 08:29 PM
Help!!! I followed the steps on the first page to the point where I enter:

sudo ndiswrapper -l

and get:

Installed ndis drivers:
bcmwl5 driver present, hardware present

So good so far? And then I try sudo ndiswrapper -m and get:

modprobe config already contains alias directive

And then sudo modprobe ndiswrapper returns nothing... my wireless does not come on. I have tried modifying the BIOS settings... any suggestions? I've been trying to get this for a while now... thanks.

If you're getting that modprobe error that says it already contains the alias directive, then that tells me you've been trying other methods before you came to this how-to. There's no telling what you did to your network/ndiswrapper settings before, so I recommend you to a complete uninstall of the ndiswrapper modules. See earlier posts in this thread on how to do that. Then start totally over once you've COMPLETELY wiped all ndiswrapper files off of your system. Make sure you get absolutely all of it.

paperdiesel
January 15th, 2007, 08:33 PM
Basically a new linux user here. I followed this howto and I was glad to see that my light lit up and when I used the iwlist command I saw my network:


eth1 Scan completed :
Cell 01 - Address: 00:06:25:F3:67:C9
ESSID:"Family_Room"
Protocol:IEEE 802.11b
Mode:Managed
Frequency:2.437 GHz (Channel 6)
Quality:59/100 Signal level:-58 dBm Noise level:-96 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
Extra:atim=0


Tried to use the gui tools in the system pulldown and set the network icon in the top left of my screen to eth1 but I don't get any signal strength. I set the ethernet connection to disabled and enabled the wireless connection. I even took off wep (know I should be using wpa, but some family members devices don't have wpa) to see if that would help. No dice. I appreciate any help you guys can give, and please try to be explicit as possible.

It's probably a managed/open/restricted issue. Make sure that your router and your wireless card are matched -- either open, managed, restricted, etc. I also recommend that you do NOT use ubuntu's built-in network manager. Use network-manager or wifi radar instead.

Finally, and this goes for everyone, please do NOT vote for the poll option "this almost worked, but I'm not quite there yet" if your wireless is indeed working. This guy's post is a good example -- linux is recognizing his wireless card properly and successfully returns scanned networks. In this case, the vote should be for "this worked on my laptop!", even though he hasn't figured out his correct wireless settings to connect to a given network.

brotherajnin
January 17th, 2007, 12:22 AM
Thanks for your patience. I redid all the steps exactly as on the first page, however it is still not working. On the step where we 'sudo make uninstall' I received:

NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.

I kept running the command but kept getting the same "note" so I continued. When I enter sudo ndiswrapper -l I recieve:

bcmwl5 : driver installed
device (14E4:4311:1028:0007) present
device (14E4:4311) present

Which is different than what I got b4, but the wireless light does not come on, etc.. Any suggestions? Thanks again.

paperdiesel
January 17th, 2007, 06:18 AM
Thanks for your patience. I redid all the steps exactly as on the first page, however it is still not working. On the step where we 'sudo make uninstall' I received:

NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.

I kept running the command but kept getting the same "note" so I continued. When I enter sudo ndiswrapper -l I recieve:

bcmwl5 : driver installed
device (14E4:4311:1028:0007) present
device (14E4:4311) present

Which is different than what I got b4, but the wireless light does not come on, etc.. Any suggestions? Thanks again.

Well I'm a little concerned about the fact that you get two lines of devices present. Are you sure you did everything possible to uninstall? This includes the sudo make uninstall, the apt-get removes, and even manually deleting any entries in /etc/modprobe.d/ndiswrapper, /etc/network/ndiswrapper, or any other ndiswrapper directories (I can't remember them all.. do a locate).

Anyway, my next question is, after you did the ndiswrapper commands, did you do a modprobe? You need that modprobe to kick the driver in to action.

brotherajnin
January 17th, 2007, 10:03 PM
In short, I backed up my files, reinstalled Ubuntu (probably unnecessary), followed the instructions once again, and this time it worked!! Thanks for helping out.

pissedoffdude
January 18th, 2007, 09:11 PM
Would this howto work if i had a compaq laptop instead of a dell? I have the same wireless card.

suhaib_
January 19th, 2007, 09:21 AM
Hello everyone
I tried running your procedure for intslling wireless card; but nothing happens. I tried multiple times and also from other sources but to no effect. Can anyone help me personally sort out this problem. I am using this laptop as desktop machine till now, cant carry it to the school because of this stupid wireless card.

suhaib_
January 19th, 2007, 09:23 AM
sudo ndiswrapper -l
bcmwl5 : invalid driver!

suhaib_
January 19th, 2007, 09:32 AM
sudo ndiswrapper -i bcmwl5.inf
driver bcmwl5 is already installed


I get this message when I try to install driver. I dont know if I need to remove this driver first. If I have, whats the easiest way to uninstall it

paperdiesel
January 19th, 2007, 09:39 AM
sudo ndiswrapper -i bcmwl5.inf
driver bcmwl5 is already installed


I get this message when I try to install driver. I dont know if I need to remove this driver first. If I have, whats the easiest way to uninstall it

A big problem that ubuntu users have when troubleshooting wireless issues is the fact that there are so many different how-tos out there, and most of them don't work. So when someone tries any particular method, their system is usually pretty fowled-up from the previous attempts. As such, even good how-tos will not work because they're assuming a clean system.

In your case, I think this holds true. You need to completely wipe your system of all ndiswrapper and bcm43xx work. I've made several posts in this thread that discuss ways to clean your system. Go back and read them. Or, it might be easier just to reinstall ubuntu and come straight to this how-to. Either way, your system is obviously in a state of chaos from previous attempts to get the wireless to work, and needs to be cleaned before you try again.

alaw005
January 19th, 2007, 09:54 AM
This worked on my Marvell 88w8335 wireless but substituting drivers from cd. I had almost given up!

xdata666
January 22nd, 2007, 09:35 PM
I just wanna give a big thank you for posting this guide. Just got my 1501's wireless working :3 cheers!

A Silver Mt Zion
January 23rd, 2007, 02:37 AM
It works now, but I can only manually edit the ESSID, otherwise it does not work at all. Any suggestions?

--------------------------------



I completed the entire how-to and got to the point where my wi-fi light is on, however, even after enabling the wireless on system > admin > networking, it does not work.

I think this might be because when I got to the step where you type in 'sudo make uninstall' I got an "Error 1" and it said that it could not uninstall one of the files because it was a directory. I found the file and tried to delete it myself but I was unable to, it said access denied.

/lib/modules/2.6.17-10-generic/kernel/drivers/net/ndiswrapper

Above is the file which I could not delete. I tried every manner of getting rid of it, but all failed. I decided to just keep going with the how-to because I did not know what else to do. Now, as I said, the light is on but it is not working. The above is the only thing that differed from the directions.

Any help would be greatly appreciated.

juniperbends
January 25th, 2007, 01:02 AM
I followed the (wonderful) directions all the way through, and basically had the same problem as the post above me. My wifi did work, even though I had to type in the ESSID manually every time. Now all of a sudden the wireless does not work at all, though I have the right ESSID typed in, the light is on, the connection properties say that the signal strength is 100%, and everything appears to be in order. I even disconnected the router and the computer picked up that it was disconnected, and yet when I connect it back Firefox still will not work.

Does anyone have any ideas?

dutchmega
January 25th, 2007, 11:17 AM
Thanks, this worked!

However, iwconfig tells me that power management is off, how do I enable it automatically on boot?
(Run 'sudo iwconfig wlan0 power' on when laptop runs on batterij?)

paperdiesel
January 25th, 2007, 04:19 PM
I followed the (wonderful) directions all the way through, and basically had the same problem as the post above me. My wifi did work, even though I had to type in the ESSID manually every time. Now all of a sudden the wireless does not work at all, though I have the right ESSID typed in, the light is on, the connection properties say that the signal strength is 100%, and everything appears to be in order. I even disconnected the router and the computer picked up that it was disconnected, and yet when I connect it back Firefox still will not work.

Does anyone have any ideas?

What do you mean by manually editing the ESSID? Manually putting in your /etc/network/interaces file? Or in the places->admin->network menu?

I highly recommend using network-manager or wifi-radar to manage your networks. And remember, when you use those tools, you need to manually edit your /etc/network/interfaces file before those tools will work. They provide easy instructions on how to do this.

Finally, when you're connected and the light is on, do a "sudo ifconfig" to see if you're getting an IP address. Also, try pinging your router (usually ping 192.168.0.1), then try pinging google (ping google.com). Let me know what the outputs are.

discord
January 26th, 2007, 04:55 AM
look here got it working and with network manager!

https://launchpad.net/ubuntu/+source/ndiswrapper/+bug/59983

mrjyg
January 28th, 2007, 08:43 AM
I couldn't get it to work using the ndiswrapper approach here. Followed every step, but:

My SSID is not broadcasted, and it shows all of my neighbors' wireless networks except mine.
Once I broadcast the SSID, it picked it up, but failed to associate. I am using WPA2 and G.Finally I got it to work using the stock bcm43xx driver and the bcm43xx-fwcutter approach:

Do not install the bcm43xx-fwcutter from Ubuntu ... download the latest bcm43xx-fwcutter source (006 at time of writing) from http://bcm43xx.berlios.de/, extract, then 'make; make install'.
Download the v3 firmware from Dell (R102318.EXE), the download URL is available in the bcm43xx-fwcutter source tree's README.
Extract the EXE and get the bcmwl5.sys: mkdir t; cd t; unzip -a ../R102318.EXE; mv bcmwl5.sys ..; cd ..; rm -rf t
Cut out the firmware and move to /lib/firmware/: bcm43xx-fwcutter bcmwl5.sys; mv bcm43xx*.fw /lib/firmware/
Make sure bcm43xx is not blacklisted: grep -v bcm43xx /etc/modprobe.d/blacklist > /tmp/blacklist; cat /tmp/blacklist > /etc/modprobe.d/blacklist; rm -f /tmp/blacklist
Load the module ('modprobe bcm43xx') and observe /var/log/messages ... you should not see errors from bcm43xx about failed to load firmware.
Use whatever tools to configure / manage your wireless link ... I use wpa_supplicant (not anything fancy like network manager) ... I prefer things that I can easily manage through makefiles and commands. The driver name for wpa_supplicant is wext. Other than that, my wpa_supplicant.conf is identical to what I used on another Ubuntu 6.10 platform (Dell 700m w/ ipw2200 which I have a thread on this forum).I'm writing this w/ the stock Ubuntu 6.10 and the above fix ... my wireless router is back to stealth mode w.r.t. not broadcasting SSID, and I'm glad I can finally replace the Dell 700m that has been my main Linux development platform in the past two years ...

paperdiesel
January 28th, 2007, 09:02 AM
I couldn't get it to work using the ndiswrapper approach here. Followed every step, but:

My SSID is not broadcasted, and it shows all of my neighbors' wireless networks except mine.
Once I broadcast the SSID, it picked it up, but failed to associate. I am using WPA2 and G.
So you're saying this how-to DID work. Again, you didn't read what I said earlier about this how-to. This is for getting people's wireless cards recognized in ubuntu. Whatever anecdotal problems you have with your wireless network's encryption is beyond the scope of this how-to. I'm assuming by what you wrote that this how-to succeeded in getting your wireless nic recognized in ubuntu.

Moreover, if you turned off the ESSID broadcast on your router, then it is working PROPERLY if your network does not show up in a scan. I don't see why you listed this as a problem of this guide.


Finally I got it to work using the stock bcm43xx driver and the bcm43xx-fwcutter approach:

Do not install the bcm43xx-fwcutter from Ubuntu ... download the latest bcm43xx-fwcutter source (006 at time of writing) from http://bcm43xx.berlios.de/, extract, then 'make; make install'.
Download the v3 firmware from Dell (R102318.EXE), the download URL is available in the bcm43xx-fwcutter source tree's README.
Extract the EXE and get the bcmwl5.sys: mkdir t; cd t; unzip -a ../R102318.EXE; mv bcmwl5.sys ..; cd ..; rm -rf t
Cut out the firmware and move to /lib/firmware/: bcm43xx-fwcutter bcmwl5.sys; mv bcm43xx*.fw /lib/firmware/
Make sure bcm43xx is not blacklisted: grep -v bcm43xx /etc/modprobe.d/blacklist > /tmp/blacklist; cat /tmp/blacklist > /etc/modprobe.d/blacklist; rm -f /tmp/blacklist
Load the module ('modprobe bcm43xx') and observe /var/log/messages ... you should not see errors from bcm43xx about failed to load firmware.
Use whatever tools to configure / manage your wireless link ... I use wpa_supplicant (not anything fancy like network manager) ... I prefer things that I can easily manage through makefiles and commands. The driver name for wpa_supplicant is wext. Other than that, my wpa_supplicant.conf is identical to what I used on another Ubuntu 6.10 platform (Dell 700m w/ ipw2200 which I have a thread on this forum).I'm writing this w/ the stock Ubuntu 6.10 and the above fix ... my wireless router is back to stealth mode w.r.t. not broadcasting SSID, and I'm glad I can finally replace the Dell 700m that has been my main Linux development platform in the past two years ...

I'm not sure why you've decided to post your own little how-to in this one. Especially considering how hard to read that is. Also, you didn't say anything about what you tried to get your WPA2 to work. Was it using ubuntu's back-end wireless tools? Or the default ubuntu wireless GUI? Or network-manager or wifi-radar? What approaches did you take before you gave up and went to a different method?

Sigh.

mrjyg
January 28th, 2007, 09:11 AM
I'm sorry if you see it this way. I'm not trying to say this thread is not helpful ...

I don't intend to start a flame here so please take my answers to your questions as clarifications so that others may find helpful:

Getting the card recognized is not useful if it does not work with hidden SSID and/or use of WPA/WPA2 (not WEP). What good would this card do if it can only get onto my neighbor's network, suppose I can find an open one?
If necessary, I can expand the approach of using bcm43xx-fwcutter into a full thread ... it's late and I was lazy. Other than not spelling out the details of the wpa_supplicant usage, I think I have provided enough info to get a WORKING environment in place.
I understand that others may like to use network manager etc. to manage the network links. This is why I did not provide details on wpa_supplicant usage ... but I did mention the same wpa_supplicant.conf file content as I provided in another thread on Dell 700m ipw2200 (search for my authorship, 'mrjyg').I do like Ubuntu for its community support. Only trying to help ... no hard feelings please.

paperdiesel
January 28th, 2007, 05:31 PM
I'm sorry if you see it this way. I'm not trying to say this thread is not helpful ...

I don't intend to start a flame here so please take my answers to your questions as clarifications so that others may find helpful:

Getting the card recognized is not useful if it does not work with hidden SSID and/or use of WPA/WPA2 (not WEP). What good would this card do if it can only get onto my neighbor's network, suppose I can find an open one?

Look, I'm really not interested in your opinion of the usefulness of this how-to. You did not answer my questions about which approaches you took before writing-off ndiswrapper. That bothers me because other people could read what you wrote and assume it's not possible to get their wireless working if they want to use WPA2. I know for a fact that hidden SSIDs, G and WPA work perfectly using ndiswrapper. Why don't you go in to full detail about your exhaustive attempts with ndiswrapper before you tried another method? I'm willing to bet that your attempt was not comprehensive, and it is indeed possible to get WPA2 and G working in your specific case. But it's academic at this point since you're already connected and happy.

Also, I suppose I have to say this again, this how-to makes no claims about getting people connected to networks. While I strive to provide support for those issues, I can only claim to get the wireless nic working. And your wireless nic DID work using ndiswrapper in your case. That is a fact.



If necessary, I can expand the approach of using bcm43xx-fwcutter into a full thread ... it's late and I was lazy. Other than not spelling out the details of the wpa_supplicant usage, I think I have provided enough info to get a WORKING environment in place.
I understand that others may like to use network manager etc. to manage the network links. This is why I did not provide details on wpa_supplicant usage ... but I did mention the same wpa_supplicant.conf file content as I provided in another thread on Dell 700m ipw2200 (search for my authorship, 'mrjyg').I do like Ubuntu for its community support. Only trying to help ... no hard feelings please.

No hard feelings, and I'm happy that you're trying to help. If you found a method that works and you want to share it, that's wonderful. It's what ubuntu is all about. But don't come in to this thread, give some nebulous claim like "this doesn't work for WPA2", back it up with absolutely zero evidence nor examples, then write your own mini how-to inside this thread. Help out by posting your own how-to and support the users who wish to try it.

mrjyg
January 28th, 2007, 09:21 PM
OK I see where you are coming from ... yes I know the feeling when someone just comes on and say it didn't work (I have a Dell 700m ipw2200 thread where I posted a poll w/ people just vote no so I do understand).

Here is what I tried with your instructions and ndiswrapper + wpa_supplicant:
- Followed your instructions.
- Tried bcmwl5.inf / .sys from three different versions from Dell (one v3 which is what I mentioned in my "little fix", two v4 including the latest one that's what you mentioned in your original posting).
- Tried upgrade ndiswrapper and wpa_supplicant (made sure it's installed under /sbin and /usr/sbin/, not /usr/local/sbin, BTW).
- Tried almost combinations of wpa_supplicant.conf tunable paremeters (it's very possible I missed a few combinations): ap_scan (0, 1, 2), BSSID (specify or comment out), scan_ssid (0, 1), starting with the working version I use on my Dell 700m Ubuntu 6.10 (see my thread on that http://ubuntuforums.org/showthread.php?p=1739259) (http://ubuntuforums.org/showthread.php?p=1739259%29).
- Tried using either wext or ndiswrapper (yes uncomment that .config thing to build the support into ndiswrapper), per http://ndiswrapper.sourceforge.net/mediawiki/index.php/WPA
- Went back, cleaned up, tried the above again, trusting that I must have overlooked something.

I use /etc/wpa_supplicant.conf and /etc/network/interfaces to drive my network setup. Admittedly I didn't try Network Manager, etc. because I have a working scheme in place w.r.t. the use of my profile-switcher init script and PROFILE= kernel boot cmdline (http://ubuntuforums.org/showthread.php?t=2968088) (http://ubuntuforums.org/showthread.php?t=296808%29). Maybe that makes some difference, maybe not.

Suggestions / help always welcome on things I can try w/ the ndiswrapper approach as I think this would be the best approach given the unstable nature of bcm43xx device driver for Dell 1390 support (although it works for me now, I have not used it long enough).

One thing I do like to emphasize w.r.t. my "little fix", aka the bcm43xx approach: you need to provide firmware cut from the Windows bcmwl5.sys to use this Linux module ... if you just modprobe this driver without any firmware prepared for it, it wouldn't do anything for you. Maybe I will start another thread on this specific approach.

mueller2004
February 1st, 2007, 06:27 AM
I am having the same problem I think...

sudo ndiswrapper -l
Installed drivers:
bcmwl5 driver installed, hardware present

sudo ndiswrapper -m
modprobe config already contains alias directive

This is were I am having trouble:

sudo modprobe ndiswrapper
FATAL: Could not open '/lib/modules/2.6.17-10-386/kernel/drivers/net/ndiswrapper/ndiswrapper.ko': No such file or directory
are you having a similar problem?

mueller2004
February 1st, 2007, 06:30 AM
I am having the same problem I think...

sudo ndiswrapper -l
Installed drivers:
bcmwl5 driver installed, hardware present

sudo ndiswrapper -m
modprobe config already contains alias directive

This is were I am having trouble:

sudo modprobe ndiswrapper
FATAL: Could not open '/lib/modules/2.6.17-10-386/kernel/drivers/net/ndiswrapper/ndiswrapper.ko': No such file or directory
are you having a similar problem?

dp_wiz
February 1st, 2007, 10:24 AM
Newest kernel in feisty works after supplying correct firmware.

71CH
February 1st, 2007, 11:32 PM
Hello
I am a complete noob with this and this thread has been great to me so far. I am at this point of the tutorial:

STEP 3: COMPILE PROGRAM

Now we'll complile the Ndiswrapper program. In a terminal, go to the directory where you extracted ndiswrapper and execute the following:

and I can't seem to get it going. When I type in the 'sudo' thing it gives me an error. How do I go to the directory where I extracted ndiswrapper from the terminal?

Thank you for any help.

71CH
February 2nd, 2007, 12:33 AM
OK
I actually figured out my initial problem and got to step 4. However when I tried to do this "sudo ndiswrapper -i bcmwl5.inf" it tells me that the driver is already installed. When I do the next command "sudo ndiswrapper -l" it tells me that the driver is invalid. What should I do? Thanks for any help.

st33med
February 2nd, 2007, 02:46 AM
71CH, you want to remove the old driver. Input this in the terminal:


sudo ndiswrapper -e bcmwl5

If it responds that you cannot do that, put in the terminal "sudo -s" and retype the above code again, but without the 'sudo' in the code.

st33med
February 2nd, 2007, 02:52 AM
mueller2004: you double posted!! But no matter. I'm having the same problem.

71CH
February 2nd, 2007, 04:57 PM
I think I did everything correctly.
I also installed wifi radar and I see that the networks that should be detected are there.
Does this mean that I did all the steps correctly?
I ask this because I still cannot seem to connect to the internet wirelessly.
Thanks for any help.

ryaaan
February 4th, 2007, 07:28 PM
I just picked up this laptop about a month ago. I didn't have to compile any extra drivers.

I simply opened the Network Connection screen on a virgin install, and typed "eth1" into the network interface "Name:" field. The wireless signal strength bar came up, and I clicked configure. The options were all available (in the gui) to enable the interface and get hooked up to my wireless.

Did anyone else find that they didn't need to install ndiswrapper or any drivers?

~Ryan

st33med
February 4th, 2007, 11:38 PM
Ummm... You might have an Intel Wireless card. It's a bit different. Note this only applies to E1505 computers with a Broadcom wireless card.

As for me, I still need help because the ndiswrapper reports that ndiswrapper.ko does not exist.

heiNey
February 5th, 2007, 07:06 AM
hi, i was wondering if someone could help me with this....i followed all the steps int he how to and it looks like it was installed correctly

i did a 'sudo iwlist scanning'

wlan0 Scan completed :
Cell 01 - Address: 00:13:46:0B:99:9C
ESSID:"linksys"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.412 GHz (Channel 1)
Quality:42/100 Signal level:-69 dBm Noise level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0

and it detected the network in my house

i also installed wifi radar and it shows up in the list, and i configured it with the WEP key, but it still wont connect...any ideas? please help!

i have a E1505 with a Dell Wireless 1500 Draft 802.11n Wireless Mini-Card, and it looks like it uses the same driver as the 1390, so i figured it should work using the same how to...if anyone could give me some ideas, please let me know...im a complete linux n00b and would really like to get this working asap

the card is also unrecognized by dapper:

@e1505:~$ lspci | grep -i network
0000:0b:00.0 Network controller: Broadcom Corporation: Unknown device 4328 (rev 01)

ritesh
February 9th, 2007, 10:52 PM
Hi All,
First of all heartiest thanks to paperdiesel .....after struglling for month i was finally able to configure my wireless internet connection.

My system is Dell Inspiron E1505, 256 MB ATI mobility radeon X1400 hypermemory, Integrated 10/100 network card and modem, dell wireless 1390 802.11b/g minicard(54Mbps.....)

My problem is....when i configured the wireless connection through ndiswrapper I was using my University wireless internet service and is connecting to that........but in my apt(home) I have AT&T yahoo DSL broadband connection wireless.....and now i am not able to connect it to my apt internet connection......
network manager is showing my internet connection and when i choose the option and enter the network key...it is not connecting....
what is the difference between hexadecimal and ascii option as my network key is purely number no character......

please help
thanks
ritesh

loismustdie
February 10th, 2007, 02:43 PM
Hey, I followed this guide a few months ago, and it was actually one of the more important docs that helped me make the decision to go linux only. so thanks to the original author.

but i have a new problem. last night, i left my laptop on to play some music as i went to bed. apparently, at some point during the night, my dog must have kicked the plug, and the laptop switched over to battery. well, i woke up and it was dead this morning. when i cut it back on, the wireless wasn't working.

so i went back and did the last step when i originally followed this guide. when i run this:

derrick@derrick-laptop:~$ sudo modprobe ndiswrapper

i get this:

derrick@derrick-laptop:~/Wireless/DRIVER$ sudo modprobe ndiswrapper
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper/ndiswrapper.ko): Invalid argument
derrick@derrick-laptop:~/Wireless/DRIVER$ iwlist scanning


i've not tried just simply restarting yet, but i was curious as to what could have caused this.

atact88
February 11th, 2007, 03:29 PM
Does this HOWTO assume that the wireless card is detected and all that? I remember running a command (I forget which) to list devices, and I get 2 - one is the Broadcom ethernet, and 1 is categorized as


0000:0c:00.0 Network controller: Broadcom Corporation: Unknown device 4311 (rev 01)
. If I remember correctly, this command was a grep command.

Will this have any effect on following the HOWTO? Thanks

maleko
February 11th, 2007, 07:22 PM
i get this:

derrick@derrick-laptop:~/Wireless/DRIVER$ sudo modprobe ndiswrapper
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper/ndiswrapper.ko): Invalid argument
derrick@derrick-laptop:~/Wireless/DRIVER$ iwlist scanning


i've not tried just simply restarting yet, but i was curious as to what could have caused this.

Same thing happening here. Wi-fi was working fine until update to 2.6.17.11 and reboot. Now wi-fi light is lit but no connection. Must be a problem with the update and ndiswrapper. I had everything working (finally) and now this. Damn!

martinluther
February 12th, 2007, 04:42 PM
Hello to all here. I have registered to just say thank you to PaperDiesel and others for their help in getting my wireless networking going on my lDell Inspiron 1501 64bit aptop. I am a SUSE user, but the information contained in this thread was perfect. Particularly Jason, who had mentioned the 64bit issue - that solved my problem getting wireless working! Props to all who contributed to this thread. It is most appreciated.:KS :KS :KS

dbpack
February 13th, 2007, 12:42 AM
First, thanks for posting these instructions!

Now, on to my problem...
I have followed all the steps, used the driver listed on the ndisdriver website for my card, blacklisted bcm43xx, installed the latest version of ndiswrapper, turned off hotkey and kept wireless always on in the BIOS, etc, etc.
BUT, when I modprobe ndiswrapper, here is the error I'm getting:

root@1[/]# dmesg | grep ndiswrapper
[17179585.032000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
[17179585.160000] ndiswrapper (import:239): unknown symbol: ntoskrnl.exe:'IoGetDeviceObjectPointer'
[17179585.160000] ndiswrapper (import:239): unknown symbol: ntoskrnl.exe:'MmFreeContiguousMemorySpecifyCache'
[17179585.160000] ndiswrapper (import:239): unknown symbol: ntoskrnl.exe:'MmAllocateContiguousMemorySpecifyCac he'
[17179585.160000] ndiswrapper (import:239): unknown symbol: ntoskrnl.exe:'MmGetPhysicalAddress'
[17179585.160000] ndiswrapper (import:239): unknown symbol: ntoskrnl.exe:'strrchr'
[17179585.164000] ndiswrapper (load_sys_files:218): couldn't prepare driver 'bcmwl5'
[17179585.164000] ndiswrapper (load_wrap_driver:112): loadndiswrapper failed (65280); check system log for messages from 'loadndisdriver'


Any ideas??
Thanks in advance.
-Dave

Phil_McCrackin
February 14th, 2007, 09:11 AM
I've been working on this all day and traversed this thread (and others all day) and still no Internet.

I have a Dell Inspiron 1501, Turion64 x2. and I've installed Ubuntu 6.10

I have followed this tutorial to the letter. Everything has installed perfectly. My wifi light is on and scanner returns a pluthera of networks (including my own), but I cannot connect. I am guessing at this point it is a network setting config that I have butchered.

My router is set to use a WPA key. I have mac filtering but have made certain that both WLAN and LAN mac addresses are on the list. router is the DHCP server and there are plenty of IPs left to dole out.

Ubuntu network settings: wireless connection is enabled. the location is blank and I am unable to select or type in the field???. in properties, I have entered the SSID and the key properly (set to ASCII) and configuration is auto (DHCP).

Once again the driver was installed flawlessly and my card is scanning and detecting all of the area networks.

If there is any information that I could give that might give someone some insight and help me resolve this, I would be eternally grateful. This is my last stand and without wifi, this notebook is pretty much useless to me. (and I really don't want to re-install windows)

EDIT (Update): I have added WiFi Radar. It detects all of the area signals (quite well actually). I configured it: mode-auto, channel-auto, inserted key, security-restricted.
I use WPA TKIP on my router and I don't know if that may be the issue or not. In the profile on WiFi Radar, under use WPA Driver, I am not sure what or if to put anything here.

I have also tried to connect throut a completely vulnerable wap nearby that I know is easy (I have connected before and they have no security whatsoever. they have all of the factory defaults set). and still cannot connect.

Any ideas??? Anyone?...

Phil_McCrackin
February 15th, 2007, 05:06 AM
I am finally connected to my home network! Many thanks to paperdiesel for this howto. I hope I will be able to contribute to the community in similar fashion someday.

It seems my issue was part network config settings, but the major part was disabling the wired LAN. I also installed xsupplicant since I have my router config'd to use WPA.

I still am unable to use WiFi Radar which would be ideal. I can view all of the networks there, but cannot connect through it (even my own network). This is something I hope I can work out soon.

EDIT:

OK, I give! After a reboot, I cannot connect any longer. I checked network settings and wired connection was enabled again. I disabled it and tried to connect wirelessly again with no success. I checked network settings again, and lo and behold wired connection was enabled again. IT RE-ENABLES ITSELF! Wow! After 3 days of working on this 'till the wee hours, I have to call it quits. I have other things to do. I will re-install the resource hogging suck-*** Vista and get on with it. At least I know my basic functions will work (after the 30 security messages asking me if I'm sure I want to do something).

To date IMO as a desktop client, Linux rocks and Ubuntu is bar none the best distro
As a server, it rocks
As a laptop OS, needs a lot of work before I would attempt this again. Seems to be lacking a lot of really basic functionality and even when something does work, you have to jump through so many hoops to get it to work and then is unreliable (re-installing drivers after kernel upgrade). Without reliable wifi, a laptop is just a weak, portable desktop.

Thank you paperdiesel for your efforts and congrats to those who had success.

TheDamned
February 19th, 2007, 04:15 AM
I followed this guide and at the sudo ndiswrapper -i bcml5.inf line in the tutorial I get driver bcmwl5 is already installed... I did all the previous steps.

Help anyone, thanks.

paperdiesel
February 19th, 2007, 09:06 PM
I followed this guide and at the sudo ndiswrapper -i bcml5.inf line in the tutorial I get driver bcmwl5 is already installed... I did all the previous steps.

Help anyone, thanks.

This is probably because you've tried other methods to get wireless working. You need to either reinstall ubuntu or undo all of the changes you've made in all of the attempts to get wireless working. The former method is easiest, but if you want to manually clean your system, see the posts earlier in this thread about how to clean your system.

paperdiesel
February 19th, 2007, 09:11 PM
I am finally connected to my home network! Many thanks to paperdiesel for this howto. I hope I will be able to contribute to the community in similar fashion someday.

It seems my issue was part network config settings, but the major part was disabling the wired LAN. I also installed xsupplicant since I have my router config'd to use WPA.

I still am unable to use WiFi Radar which would be ideal. I can view all of the networks there, but cannot connect through it (even my own network). This is something I hope I can work out soon.

EDIT:

OK, I give! After a reboot, I cannot connect any longer. I checked network settings and wired connection was enabled again. I disabled it and tried to connect wirelessly again with no success. I checked network settings again, and lo and behold wired connection was enabled again. IT RE-ENABLES ITSELF! Wow! After 3 days of working on this 'till the wee hours, I have to call it quits. I have other things to do. I will re-install the resource hogging suck-*** Vista and get on with it. At least I know my basic functions will work (after the 30 security messages asking me if I'm sure I want to do something).

To date IMO as a desktop client, Linux rocks and Ubuntu is bar none the best distro
As a server, it rocks
As a laptop OS, needs a lot of work before I would attempt this again. Seems to be lacking a lot of really basic functionality and even when something does work, you have to jump through so many hoops to get it to work and then is unreliable (re-installing drivers after kernel upgrade). Without reliable wifi, a laptop is just a weak, portable desktop.

Thank you paperdiesel for your efforts and congrats to those who had success.

I think you're making this too complicated. Just use network-manager to manage all of your network connections. And, for pete's sake, READ THE DOCS for network-manager.. particularly the part about commenting-out your network connections in /etc/network/interfaces.

As far as ditching linux for vista.. that's your choice. But keep in mind -- it's not "linux's" fault that your wireless doesn't work as well as it does in windows. Maybe you should send an Email to Dell (or whoever is responsible) and encourage them to either make linux drivvers or open their source. Broadcom refuses to work with Linux for driver support. It's people writing drivers for free on their spare time that makes it possible at all. And if it takes me an extra few minutes to enable my drivers to work in Linux, it's well worth it. But that's just me.

paperdiesel
February 19th, 2007, 09:17 PM
Same thing happening here. Wi-fi was working fine until update to 2.6.17.11 and reboot. Now wi-fi light is lit but no connection. Must be a problem with the update and ndiswrapper. I had everything working (finally) and now this. Damn!

This is one weakness of using this method. Whenever you upgrade your kernel version, you'll have to re-compile ndiswrapper. Here's a quick and easy way to do it, but MAKE SURE you use your exact directory names, NOT the ones I use in this example:


sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5
cd ndiswrapper-1.28
sudo make uninstall
sudo make uninstall
sudo make uninstall
sudo make
sudo make install
cd DRIVER
sudo ndiswrapper -i bcmwl5.inf
sudo ndiswrapper -m
sudo modprobe ndiswrapper


Again, make sure that the ndiswrapper directory is whatever is on your system, and the DRIVER directory is wherever you extracted the wireless drivers from Dell.

Phil_McCrackin
February 19th, 2007, 11:06 PM
I think you're making this too complicated. Just use network-manager to manage all of your network connections. And, for pete's sake, READ THE DOCS for network-manager.. particularly the part about commenting-out your network connections in /etc/network/interfaces.
I appreciate the reply, but this is not my first computer, or my first Linux install. I have had Ubuntu installed on my desktop for 2 years now. I did read the docs and initially tried just using the network manager all with no success. [/QUOTE]



As far as ditching linux for vista.. that's your choice. But keep in mind -- it's not "linux's" fault that your wireless doesn't work as well as it does in windows. Maybe you should send an Email to Dell (or whoever is responsible) and encourage them to either make linux drivvers or open their source. Broadcom refuses to work with Linux for driver support. It's people writing drivers for free on their spare time that makes it possible at all. And if it takes me an extra few minutes to enable my drivers to work in Linux, it's well worth it. But that's just me.

Easy there big fella. No need to defend all of Linux. I am not attacking Linux. I rather enjoy it. I have had it installed on one of my desktops for 2 years and like it. I was disappointed that I had to go with the MS install, but I need the laptop for work. I simply have more productive ways to spend my time than installing and re-installing an operating system to get a driver to work. Its not Dell's or Broadcom's fault. If I were that concerned about setting up Ubuntu on my laptop, I would have bought one without known issues. It' good you have a productive venue to channel your extra time and energy on.

Once again, thank you paperdiesel for your time and efforts.

paperdiesel
February 21st, 2007, 09:08 PM
I appreciate the reply, but this is not my first computer, or my first Linux install. I have had Ubuntu installed on my desktop for 2 years now. I did read the docs and initially tried just using the network manager all with no success.

Easy there big fella. No need to defend all of Linux. I am not attacking Linux. I rather enjoy it. I have had it installed on one of my desktops for 2 years and like it. I was disappointed that I had to go with the MS install, but I need the laptop for work. I simply have more productive ways to spend my time than installing and re-installing an operating system to get a driver to work. Its not Dell's or Broadcom's fault. If I were that concerned about setting up Ubuntu on my laptop, I would have bought one without known issues. It' good you have a productive venue to channel your extra time and energy on.

Once again, thank you paperdiesel for your time and efforts.

Sigh. Look, there's no need to be patronizing. I never made any assumptions about your apititude in ubuntu, and I'm certainly not defending "all of linux". If you recall, it was YOU who brought up the Vista vs. Linux issue when you decided you were giving up on trying to get the wireless to work. The point I was trying to address was that it's not Linux's fault that wireless is such a pain. Instead, it's more the fault of the chipset manufacturers and vendors who refuse to work with anyone not using Windows.

I decided to articulate that point hoping that others who are similarly frustrated with the state of wireless in linux might actually do something about it instead of whining back to the linux community -- calling or writing the chipset manufacturers is a great place to start. Another great idea is to only purchase wireless products from manufacturers that support linux and/or open source. I realize that Dell limits your choices, but it wouldn't hurt to drop them an Email and ask that they offer more vender choices due to lack of driver support.

st33med
February 21st, 2007, 11:12 PM
My wifi will not connect and ndiswrapper -l states:

root@andrew-laptop:~# ndiswrapper -l
bcmwl5 : driver installed
device (14E4:4311) present (alternate driver: bcm43xx)

Help?

paperdiesel
February 22nd, 2007, 08:18 AM
My wifi will not connect and ndiswrapper -l states:

root@andrew-laptop:~# ndiswrapper -l
bcmwl5 : driver installed
device (14E4:4311) present (alternate driver: bcm43xx)

Help?

What brand and version laptop are you using? What kind of wireless card is inside? What is the output from your lspci command?

M_N_M74
February 22nd, 2007, 05:46 PM
Ok up to this point I'm doing fine. I ge to the point of using the make commands, but I can not get to the directory that ndiswrapper is contained in, I keep getting the following error.
bash: ndiswrapper-1.32rcl: No such file or directory.

I have two such directories..one on the desktop and one in the home folder both give me the same error....Help!!!

Also how does one log in as root in edgy?

st33med
February 22nd, 2007, 09:04 PM
What brand and version laptop are you using? What kind of wireless card is inside? What is the output from your lspci command?

It is Dell E1505 and it is the same as the title (Broadcom 1390 WLAN). As for lspci:

0b:00.0 Network controller: Broadcom Corporation Unknown device 4311 (rev 01)

paperdiesel
February 23rd, 2007, 06:00 AM
It is Dell E1505 and it is the same as the title (Broadcom 1390 WLAN). As for lspci:

0b:00.0 Network controller: Broadcom Corporation Unknown device 4311 (rev 01)


Did you try toggling your wireless key? Or, did you set your wireless to always on/hotkey disabled in the bios? See earlier posts for help.

paperdiesel
February 23rd, 2007, 11:15 PM
Ok up to this point I'm doing fine. I ge to the point of using the make commands, but I can not get to the directory that ndiswrapper is contained in, I keep getting the following error.
bash: ndiswrapper-1.32rcl: No such file or directory.

I have two such directories..one on the desktop and one in the home folder both give me the same error....Help!!!

Also how does one log in as root in edgy?

In your console, to change to the directory, just type it like this:
cd directory. Make sure that you've extracted the archive first, otherwise the directory won't exist.

As far as logging in as root, just use sudo. Ubuntu disables the root account by default for a number of reasons. It is possible to enable the root account, but you certainly don't need to do that to get your wireless working. Use sudo in the form of
sudo command. It will prompt you to enter your password the first time you use it for each session,

st33med
February 23rd, 2007, 11:30 PM
Nope. Doesn't work, sadly enough.

ERGGHH! I'm so close that I can FEEL it!

paperdiesel
February 24th, 2007, 12:09 AM
Nope. Doesn't work, sadly enough.

ERGGHH! I'm so close that I can FEEL it!

Please post the RELEVANT output from dmesg the RELEVANT lines from /var/log/syslog. Basically, do a sudo ndiswrapper -e bcmwl5 to remove the current driver from ndiswrapper, then do sudo ndiswrapper -i bcmwl5.inf to install the driver again. Once that's done, get the logs and post them here.

st33med
February 24th, 2007, 12:44 AM
Here is dmesg:

[17179593.076000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[17179593.076000] IPv6 over IPv4 tunneling driver

log shows the same thing 'eth1: link is not ready'

Sooooo.... What now?

sstucky
February 24th, 2007, 03:09 AM
I've seen 1 or 2 other folks say they get connected, but each time they re-boot or re-start their computer they loose their wireless connection. Have to do the modprobe again. I have the same problem, anyone have an answer as to how to stop that from happening?

garg
February 24th, 2007, 09:51 PM
Mine light came on after following all the instructions in the first post of this thread and then adding

ndiswrapper

in /etc/modules

and then rebooting

credit: http://pervasivecomputing.net/ubuntu_edgy_on_dell_inspiron_e1505

I'll edit this post and update it with progress of actually being able to use wireless (so far only the wifi light came on)

Ek0nomik
February 24th, 2007, 11:48 PM
I haven't had any luck getting the wireless to work. I have a Dell 1500


fleur@fleur-laptop:~$ ndiswrapper -l
bcmwl5 : invalid driver!


fleur@fleur-laptop:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 7145
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832
03:01.1 Class 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
03:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05)
0b:00.0 Network controller: Broadcom Corporation Unknown device 4328 (rev 01)


fleur@fleur-laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.


fleur@fleur-laptop:~$ sudo iwlist scan
Password:
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.



fleur@fleur-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:19:B9:4F:DA:9C
inet addr:137.28.247.42 Bcast:137.28.247.255 Mask:255.255.254.0
inet6 addr: fe80::219:b9ff:fe4f:da9c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16571 errors:0 dropped:0 overruns:0 frame:0
TX packets:2319 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3903347 (3.7 MiB) TX bytes:381084 (372.1 KiB)
Interrupt:217

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:200 (200.0 b) TX bytes:200 (200.0 b)


fleur@fleur-laptop:~$ lspci | grep Broadcom\ Corporation
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0b:00.0 Network controller: Broadcom Corporation Unknown device 4328 (rev 01)

Thanks in advance for any help you can offer! I've been trying out some of the "HOW TO's", but I haven't had any luck. Thanks!

Ek0nomik
February 24th, 2007, 11:51 PM
fleur@fleur-laptop:~$ ndiswrapper -l
fleur@fleur-laptop:~$



fleur@fleur-laptop:~$ sudo ndiswrapper -i
install/manage Windows drivers for ndiswrapper

usage: ndiswrapper OPTION
-i inffile install driver described by 'inffile'
-a devid driver use installed 'driver' for 'devid'
-r driver remove 'driver'
-l list installed drivers
-m write configuration for modprobe
-ma write module alias configuration for all devices
-mi write module install configuration for all devices
-v report version information

where 'devid' is either PCIID or USBID of the form XXXX:XXXX,
as reported by 'lspci -n' or 'lsusb' for the card
fleur@fleur-laptop:~$


It looks as though I may have successfully removed the bcmwl5 driver... so that's a start.

Ek0nomik
February 26th, 2007, 07:29 AM
So, I am trying to do this for a Dell Wireless 1500.

I want to make sure I am doing a few things correctly:


fleur@fleur-laptop:~/src$ sudo apt-get install linux-headers
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers is a virtual package provided by:
linux-headers-2.6.17-11-server-bigiron 2.6.17.1-11.35
linux-headers-2.6.17-11-server 2.6.17.1-11.35
linux-headers-2.6.17-11-generic 2.6.17.1-11.35
linux-headers-2.6.17-11-386 2.6.17.1-11.35
linux-headers-2.6.17-11 2.6.17.1-11.35
linux-headers-2.6.17-10-server-bigiron 2.6.17.1-10.34
linux-headers-2.6.17-10-server 2.6.17.1-10.34
linux-headers-2.6.17-10-generic 2.6.17.1-10.34
linux-headers-2.6.17-10-386 2.6.17.1-10.34
linux-headers-2.6.17-10 2.6.17.1-10.34
You should explicitly select one to install.
E: Package linux-headers has no installation candidate
fleur@fleur-laptop:~/src$ sudo apt-get install linux-headers-2.6.17-11-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-2.6.17-11-server is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
fleur@fleur-laptop:~/src$


I have no idea what linux headers are, but I know I have install server-bigiron and -server. Everything looks good there, yes?

Next..


fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
fleur@fleur-laptop:~/src/ndiswrapper-1.37$


Looks good, I guess?

Next...


fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make
make -C driver
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C /lib/modules/2.6.17-11-generic/build SUBDIRS=/home/fleur/src/ndiswrapper-1.37/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-11-generic'
LD /home/fleur/src/ndiswrapper-1.37/driver/built-in.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/crt.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/hal.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/iw_ndis.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/loader.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/ndis.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/ntoskernel.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/ntoskernel_io.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/pe_linker.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/pnp.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/proc.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/rtl.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/wrapmem.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/wrapndis.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/wrapper.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/usb.o
CC [M] /home/fleur/src/ndiswrapper-1.37/driver/divdi3.o
LD [M] /home/fleur/src/ndiswrapper-1.37/driver/ndiswrapper.o
Building modules, stage 2.
MODPOST
CC /home/fleur/src/ndiswrapper-1.37/driver/ndiswrapper.mod.o
LD [M] /home/fleur/src/ndiswrapper-1.37/driver/ndiswrapper.ko
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-11-generic'
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C utils
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/utils'
gcc -g -Wall -I../driver -o loadndisdriver loadndisdriver.c
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/utils'
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make install
make -C driver install
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C /lib/modules/2.6.17-11-generic/build SUBDIRS=/home/fleur/src/ndiswrapper-1.37/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-11-generic'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-11-generic'
echo /lib/modules/2.6.17-11-generic/misc
/lib/modules/2.6.17-11-generic/misc
mkdir -p /lib/modules/2.6.17-11-generic/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.17-11-generic/misc
/sbin/depmod -a 2.6.17-11-generic -b /
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C utils install
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/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.5. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
install -m 644 loadndisdriver.8 /usr/share/man/man8
fleur@fleur-laptop:~/src/ndiswrapper-1.37$


Still looks good... to my knowledge...

Next...


fleur@fleur-laptop:~/src$ sudo tar -zxvf wifi-drivers-x32.tar.gz
bcmwl5.sys
bcmwl5.inf
fleur@fleur-laptop:~/src$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5 ...
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
forcing parameter IBSSGMode from 0 to 2
fleur@fleur-laptop:~/src$ sudo ndiswrapper -l
bcmwl5 : driver installed
fleur@fleur-laptop:~/src$ sudo ndiswrapper -m
adding "alias wlan0 ndiswrapper" to /etc/modprobe.d/ndiswrapper ...
fleur@fleur-laptop:~/src$ sudo modprobe ndiswrapper
fleur@fleur-laptop:~/src$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.

fleur@fleur-laptop:~/src$


It still doesn't show up. Not even under network manager, or the iwlist scan.

PLEASE could someone give me some input on what I am doing wrong? I really would like to get the Wireless working.

Thanks!

Ek0nomik
February 26th, 2007, 07:37 AM
Also, let me add, that at the end of this (and a restart), this is still showing:


fleur@fleur-laptop:~$ lspci | grep Broadcom\ Corporation
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0b:00.0 Network controller: Broadcom Corporation Unknown device 4328 (rev 01)


It is still an unknown device!

paperdiesel
February 26th, 2007, 07:01 PM
Also, let me add, that at the end of this (and a restart), this is still showing:


fleur@fleur-laptop:~$ lspci | grep Broadcom\ Corporation
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0b:00.0 Network controller: Broadcom Corporation Unknown device 4328 (rev 01)


It is still an unknown device!

Hey. FIrst, let me say THANK YOU for posting your quesions so well, and providing the perfect level of console and log output. I'm happy to help. Let's get started:

1) You did all of the initial steps fine. You have the right headers, you compiled ndiswrapper fine, and you went through the steps correctly.

2) I have two main concerns. The first thing I need to know is whether or not your system is clean -- any by clean, I mean you have undone any of the changes you've made in previous attempts to get your wireless working. Assuming a clean system, the second thing that bothers me is:

3) Your output from lspci. The first thing you need to know is that even after you install everything and your wireless is working, you're ALWAYS going to get the "unknown device" message. Using ndiswrapper doesn't magically make your device known to the system bus, it simply provides a wrapper around that device and applies windows drivers to it so that it will work in linux. The part that bothers me, though, is the card number -- yours is a 4328. This howto is for 4311. I'm farily certain that this howto will work for you, except that you need to go to dell.com and download the drivers for your specific wireless card (which is not the same as the card example in the how-to). Go download the right driver from dell.com, undo your changes, and try again. To undo your changes, I would so something like this:



sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5
cd NDISWRAPPER-DIRECTORY
sudo make uninstall
sudo make uninstall
sudo make uninstall
sudo rm -rf /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
sudo make
sudo make install

Then pick back up with the part where you do sudo ndiswrapper -i bcmwl5.inf (or whatever your driver is called), etc.

Ek0nomik
February 26th, 2007, 09:09 PM
Thanks paperdiesel. I will try that out tonight!

If you click on this link: http://www.ubuntuforums.org/showthread.php?t=342558 - it shows a walk through for my card.


9. Then run the following to install the drivers (change path if required):
ndiswrapper -i /DRIVER/bcmwl5.inf

This HOW TO also uses bcmwl5.inf. I presume all bcmwl5.inf files are the same, yes? Why would they call a driver for different devices under the same? Doesn't that seem odd, or is that actually how they do things?

Thanks again, and I look forward to a response. :)

Ek0nomik
February 26th, 2007, 09:13 PM
Dell Driver Link (http://support.dell.com/support/downloads/download.aspx?c=us&cs=19&l=en&s=dhs&releaseid=R140747&SystemID=InspironI6400/E1505&os=WW1&osl=en&deviceid=12300&devlib=0&typecnt=1&vercnt=5&formatcnt=1&libid=5&fileid=187881)

This is the driver for my wireless card if I am not mistaken. This is what I want to download, yes?

Thanks again. ;)


Here is the output from the steps I followed that you gave me (yes I know I had some brain farts in there, :P)


fleur@fleur-laptop:~$ sudo rmmod ndiswrapper
Password:
fleur@fleur-laptop:~$ sudo rmmod ndiswrapper
ERROR: Module ndiswrapper does not exist in /proc/modules
fleur@fleur-laptop:~$ sudo ndiswrapper -e bmcwl5
Driver bmcwl5 is not installed. Use -l to list installed drivers
fleur@fleur-laptop:~$ sudo ndiswrapper -l
Installed ndis drivers:
bcmwl5 driver present
fleur@fleur-laptop:~$ cd
fleur@fleur-laptop:~$ dir
commands Desktop Examples Firefox_wallpaper.png img src stalin
fleur@fleur-laptop:~$ cd src
fleur@fleur-laptop:~/src$ dir
bcmwl5.inf ndiswrapper-1.37 wifi-drivers-x32.tar.gz
bcmwl5.sys ndiswrapper-1.37.tar.gz
fleur@fleur-laptop:~/src$ cd ndiswrapper01.37
bash: cd: ndiswrapper01.37: No such file or directory
fleur@fleur-laptop:~/src$ cd ndiswrapper-1.37
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo rmmod ndiswrapper
ERROR: Module ndiswrapper does not exist in /proc/modules
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo ndiswrapper -e bcml5.inf
Driver bcml5.inf is not installed. Use -l to list installed drivers
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo ndiswrapper -e bmcwl5
Driver bmcwl5 is not installed. Use -l to list installed drivers
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo ndiswrapper -e bmcwl5.inf
Driver bmcwl5.inf is not installed. Use -l to list installed drivers
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo ndiswrapper -l
Installed ndis drivers:
bcmwl5 driver present
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /sbin/loadndisdriver
removing /usr/sbin/ndiswrapper
removing /usr/sbin/ndiswrapper-buginfo
removing /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper': Is a directory
removing /lib/modules/2.6.17-11-generic/misc/ndiswrapper.ko
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make uninstall
NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.
Run uninstall as many times as necessary until no "removing" messages appear below.
removing /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
/bin/rm: cannot remove `/lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper': Is a directory
make: *** [uninstall] Error 1
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo rm -rf /lib/modules/2.7.17-11-generic/kernel/drivers/net/ndiswrapper
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make
make -C driver
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C /lib/modules/2.6.17-11-generic/build SUBDIRS=/home/fleur/src/ndiswrapper-1.37/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-11-generic'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-11-generic'
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C utils
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/utils'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/utils'
fleur@fleur-laptop:~/src/ndiswrapper-1.37$ sudo make install
make -C driver install
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C /lib/modules/2.6.17-11-generic/build SUBDIRS=/home/fleur/src/ndiswrapper-1.37/driver
make[2]: Entering directory `/usr/src/linux-headers-2.6.17-11-generic'
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-headers-2.6.17-11-generic'
echo /lib/modules/2.6.17-11-generic/misc
/lib/modules/2.6.17-11-generic/misc
mkdir -p /lib/modules/2.6.17-11-generic/misc
install -m 0644 ndiswrapper.ko /lib/modules/2.6.17-11-generic/misc
/sbin/depmod -a 2.6.17-11-generic -b /
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/driver'
make -C utils install
make[1]: Entering directory `/home/fleur/src/ndiswrapper-1.37/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.5. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/home/fleur/src/ndiswrapper-1.37/utils'
mkdir -p -m 0755 /usr/share/man/man8
install -m 644 ndiswrapper.8 /usr/share/man/man8
install -m 644 loadndisdriver.8 /usr/share/man/man8
fleur@fleur-laptop:~/src/ndiswrapper-1.37$

So now you are telling me I should start install the driver device? All the other steps have been completed?

paperdiesel
February 26th, 2007, 10:06 PM
Here is the output from the steps I followed that you gave me (yes I know I had some brain farts in there, :P)

So now you are telling me I should start install the driver device? All the other steps have been completed?

Turns out I made a mistake too -- I made a typo in the ndiswrapper -e command. I corrected it in my original post to you -- it should be sudo ndiswrapper -e bcmwl5. Note that there is no .inf extension when using the ndiswrapper -e command.

Try those commands again (with the right spelliing.. oops).

Oh and no, all bcmwl5.inf files are not the same. Even though they have the same name, the code inside (and the code in the other files included in the package) can be very, very different depending on the vendor.

Ek0nomik
February 26th, 2007, 10:29 PM
Ok, it looks as though I got the driver uninstalled.

sudo ndiswrapper -l : it doesn't list anything.


sudo rm -rf /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
sudo make
sudo make install

I just finished that. So now ndiswrapper is installed again?

Now I can just proceed to trying to install my newly downloaded Dell driver, correct?

paperdiesel
February 26th, 2007, 11:59 PM
Ok, it looks as though I got the driver uninstalled.

sudo ndiswrapper -l : it doesn't list anything.



I just finished that. So now ndiswrapper is installed again?

Now I can just proceed to trying to install my newly downloaded Dell driver, correct?

Yep, it looks like you're good to go. It wouldn't hurt to reboot first.

Ek0nomik
February 27th, 2007, 12:57 AM
This is the output I got.


fleur@fleur-laptop:~/src$ unzip -a R140447.exe
unzip: cannot find or open R140447.exe, R140447.exe.zip or R140447.exe.ZIP.
fleur@fleur-laptop:~/src$ unzip -a R140747.exe
Archive: R140747.exe
error: cannot create msvcr71.DLL
error: cannot create preflib.dll
error: cannot create README.rtf
error: cannot create setup.exe
error: cannot create setup.inx
error: cannot create Setup.ini
error: cannot create setup.iss
error: cannot create WLBCGCBPRO731.DLL
error: cannot create wltray.exe
error: cannot create wltrynt.dll
error: cannot create wltrysvc.exe
checkdir error: cannot create AMD64
unable to process AMD64/atl71.dll.
checkdir error: cannot create AMD64
unable to process AMD64/BCMLogon64.dll.
checkdir error: cannot create AMD64
unable to process AMD64/bcmwlcpl64.cpl.
checkdir error: cannot create AMD64
unable to process AMD64/MFC71.DLL.
checkdir error: cannot create AMD64
unable to process AMD64/msvcp71.DLL.
checkdir error: cannot create AMD64
unable to process AMD64/msvcr71.DLL.
checkdir error: cannot create DRIVER
unable to process DRIVER/bcm43xx.cat.
checkdir error: cannot create DRIVER
unable to process DRIVER/bcm43xx64.cat.
checkdir error: cannot create DRIVER
unable to process DRIVER/bcmwl5.inf.
checkdir error: cannot create DRIVER
unable to process DRIVER/bcmwl5.sys.
checkdir error: cannot create DRIVER
unable to process DRIVER/bcmwl564.sys.
error: cannot create ATL71.DLL
error: cannot create bcm1xsup.dll
error: cannot create BCMLogon.dll
error: cannot create Bcmnpf64.sys
error: cannot create bcmwlcpl.cpl
error: cannot create bcmwlhlp.cab
error: cannot create bcmwlhlp.chm
error: cannot create bcmwliss.dll
error: cannot create bcmwlnpf.sys
error: cannot create bcmwlpkt.dll
error: cannot create bcmwls.ini
error: cannot create bcmwls32.exe
error: cannot create bcmwls64.exe
error: cannot create bcmwltry.exe
error: cannot create bcmwlu00.exe
error: cannot create data1.cab
error: cannot create data1.hdr
error: cannot create data2.cab
error: cannot create DellInfo.exe
error: cannot create DellInfo64.exe
error: cannot create dellinst.exe
error: cannot create ikernel.ex_
error: cannot create is.exe
error: cannot create launcher.ini
error: cannot create layout.bin
error: cannot create MFC71.DLL
error: cannot create msvcp71.DLL
error: cannot create Version.txt
fleur@fleur-laptop:~/src$ sudo unzip -a R140747.exe
Password:
Archive: R140747.exe
inflating: msvcr71.DLL [binary]
inflating: preflib.dll [binary]
inflating: README.rtf [text]
inflating: setup.exe [binary]
inflating: setup.inx [binary]
inflating: Setup.ini [text]
inflating: setup.iss [text]
inflating: WLBCGCBPRO731.DLL [binary]
inflating: wltray.exe [binary]
inflating: wltrynt.dll [binary]
inflating: wltrysvc.exe [binary]
inflating: AMD64/atl71.dll [binary]
inflating: AMD64/BCMLogon64.dll [binary]
inflating: AMD64/bcmwlcpl64.cpl [binary]
inflating: AMD64/MFC71.DLL [binary]
inflating: AMD64/msvcp71.DLL [binary]
inflating: AMD64/msvcr71.DLL [binary]
inflating: DRIVER/bcm43xx.cat [binary]
inflating: DRIVER/bcm43xx64.cat [binary]
inflating: DRIVER/bcmwl5.inf [binary]
inflating: DRIVER/bcmwl5.sys [binary]
inflating: DRIVER/bcmwl564.sys [binary]
inflating: ATL71.DLL [binary]
inflating: bcm1xsup.dll [binary]
inflating: BCMLogon.dll [binary]
inflating: Bcmnpf64.sys [binary]
inflating: bcmwlcpl.cpl [binary]
inflating: bcmwlhlp.cab [binary]
inflating: bcmwlhlp.chm [binary]
inflating: bcmwliss.dll [binary]
inflating: bcmwlnpf.sys [binary]
inflating: bcmwlpkt.dll [binary]
inflating: bcmwls.ini [binary]
inflating: bcmwls32.exe [binary]
inflating: bcmwls64.exe [binary]
inflating: bcmwltry.exe [binary]
inflating: bcmwlu00.exe [binary]
inflating: data1.cab [binary]
inflating: data1.hdr [binary]
inflating: data2.cab [binary]
inflating: DellInfo.exe [binary]
inflating: DellInfo64.exe [binary]
inflating: dellinst.exe [binary]
inflating: ikernel.ex_ [binary]
inflating: is.exe [binary]
extracting: launcher.ini [text]
inflating: layout.bin [binary]
inflating: MFC71.DLL [binary]
inflating: msvcp71.DLL [binary]
inflating: Version.txt [binary]
fleur@fleur-laptop:~/src$ dir
AMD64 bcmwlpkt.dll DRIVER README.rtf
ATL71.DLL bcmwls32.exe ikernel.ex_ setup.exe
bcm1xsup.dll bcmwls64.exe is.exe Setup.ini
BCMLogon.dll bcmwls.ini launcher.ini setup.inx
Bcmnpf64.sys bcmwltry.exe layout.bin setup.iss
bcmwl5.inf bcmwlu00.exe MFC71.DLL Version.txt
bcmwl5.sys data1.cab msvcp71.DLL wifi-drivers-x32.tar.gz
bcmwlcpl.cpl data1.hdr msvcr71.DLL WLBCGCBPRO731.DLL
bcmwlhlp.cab data2.cab ndiswrapper-1.37 wltray.exe
bcmwlhlp.chm DellInfo64.exe ndiswrapper-1.37.tar.gz wltrynt.dll
bcmwliss.dll DellInfo.exe preflib.dll wltrysvc.exe
bcmwlnpf.sys dellinst.exe R140747.exe
fleur@fleur-laptop:~/src$ cd DRIVER
fleur@fleur-laptop:~/src/DRIVER$ sudo ndiswrapper -i bcmwl5.inf
installing bcmwl5 ...
fleur@fleur-laptop:~/src/DRIVER$ sudo ndiswrapper -l
bcmwl5 : driver installed
device (14E4:4328) present
fleur@fleur-laptop:~/src/DRIVER$ sudo ndiwrapper -m
sudo: ndiwrapper: command not found
fleur@fleur-laptop:~/src/DRIVER$ sudo ndiswrapper -m
module configuration already contains alias directive

fleur@fleur-laptop:~/src/DRIVER$ sudo modprobe ndiswrapper
fleur@fleur-laptop:~/src/DRIVER$


My WiFi light isn't on. I will say, the WiFi light did light up when I first tried some of these How To's, but it no longer does.

Any ideas?

My laptop has a button (it's called Fn), and if you hold that plus F2 on my laptop, you can turn on or off the wireless device. When I "turn it on" a blue icon next to the WiFi symbol lights up instead. I don't actually know what that symbol is... it's just some straight lines going in different directions all lit up in blue.

Thanks again paper, hopefully we can narrow down this problem!

Ek0nomik
February 27th, 2007, 01:15 AM
Nevermind! Thanks a lot paperdiesel. I rebooted and it works like a charm. Thanks a lot for your help, much appreciated!

paperdiesel
February 27th, 2007, 01:18 AM
Nevermind! Thanks a lot paperdiesel. I rebooted and it works like a charm. Thanks a lot for your help, much appreciated!

Nice! Glad to hear it. By the way, that blue light that comes on is your bluetooth link. You can control how that button works in your BIOS settings, if you'd like to turn your wireless to always on / hotkey disabled.

Ek0nomik
February 27th, 2007, 02:59 AM
I figured it was Bluetooth, but I wasn't sure. Thanks again paperdiesel. Always awesome to see strangers online come through and help another person. :)

sstucky
February 27th, 2007, 09:54 PM
Garg,

Thanks! That was just what I needed. Its all working now.

M_N_M74
March 1st, 2007, 05:38 AM
Yeah!! I finally got all the steps to work on the tutorial....well execpt for the one where you connect to the internet...

anyway, have a Dell Inspirion 1501. broadcom 4311

iwlist gives me interface doesn't support scanning.
I have attempted to follow all the other advice for getting the card to work to no avial...ie have the bios disabled.

I downloaded ndiswrapper-1.32rcl and R140747.exe (did I get the wrong programs somewhere along the line?)

Any advice/help will be greatly appreciated.
Thanks
M_N_M

Ek0nomik
March 1st, 2007, 06:29 AM
Did you get the correct driver for your network card?

I was downloading the wrong driver for a few days. Go to Dell.com and make sure you get the correct one.

M_N_M74
March 1st, 2007, 04:06 PM
Quick question, as none of the fixes listed on this thread seem to be working, maybe I did something wrong in the original attempt at loading all of this information, how do I go about completely undoing everything and starting fresh to make sure all the steps were done correclty?

Ek0nomik
March 1st, 2007, 05:02 PM
I know the frustrating feeling M_N_M74


sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5
cd NDISWRAPPER-DIRECTORY
sudo make uninstall
sudo make uninstall
sudo make uninstall

Try this to get rid of ndiswrapper and the driver. (You installed the bcmwl5 driver, right?)

Than, to check if you successfully got rid of it:


sudo ndiswrapper -l

Hopefully it won't list anything, and just put you to another line in the Terminal.

You can also look a few posts up where I posted a lot of my output trying to get it to work. I would make sure you look at it, for it should help you a bit.

I hope this helps! I may not be on the forum a lot this weekend, but if you respond I'll hopefully try to help when I get back Sunday night.

Cheers!

Ek0nomik
March 1st, 2007, 05:26 PM
http://support.dell.com/support/downloads/download.aspx?c=us&cs=19&l=en&s=dhs&releaseid=R140747&SystemID=INS_PNT_1501&os=WW1&osl=en&deviceid=8041&devlib=0&typecnt=1&vercnt=1&formatcnt=1&libid=5&fileid=187881

I think this is the driver you need, but I am not 100% certain.

So, assuming you got the driver uninstalled and ndiswrapper out of the system...

1.

sudo apt-get install linux-headers

Running that command will produce something like this:


fleur@fleur-laptop:~/src$ sudo apt-get install linux-headers
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package linux-headers is a virtual package provided by:
linux-headers-2.6.17-11-server-bigiron 2.6.17.1-11.35
linux-headers-2.6.17-11-server 2.6.17.1-11.35
linux-headers-2.6.17-11-generic 2.6.17.1-11.35
linux-headers-2.6.17-11-386 2.6.17.1-11.35
linux-headers-2.6.17-11 2.6.17.1-11.35
linux-headers-2.6.17-10-server-bigiron 2.6.17.1-10.34
linux-headers-2.6.17-10-server 2.6.17.1-10.34
linux-headers-2.6.17-10-generic 2.6.17.1-10.34
linux-headers-2.6.17-10-386 2.6.17.1-10.34
linux-headers-2.6.17-10 2.6.17.1-10.34
You should explicitly select one to install.
E: Package linux-headers has no installation candidate

Essentially what that will do, is list the different headers you can install. I for an example ran this next:


fleur@fleur-laptop:~/src$ sudo apt-get install linux-headers-2.6.17-11-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-headers-2.6.17-11-server is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
fleur@fleur-laptop:~/src$

Note:: It won't say "linux-headers-2.6.17-11-server is already the newest version." on your computer if you don't have it installed, so don't worry if that isn't the same.

2.
Download ndiswrapper (newest version is 1.38.): http://superb-west.dl.sourceforge.net/sourceforge/ndiswrapper/ndiswrapper-1.38.tar.gz

3.

Make sure you have blacklisted useless drivers:


sudo echo blacklist bcm43xx >> /etc/modprobe.d/blacklist

(If you have already done that, you probably don't need to run it again. You can always gedit the blacklist file and see what it looks like towards the end to see if you have written to it or not)

The OP (paperdiesel) suggests rebooting here, so I would do that.

Than you should be able to move on with the rest of the original HOW TO (http://www.ubuntuforums.org/showthread.php?t=297092)

Good luck!

(You can thank my boring lecture professor... this class is teh suck.)

M_N_M74
March 1st, 2007, 05:38 PM
thanks, I'll try all that tonight after I get back from class. Hope it works and I can completely ditch windows

paperdiesel
March 1st, 2007, 11:34 PM
sudo apt-get install linux-headers


An easier way to go about this is to let the system figure out which version to get for you, based on the kernel you're currently running:


sudo apt-get install linux-headers`uname -r`

Note that those are back-tics, NOT apostrophes. Just copy-paste the code in to your terminal and you'll be fine.

Ek0nomik
March 2nd, 2007, 02:07 AM
An easier way to go about this is to let the system figure out which version to get for you, based on the kernel you're currently running:


sudo apt-get install linux-headers`uname -r`

Note that those are back-tics, NOT apostrophes. Just copy-paste the code in to your terminal and you'll be fine.

Dang, no wonder that command never worked for me. I always thought I was somehow typing that in wrong.

scottness
March 2nd, 2007, 04:54 PM
I'm not completely sure if this is connected to the wireless card, but it definitely seems to be.

While I'm using Firefox, Opera, or really any application that needs online connectivity, the screen locks up and the system freezes. My mouse still moves around, but cannot click on anything on screen.

I originally thought this was connected to my video card, as some other people had similar problems with Firefox and the Nvidia driver. But I had no lockup problems while I was using a wired network connection all day yesterday, and only showed up again last night while I was using the wireless. So here goes.

I'm using a new Ubuntu 6.10 install on a Dell e1505 with the Broadcom 1390 driver. I have the Nvidia drivers installed and Beryl running. I followed the HowTo in the first post of the thread, and it worked well. I was able to set up my internet connection wirelessly and had no problems for a few hours. Then after installing the Nvidia drivers, the system locked up nearly everytime I got online. I ran Firefox in the terminal, hoping to see an error message, but all I got was this:


** Message: plugin_get_value 1 (1)
** Message: plugin_get_value 2 (2)

I looked back through the error logs hoping to find something else to let me know what happened and found this just before I had to restart the system:


sbevill-laptop gconfd (root-501: Resolved address "xml:readonly; /var/lib/gconf/defaults" to a read-only configuration source at position 4
sbevill-laptop gconfd (root-501: GConf server is not in use, shutting down.
sbevill-laptop gconfd (root-501: Exiting
sbevill-laptop kernel: [17180433.560000] <c01499a4> __report_bad_irq+0x24/0x80 <0149a9d>note_interrupt+0x9d/0x270
sbevill-laptop kernel: [17180433.560000] <f9595415>nv_kern_isr+0x2f/0x62[nvidia] <c0149323>handle_IRQ_event+0x33/0x60
sbevill-laptop kernel: [17180433.560000] <c0149448>__do_IRQ+0xf8/0x110 <c0105c89>do_IRQ_0x19/0x30
sbevill-laptop kernel: [17180433.560000] <c010408a> common_interrupt+0x1a/0x20 <f88586dd>acpi_processor_idle+0x220/0x3af[processor]
sbevill-laptop kernel: [17180433.560000] <c02d902a> schedule+0x48a/0xcc0 <c0102122>cpu_idle+0x42/0xb0
sbevill-laptop kernel: [17180433.560000] <c03f27a1> start_kernel+0x321/0x3a0 <c03f2210>unknown_bootoption+0x0/0x270
sbevill-laptop syslogd 1.4.1#18ubuntu6: restart.

Above the gconf messages were other lines about disconnects and unresolved addresses. To me it looked like the wireless hiccuped and stopped connecting, and then the video card stopped responding. I'm not sure if that's true or not, but it seems to make sense considering that this problem only happens while I am connected wirelessly, but not when I'm using the wired connection.

Right now, I'm planning on re-installing the ndiswapper setup. How would I go about removing everything I've done so far? Is there another way to configure the wireless card so it won't cause this problem?

One other note that may be helpful...the last setting change I made with Nvidia was in the xorg.conf file...changed the default screen depth from 16 to 24 in order to get Beryl to work properly. So right now, I could probably run one or the other, but I'd like to run both. I've already reinstalled and reconfigured the Nvidia driver, but still am having some lock-up problems while connected wirelessly. If anything else is needed from me, let me know and I'll try to provide it. Thanks.

paperdiesel
March 2nd, 2007, 05:24 PM
post

Man... you're covering a lot of ground here. There could be any number of things wrong with your setup that would cause it to lock up like that. Most of the possibilities are well beyond the scope of this how-to.

However, I have two thoughts: First, I'd try uninstalling all of your firefox extensions.

If that doesn't work, you can try editing your grub boot-up options and adding these two commands to the boot up options in your menu.lst file: noapic nolapic

Finally, if you want uninstall steps for ndiswrapper, search earlier posts in this thread. I've detailed the steps many times over to other people.

Good luck!

M_N_M74
March 2nd, 2007, 05:58 PM
WHOHOOO!!!! IT finally worked, I have internet on my Linux box. Thanks everyone for their help.

Now I have to go do homework.

Thanks again.
M&M

RussellBls
March 3rd, 2007, 03:01 AM
I'm new to Linux so help me if you can. When I get to the step where you enter
sudo make uninstall
I get this
russell@russell-laptop:~$ dir
Desktop Examples ndiswrapper-1.32 ndiswrapper-1.32.tar.gz R140747.EXE
russell@russell-laptop:~$ sudo make uninstall
Password:
make: *** No rule to make target `uninstall'. Stop.
russell@russell-laptop:~$
I did the dir command so you can see that ndiswrapper is in this directory. Any help or advice would be much appreciated.

perfidious_alban
March 3rd, 2007, 04:04 PM
Thanks for that !
Albeit it's an IBM and not a Dell laptop that I have, that clear explanation has given me a much better understanding of what I probably need to do to resolve my own installation problems. Your taking the time to explain is much appreciated.

Ek0nomik
March 3rd, 2007, 09:20 PM
I'm new to Linux so help me if you can. When I get to the step where you enter
sudo make uninstall
I get this
russell@russell-laptop:~$ dir
Desktop Examples ndiswrapper-1.32 ndiswrapper-1.32.tar.gz R140747.EXE
russell@russell-laptop:~$ sudo make uninstall
Password:
make: *** No rule to make target `uninstall'. Stop.
russell@russell-laptop:~$
I did the dir command so you can see that ndiswrapper is in this directory. Any help or advice would be much appreciated.

RussellBls: When you type "dir", you are simply listing all the contents inside of a directory. Firstly, I would download the newest ndiswrapper instead of 1.32. Regardless of what you do, you need to navigate inside of the ndiswrapper directory.


russell@russell-laptop:~$ cd ndiswrapper-1.32

If you type that, it will put you INSIDE of the ndiswrapper directory. Now you should be able to run the install commands!

Hope that helps!

RussellBls
March 4th, 2007, 07:11 AM
I'm running the sudo make uninstall and i've done the command about 3000 times and still am not where there are no files left to be removed. How many times do you have to run the command and are there any other users out there having similar problems? Can I move to the next step or should I continue to run this command? I've been at it for over an hour. Thanks for your input. Russell

Ek0nomik
March 4th, 2007, 08:03 PM
When you run sudo make uninstall, what does it say exactly?

Copy and paste your output into the forum. Also, you can look back in this very thread to see some of my output when I was having troubles. I think I posted by sudo make uninstall output.

Cheers!

RussellBls
March 4th, 2007, 08:42 PM
When you run sudo make uninstall, what does it say exactly?

Copy and paste your output into the forum. Also, you can look back in this very thread to see some of my output when I was having troubles. I think I posted by sudo make uninstall output.

Cheers!
Thanks very much for your help Ek0nomic. As I posted earlier in this thread, I am new to linux and without your help in navigating to the proper directory I wouldn't be posting this wirelessly. As for the output you requested, I have forgotten what it said exactly but it was something like this: "Not all files were uninstalled. run uninstall until you see below no files available. " Not verbatim but a repeat message several hundred times. I went on to the next step at that point and everything else worked properly. I would also like to thank paperdiesel and all others who posted on this thread for their efforts on this project. I love linux, Thanks, Russell

scottness
March 4th, 2007, 10:37 PM
Paperdiesel, thanks for the Howto and the suggestion...my problem appears to be connected to the video card and not the wireless driver, so I'm voting that this howto worked. Thanks!

Ek0nomik
March 5th, 2007, 07:38 AM
Thanks very much for your help Ek0nomic. As I posted earlier in this thread, I am new to linux and without your help in navigating to the proper directory I wouldn't be posting this wirelessly. As for the output you requested, I have forgotten what it said exactly but it was something like this: "Not all files were uninstalled. run uninstall until you see below no files available. " Not verbatim but a repeat message several hundred times. I went on to the next step at that point and everything else worked properly. I would also like to thank paperdiesel and all others who posted on this thread for their efforts on this project. I love linux, Thanks, Russell

No problem. :) paperdiesel did most of the work. ;)

st33med
March 5th, 2007, 10:29 PM
Here is dmesg:

[17179593.076000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[17179593.076000] IPv6 over IPv4 tunneling driver

log shows the same thing 'eth1: link is not ready'

Sooooo.... What now?
Still need an answer for this post.

Ek0nomik
March 6th, 2007, 12:25 AM
Still need an answer for this post.

What wireless card are you trying to hook up?

ant2ne
March 6th, 2007, 12:26 AM
I guess I lucked out 'cause I had very little issues following this step by step instruction. Loved it. Possibly my success was because this was the 1st thing I did after installing my OS


I just have one problem, I'm forced to enter these lines each time I boot the OS.

sudo ndiswrapper -m
sudo modprobe ndiswrapper
why is this?

If you use a WPA then never run Wireless Assistant as it doesn't support WPA and will convert your settings to WEP and make you need to start over with setp 1. =)

st33med
March 6th, 2007, 11:34 PM
What wireless card are you trying to hook up?

:roll: Ummmm..... I answered this before... Well, I have a Dell Wireless MiniCard 1390. It SHOULD be connecting! I've tried Wireless Assistant and it says I can't connect... Even though it sees the network... I've triple-checked the WEP, and I don't know what to do...

Feuerdrache
March 7th, 2007, 07:53 AM
I actually got my WiFi up and running. Then I rebooted.

Now, not only does it not work, but I've lost the wireless interface entirely!

When I enter the ESSID of the wireless interface, it gives me an error.
[Never mind. See below.]

When I open the WiFi Radar, the network has no signal strength, and I can't connect to it (I suspect this is because my interface disappeared).
[Never mind. See below.]

So I went into the terminal to try the "sudo ndiswrapper -m" and "sudo modprobe ndiswrapper" lines again.
[Never mind. See below.]

For reference, the WiFi light is on.

Should I just reinstall and start over again, or is there a more practical option? I really don't want to have to reinstall Ubuntu every time I boot it up!

dfreer
March 8th, 2007, 01:18 AM
When I tried this how-to on my friends laptop, we had to manually assign a IP address, subnet mask, and gateway using System > Administration > Networking. Once the IP address was assigned and the interface brought up, THEN and only then would the wifi light come on. From there we were able to scan for networks and connect to them with dhcp with no further problems. You might want to add this to the guide :)

Feuerdrache
March 8th, 2007, 02:26 AM
Alright, I was only just teasing with you.

I really did have a problem, but I fixed it by going back through the HOWTO again. I can only surmise that something I installed (or maybe uninstalled) ousted the work I did to get the WiFi working, because I just rebooted the laptop twice and got Internet working both times.

Thank you very much for this, you're a life-saver.

specv
March 9th, 2007, 03:38 AM
I guess I lucked out 'cause I had very little issues following this step by step instruction. Loved it. Possibly my success was because this was the 1st thing I did after installing my OS


I just have one problem, I'm forced to enter these lines each time I boot the OS.

why is this?

If you use a WPA then never run Wireless Assistant as it doesn't support WPA and will convert your settings to WEP and make you need to start over with setp 1. =)


here is your answer from page 2


Thanks for posting. Very nice, clear guide. There is one more step I would mention. To get the driver to load automatically when you boot, insert "ndiswrapper" into /etc/modules. In terminal, type

sudo nano /etc/modules

-then add 'ndiswrapper' to it (no quotes). then press ctrl-O to save it.

Then it will load automatically for you on each boot *instead of having to load it manually each time).


OP i would like to thank you very much for such a great how to, im now the envy of all my friends with kbuntu on my laptop with wireless and bluetooth both working and dual booting vista


also if anyone is interesting i have a e1405 and its the same driver and all the same instructions worked for me

Rock`
March 10th, 2007, 12:29 AM
I'm having problems with the ndiswrapper, doing the sudo make gives me a 'Can't find kernel build files in /lib/modules/versnumber/build;' though I successfully unpacked it.

any ideas?

Rock`
March 10th, 2007, 12:41 AM
I think I pinpointed my problem to

> sudo make uninstall

I've done this seriously about 100 times and I still get

NOTE: not all installed files are removed, as different distribtuions install ndiswrapper files at different places, etc.

Ek0nomik
March 10th, 2007, 02:16 AM
Do you have the linux headers installed from Step 2?

Having the message...


NOTE: Not all installed files are removed, as different distributions install ndiswrapper files at different places.

isn't a bad thing. I had that too.

Start posting your terminal output, it makes it much easier.

Rock`
March 10th, 2007, 02:28 AM
Unfortunately due to my current setup I can't get my laptop to get wired internet as well. I definetly got the headers...all thats left is for the make install to actually work, i always get an error (error 2) when trying the command.

Ek0nomik
March 10th, 2007, 05:23 PM
Well, without the terminal output it's hard for me to look at stuff since I don't know what/where your doing things.

Try the following...


sudo rmmod ndiswrapper
sudo ndiswrapper -e bcmwl5
cd NDISWRAPPER-DIRECTORY
sudo make uninstall
sudo make uninstall
sudo make uninstall
sudo rm -rf /lib/modules/2.6.17-11-generic/kernel/drivers/net/ndiswrapper
sudo make
sudo make install

The first two commands probably won't do anything, but whatever. It won't hurt since I don't know how far you have ever gotten in this wireless project.

Again, you have Linux Headers installed as from Step 2?

Ek0nomik
March 10th, 2007, 05:25 PM
Rock`, I am quite positive you are getting that error because you haven't installed/updated the kernel. Make sure you do that in Step 2, and THAN try your sudo make, sudo make install.

Rock`
March 10th, 2007, 08:51 PM
Thanks for the reply, I got ndiswrapper installed using automatix, and my headers were up to date :shrug:

After doing everything, seeing that the hardware is present, drivers present and modprobe-ing, I scan to get this:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.


No wireless interface :\ any ideas?

paperdiesel
March 11th, 2007, 02:12 AM
Thanks for the reply, I got ndiswrapper installed using automatix, and my headers were up to date :shrug:

After doing everything, seeing that the hardware is present, drivers present and modprobe-ing, I scan to get this:

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

sit0 Interface doesn't support scanning.


No wireless interface :\ any ideas?

Rock,

The whole point is that you can't use the ndiswrapper that comes packaged through synaptic. The version of ndiswrapper that is in the repositories is old and will not work. You have to download the latest ndiswrapper source, compile it on your specific system, and then run it.

You'll need to remove the synaptic version of ndiswrapper and start over if you want to use the method outlined in this howto.

If you give the actual console output and the relevant lines from your log files (/var/log/syslog and dmesg), we can help you out.

Mark Taylor
March 11th, 2007, 11:20 AM
I can confirm that as well as Ubuntu/Kubuntu Edgy/Dapper this also works with Mepis 6.5 RC1 (though Mepis users will have to run everything as root and drop "sudo" from all commands for it to work) on the Inspiron 640m (some models of which, including mine, have the Broadcom 1390 wireless card). After 5 or so hours of frustration trying to get it set up this was the only thing that worked! Thanks!