LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Ndiswrapper does not detect my wireless adapter in Fedora 9 (https://www.linuxquestions.org/questions/linux-networking-3/ndiswrapper-does-not-detect-my-wireless-adapter-in-fedora-9-a-681831/)

brozell 11-07-2008 02:11 PM

Ndiswrapper does not detect my wireless adapter in Fedora 9
 
Ive been trying to get Ndiswrapper to work for me for about five days now,
I have an up to date kernel (2.6.26.6-79.fc9.i686) and up to date Ndiswrapper from Livna.

Its an Acer Extensa 4420, with a Broadcom BCM94312MCG. I have current Windows XP ini. and sys. files from the Broadcom website.

In the terminal I type: /usr/sbin/ndiswrapper -l
and i get: bcmxxx*:driver present

* I'm using Windows to get online and i dont remember the driver name.

For some reason it's not detecting the card and Network Config. doesn't list it either, Ive had other laptops before and everything works just fine when i use Ndiswrapper.

I'm out of ideas and would appreciate any help I could get.

SkyEye 11-08-2008 01:52 PM

Welcome to LQ!

You'll have to install a Windows driver to get it working with ndiswrapper. Try to locate your driver CD or download it from vendors site. If you have it running under Windows, you might be able to extract it from there.

Then locate the .inf file and run
# ndiswrapper -i yourinffile.inf

After it installs you may want to run
# ndiswrapper -m

On a side note, if you already have a module loaded (which seems to be your case), you might have to black list it in order to get the new driver working.

brozell 11-10-2008 02:14 PM

I'll give that a try.

Larry Webb 11-10-2008 04:29 PM

The Suse I just installed on my wifes laptop had the similar problem and I had to blacklist 4 drivers that come with the kernel. Those broadcom chips are tempermental. Here is a link to my thread with the solution I came up with. Suse has a way of using different name for some of their folders so I can not say this will work word for word.

http://www.linuxquestions.org/questi...search-674226/

PTrenholme 11-10-2008 05:17 PM

Fedora 9 installs the FOSS b43 Broadcom device driver by default when it detects a Broadcom device. The driver will not work until you run the b43-fwcutter program to extract the Broadcom microcode from the Windows .inf file that should be on the CD that came with your system or, if you still have windows installed, look on your Windows partition.

So I recommend that you abandon the ndiswrapper approach, remove it from your system, run the fwcutter program, and you should be "good to go." If you choose to try to stay with the ndiswrapper method, you'll need to add the b43 driver(s) - there may be more than one - to /etc/modprob.d/blacklist so they are not automatically started when you boot. It should be obvious that you will never be able to use the device if two different drivers are attempting to use it at the same time.

FYI: Fedora cannot include the propitiatory microcode in their distribution because, by policy, Fedora will not include any propitiatory code in a Fedora distribution.

brozell 11-11-2008 08:14 PM

PTrenholme, I'll try your method.

I've never used b43-fwcutter,so ill have to find a page to tell me how to use it, but then what?

PTrenholme 11-11-2008 09:38 PM

Look at man b43-fwcutter for the basic information. You'll need to Windows .sys file (not the .inf - sorry, my bad) from your windows installation. What the program does is parse the .sys file and extract the firmware from it into a file. (I.e., the program is a firmwarecutter.)

Specifically, Fedora will look for those files in /lib/firmware, so you need to use that as the -w argument to b43-fwcutter. Here's a copy of the README.Fedora file on my laptop:
Code:

$ cat /usr/share/doc/b43-fwcutter-011/README.Fedora
Using the b43-fwcutter tool to install Broadcom firmware in Fedora.
-----------------------------------------------------------------------

The b43 and b43legacy drivers included in the Fedora kernel require
firmware images to load onto a Broadcom wireless device in order to
make it function.  These firmware images can be extracted from any
of a number of driver binaries released for OSX, Windows, or Linux.

The following URL (taken from the README file) points to sources of
firmware images which are known to work with these drivers:

        http://www.linuxwireless.org/en/users/Drivers/b43#devicefirmware

Pleae note that the b43legacy driver requires "version 3" firmware,
while the b43 driver requires "version 4" firmware.

Once you have obtained the source of the appropriate firmware,
run the command below as root.  Be sure to replace '<DRIVERFILE>'
with the actual name of the source file (e.g. wl_apsta.o):

  b43-fwcutter -w /lib/firmware <DRIVERFILE>

The command above will extract the firmware to the appropriate location
for loading by the driver as necessary.

Note: Since the program will be writing to /lib, it will need &quot;root&quot; access to run properly.

Once you've extracted the firmware and either removed or blacklisted ndiswrapper, just reboot and you should find that a left-click on the NetworkManager icon will present you with a list of access points to which you can connect. (Unless you don't have the passwords, of course.)

brozell 11-27-2008 11:24 PM

Now What?
 
Sorry for taking so long to post, been very busy.

OK PTrenholme,I did as you recomended but after I reboot the wlan is still not there. Was there a command I have to run or what?

PTrenholme 11-28-2008 11:56 AM

What do you see when you do a ls /lib/firmware/? My laptop with the Broadcom card in it has a broken screen, so I can't check, but, IIRC, there should be a sub-directory called b43 containing the firmware.

Also, run the command dmesg | grep -A 3 -B 3 -i b43 in a terminal window to print all the boot messages with b43 (or B43) in them. That may be helpful. (You might also try dmesg |grep -A 3 -B 3 -i eth to see Ethernet related messages.) (F.Y.I., The -A and -B options in the grep command tell grep to print the three lines before an after the matching line.)

Let us know what the output looks like if it's not clear to you what you need to do to resolve the issue.

Oh, a thing that's caught me: If your laptop has an on/off switch for the wireless card, make sure it's turned on. I once spent a couple hours trying to fix a "suddenly not working" wireless connection, rebooting my routers, etc., etc., before I discovered it wasn't working because it wasn't turned on. (Moral of story: Don't let the grandchildren play with the laptop.)

Hangdog42 11-28-2008 03:17 PM

At the risk of derailing this thread, Broadcom has actually released their own driver for the 4312 chipset. It is most definitely NOT an open source driver, but it does seem to work with less fuss than b43. You can find it here along with installation instructions.

brozell 11-28-2008 11:59 PM

OK the b43 driver does not support my chipset, says there website, so i must use bcm43xx-fwcutter.
after i extract the .sys to /lib/firmware, i try to load it with /sbin/modprobe bcm43xx I get FATAL: bcm43xx module not found. which is wierd because i installed it as an option during the distro's installation, so i figured THAT kernal module would be installed. but i guess im wrong, PTrenholme i hope you have an answer, cause i cant find it, and after looking at Hangdog42's post Im going to try that right after we run out of ideas for this fwcutter thing.

Thanks guys

wificraig 11-29-2008 04:03 AM

sandypeter111
 
You might want to stick to asking questions rather than answering any.

Hangdog42 11-29-2008 06:52 AM

I would strongly suggest NOT using bcm43xx. That driver is no longer being developed since it was replaced by b43/b43-legacy. Even if you got it working, it almost certainly would break at some point in the future when the kernel changed and bcm43xx didn't.

PTrenholme 11-29-2008 07:55 AM

Quote:

Originally Posted by brozell (Post 3358420)
OK the b43 driver does not support my chipset, says there website, so i must use bcm43xx-fwcutter.
after i extract the .sys to /lib/firmware, i try to load it with /sbin/modprobe bcm43xx I get FATAL: bcm43xx module not found. which is wierd because i installed it as an option during the distro's installation, so i figured THAT kernal module would be installed. but i guess im wrong, PTrenholme i hope you have an answer, cause i cant find it, and after looking at Hangdog42's post Im going to try that right after we run out of ideas for this fwcutter thing.

Thanks guys

I was not aware the Broadcom had provided a driver. Thanks Hangdog42.

Assuming you're not a FOSS purist, try the Broadcom hybrid version. Note that neither b43 nor ndiswrapper are FOSS in the sense that they both require extraction of proprietary code from the Broadcom Windows drivers. I looked at the instruction at the site Hangdog42 referenced and they seemed fairly easy to follow. Don't forget to add the three drivers they referenced (b43, b43_legacy, and ssd) to /etc/modprob.d/blacklist. You may not need to install the WPA security driver since it's usually pre-installed in kernels after 2.6.26.

If you want to stick with FOSS, and b43 doesn't support your card, did you check b43_legacy?

brozell 11-29-2008 12:09 PM

if you look at Broadcom 's README, it says to make a directory (hyrbid_wl) in the source folder, is that / or a folder called source?


All times are GMT -5. The time now is 11:48 AM.