LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (http://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   bcm4318 wireless probs (still) (http://www.linuxquestions.org/questions/linux-wireless-networking-41/bcm4318-wireless-probs-still-593245/)

mountainman 10-20-2007 08:53 AM

bcm4318 wireless probs (still)
 
ok, Still trying to get wireless working on my laptop. Its a dell inspiron 2200 with the above mentioned wireless card. I used bw43xx cutter and I think I have that ready to go, I did an lsmod and didnt see the bw43xx driver running, so I did a modprobe bw43xx and it looks like it started. BUT, my wireless card doesnt even show up in Network config. I looked in /etc/sysconfig/hwconf and it wasnt listed. BUT if I do a kudzu -c wireless, it shows up. I manually added the appropriate section to the hwconf file, but it still doesnt show up in the netconfig tool. I tried to manually add a new wireless connection and the only broadcom option it gives me is a TG3 controller, which doesnt work at all. Any ideas as to what I need to do to get this up?

Brian1 10-20-2007 09:52 AM

Never used one but my guess is use the ifconfig and iwconfig commands to manually set it up. What does the command ' /sbin/ifconfig -a ' show.

Brian

mountainman 10-20-2007 05:36 PM

This is ifconfig -a. I manually did a iwconfig wlan0 and associated an ip address.

Code:

wlan0    Link encap:Ethernet  HWaddr 00:14:A5:3D:FC:78 
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          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)

wmaster0  Link encap:UNSPEC  HWaddr 00-14-A5-3D-FC-78-28-8B-00-00-00-00-00-00-00-00 
          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)

But, When I do a dhclient, I get ALL Kindsa Errors:
Code:

dhclient
Internet Systems Consortium DHCP Client V3.0.5-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
wmaster0: unknown hardware address type 801
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: wlan0: No such file or directory
SIOCSIFFLAGS: No such file or directory
SIOCSIFFLAGS: No such file or directory
/sbin/dhclient-script: configuration for wmaster0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: wmaster0: No such file or directory
SIOCSIFFLAGS: Operation not supported
SIOCSIFFLAGS: Operation not supported
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:14:a5:3d:fc:78
Sending on  LPF/wlan0/00:14:a5:3d:fc:78
Listening on LPF/wmaster0/
Sending on  LPF/wmaster0/
Listening on LPF/eth0/00:14:22:c3:16:b8
Sending on  LPF/eth0/00:14:22:c3:16:b8
Sending on  Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
DHCPREQUEST on eth0 to 255.255.255.255 port 67
receive_packet failed on wlan0: Network is down
receive_packet failed on wmaster0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
send_packet: Network is down
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down

My Dmesg has lots of erros in it as well, when it is trying to bring up the wlan0 (broadcom) interface.
Code:

b43-phy0 debug: Adding Interface type 2
b43-phy0 ERROR: Microcode "bcm43xx_microcode5.fw" not available or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#dev
icefirmware and download the correct firmware (version 4)
b43-phy0 debug: Adding Interface type 2
b43-phy0 ERROR: Microcode "bcm43xx_microcode5.fw" not available or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#dev
icefirmware and download the correct firmware (version 4)
b43-phy0 debug: Adding Interface type 2
b43-phy0 ERROR: Microcode "bcm43xx_microcode5.fw" not available or load failed.
b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#dev
icefirmware and download the correct firmware (version

The wierd thing is I am using the version 4 firmware. Here is a listing of the /lib/firmware directory where I pulled the firmware out with b43-fwcutter:
Code:

ipw2100-1.3.fw      ipw-2.4-boot.fw        ipw-2.4-sniffer_ucode.fw
ipw2100-1.3-i.fw    ipw-2.4-bss.fw        iwlwifi-3945-1.ucode
ipw2100-1.3-p.fw    ipw-2.4-bss_ucode.fw  iwlwifi-3945.ucode
ipw2200-bss.fw      ipw-2.4-ibss.fw        LICENSE.ipw2100
ipw2200-ibss.fw    ipw-2.4-ibss_ucode.fw  LICENSE.ipw2200
ipw2200-sniffer.fw  ipw-2.4-sniffer.fw    zd1211


What am I missing here?

Brian1 10-21-2007 09:14 AM

I never had much luck with the bcm43xx module but thats been a while back. I ususally install ndiswrapper and use the windows inf driver. Blacklist the bcm43xx module or recompile the kernel and leave it out.

Brian

yogi_texas 10-25-2007 04:08 PM

I just remove the bcm43xx driver and install bcmwl5 instead through ndiswrapper. Downside to using proprietary drivers is the inability to take advantage of specific features, but it gets you connected. No need to recompile the kernel this way

Hangdog42 10-27-2007 07:30 AM

The 4318 chipset doesn't work well with the bcm43xx driver, so the suggestions to blacklist it and use ndiswrapper are on target.

mountainman 05-17-2008 09:33 PM

I must say that I gave up after a while of not getting this working. After talking with a friend the other day, I say that Fedora core 9 was out. Does anyone know if this version has any better support for the broadcom 4318 wireless interface? I'm hoping this is better supported and I can do a dualboot again on the ol' laptop.

Hangdog42 05-18-2008 06:54 AM

The answer is, it might. The old bcm43xx driver has been retired and replaced by b43 (or b43-legacy for some chips) and it might be doing a better job. Ndiswrapper is still around and a reasonable choice if b43 doesn't work out. If you use ndiswrapper, you have two modules you need to blacklist, b43 and ssb. Blacklisting both seem to let ndiswrapper work.

kkjensen 05-20-2008 03:38 PM

I would like to give the bc43 another chance (after using ndiswrapper since F6) since I'd like to throw the support to people trying to debug the native driver rather than keep falling back on our beloved friend, Broadcom, and all the help they have offered over the years <*ahem*>. I tried fwcutter before that but it was quite buggy and would cut out a lot.

Where to start? I've removed ndiswrapper...un-blacklisted the bc43 driver...now what??? If I've got the whole windows driver pack that I used to use for ndiswrapper, is the needed file there for bc43-cutter? I've rebooted my machine and the wireless light is on but I see no sign of the card anywhere except in lspci where I see
Code:

06:05.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Anyone have a good, relevant link for F9? I've spent the best part of the afternoon but I'm going to need the step-by-step to be sure I'm getting it right.

A million thanks in advance!

Hangdog42 05-20-2008 05:02 PM

Quote:

If I've got the whole windows driver pack that I used to use for ndiswrapper, is the needed file there for bc43-cutter?
If you visit the b43 homepage, they have instructions on which version of fwcutter to use and a link to the proper Broadcom file to use. You might be able to use your Windows driver, but it is probably best to use the file they suggest. I think that the b43 is pickier about firmware than bcm43xx was, and that might be part of the problem. I do know that the firmware files for bcm43xx won't work with b43.

Quote:

Where to start? I've removed ndiswrapper...un-blacklisted the bc43 driver.
I think that there were a couple of modules (ssb?) that needed to be un-blacklisted as well if you blacklisted them in the first place. You probably should double-check your blacklist and be sure that nothing b43 needs is there.
Quote:

but I'm going to need the step-by-step to be sure I'm getting it right.
Check out the instructions on the b43 site. I think they're pretty good, but that just might be me.


All times are GMT -5. The time now is 08:01 PM.