View Full Version : FC6 Wireless Using Broadcom BCM4308
zenarcher
2006-11-03, 01:51 PM CST
I have been trying to set up my wireless from information at this forum: http://forums.fedoraforum.org/showthread.php?t=102697&highlight=bcm43xx
My notebook is a HP Pavilion ze2000 using the Broadcom BCM4308 for wireless. I had it working with SUSE 10.0 using ndiswrapper.
After my install, both eth0 and eth1 (the wireless) appear when I go to Administration>Network. However, the wireless is not configured there and shows as "inactive." I have checked and the install did use the correct i686 kernel, rather than the often incorrect i586, as I have noted some people found.
I have installed the fwcutter and dowloaded and extracted the file shown at the end of the post mentioned above. Once the steps have been followed, I do get a light on the notebook, indicating active wireless. Going back into Administration>Network, I see the wireless there, however it is denoted as BCM4318 rather than BCM4308, as my notebook uses. I don't know if that is critical or not. When I attempt to activate the wireless at this point, I get an error message that a connection cannot be made and I should check the cable. At the moment, I am using no security on my Linksys wireless router, in an effort to get this working.
I am a little confused at the above mentioned instructional post regarding the wireless and am not sure whether I am supposed to install the Windows BCM4308 driver somewhere, or not.
I really hope someone here can help me get this wireless working. Everything else is just fine using FC6 and this is the one problem I have to overcome.
I'm not very familiar with wireless, nor Fedora Core, so any detailed help/troubleshooting would be appreciated. If all else fails, I'd even appreciate a link to where I can get specifics for installing my wireless, preferably with fwcutter, but failing that, with ndiswrapper.
Regards,
zenarcher
zenarcher
2006-11-03, 05:57 PM CST
Okay, I finally have wireless with the Broadcom working....sort of. I went ahead and extracted the files from my Windows disk for the Broadcom and moved them into Home. I then followed Stan's instructions for installing fwcutter.
I managed to get the wireless light...even when I boot up and can see the wireless eth1 when I go into Administration>Network. But, I cannot connect wireless. Each time I boot, I must go to Administration>Network, where eth0 is shown as "Inactive" and I must Activate it. Once activated, it's working and I can connect.
Can anyone help me at this point, so my wireless will automatically activate when I boot up?
Thanks,
zenarcher
Batman2372
2006-11-04, 08:29 AM CST
I actually have a really noobish question for you. I'm trying to do basically the same thing (have a Presario V3015), but the drivers I have are in an EXE. How do extract the drivers from the exe so that I can put them in?
partha
2006-11-04, 09:22 AM CST
I actually have a really noobish question for you. I'm trying to do basically the same thing (have a Presario V3015), but the drivers I have are in an EXE. How do extract the drivers from the exe so that I can put them in?
If you have cabextract installed, simply do
cabextract driver.exe
where driver.exe is the exe file containing the drivers.
If you do not have cabextract installed then do
yum install cabextract
That should do it.
HTH,
Partha
www.partha.com
partha
2006-11-04, 09:26 AM CST
...
I managed to get the wireless light...even when I boot up and can see the wireless eth1 when I go into Administration>Network. But, I cannot connect wireless. Each time I boot, I must go to Administration>Network, where eth0 is shown as "Inactive" and I must Activate it. Once activated, it's working and I can connect.
Can anyone help me at this point, so my wireless will automatically activate when I boot up?
Thanks,
zenarcher
Go to Administration ->Network and click on eth0 and then hit edit. In the resulting dialogbox, check the button that says, "Activate device when computer starts".
HTH,
Partha
www.partha.com
zenarcher
2006-11-04, 11:20 AM CST
I did go into Network and checked the box to Activate device when computer starts, but it doesn't seem to be doing so. That's the only real problem I have left.
When I reboot the system, the progress bar goes right along....doesn't come up to Interactive Menu or anything.....and at the end, before the KDE sign in appears, the blue wireless light turns on, indicating wireless running. I log in....bring up the KDE desktop....and the Network monitor shows full signal, etc. But, I cannot connect. In order to connect, I must go to Administration>Network....and I see "Inactive" for the wireless. I click to Activate...see the message that it's looking for the IP address....then, after a short delay, the wireless activates. I am then good for the entire session, until I reboot.
Any ideas??
zenarcher
partha
2006-11-04, 11:57 AM CST
I did go into Network and checked the box to Activate device when computer starts, but it doesn't seem to be doing so. That's the only real problem I have left.
When I reboot the system, the progress bar goes right along....doesn't come up to Interactive Menu or anything.....and at the end, before the KDE sign in appears, the blue wireless light turns on, indicating wireless running. I log in....bring up the KDE desktop....and the Network monitor shows full signal, etc. But, I cannot connect. In order to connect, I must go to Administration>Network....and I see "Inactive" for the wireless. I click to Activate...see the message that it's looking for the IP address....then, after a short delay, the wireless activates. I am then good for the entire session, until I reboot.
Any ideas??
zenarcher
Well you did not tell us that you use KDE did you? :) Anyway, I don't work with KDE.
Please print out the contents of the following file.
/etc/sysconfig/network-scripts/ifcfg-eth0
Partha
www.partha.com
zenarcher
2006-11-04, 12:54 PM CST
Sorry I failed to mention KDE, as that has always been what I've used with Linux, so I didn't think about it. Actually, eth0 is the designation for my wired LAN and eth1 is the designation for my wireless. So I am posting here the info. from eth1
# Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
DEVICE=eth1
ONBOOT=no
BOOTPROTO=dhcp
HWADDR=00:14:a5:15:05:dd
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
TYPE=Wireless
ESSID=
CHANNEL=1
MODE=Managed
RATE='11 Mb/s'
USERCTL=no
IPV6INIT=no
PEERDNS=yes
I don't know if it's important or not, but I'm using a Linksys Wireless router...Mod. WRT56G which works well with other wireless devices here.
Cheers,
zenarcher
partha
2006-11-04, 01:03 PM CST
Sorry I failed to mention KDE, as that has always been what I've used with Linux, so I didn't think about it. Actually, eth0 is the designation for my wired LAN and eth1 is the designation for my wireless. So I am posting here the info. from eth1
# Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
DEVICE=eth1
ONBOOT=no
BOOTPROTO=dhcp
HWADDR=00:14:a5:15:05:dd
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
TYPE=Wireless
ESSID=
CHANNEL=1
MODE=Managed
RATE='11 Mb/s'
USERCTL=no
IPV6INIT=no
PEERDNS=yes
I don't know if it's important or not, but I'm using a Linksys Wireless router...Mod. WRT56G which works well with other wireless devices here.
Cheers,
zenarcher
Using a text editor, change ONBOOT=no to ONBOOT=yes
and your problems should be solved.
HTH,
Partha
www.partha.com
zenarcher
2006-11-04, 01:22 PM CST
Okay, I followed your instructions here, rebooted and still seem to have the same problem, for some reason. I checked the file again and it is showing ONBOOT=yes, so I'm thinking that is okay now.
To get the wireless working after a reboot, I have to go to Administration>Network and there I see eth1 checked but appearing as inactive. I then must deactivate it and click on Activate again...wait a few seconds...and it begins working and shows as Active.
I better not make an assumption here, but I believe you meant for me to log in as su - to look at and make the changes to the ONBOOT=yes. I'm still fairly new with Linux.
Cheers,
zenarcher
Batman2372
2006-11-04, 01:54 PM CST
I feel like I'm starting to hijack this thread, and I'm sorry for that, but I think I'm a bit lost.
Just reinstalled a fresh FC6. I used cabextract to extract everything from the Broadcom driver that is given on the HP site for my computer. I'd like to use fwcutter, but at this point, using DarkMage's instructions, I don't know where to go from here. Here's what I've done so far:
a) downloaded and installed fwcutter
b) cut the driver with /usr/bin/bcm43xx-fwcutter -w /lib/firmware bcmwl5.sys
c) /sbin/depmod -a
d /sbin/modprobe bcm43xx
When I go into system-config-network, I don't see the wireless at all
I'm sorry for being such a noob, but the laptop is brand new, and I can't find anyone who's even attempted this on mine, let alone got it to work.
Any assistance would definitely be welcomed.
partha
2006-11-04, 01:57 PM CST
Okay, I followed your instructions here, rebooted and still seem to have the same problem, for some reason. I checked the file again and it is showing ONBOOT=yes, so I'm thinking that is okay now.
To get the wireless working after a reboot, I have to go to Administration>Network and there I see eth1 checked but appearing as inactive. I then must deactivate it and click on Activate again...wait a few seconds...and it begins working and shows as Active.
Cheers,
zenarcher
So, when you boot, the ifcfg-eth1 file is OK, but you still don't have wireless on boot?
Can you post any error messages you see regarding eth1 during boot up? You can try something like dmesg |grep eth1 or look through the file /var/log/message and grep for eth1 and post that information here?
Partha
www.partha.com
partha
2006-11-04, 02:14 PM CST
I feel like I'm starting to hijack this thread, and I'm sorry for that, but I think I'm a bit lost.
Just reinstalled a fresh FC6. I used cabextract to extract everything from the Broadcom driver that is given on the HP site for my computer. I'd like to use fwcutter, but at this point, using DarkMage's instructions, I don't know where to go from here. Here's what I've done so far:
a) downloaded and installed fwcutter
b) cut the driver with /usr/bin/bcm43xx-fwcutter -w /lib/firmware bcmwl5.sys
c) /sbin/depmod -a
d /sbin/modprobe bcm43xx
When I go into system-config-network, I don't see the wireless at all
I'm sorry for being such a noob, but the laptop is brand new, and I can't find anyone who's even attempted this on mine, let alone got it to work.
Any assistance would definitely be welcomed.
Hey no hijacking! :)
When you "cut" the firmware files out, did you get a bunch of files with the extension .fw in the same directory as the driver file?
If yes, then copy them to the directory /lib/firmware
Once you do that if you restart your network
service network restart
or reboot, your wireless should work. This assumes that when you installed FC6, it recognized your wireles card and automatically modprobes bcm43xx at bootup. if not, you do:
modprobe bcm43xx
Check to see that a wireless card is recognized by
iwconfig
If yes, then do
dhclient wlan0 #(or eth1 or whatever is shown by iwconfig)
Now check to see if you have a network connection
ping 192.168.1.1 #(or whatever the ipaddress of your AP)
Now ping any computer such as comcast.net or your ISP
ping comcast.net
if you have a response, you are all set, open firefox and have fun.
HTH,
Partha
www.partha.com
zenarcher
2006-11-04, 02:18 PM CST
Maybe I have misled you with this, but I'm not getting any error during bootup. In fact, the progress bar, during bootup, goes right through network without an issue. Once KDE is up, KiWiFi Manager shows a connection, with a signal strength of 100. As to the status of Active Connection....LocalIP is shown as "unavailable." Likewise, eth1 does not appear on gkrellm.
If I then go to Administration>Network, I see eth1 but it is "Inactive." I cannot just click to Activate, as I get an error that no connection could be made. If I click to "Deactivate" and allow eth1 to be deactivated, then click Activate...wait about 3 seconds, eth1 changes to "Activated." At this time, eth1 appears in gkrellm and KiWiFiManager then shows an active IP address.
So, the only error I seem to get getting is if I try to activate from Administration>Network, that a connection cannot be made, until I Deactivate eth1, then Activate it again.
I am using SELinux, if that makes any difference.
Cheers,
zenarcher
partha
2006-11-04, 02:33 PM CST
Maybe I have misled you with this, but I'm not getting any error during bootup. In fact, the progress bar, during bootup, goes right through network without an issue. Once KDE is up, KiWiFi Manager shows a connection, with a signal strength of 100. As to the status of Active Connection....LocalIP is shown as "unavailable." Likewise, eth1 does not appear on gkrellm.
....
I am using SELinux, if that makes any difference.
Cheers,
zenarcher
No, you have not misled me yet. I am asking you to post the output of dmesg |grep eth1 here. It is possible that while booting, the network is started prior to initializing the wireless card and if that is true, you will get something like what you say.
SELinux is new information :)
I don't use it and and don't know how it will affect wireless.
HTH,
Partha
www.partha.com
Batman2372
2006-11-04, 02:34 PM CST
oops... I just made a new topic to stop the hijacking... sorry.
http://forums.fedoraforum.org/showthread.php?p=668423#post668423
partha
2006-11-04, 02:40 PM CST
...
Can anyone point me in the right direction?
I just gave you a step-by-step and you ignored them all.
HTH,
Partha
www.partha.com
Batman2372
2006-11-04, 02:47 PM CST
I followed your instructions.
All the .fw files are in /usr/firmware
After a network restart, doing an iwconfig showed nothing. So I did a modprobe bcm43xx and then did an iwconfig again, and it lists lo (no wireless extensions), eth0 (no wireless extensions), and sit0 (no wirless extensions).
So something still isn't working. I just don't know what.
partha
2006-11-04, 02:51 PM CST
Please reboot and tell me what the error message related to eth1 are.
HTH,
Partha
www.partha.com
Batman2372
2006-11-04, 02:59 PM CST
No mention of eth1 throughout the startup.
zenarcher
2006-11-04, 03:01 PM CST
Okay, now I understand what you are saying. I don't think SELinux would cause an issue, as eth0 works fine when I plug a cable into it....and looking in Administration>Network....everything as far as settings appears to be the same for eth0 and eth1.
Here is the info you requested:
[zenarcher@localhost ~]$ dmesg |grep eth1
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
eth1: no IPv6 routers present
[zenarcher@localhost ~]$
zenarcher
partha
2006-11-04, 03:13 PM CST
No mention of eth1 throughout the startup.
What is the output of ifconfig -a ?
Partha
www.partha.com
partha
2006-11-04, 03:20 PM CST
Okay, now I understand what you are saying. I don't think SELinux would cause an issue, as eth0 works fine when I plug a cable into it....and looking in Administration>Network....everything as far as settings appears to be the same for eth0 and eth1.
Here is the info you requested:
[zenarcher@localhost ~]$ dmesg |grep eth1
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
eth1: no IPv6 routers present
[zenarcher@localhost ~]$
zenarcher
I don't see any problems here and your system should boot up with the wireless device. I am at a loss here. Perhaps there is something else that is preventing it from becoming active at boot. what does the following output say?
dmesg |grep eth1 -A10
Partha
www.partha.com
PS: Have you considered using ndiswrapper? Check out my site.
Batman2372
2006-11-04, 03:34 PM CST
eth0 Link encap:Ethernet HWaddr 00:16:D3:08:D0:7F
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:d3ff:fe08:d07f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1185 errors:0 dropped:0 overruns:0 frame:0
TX packets:1335 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:984593 (961.5 KiB) TX bytes:221338 (216.1 KiB)
Interrupt:225 Base address:0xc000
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:1471 errors:0 dropped:0 overruns:0 frame:0
TX packets:1471 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2708908 (2.5 MiB) TX bytes:2708908 (2.5 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
zenarcher
2006-11-04, 03:50 PM CST
Okay, I have the information you requested. I used ndiswrapper with SUSE10.0...but had problems with it using SUSE 10.1. My biggest complaint about ndiswrapper was when doing a kernel update, I never could manage to clean it and get it working again, without doing a complete SUSE reinstall. I also recall that I had to find some sort of script to get it to run automatically, at boot up. I will look at your site, though...as it might be an answer with Fedora. I have four desktop systems on my network, along with this notebook system. One of the boxes, which my wife uses for games, is on Windows and is wireless. I would like to get the other three boxes on FC to go wireless, if I can find some sort of inexpensive PCI wireless card or USB wireless, which would be reasonably easy to set up with FC6.
I was just getting the hang of SUSE, when I switched to FC....and I like FC real well....but have a lot to learn. I used MS since the days of DOS 5.0, been on the Internet since 1991 and worked in hardware design way back in the 1970's, but this stuff is all new and as an old retired guy, I'm slower learning than I used to be!
ADDRCONF(NETDEV_UP): eth1: link is not ready
SoftMAC: Scanning finished
SoftMAC: Queueing Authentication Request to 00:16:b6:cd:fb:05
SoftMAC: Cannot associate without being authenticated, requested authentication
SoftMAC: Already requested authentication, waiting...
SoftMAC: Sent Authentication Request to 00:16:b6:cd:fb:05.
SoftMAC: Open Authentication completed with 00:16:b6:cd:fb:05
SoftMAC: sent association request!
SoftMAC: associated!
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
Bluetooth: Core ver 2.10
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
--
eth1: no IPv6 routers present
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Canceling existing associate request!
SoftMAC: Associate: Scanning for networks first.
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
--
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
--
eth1: no IPv6 routers present
audit(1162674824.135:12): avc: denied { write } for pid=3206 comm="ifconfig" name="[12410]" dev=pipefs ino=12410 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.135:13): avc: denied { write } for pid=3206 comm="ifconfig" name="[12410]" dev=pipefs ino=12410 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.135:14): avc: denied { read } for pid=3206 comm="ifconfig" name="[11963]" dev=pipefs ino=11963 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.135:15): avc: denied { write } for pid=3206 comm="ifconfig" name="[11963]" dev=pipefs ino=11963 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.135:16): avc: denied { read } for pid=3206 comm="ifconfig" name="[11964]" dev=pipefs ino=11964 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.135:17): avc: denied { write } for pid=3206 comm="ifconfig" name="[11964]" dev=pipefs ino=11964 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.135:18): avc: denied { read } for pid=3206 comm="ifconfig" name="[11965]" dev=pipefs ino=11965 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.135:19): avc: denied { write } for pid=3206 comm="ifconfig" name="[11965]" dev=pipefs ino=11965 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.175:20): avc: denied { write } for pid=3217 comm="ip" name="[12410]" dev=pipefs ino=12410 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
audit(1162674824.175:21): avc: denied { write } for pid=3217 comm="ip" name="[12410]" dev=pipefs ino=12410 scontext=system_u:system_r:ifconfig_t:s0 tcontext=system_u:system_r:unconfined_t:s0 tclass=fifo_file
[zenarcher@localhost ~]$
I don't mind doing a fresh install on this notebook, if need be. It took me 6 fresh installs on one box, moving from FC5 to FC6....only to get it right and have the LAN port die on the motherboard...so it's back for warranty replacement. If I can get this wireless worked out, using ndiswrapper or whatever, it would be great....as I have four FC6 systems to maintain here in the house.
Cheers,
zenarcher
partha
2006-11-04, 04:00 PM CST
Okay, I have the information you requested.
...
ADDRCONF(NETDEV_UP): eth1: link is not ready
SoftMAC: Scanning finished
SoftMAC: Queueing Authentication Request to 00:16:b6:cd:fb:05
SoftMAC: Cannot associate without being authenticated, requested authentication
SoftMAC: Already requested authentication, waiting...
SoftMAC: Sent Authentication Request to 00:16:b6:cd:fb:05.
SoftMAC: Open Authentication completed with 00:16:b6:cd:fb:05
SoftMAC: sent association request!
SoftMAC: associated!
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts
Bluetooth: Core ver 2.10
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
--
eth1: no IPv6 routers present
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Canceling existing associate request!
SoftMAC: Associate: Scanning for networks first.
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
bcm43xx: set security called, .level = 0, .enabled = 0, .encrypt = 0
--
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
SoftMAC: Scanning 14 channels
SoftMAC: Scanning finished
SoftMAC: Start scanning with channel: 1
--
....
Cheers,
zenarcher
Here is your culprit. This is the problem I recall with bcm43xx. The driver would not be ready and SoftMAC would do it's stuff and then you have this problem and you have to do this all over again. So, you are stuck with waiting till you finish the boot process and then try to associate again.
Alternatively, take a look at www.partha.com where I tell you how to do the ndiswrapper dance.
HTH,
Partha
www.partha.com
(Feel free to send me email if it does not work).
partha
2006-11-04, 04:02 PM CST
[HTML]eth0 ...
I don't see any card other than eth0 which means your wireless card is not recognized. Just to verify, what is the output of
lspci
and is bcm43xx loaded when you check
lsmod
?
Partha
www.partha.com
zenarcher
2006-11-04, 04:06 PM CST
I sincerely appreciate all your help and wisdom. I have gone to your website and it's wonderful, by the way! I think I will do a fresh install, then go the ndiswrapper route. You will most likely be getting an email from me before I'm done!
Just out of curiosity, will ndiswrapper work with most any wireless card, designed for Windows? I'm wondering, in respect to my desktop systems. If I were to pick up wireless PCI cards, with Windows drivers, would ndiswrapper most likely work for setting up wireless on the desktop systems with FC6?
Again, I sincerely appreciate the time and effort!
Cheers,
zanearcher
partha
2006-11-04, 04:13 PM CST
I sincerely appreciate all your help and wisdom. I have gone to your website and it's wonderful, by the way! I think I will do a fresh install, then go the ndiswrapper route. You will most likely be getting an email from me before I'm done!
Just out of curiosity, will ndiswrapper work with most any wireless card, designed for Windows? I'm wondering, in respect to my desktop systems. If I were to pick up wireless PCI cards, with Windows drivers, would ndiswrapper most likely work for setting up wireless on the desktop systems with FC6?
Again, I sincerely appreciate the time and effort!
Cheers,
zanearcher
You are welcome and thank you.
As for ndiswrapper, I don't see why not re your desktop.
As for all the cards that ndiswrapper works with, here is the list:
http://ndiswrapper.sourceforge.net/mediawiki/index.php/List
HTH,
Partha
www.partha.com
Batman2372
2006-11-04, 04:18 PM CST
For lspci , I get this:
01:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
for lsmod, I get this:
bcm43xx 469697 0
ieee80211softmac 69569 1 bcm43xx
ieee80211 67081 2 bcm43xx,ieee80211softmac
ieee80211_crypt 40129 1 ieee80211
partha
2006-11-04, 04:26 PM CST
For lspci , I get this:
01:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)
for lsmod, I get this:
bcm43xx 469697 0
ieee80211softmac 69569 1 bcm43xx
ieee80211 67081 2 bcm43xx,ieee80211softmac
ieee80211_crypt 40129 1 ieee80211
OK, so your card is recognized by FC6. Are you sure it is supported by bcm43xx.? What are the error messages regarding your wireless card in dmesg? Also, when you check System -> Network, do you see your card in the resulting dialogbox?
HTH,
Partha
www.partha.com
Batman2372
2006-11-04, 09:20 PM CST
No, I'm not sure that it's supported, which may be the problem *sigh*
I don't see any error messages in dmesg, much less one for the card, and no, the card doesn't show up when I use system-config-network.
Maybe bcm43xx isn't an option for me.
I do appreciate all of your help. I apologize for wasting your time.
zenarcher
2006-11-05, 04:01 AM CST
Well, again, I appreciate the help. Having looked closely at your website, I have basically the identical hardware in my notebook that you are using. Even the same controller and version number. Likewise, the very same ATI video, which has boggled me as to trying to install the proper driver. I will certainly be emailing you with a couple of questions, I'm sure, as I get this all going. I'm going to do a fresh install this morning, then begin with the ndiswrapper deal. Then, I can go from there.
Cheers,
zenarcher
partha
2006-11-05, 06:12 AM CST
No, I'm not sure that it's supported, which may be the problem *sigh*
I don't see any error messages in dmesg, much less one for the card, and no, the card doesn't show up when I use system-config-network.
Maybe bcm43xx isn't an option for me.
I do appreciate all of your help. I apologize for wasting your time.
Hey not a problem - glad to help. :)
My suggestion to you is the same that I gave Zenarcher. Try ndiswrapper. Take a look at my website to see how I installed it.
Let me know if you have any questions.
HTH,
Partha
www.partha.com
scheidecker
2006-11-15, 11:13 AM CST
Hello all,
I've always had troubles setting up wireless with this notebook due to the fact that it is 64 bits. I've tried loading both the 32 and 64 bits of the windows driver through ndiswrapper without any success. After installing FC6 I've got my wireless card recognized.
eth0 Link encap:Ethernet HWaddr 00:0F:B0:B8:C7:A9
inet addr:10.150.150.132 Bcast:10.150.150.255 Mask:255.255.255.0
inet6 addr: fe80::20f:b0ff:feb8:c7a9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5397 errors:0 dropped:0 overruns:0 frame:0
TX packets:3470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3827689 (3.6 MiB) TX bytes:643862 (628.7 KiB)
Interrupt:50 Base address:0xa400
eth1 Link encap:Ethernet HWaddr 00:14:A5:2B:F6:BE
BROADCAST 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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0x4000
Now, how can I set it up from here?
Thanks,
Scheidecker
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.