[SOLVED] help with BCM4312 [14e4:4315]

I7IZI · 2011-01-03 19:36:08

please excuse my n00bness!
I know this has been posted multiple times for I have read through many posts. and I have followed through the various steps in the wiki for b43 and bcm43xx and from broadcoms README. from what I can tell I have correctly installed the driver and have been able to bring the interface up, but I keep getting an error everytime I try to scan for networks, whether using sudo and as root. here is a copy of the terminal commands I have been using, if there is any other information I can provide please let me know as I may need a little guidance here.

[i7izi@I7IZI ~]$ sudo ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:25:64:69:53:3E  
          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:41 Base address:0xc000 

eth1      Link encap:Ethernet  HWaddr 90:4C:E5:83:4B:F5  
          inet addr:98.127.114.194  Bcast:255.255.255.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
          RX packets:3127 errors:0 dropped:0 overruns:0 frame:0
          TX packets:197 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:213119 (208.1 Kb)  TX bytes:19147 (18.6 Kb)

eth2      Link encap:Ethernet  HWaddr 70:1A:04:68:85:F4  
          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:17 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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:520 (520.0 b)  TX bytes:520 (520.0 b)

[i7izi@I7IZI ~]$ sudo ifconfig eth1 down
[i7izi@I7IZI ~]$ sudo ifconfig eth2 up
[i7izi@I7IZI ~]$ sudo iwconfig
lo        no wireless extensions.

eth2      IEEE 802.11bg  ESSID:""  Nickname:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Bit Rate:54 Mb/s   Tx-Power:off   
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Power Managementmode:All packets received
          Link Quality=5/5  Signal level=0 dBm  Noise level=0 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

eth1      no wireless extensions.

[i7izi@I7IZI ~]$ sudo iwlist eth2 scan
eth2      Failed to read scan data : Invalid argument

[i7izi@I7IZI ~]$ sudo /etc/rc.d/network restart
:: Stopping Network                                                                                                                                              [DONE] 
:: Starting Network                                                                                                                                             
[BUSY] up: error fetching interface information: Device not found
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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:520 (520.0 b)  TX bytes:520 (520.0 b)

up: error fetching interface information: Device not found
eth1      Link encap:Ethernet  HWaddr 90:4C:E5:83:4B:F5  
          inet addr:98.127.114.194  Bcast:255.255.255.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
          RX packets:3957 errors:0 dropped:0 overruns:0 frame:0
          TX packets:205 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:261491 (255.3 Kb)  TX bytes:19971 (19.5 Kb)

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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:520 (520.0 b)  TX bytes:520 (520.0 b)

                                                                                                                                                                 [DONE] 
[i7izi@I7IZI ~]$ sudo ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:25:64:69:53:3E  
          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:41 Base address:0xc000 

eth1      Link encap:Ethernet  HWaddr 90:4C:E5:83:4B:F5  
          inet addr:98.127.114.194  Bcast:255.255.255.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:576  Metric:1
          RX packets:5003 errors:0 dropped:0 overruns:0 frame:0
          TX packets:207 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:318118 (310.6 Kb)  TX bytes:20055 (19.5 Kb)

eth2      Link encap:Ethernet  HWaddr 70:1A:04:68:85:F4  
          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:17 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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:520 (520.0 b)  TX bytes:520 (520.0 b)

I would also like to note that I am a computer science major and have been using ubuntu for the past year now and thought that I had a pretty good handle on the linux system, ahem, after making this move to arch I have realized that my knowledge of the linux system is not as great as I thought it was, but I am loving the exposure to the finer details of what makes a linux system tick. all help is greatly appreciated and thank you for your time.

[EDIT]
here is a copy of my rc.conf settings as well.

MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(lib80211 lib80211_crypt_tkip wl !b43 !ssb)

eth1="dhcp"
INTERFACES=(eth0 eth1 eth2)

DAEMONS=(syslog-ng @network netfs crond alsa)

Last edited by I7IZI (2011-01-04 17:51:46)

.:B:. · 2011-01-03 22:44:42

Is there a reason why you are not using the b43 driver? If your card is an 802.11b/g model it should work just fine.

Kinch · 2011-01-04 00:07:10

Shouldn't there also be a wlan0 interface? I guess it doesn't really matter what you call it. If it's shutting down then I think it's a firmware problem or the way you have your modules listed. I believe the b43 module should work best. I would just go ahead and blacklist all the other ones. WL is also usable I believe so I would try switching between the two.

http://wireless.kernel.org/en/users/Dri … -b43legacy

The above page cites that either b43/wl should be usable.

marjonis · 2011-01-04 09:19:57

hi, all info https://wiki.archlinux.org/index.php/Broadcom_BCM43XX

I7IZI · 2011-01-04 17:45:06

First, thank you all for your replies, particularly .:B:..

Is there a reason why you are not using the b43 driver?

yes I was recieving

SIOCSIFFLAGS: Operation not possible due to RF-kill

with the b43 driver, naturally I did some quick searching on that error and came up with mostly unrelevant finds.

If your card is an 802.11b/g model it should work just fine.

and it did after digging a little deeper into that error and finding an insightful link where it was mentioned that if your card is blocked by a on/off switch then you need to switch it on in order for the card to work...
so after several installations of arch and many hours of troubleshooting and researching my wifi card works thank you all for you help.

.:B:. · 2011-01-04 19:00:24

Rfkill can be a b*tch . Glad to see you're up and running.

Kinch · 2011-01-05 01:58:16

May I ask how you switched it on? Was it the following line?

sudo ifconfig wlan0 up

I've been having the same issue with another BCM43xx card and although it's on I can't seem to have it scan or do anything of relevance. Anyways, cheers on getting it working.

.:B:. · 2011-01-05 04:35:14

# pacman -Ss rfkill
core/rfkill 0.4-1
    Tool to query and set the rfkill state of wireless devices

Arch Linux

#1 2011-01-03 19:36:08

[SOLVED] help with BCM4312 [14e4:4315]

#2 2011-01-03 22:44:42

Re: [SOLVED] help with BCM4312 [14e4:4315]

#3 2011-01-04 00:07:10

Re: [SOLVED] help with BCM4312 [14e4:4315]

#4 2011-01-04 09:19:57

Re: [SOLVED] help with BCM4312 [14e4:4315]

#5 2011-01-04 17:45:06

Re: [SOLVED] help with BCM4312 [14e4:4315]

#6 2011-01-04 19:00:24

Re: [SOLVED] help with BCM4312 [14e4:4315]

#7 2011-01-05 01:58:16

Re: [SOLVED] help with BCM4312 [14e4:4315]

#8 2011-01-05 04:35:14

Re: [SOLVED] help with BCM4312 [14e4:4315]

Board footer