Wireless

[Dikk]

i have an atheros chipset card and recently installed fedora 8. I used madwifi rpms and installed drivers as instructed in the install file and didnt get any errors. but i still cant see my wireless device in the network devices. any clues on whats happening?

[bbfuller]

Hello Dikk

Welcome to the Forum.

Often wireless devices don't turn up in the Network Configuration program. By which I assume you mean Gnome system Menu - Administration - Network.

You would usually control a wireless card by NetworkManager.

Try these commands to see if your card is working properly. In a terminal:

su -

to obtain full root control of your machine. That's a space and a minus sign after the su.

Then:

iwconfig.

That will probably find you a wireless card 'ath0'. If it does run:

iwlist ath0 scan

and see what the results are.

If you post back about that and tell us if you installed from a Live CD or a DVD then we can probably get you online with your wireless.

[Dikk]

i dont see the ath0 device only eth0

[Dikk]

Let me start from the gecko...I had installed everything as specified and after a couple of headaches finally got fedora to recognize my atheros chipset wireless card. But i couldnt connect to any network and i couldnt get it to show in network manager it would only show in the network devices. So after trying virtually everything I decided to do a clean install with the difference this time i installed the develpoment libr devel tools gnome softw devel and x software devel, and followed the same procedure to install driver but this time the system is not recognizing my wireless card. thank you in advance

[bbfuller]

Hello Dikk

If you don't get any interfaces listed with wireless extensions in the output from 'iwconfig' then that is a puzzle.

Where did you get the rpm's you mention from. Fedora has a third party repository called Livna that provides packages precompiled for Fedora. Was it from there or some other source?

What is the output from the command:

lsmod | grep ath

once again from the root command prompt.

Edit

I see that you mention installing development tools and that pretty certainly means that you didn't install madwifi from Livna.

I think we also need to run the command:

/sbin/lspci

to determine exactly what atheros card you have.

[Dikk]

[Dikk@localhost ~]$ /sbin/lsmod | grep ath
dm_multipath 25425 0
ath5k 127825 0
mac80211 230721 1 ath5k
cfg80211 34769 2 ath5k,mac80211
dm_mod 62201 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
[Dikk@localhost ~]$

[Dikk]

code:
dm_multipath 25425 0
ath5k 127825 0
mac80211 230721 1 ath5k
cfg80211 34769 2 ath5k,mac80211
dm_mod 62201 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
[Dikk@localhost ~]$ /sbin/lspci
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
00:04.1 Modem: nVidia Corporation CK804 AC'97 Modem (rev a2)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:06.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
01:06.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
01:06.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a)
01:08.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1)
01:0a.0 Network controller: Atheros Communications, Inc. AR5416 802.11a/b/g/n Wireless PCI Adapter (rev 01)
05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12)
07:00.0 VGA compatible controller: nVidia Corporation GeForce Go 7900 GS (rev a1)
[Dikk@localhost ~]$

[bbfuller]

Hello Dikk

Don't miss my edit from my last post.

The ath5k driver that you see in the output of lsmod is one that is built into Fedora and is not part of madwifi.

For my madwifi installations I have blacklisted that driver as it probably over rides madwifi.

In the file:

/etc/modprobe.d/blacklist

add a line that reads:

blacklist ath5k

reboot and run the lsmod command again.

[Dikk]

[Dikk@localhost ~]$ /sbin/lsmod | grep ath
dm_multipath 25425 0
dm_mod 62201 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
[Dikk@localhost ~]$

[bbfuller]

Hello Dikk

In that case the madwifi drivers aren't properly installed. If they were and an atheros card was found you would be seeing the 'ath_pci' module loading.

I think in any case you are going to have a problem with this particular card.

Take a look at this page:

http://madwifi.org/wiki/Compatibility/D-Link

and see what madwifi have to say about a card containing the same chipset.

[Dikk]

ok I got it to display this

[root@localhost trunk]# /sbin/lsmod |grep ath
ath_rate_sample 20992 1
ath_pci 241728 0
wlan 220192 4 wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 283776 3 ath_rate_sample,ath_pci
dm_multipath 25425 0
dm_mod 62201 9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
[root@localhost trunk]#

but its still not showing in the network manager

[Dikk]

[root@localhost trunk]# /sbin/iwconfig ath0
ath0 IEEE 802.11g ESSID:"" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power:13 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=0/70 Signal level=-96 dBm Noise level=-96 dBm
Rx invalid nwid:2853 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[Dikk]

ok I am having the same problems as before no luck connecting to wireless network i tried using wicd but no luck either dont know what else to do...

[bbfuller]

Hello Dikk

You didn't answer earlier when I asked if you were installing from a Live CD or a DVD and it's difficult in that instance to know if you are actually seeing NetworkManager or not.

If you are going to "Gnome System Meny - Administration - Network", or opening the same application in a different way, you will see that on its title bar it is named as "Network Configuration". That is not NetworkManager.

If you installed from Live CD then NetworkManager won't even be started unless you specifically initiate it's service.

Let me know exactly which program you are trying to control the card with as they are mutually exclusive - one interferes with the other.

[Dikk]

Yes sorry i installed from DVD

[Dikk]

I tried using network manager with the taskbar icon on gnome.It sees my wired connection but when i click on the wireless tab there is nothing there. So I did some research and tried using wicd but same problem no luck with that either. I just turned network manager back on. and thanks by the way its a bit frustrating.

[Dikk]

These are some of my outputs

lo no wireless extensions.

eth0 no wireless extensions.

wifi0 no wireless extensions.

ath0 IEEE 802.11g ESSID:"Apple" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.452 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:13 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=47/70 Signal level=-49 dBm Noise level=-96 dBm
Rx invalid nwid:8 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

and

lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 Interface doesn't support scanning.

ath0 Scan completed :
Cell 01 - Address: 00:15:E9:64:7F:16
ESSID:"buckrodgrs net"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=19/70 Signal level=-76 dBm Noise level=-95 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
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
Cell 02 - Address: 00:1E:2A:5D:E8:06
ESSID:"Jenny"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=18/70 Signal level=-77 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:bcn_int=100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Extra:wme_ie=dd180050f2020101800003a4000027a400004 2435e0062322f00
Cell 03 - Address: 00:14:51:6F:17:37
ESSID:"Apple"
Mode:Master
Frequency:2.452 GHz (Channel 9)
Quality=29/70 Signal level=-66 dBm Noise level=-95 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
Extra:bcn_int=100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK

and


ath0 Link encap:Ethernet HWaddr 00:1F:F3:BF:8A:A2
inet6 addr: fe80::21f:f3ff:febf:8aa2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:03:25:3D:DA:2D
inet addr:192.168.0.162 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::203:25ff:fe3d:da2d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2900 errors:0 dropped:0 overruns:0 frame:0
TX packets:3249 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1306952 (1.2 MiB) TX bytes:709080 (692.4 KiB)
Interrupt:19

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:5998 errors:0 dropped:0 overruns:0 frame:0
TX packets:5998 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5147392 (4.9 MiB) TX bytes:5147392 (4.9 MiB)

wifi0 Link encap:UNSPEC HWaddr 00-1F-F3-BF-8A-A2-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9544 errors:0 dropped:0 overruns:0 frame:445
TX packets:3654 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:280
RX bytes:1018276 (994.4 KiB) TX bytes:164723 (160.8 KiB)
Interrupt:18

[bbfuller]

Hello Dikk

The first output in your post #17 indicates that you are already connected to a wireless network called "apple". Can you not use it.

If not you have to find just what configuration options you have used to get the machine to think it is linked to that access point as that will be stopping NetworkManager controlling the card.

[Dikk]

That is the problem i did use the terminal to state a essid but i never put in a key because it wouldnt let me. what can i do to have network manager control my card ?

[Dikk]

ok finally dont know exactly what happened but i got it to work using network manager. Any reason why the signal is so low?? Thanks by the way you where very helpfull bbfuller

[bbfuller]

Hello Dikk

I'm not sure whay the signal should be low. That on my atheros is better than most. I do have a suspicion though that the Linux drivers underestimate signal level though in order to be sure of providing consistent throughput.

What sort of rate can you transfer data at over your link?

[Dikk]

i see 11mbs transfer rate but the signal level is really about 50 % and am not more than 10 feet away from my router. Do you have any experience with aircrack

[bbfuller]

Hello Dikk

Does seem a bit low that close to the access point.

I've no experience at all of 'aircrack' I'm afraid.

[Iron_Mike]

i see 11mbs transfer rate but the signal level is really about 50 % and am not more than 10 feet away from my router. Do you have any experience with aircrack


Why you you want to use Aircrack as this is a wireless password retrieval tool?

[Zahori]

Fedora 9 doesn't find my wireless driver (BMCWL5.SYS) Oor I am unable to set it up. This is my first time that I install Linux on my HP L2000 SE. :mad:

I did a Iwconfig on my Terminal and here are the results:

[root@localhost ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
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

pan0 no wireless extensions.

ppp0 no wireless extensions.

[root@localhost ~]# iwlist ath0 scan
ath0 Interface doesn't support scanning.

Thank you for the help

[bbfuller]

Hello Zahori

As 'iwconfig' returns a wireless interface called 'wlan0', you should be using the command:

iwlist wlan0 scan

don't forget to use the command:

su -

before that to get full root control over your machine. That's a space and a minus sign after the su.

[Zahori]

Thank you for the response.

I did what you suggested: iwlist wlan0 scan and here is the result:: wlan0 Interface doesn't support scanning : Network is down

I would like fedora find and work with my BCMWL5. sys wireless driver and set it up, but do not know how.

any help I would appreciated

[bbfuller]

Hello Zahori

There are two ways of controlling a broadcom wireless card under Fedora. You don't always get a choice of which to use as the best method only works with some broadcom cards.

I think the way you are referring to with you bcmwl5 driver is ndiswrapper. Can I presume that you haven't installed the ndiswrapper software yet?

That is not necessarily the best way of controlling your card. There is a new driver called 'b43' already built into Fedora that is probably responsible for the result from iwconfig. That requires you to download and install some firmware but does not use your bcmwl5 driver. It's by far the best way to go if you have a supported card.

Could you run the command:

/sbin/lspci

in a terminal window and post back the parts about "ethernet" and "network" cards and we'll talk about the best option for you when we see what the card is.

[Zahori]

Hello Zahori

There are two ways of controlling a broadcom wireless card under Fedora. You don't always get a choice of which to use as the best method only works with some broadcom cards.

I think the way you are referring to with you bcmwl5 driver is ndiswrapper. Can I presume that you haven't installed the ndiswrapper software yet?

That is not necessarily the best way of controlling your card. There is a new driver called 'b43' already built into Fedora that is probably responsible for the result from iwconfig. That requires you to download and install some firmware but does not use your bcmwl5 driver. It's by far the best way to go if you have a supported card.

Could you run the command:

/sbin/lspci

in a terminal window and post back the parts about "ethernet" and "network" cards and we'll talk about the best option for you when we see what the card is.
----------

I really appreciate the time and the help. Here are the results:

[root@Linksys ~]# /sbin/lspci
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
00:14.6 Modem: ATI Technologies Inc SB400 AC'97 Modem Controller (rev 02)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
05:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
05:09.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
05:09.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
05:09.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
05:09.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
[root@Linksys ~]#

Thank you,

[bbfuller]

Hello Zahori,

This:

05:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

is your wireless card and you are in luck. It's one of the easier ones to set up under Linux, I use one myself.

That does suppose that you have not done any configuring or installing of wireless bits so far. However, if you haven't, try these notes:

Download this file and put it into a directory somewhere:

http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2

Acquire full root rights over your machine with this command in a terminal window:

su -

That's a space and a minus sign after the su. It gives you full root rights over your machine rather than just root rights over your ordinary users environment without it.

Use the cd command to navigate into the directory where you downloaded the above file. Issue the command:

tar xjf broadcom-wl-4.150.10.5.tar.bz2

That unpacks the file archive you downloaded and will create you a new directory where you are working called 'broadcom-wl-4.150.10.5'.

cd into that and then the 'driver' directory within that and use the command:

b43-fwcutter -w /lib/firmware wl_apsta_mimo.o

That cuts the required firmware for your card from the downloaded file and places it in the correct place for the b43 driver to find it.

Check and see if you have NetworkManager showing on the top Gnome Panel to the right in the notification area. Wait a minute or so and it "may" offer you wireless access points when you left click on it.

If not then restart the machine and left click on the NetworkManager icon, it should then bring up a list of wireless access points to connect to.

If you have an questions or problems then post back.

[kc8rmu]

For fffuller:

I'm brand new to Fedora (and this group) and I've been watching this thread with interest. I have the same wireless problem that Zahori discussed except that my notebook wireless card is a little different:

lspci | grep -i wireless command resulted in the following:
00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)

The iwconfig command yielded similar results as Zahori's

Based on your reply, I explored the http://mirror2.openwrt.org/sources/ site and found six Broadcom wireless files but was unable to find a anything that showed which driver might work with which card. If you have any suggestions along this line, I would be grateful.


The PC is an old HP ze4560us laptop on which I installed Fedora 9 to satisfy my curiosity about Linux.

Thanks in advance

Jay - kc8rmu

[bbfuller]

Hello kc8rmu

I have a 4306 card in an older desktop machine that I use for experimenting on.

I use exactly the same instructions as I posted for Zahori with the 4318.

It should get you going. That is assuming you are using Fedora 9. If you are using Fedora 8 then the situation is variable depending on how up to date it is.

As I said in an earlier post, post back with any problems or questions.

[kc8rmu]

Hello bbfuller

Thank you for the quick reply. I'll try it and let you know how it turns out.

[kc8rmu]

Hello bbfuller

Wish I had better news but my system doesn't seem to recognize b43-fwcutter as a legitimate command (see below).

[root@192 broadcom-wl-4.150.10.5]# cd driver
[root@192 driver]# b43-fwcutter -w /lib/firmware wl_apsta_mimo.o
-bash: b43-fwcutter: command not found
[root@192 driver]#

I'll keep poking around and checking the internet - probably something fundamental I forgot to install or include. If you do happen to think of anything that might help, I'd appreciate hearing from you.

Thanks again for the help so far.

[bbfuller]

Hello kc8rmu

The usual reason for that particular error is not appreciating that there are two versions of the su command.

su

gives you root rights, but only over the areas that you would have access to as your usual user. So using su would fail on two counts as your ordinary user doesn't have the right to run the file b43-fwcutter nor the path in their environment to the folder it is located in. The ordinary user also won't have write access to the /lib/firmware folder.

su -

gives you full root access over the whole machine. It's that space and minus sign after the su that make all the difference.

Give it a try and post back in case of problems.

[kc8rmu]

Hello bbfuller,

I was exploring around and found at least one problem. I hadn't loaded b43-fwcutter-011 onto my system. based upon your post on another thread, I realized that I needed it. I downloaded it to my system into the same download folder and extracted it. The command still doesn't work but my guess is that I failed to extract it to the right place where the system would expect it to be. I'll do some more research and get smarter on this (been using Linux for all of 3 days now). However, if you have any additional advice on any of this, I would love to hear it.

I have been doing this all logged in as root vs. using the su - command so, as I understand it, I should have access to the right directories.

Thanks for all the help you've been so far. I will figure this out - it will just take time.

kc8rmu

[bbfuller]

Hello kc8rmu

I've never yet seen an installation of Fedora 8, or 9 come without b43-fwcutter installed.

Try the command:

rpm -q b43-fwcutter

That will query the Fedora rpm database and tell us if it is installed.

Just where did you download your extra copy of b43-fwcutter from and how did you install it?

If you are not careful here you will end up with conflicts on your system.

I'd suggest as well that you do not do this logged in as Root. That goes against all the principles that Linux stands for. It reputation for robustness and security are based at least in part on users taking all the proper precautions and that means working as a limited user most of the time and only calling for root privileges when they are needed.

I would assume that you would get the same effect using the above commands, but I've never tried it.

My suggestion is that you get yourself into an ordinary user account and try it from there. I use that command and I've talked quite a few users through it now and I know it works.

[kc8rmu]

Hello bbfuller,

Thanks again for the quick response. As you can see, I'm groping my way around Linux. The reason I logged in as root was that for whatever reason, I would get different results using the su - command than when actually logged in as root. I'll take your advice and try to use the su - command.

I tried running the rpm -q b43-fwcutter command and got a message that said it's not installed on this machine. I then deleted the old b43fwcutter files and plan to do more research on how to install it properly.

By way of background, I initially loaded Fedora 7 from a DVD included with a Linux book, played with the GUI for a day, then downloaded Fedora 9 DVD iso file from the Fedora web site. I then prepared an installation DVD from the iso file and installed it as an update. Worst case scenario if I messed things up would be to clean the partition and reinstall so I won't be losing anything significant. This has been and continues to be a good learning experience for me.

Meanwhile, I'll try to locate the RPM file and install it properly. Thanks again for all the help and advice.

[Zahori]

I fallowed your instructions and finally my Wireless is recognized but when I tried to activated my computer crashes, that I have to turn it off and log in again.

Let me explain: I am connected to internet through a usb Aircard CDMA and use Linksys W54G router to connect Wireless with my HP printer. While I am connected to my CDMA and I try to use my wireless everythig crashes. I guess is something on the settings. Just a guess.

I thank you enormously the help and knowledge once again

Zahori



Hello Zahori,

This:



is your wireless card and you are in luck. It's one of the easier ones to set up under Linux, I use one myself.

That does suppose that you have not done any configuring or installing of wireless bits so far. However, if you haven't, try these notes:



If you have an questions or problems then post back.

[bbfuller]

Hello Zahori

I'm not sure I understand your situation.

One minute we are talking about a "broadcom 4318" card, and you posted me the output from 'lspci' to prove it, and the next minute we are talking about an "Aircard CDMA".

The latter I have never heard of and wouldn't expect the broadcom drivers to work with it in any case.

What card are we trying to control here?

[Zahori]

Hello Zahori

I'm not sure I understand your situation.

One minute we are talking about a "broadcom 4318" card, and you posted me the output from 'lspci' to prove it, and the next minute we are talking about an "Aircard CDMA".

The latter I have never heard of and wouldn't expect the broadcom drivers to work with it in any case.

What card are we trying to control here?
Hi bbfuller,

Let me try to explain: Broadcom drivers were install with no problem and are working thank to your help. I can see it in my NM, I see is connected to my Linksys Router WRT54G and the reception bar shows a strong signal. The problem is when I click the connect button. While trying to connect crashes the system so badly that I need to turn the computer off and log back in.

Thanks again
Zahori

[bbfuller]

Hello Zahori

Not being able to see you equipment you are going to have to explain this to me.

What is the USB device "Aircard CDMA" then and how does that come into the picture. Being called "Aircard" it sounds like some form of wireless network card to the uninitiated.

[Zahori]

I connect to internet using a Sprint Sierra Wireless Air Card 595U hooked to a USB port. It work perfectly. On the other hand I use my wireless to connect through WRT54G router to access my HP printer 4385, Bluetooth etc. I just mentioned the Air Card to you guessing about the possibility of a conflict between the two. Trying some troubleshooting I disconnected the Modem (Sierra) rebooted the system, log back in with out it and tried to connect the wireless again with the same result (crashed).

Thank you for your Patience
Zahori

[bbfuller]

Hello Zahori

I cannot imagine why trying to connect your wireless card will cause the system to crash that badly. My 4318 wireless card is the most reliable of cards.

Can I suggest that if you have a live cd of Fedora that you boot up from that and try configuring just the broadcom card without installing. That will at least narrow down where the problem lies.

Either with the card itself or some previous configuration.

[kc8rmu]

Hello bbfuller

Well, I reloaded Fedora 9 completely; thought the old install might have been corrupted by my mis-installation of b43-fwcutter.

It turns out, that Fedora 9 thought it was installed but I still got errors when I tried to use it - possibly a typo as I'm not the most accurate typist. I connected the machine to internet via cat 5 cable and removed then reinstalled it.

I logged in with su -, tried again to load the b43-fwcutter -w /lib/firmware wl_apsta_mimo.o command and it worked! Several files installed. However, when I tried to activate my wireless card (wlan0), I received a famaliar message:

"Determining IP information for wlan0...SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory"

I'm almost ready to admit defeat and use Windows XP for my wireless connections on that notebook (I dual boot with WinXP and the wireless card works fine)

As we used to say back when I was flying for the Air Force, "I'm out of altitude, airspeed and ideas."

Thanks for all the help.

kc8rmu

[Zahori]

Hi BBfuller,

I did what you suggested and used a live disk and had the same result. I went on and uninstall Fedora 9 386-64 to start from scratch and did not work either. I remember that at the beginning you mention that there was another way to go around the problem maybe if you don't have another idea we could use this other alternative. To be honest I would preferred to use Linux and only linux to solve the problem because my intent is leave windows once for all. I am sick of it.

Thank you again and again for all you are doing

Zahori

[bbfuller]

Hello kc8rmu

You may be neare a resolution than you think.

That message is typical of what you get if you try to contol the card from the program that starts with "Network Configuration" in its title bar, or indeed any manual way of controlling the card while NetworkManager is running.

In Fedora 9 you are expected to control you card through NetworkManager.

That may yet fail, but if it does you won't see any messages which is why I am fairly sure you are going the wrong way about this.

If you see any wireless interface on the "Devices" tab of "Network Configuration" - reached from "Gnome System Menu - Administration - Network" it would be unusual. If there is one there then its properties should be edited so that it is set NOT to "Activate device when computer starts" and that it is "Controlled by NetworkManager".

NetworkManager should be on the top Gnome Panel in the notification area, near the clock. LEft clicking on it in a working system should bring up a list of wireless networks to connect to and left clicking on one of those should prompt you for any encryption key.

Do you see any of that?

[bbfuller]

Hello Zahori

My belief is that if you can't get a 4318 to work with the b43 driver then the alternative is going to cause problems as well.

Are we still in the situation where on a new install, without the aircard connected and the machine rebooted since it was removed, that you see wireless networks in NetworkManager but the system freezes solidly when you try to connect to one of them?

The alternative method is to control the card by ndiswrapper, but my suspicion is that if the b43 driver is going this far then ndiswrapper won't be any different.

If you'd like to try though, post back and I'll dig out my ndiswrapper notes.

[Zahori]

Hello Zahori

My belief is that if you can't get a 4318 to work with the b43 driver then the alternative is going to cause problems as well.

Are we still in the situation where on a new install, without the aircard connected and the machine rebooted since it was removed, that you see wireless networks in NetworkManager but the system freezes solidly when you try to connect to one of them?

The alternative method is to control the card by ndiswrapper, but my suspicion is that if the b43 driver is going this far then ndiswrapper won't be any different.

If you'd like to try though, post back and I'll dig out my ndiswrapper notes.
Hello BBfullur,

Are any tests that I can run to be sure everything has been installed correctly or any trouble shooting that I can do to pin point the source of the problem? Are any issues that I should know about Fedora 9 386-64 version on this issue. I love Fedora because everything else works perfectly and before trying other Linux Distros I would like to give it a shot fixing the problem. I am open to new ideas. I has to be a way.

We the most appreciation,

Zahori

[bbfuller]

Hello Zahori

I haven't bothered with this particular diagnostic before because you said:

Broadcom drivers were install with no problem and are working thank to your help. I can see it in my NM, I see is connected to my Linksys Router WRT54G and the reception bar shows a strong signal

If you try:

su -

and then:

iwconfig

and then:

iwlist wlan0 scan

you should receive a list of local access points.

Obviously, if you receive some other wireless interface than 'wlan0' from the 'iwconfig' command then use that instead in 'iwlist'.

If you do receive a list of access points then your card is as nearly configured as any I would have seen. There are still circumstances where a card might not connect even then, but I've never seen the case where it brings the whole machine down.

Is it the whole machine or is it just the Desktop? Do you retain any control? Does holding down Alt - Ctrl and tapping F2 for instance give you a command line?

[Zahori]

I am sending the results of the test so you can check it out and see if you see something wrong.

[caminante@caminante ~]$ su -
Password:
[root@caminante ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
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

pan0 no wireless extensions.

ppp0 no wireless extensions.

[root@caminante ~]# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:14:BF:E4:54:1C
ESSID:"linksys"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=50/100 Signal level:-63 dBm Noise level=-73 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000001e8e8a5cfb




Any more suggestion?

Zahori

[bbfuller]

Hello Zahori

You didn't say if this crash is just the desktop or if you can get back to a command prompt.

Is the mouse movable when this happens?

You might try looking (as root) in /var/log/messages to see if it has trapped any messages indicating failure. If not then I've no more idea where to go.

Your wireless is set up so that the card is scanning and detecting your access point - I assume that is yours - personally I can't imagine the circumstance where NetworkManager can then bring the whole machine down.

If you still want to narrow the problem down, I suppose you could always turn off encryption on your access point for a short while and see what happens then.

If it crashes in those circumstances then it may be worth while, with encryption turned off, to go into "Gnome System Menu - Administration - Services", turn off the NetworkManager components and turn on the "network" service. Then try controlling your card from "Gnome System Menu - Administration - Network". That will at least determine if it is your method of controlling the card that is the problem or the driver/card combination. The "Network" tool from the menu though is only easily capable of controlling the card up to and including WEP encryption.

There is still the possibility of ndiswrapper, I can't see that it will be any different but it's something I'd try. However, only you know how much time you have and how good your patience is.

If that sheds no light then I can only suggest a new thread along the lines of "Using NetworkManager causes whole system to crash"

[Zahori]

In response to your questions: When the computer crashes I don't mouse. keyboard, and the caps lock light stars blicking. The only thing that works is the on/off button.

I am going to try turning NM off and let you know

[kc8rmu]

Hello bbfuller

Thanks for the encouragement. wlan0, my wireless card, was one of the devices listed under the "Network Configuration" tab, listed as inactive. I edited the device properties so it is controlled by NetworkManager.

The NetworkManager icon on my top bar has a red square with a white x inside. Attempts to start the card with NetworkManager resulted in a dialog box:

"DISCONNECTED.
The Network Connection has been disconnected"

Clicking on this shows wireless and wired networks greyed out.

right clicking shows "Enable Networking" and "Wireless Networks" both checked.

I did set up a wireless session with the correct SSID and WEP code. Still no luck.

The wired network works OK as I used a Cat 5E connection to check software packets.

As you said, I'm probably close, just can't quite get it to connect. Appreciate whatever advice you may have.

kc8rmu

[bbfuller]

Hello kc8rmu

Let's try:

su -

in a terminal and then:

iwconfig

and then

iwlist wlan0 scan

and post back the results.

If the output from 'iwconfig' is not 'wlan0' then use whatever interface you do get with wireless extensions in 'iwlist' in place of it.

I'm still puzzled by your installation. Did you use a DVD to perform it or a live cd? I still don't believe I've seen an installation that doesn't include b43-fwcutter.

[kc8rmu]

Hello bbfuller

I'm at work now so I'll run those checks when I get home and post the results.

I installed from a DVD - Downloaded the ISO file from http://fedoraproject.org/en/get-fedora. I did a media check before install and it passed no problem.

Linux seems to want an internet connection and I installed disconnected which may be part of the problem. I might do a complete reinstall tonight connected via cat5 cable and see it that works better. I don't really have any data saved so reinstalling is not a big deal.

My distribution DVD has b43-fwcutter in a "Packages" directory; Unfortunately, Linux doesn't seem to be able to get at it once it's installed. The software install/uninstall program in Gnome lacks the flexibility to specify a soucre - options are limited to checking/unchecking preloaded sources, none of which seem to be the distribution DVD.

Thanks again for taking time for me. I'll post that data as soon as possible.

[bbfuller]

Hello kc8rmu

Fedora doesn't actually need an internet connection during install but it does tend to assume one thereafter. I understand it is possible in F9 to install extra programs from the install media after install though I've never done it.

Humor me though.

After you have done the reinstall, before you do anything else, try in a terminal window:

rpm -q b43-fwcutter

That queries the rpm database of your installation for the specific package.

On every machine I've looked at since we've been talking - even if it doesn't have a broadcom card onboard - that package is installed

[Zahori]

Hello Zahori

You didn't say if this crash is just the desktop or if you can get back to a command prompt.

Is the mouse movable when this happens?

You might try looking (as root) in /var/log/messages to see if it has trapped any messages indicating failure. If not then I've no more idea where to go.

Your wireless is set up so that the card is scanning and detecting your access point - I assume that is yours - personally I can't imagine the circumstance where NetworkManager can then bring the whole machine down.

If you still want to narrow the problem down, I suppose you could always turn off encryption on your access point for a short while and see what happens then.

If it crashes in those circumstances then it may be worth while, with encryption turned off, to go into "Gnome System Menu - Administration - Services", turn off the NetworkManager components and turn on the "network" service. Then try controlling your card from "Gnome System Menu - Administration - Network". That will at least determine if it is your method of controlling the card that is the problem or the driver/card combination. The "Network" tool from the menu though is only easily capable of controlling the card up to and including WEP encryption.

There is still the possibility of ndiswrapper, I can't see that it will be any different but it's something I'd try. However, only you know how much time you have and how good your patience is.

If that sheds no light then I can only suggest a new thread along the lines of "Using NetworkManager causes whole system to crash"
BBfuller,

I have been travelling on the Internet looking for answers on my problem and I read that they are some issues that are difficult to set on Fedora 386-64 one of those problems are related to the BMC drivers (installation load and stetting). Before I give up on this issue I would like to try the other alternative (ndiswrapper) if you could help, step by step, on that I would be great.

Note: I don't know how to describe it but it seems that the is related to Fedora and only to Fedora because I have Ubuntu 8.4 386-64 in an other Laptop (my wife) that is exactly like mine and had no problem setting the BCM4318, in her computer is up and working.

Before hand I appreciate the help,

Zahori

[kc8rmu]

Hello bbfuller

Ref your second last post, here's what you asked for:

[jay@localhost ~]$ su -
Password:
[root@localhost ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
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

pan0 no wireless extensions.

[root@localhost ~]# iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down

Regarding your most recent post:

[jay@localhost ~]$ rpm -q b43-fwcutter
b43-fwcutter-011-3.fc9.i386

I know that b43-fwcutter is available because I used it last night to install
the wireless card firmware. Not sure if it was available before I reinstalled it.

I may still completely reinstall Fedora 9; First thing I'll do is check on the above.

Thanks again

kc8rmu

[bbfuller]

Hello Zahori

Over the last day or so I've been stumbling across posts on the forum where people have been having trouble with the latest F9 updates, possibly the kernel, possibly NetworkManager. It's not universal, but if you have a kernel still installed on your system earlier than 2.6.25.6-55.fc9 then it might be worth booting with that and trying your wireless.

If you decide to give ndiswrapper a try please remember that sometimes there are incompatibilities between the Fedora kernel and some wireless drivers.

Below are the general notes for ndiswrapper:

This is the generic instruction set for installing your windows driver with ndiswrapper:

Acquire full root rights with:

su -

That's a space and a minus sign after the su. It gives full root rights over the machine, not just over your own environment which is what you get with plain su.

If you haven't already, install the Livna repository:

rpm -i http://rpm.livna.org/livna-release-9.rpm

Obviously, if you are still running Fedora 8 replace the 9 in the above with an 8

Install ndiswrapper:

yum install kmod-ndiswrapper

should bring in the three relevant packages.

The set up and configure ndiswrapper with:

ndiswrapper -i <path to your windows driver file>.inf

should install the driver,

ndiswrapper -l

if it is going to work should return "driver present" and "hardware present"

modprobe ndiswrapper

should load the driver into the kernel, but probably only until you reboot.

If you are lucky now and NetworkManager is running then after a short while it 'may' begin reporting wireless networks. NetworkManager is the preferred method of connecting to wireless networks with Fedora and should be located on the top Gnome Panel to the right in the notification area.

If it's not there, "Gnome System Menu - Administration - Services" will give you the opportunity to start it, set it to start at boot time and save the changes. {This last sentence will probably only be necesary if you have installed Fedora 8 from a DVD.}

If it works, or indeed if it doesn't you will also need to run:

ndiswrapper -ma

and then edit the file:

/etc/modprobe.conf

as root and add the line:

alias wlan0 ndiswrapper

to it.

{Editing modprobe.conf should only be applicable to Fedora 8. In many instances Fedora 9 doesn't even have the file.}

With that all in place, reboot the computer to get the alias recognised and open "Gnome System Menu - Administration - Network", highlight your wlan0 entry, click "Edit" and make sure now that it is set NOT to "Activate device when computer starts" but that if it is there, "Controlled by NetworkManager" is ticked. That last item will only be in place if your machine is currently fairly up to date.

{This section will also probably only be applicable to Fedora 8}

Reboot and try connecting again.

If you are not able to connect at this stage, adding the line:

blacklist b43

to the file:

/etc/modprobe.d/blacklist

may help. The b43 driver is supposed to bow out gracefully but this appears not always to be the case.

If you have problems during that process I'll be looking for questions.

[bbfuller]

Hello kc8rmu

As a last thought I'd suggest taking a look in the '/lib/firmware' directory and if there is a b43 directory there look and see if it is populated. On my system there are 38 files in it.

If your system has that and your 'iwconfig' is finding an interface then the failure of 'iwlist' is odd.

If you do consider a new install please try the check for b43-fwcutter before you go anywhere after the install.

Also, try the wireless before you do any updating. As I said to Zahori above, I've seen one or two instances recently of people reporting wireless problems after the latest batch of updates.

[kc8rmu]

Hello bbfuller

In fact I have exactly 38 files in the '/lib/firmware/b43' directory. I know that the wireless "card" in the notebook works as I have Windows XP and Fedora 9 both installed. The wireless card and ethernet card both work fine under Windows XP; the ethernet card works but the wireless card seems to go stupid on me in Fedora 9.

I probably won't have time to do a reinstall tonight. I'll reinstall connected via Cat5 cable and see if that helps. First thing I'll do after reinstall is try to install the wireless card and see if I can get it running.

Really do appreciate your help.

kc8rmu

[kc8rmu]

Hello bbfuller,

A quick update.


I encountered problems reloading Fedora last night so I downloaded another copy of the i386 DVD iso file and burned a new copy to DVD. That seemed to load fine and I'm updating it now.

It seems to be a fairly comprehensive update. I'll probably have to let it go through the night - It's been running for around an hour now and is only about 20% complete.

per your request, I ran the command 'rpm -q b43-fwcutter' and the system recognized the command. Not sure what the problem was with the previous install - might have had a bad download or DVD burn (although the DVD passed the install media check).

I'll try to get the card working tomorrow per your previous instructions and let you know how that turns out.

kc8rmu

[kc8rmu]

Hello bbfuller

Downloaded, burned to DVD, reinstalled and updated Fedora 9. tonight I installed the firmware via b42-fwcutter. It installed some files but no luck connecting anything with the wireless. see my results below:

[root@localhost ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
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

pan0 no wireless extensions.

[root@localhost ~]# iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down

Basically, the same response as before. Any chance the firmware file might not be the right one for my HP ZE4560us??

Trying to use NewtorkManager resulted in the following:

DISCONNECTED

The network conection has been disconnected. The wireless card works well under Windows XP so it shouldn't be the card or network.


Any ideas??

Thanks.

[bbfuller]

Hello kc8rmu

Given that the actual file you cut was from within the broadcom-wl-4.150.10.5 package, that the form of the cut command you used was - give or take paths to the actual file - like the one below:

b43-fwcutter -w /lib/firmware wl_apsta_mimo.o

and that you have 38 files in the /lib/firmware/b43 directory, it's hard to understand why your card is not picking up like mine does.

The fact that you are seeing a response from 'iwconfig' would indicate that the b43 module is loading.

Can I suggest that you reboot the machine and then run:

dmesg | grep b43

from the command line so that we can examine any messages generated by the b43 module when loading.

I know what my b43 looks like at boot so a comparison could be illuminating.

[kc8rmu]

Hello bbfuller,

Thanks for the reply. Tried the dmesg | grep b43 command:

[root@localhost ~]# dmesg | grep b43
b43legacy-phy0: Broadcom 4306 WLAN found
b43legacy-phy0 debug: Found PHY: Analog 1, Type 2, Revision 1
b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43legacy-phy0 debug: Radio initialized
input: b43legacy-phy0 as /devices/virtual/input/input9
b43legacy-phy0 ERROR: Firmware file "b43legacy/ucode4.fw" not found or load failed.
b43legacy-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 3).
[root@localhost ~]#

Also did another iwconfig and got:

[root@localhost ~]# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
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

pan0 no wireless extensions.


As an aside, after I updated the basic installation, I noticed two different variations of Linux in my dual boot menu (I dual boot with Win XP as the "other" OS)

Fedora (2.6.6.25.6-55.fc9.i686)
and
Fedora 2.6.6.25-14.fc9.i686)

I assume that the -55 version is the more current. Tried the above with both and got the same results.

Maybe I'm missing something fundamental. Again, I'd welcome any ideas you may have on this.

[Zahori]

Hi BB fuller,

For some reason we lost contact. I have not been able so solve problem (crash) that we have been trying to solve. It seems the problem occurred when the wireless tries to make a hand shake with my router WRT54G. The first time I hit the connect button it asked for the encryption key, I wrote it down and... tries to connect Crashes the whole computer. Please do not give up on me i need the help.

Thank you wvery much

Zahori

[bbfuller]

Hello kc8rmu,

Not come across this particular problem before, it's this part of your output:

b43legacy-phy0 ERROR: Firmware file "b43legacy/ucode4.fw" not found or load failed.
b43legacy-phy0 ERROR: You must go to http://linuxwireless.org/en/users/D...#devicefirmware and download the correct firmware (version 3).

that gives the game away.

You are going to need the b43-legacy firmware which is this file:

http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o

It then looks as if you only need to issue the command:

b43-fwcutter -w /lib/firmware wl_apsta-3.130.20.0.o

from within the same directory for it to cut.

It shouldn't hurt leaving the original b43 firmware in place as this should either create a b43-legacy folder of its own or append the files in b43.

I'd be interested to hear which as I have no need to do this and so can't gain experience with it.

Incidentally, the background to the broadcom cards is quite complex. If you are interested, I'm getting my information from the b43 home site here:

http://linuxwireless.org/en/users/Drivers/b43?action=show&redirect=en%2Fusers%2FDrivers%2Fbcm43xx#devicefirm ware

[bbfuller]

Hello Zahori

Certainly haven't given up on you, not sure what to suggest next though.

If we haven't tried it you could run the commands:

dmesg | grep b43

and

dmesg | grep wlan0

to see if they give any indication that the card is not initialising correctly.

Question for you, when you tried the live cd, did you try it without ever introducing the Aircard to the computer. It's the easiest thing to blame of course as it's the significant different factor. I don't just mean unplugging it, I mean trying before it had ever been plugged in on that installation.

You mention the 64bit operating system. I'd be inclined to try the 32bit version. If only from a live cd and see if the problem recurs there. You can run the 32bit version of an OS easily on 64bit hardware.

The only other thing I can think of trying is ndiswrapper and the instructions for that are in post #60.

[kc8rmu]

Hello bbfuller

SUCCESS!!!!

I am really embarrassed. When I was posting the "dmesg | grep b43" for you this morning, I got diverted (I'm the breakfast cook on weekends) and failed to read the actual results. I had been exploring the b43-Linux Wireless web site and thought that, due to the age of this laptop (about 6 years), the legacy driver might work. Your instructions were much more clear than what was on the page though. Thanks very much for hanging in there with me.

After I installed the driver/firmware, I had to start the wireless card manually by using the "Connect to other Wireless Network" function of the NetworkManager applet. Once I typed in the SSID and WEP Key, it quickly connected and now connects when I reboot.

I checked the lib/firmware directory and there are both b43 and b43legacy subdirectories.:

[root@localhost b43legacy]# ll
total 132
-rw-r--r-- 1 root root 18 2008-06-21 16:38 a0g0bsinitvals2.fw
-rw-r--r-- 1 root root 158 2008-06-21 16:38 a0g0bsinitvals5.fw
-rw-r--r-- 1 root root 2520 2008-06-21 16:38 a0g0initvals2.fw
-rw-r--r-- 1 root root 1818 2008-06-21 16:38 a0g0initvals5.fw
-rw-r--r-- 1 root root 158 2008-06-21 16:38 a0g1bsinitvals5.fw
-rw-r--r-- 1 root root 1818 2008-06-21 16:38 a0g1initvals5.fw
-rw-r--r-- 1 root root 18 2008-06-21 16:38 b0g0bsinitvals2.fw
-rw-r--r-- 1 root root 158 2008-06-21 16:38 b0g0bsinitvals5.fw
-rw-r--r-- 1 root root 2520 2008-06-21 16:38 b0g0initvals2.fw
-rw-r--r-- 1 root root 1818 2008-06-21 16:38 b0g0initvals5.fw
-rw-r--r-- 1 root root 1320 2008-06-21 16:38 pcm4.fw
-rw-r--r-- 1 root root 1320 2008-06-21 16:38 pcm5.fw
-rw-r--r-- 1 root root 21680 2008-06-21 16:38 ucode11.fw
-rw-r--r-- 1 root root 16360 2008-06-21 16:38 ucode2.fw
-rw-r--r-- 1 root root 20096 2008-06-21 16:38 ucode4.fw
-rw-r--r-- 1 root root 22280 2008-06-21 16:38 ucode5.fw
[root@localhost b43legacy]#


Once again, Thank you very much for all of your help. I don't know if your helpful attitude is typical of the Linux community, but I really enjoyed working with you - I would probably have given up without your encouragement and certainly learned a lot about Linux (still have much to learn) in the process.

kc8rmu

[bbfuller]

Hello kc8rmu

Forums vary but you'll find a lot of helpful people on this one, just ignore any that aren't!

I've been playing with Linux now for 10 years and I'm always learning. I think it's one of the best parts. Anytime you think you know all about something in it, it just means you haven't been paying attention, things change all the time.

This business about drivers for broadcom cards is a good example. This time last year we were all struggling with a different driver that didn't work very well and then moving on to ndiswrapper. Then over a few month period last Autumn b43 appeared, matured and works brilliantly for all the cards it supports.

Enjoy your Linux, look forward to seeing you around the forum.

[Zahori]

Thank you for your quick replay. After playing a little bit with Ubuntu and Mandriva a while a go I am hooked with Fedora despite this problem (that's how much I like it) so I am willing to go as far is needed to fix it

I am sending result of the test you asked for hoping that it might help the source of the problem.I am worried the second test result: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Don't what exactly means.

Thank you

[caminante@caminante ~]$ su -
Password:
[root@caminante ~]# dmesg | grep b43
b43-phy0: Broadcom 4318 WLAN found
b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8
input: b43-phy0 as /devices/virtual/input/input10
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 32-bit DMA initialized
Registered led device: b43-phy0::radio
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
[root@caminante ~]#

[root@caminante ~]# dmesg | grep wlan0
ADDRCONF(NETDEV_UP): wlan0: link is not ready
[root@caminante ~]#

[bbfuller]

Hello Zahori

I really don't know, your card initialising is very like both my broadcom 4318 and 4306 so no clues there.

Did you try the other suggestions I made, repeated below.

Question for you, when you tried the live cd, did you try it without ever introducing the Aircard to the computer. It's the easiest thing to blame of course as it's the significant different factor. I don't just mean unplugging it, I mean trying before it had ever been plugged in on that installation.

You mention the 64bit operating system. I'd be inclined to try the 32bit version. If only from a live cd and see if the problem recurs there. You can run the 32bit version of an OS easily on 64bit hardware.

The only other thing I can think of trying is ndiswrapper and the instructions for that are in post #60.

[Zahori]

I uninstall 86-64 version and went on and install the 386, thinking that it might help solve the problem. At the beginning I got connected but a got disconnected (at the same time) from Internet, when I tried use both at the same time it crashed the system. I haven't been able to connect since then. The ndisk didn't work either. I don't know what to do. Any ideas or where to go for answers?

Thank you for your patiences,
zahori

Hello Zahori

I really don't know, your card initialising is very like both my broadcom 4318 and 4306 so no clues there.

Did you try the other suggestions I made, repeated below.

[bbfuller]

Hello Zahori

I personally am out of ideas.

I think it's some combination of your Aircard with your wireless card, as they are both some sort of wireless device I'm not even sure you can use them both at once.

I suggest a new thread along the lines of "Aircard and wirless interface at same time crashes machine" and see if you get anyone with specific knowledge.

Good Luck.