LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 01-16-2008, 08:50 PM   #16
betterthanyou
LQ Newbie
 
Registered: Jan 2008
Posts: 9

Rep: Reputation: 0

Ok I can easily get the win XP drivers from the Dell website. I will do that right now. But then I am going to need some instructions that a simpleton can follow. I have not run a command line since I had Win 95 and used MS DOS to play Need For Speed!

Thanks Guys. If I get this wireless working I am all set and I will be over a big hurdle. At least I can use my wired connection. I am actually quite surprised the installation of Fedora was quite easy and this wireless problem is the only snag I have had.
 
Old 01-17-2008, 03:39 AM   #17
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello betterthanyou

Wireless is still one of the "black magic" areas of Linux but it's getting better all the time. The b43 driver is a prime example. It's a great deal better than it's predecessor bcm43xx but it's still under development.

When you have the windows driver from Dell, you may find it has components for various Windows operating systems.

As root, cd into the folder containing the Windows XP driver and issue the command:

Code:
b43-fwcutter -w /lib/firmware <name of .sys file here>
If the b43-fwcutter program complains about the file try replacing the name of the .sys file with that of the .inf file.

With the firmware in place then it is going to be simplest to restart the machine.

From a root command line again, run the command:

Code:
iwconfig
and see if you get any sensible output back about wireless extensions.

If you do then it should tell you the name of your wireless interface. Probably it will be wlan0 but could be eth1. Then the output of the command:

Code:
iwlist wlan0 scan
should tell you about available access points in your area.

Where you go beyond that will depend on if the above works and how you installed Fedora.

Believe it or not, if you installed from DVD it is different from installing by way of a Live CD. It is also different if you are running a Gnome or KDE desktop.

If you try the above and post back results, and how you installed and what desktop, we'll be ready to go on to the next step.
 
Old 01-17-2008, 09:53 PM   #18
betterthanyou
LQ Newbie
 
Registered: Jan 2008
Posts: 9

Rep: Reputation: 0
Ok well the Win XP drivers did not seem to work. I get the following for the SYS and INI files

[root@localhost v4.23]# b43-fwcutter -w /lib/firmware bcm4sbxp.sys
Sorry, the input file is either wrong or not supported by b43-fwcutter.
This file has an unknown MD5sum e727776a56a51b7e6b7c87c02ea8b405.
[root@localhost v4.23]# b43-fwcutter -w /lib/firmware bcm4sbxp.inf
Sorry, the input file is either wrong or not supported by b43-fwcutter.
This file has an unknown MD5sum 6906b12fc2e6a06591d0990323c10e0c.

And when I run iwconfig I get the following.

lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:""
Mode:Managed Channel:0 Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thrff Fragment thr=2352 B
Encryption keyff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

virbr0 no wireless extensions.

But hey at least I am further than i was LOL
 
Old 01-18-2008, 03:36 AM   #19
jfburns
LQ Newbie
 
Registered: Dec 2003
Posts: 4

Rep: Reputation: 0
Hello deepumnit,

The b43-fwcutter in the fedora repos is version 008 which is now deprecated and won't work with the firmware that they link to at linuxwireless.org.

The firmware version you want to use is broadcom-wl-4.150.10.5.tar.bz2 I believe, because the other one (broadcom-wl-4.80.53.0.tar.bz2) is for kernel version 2.6.24(-rc). The current stable kernel is 2.6.23.9-85.fc8.

Also, if you type

b43-fwcutter -l

at a prompt, you will get a list of driver files that will work with that version.

So we will have to wait for a new version of b43-fwcutter to be packaged, or you should be able to find the new one by googling for "site:bu3sch.de b43-fwcutter" and do it yourself. It should be version 010.

Cheers
 
Old 01-18-2008, 03:51 AM   #20
jfburns
LQ Newbie
 
Registered: Dec 2003
Posts: 4

Rep: Reputation: 0
Hey all,

I just went digging around in the header files of b43-fwcutter-008 (the one currently in the repos) and it should work with

wl_apsta_mimo.o

from http://downloads.openwrt.org/sources...0.53.0.tar.bz2

The md5 sums match, at least.
 
Old 01-18-2008, 04:50 PM   #21
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello betterthanyou

I realised that the b43fwcutter program and it's files had changed in the last couple of days which is why I suggested that you try your own wireless card driver first. Some people find it works for them.

I don't know if the file jfburns mentions will work - I don't know if the output of the new b43fwcutter will work with the existing b43 driver in fedora.

However, when I did my wireless I downloaded the file that was recommended for use with the b43fwcutter/b43 driver combination at present in Fedora 8 and I still have it archived here.

This forum doesn't do attachments so if you wanted that file we will have to find some other way to get it to you.

If you want it send me a personal message through the forum with an e-mail address and I'll attach it and send it on. It's just under 850KB in size.
 
Old 01-20-2008, 12:54 PM   #22
betterthanyou
LQ Newbie
 
Registered: Jan 2008
Posts: 9

Rep: Reputation: 0
Ok I followed the instructions by jfburns and fwcutter did extract. I just did it so I will try a reboot and see if there is any progress on my wireless. On the positive side I got samba up and running and networked my printer and have full file sharing. Woo Hoo!!
 
Old 01-20-2008, 06:32 PM   #23
betterthanyou
LQ Newbie
 
Registered: Jan 2008
Posts: 9

Rep: Reputation: 0
Well there was no difference. The status of B43 in the hardware tab of the network configuration still reads "system" as it did before.
 
Old 01-20-2008, 11:31 PM   #24
jfburns
LQ Newbie
 
Registered: Dec 2003
Posts: 4

Rep: Reputation: 0
Quote:
Originally Posted by betterthanyou View Post
Ok I followed the instructions by jfburns and fwcutter did extract. I just did it so I will try a reboot and see if there is any progress on my wireless. On the positive side I got samba up and running and networked my printer and have full file sharing. Woo Hoo!!

Well there was no difference. The status of B43 in the hardware tab of the network configuration still reads "system" as it did before.
Hi betterthanyou,

I should have posted earlier and saved you the trouble: it didn't work for me either.

I'm going to play with ndiswrapper until b43-fwcutter-010 hits the main fedora repo. I'm so close with ndiswrapper right now; I blacklisted the b43 driver so ndiswrapper doesn't have to compete with it, but now some other driver named ssb has control of the wireless card! Very annoying.

Code:
[root@localhost ~]# ndiswrapper -l
bcmwl5 : driver installed
        device (14E4:4320) present (alternate driver: ssb)
I don't want to start indiscriminate blacklisting of drivers when I don't know what the do. Anyone know what the solution is?

Last edited by jfburns; 01-21-2008 at 03:40 PM.
 
Old 01-21-2008, 03:06 AM   #25
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello betterthanyou, Hello jfburns.

A couple of thoughts here.

First, what betterthanyou sees in the hardware tab of the network configuration dialogue is similar to what I see for my bcm4318 card. It has a b43 entry,and peculiarly two broadcom entries, all show that their status is system. I have no other entries in the network configuration for the card at all. At that stage my card came under the control of NetworkManager and works very well for me.

Second, which firmware you cut can be dependent on the exact model of your wireless card. The file "broadcom-wl-4.80.53.0" is the one that should run with the existing b43 fedora driver, it's the one I used. However, there is a b43legacy driver from the same stable which uses a different package and you should check, if you haven't already, if your system is using that. b43legacy is loaded automatically by the system for certain broadcom cards. The output from the command:

Code:
lsmod | grep b43
will tell you that.

The command I used to cut my firmware was:

Code:
b43-fwcutter -w /lib/firmware wl_apsta.o
Note that the instructions that go with the b43 driver included in Fedora as of this date never said to use the mimo.o file in the firmware package. That is something new for the driver that jfburns is waiting for.

By the way, I've used ndiswrapper with another card and the advice then was to blacklist the ssb driver as well. It can easily be un-blacklisted if you require it later.

Last edited by bbfuller; 01-21-2008 at 03:09 AM.
 
Old 01-21-2008, 04:02 AM   #26
dyasny
Member
 
Registered: Dec 2007
Location: Canada
Distribution: RHEL,Fedora
Posts: 995

Rep: Reputation: 115Reputation: 115
Quote:
wget http://downloads.openwrt.org/sources...0.53.0.tar.bz2
tar -xjvf broadcom-wl-4.80.53.0.tar.bz2
bcm43xx-fwcutter -w /lib/firmware/ broadcom-wl-4.80.53.0/kmod/wl_apsta.o
restart..
this solved my bcm43xx problem on Fedora8+Dell Latitude D520 just two days ago
 
Old 01-21-2008, 05:04 AM   #27
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello dyasny

You may have been a bit lucky there.

The bcm43xx-fwcutter that you used was designed for use with the bcm43xx driver which is no longer included in Fedora.

There is a b43-fwcutter included in Fedora 8 specifically to work with the new b43/b43legacy driver that is now standard.
 
Old 01-21-2008, 05:28 AM   #28
dyasny
Member
 
Registered: Dec 2007
Location: Canada
Distribution: RHEL,Fedora
Posts: 995

Rep: Reputation: 115Reputation: 115
bbfuller, I have used the yum provided fwcutter (livna rep I think)
the driver I linked to is fw version 4, which is VERY new (the recommended is v3) but this one worked for me, when v3 didn't (as well as trying to get the dell and/or broadcom provided drivers through ndiswrapper)
 
Old 01-21-2008, 06:06 AM   #29
bbfuller
Member
 
Registered: Dec 2007
Location: UK
Distribution: Mageia, MX, Manjaro, OpenSuSE, PCLinuxOS
Posts: 214

Rep: Reputation: 35
Hello dyasny

I'm always trying to keep clear in my own mind just where the broadcom situaton has got and I wonder if you could clarify for me.

You say:

Quote:
I have used the yum provided fwcutter (livna rep I think)
I'd like to clarify that. The only fwcutters I can find specifically for Fedora at the moment are in the Fedora base repository. That is both the b43 and the bcm43xx.

What I would like to be sure of is if they are working with the current firmware available on the linuxwireless.org site.

There it says that the new b43-fwcutter works only with the wl_apsta_mimo.o file in the package whereas you used the wl_apsta.o which was always specified for the b43fwcutter originally supplied with Fedora.

The difference between the bcm43xx-fwcutter which you say you used and the b43-fwcutter that I used is that they store their files in a different place in /lib/firmware and if you used bcm43xx-fwcutter I'm surprised that the b43 driver knew where to look for it.

Sorry to appear pedantic about this, but I talk to quite a few people on various forums about wireless and I like to be sure of my ground when I do.

Hope you can clarify it for me.
 
Old 01-21-2008, 07:28 AM   #30
dyasny
Member
 
Registered: Dec 2007
Location: Canada
Distribution: RHEL,Fedora
Posts: 995

Rep: Reputation: 115Reputation: 115
right. well, it took me about 3 hours to figure out - loads of googling.

1. I installed all of the available fwcutters, having tried to follow different guides I found.
2. I assume it was livna and not the base rep, but I may be wrong (and probably am))
3. when I found the advice quoted above and run the steps - it worked.
4. the laptop where I used it is a Dell Latitude D520, about 8 months old.
5. while installing, the fwcutter command presented a warning, about this being v4 of the firmware, which is new and probably not as good as v3. Ignored that - everything started working. the other fw available from berlios.de/.. did NOT work.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Help understanding wireless set up with bcm43xx on Fedora 8 Grub3r Linux - Wireless Networking 18 03-04-2008 04:35 AM
Wire network is ok but unable to connect to wireless and wireless card is not detect vitalstrike82 SUSE / openSUSE 4 11-01-2007 06:56 AM
Can't connect to wireless network with Fedora 7 Xeeon Linux - Wireless Networking 2 07-21-2007 04:19 PM
Unable to connect to TKIP encrypted network using BCM43xx & wpa_supplicant SlackwareInAZ Slackware 1 09-07-2006 07:22 AM
cannot connect to secure wireless network with Fedora 3 raindogs Linux - Wireless Networking 5 09-15-2005 10:30 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 06:33 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration