You are not logged in.
Pages: 1
hey guys have been trying to get my wireless working all weekend and seem to need a little more help with this.
this is my card
Network controler: Broadcom Corportation BCM4321 802.11b/g/n (rev 01)
after an iwconfig
eth0 IEEE 802.11 Nicname:""
After i # iwconfig eth0 essid skynet
nothing comes about
changed my modules so they look like
Modules=( lib80211 wl !b43 !ssb )
And this is all useing broadcom-wl drivers
and i still cant connect to my router which i have open purposefully.
Offline
Hi achingtwin21,
are you sure your wireless interface is on eth0? I'm used to seeing it on wlan0. What else have you tried before loading and blacklisting modules? And how is your WLAN configured (WEP, WPA, WPA2, no security, dhcp / static ??). Have you tried loading the interface through "ifconfig wlan0 up" before playing with modules? Have you tried scanning your essid (iwlist eth0 scan essid "your ESSID")??
Offline
well idk for some reason in the wiki i saw it could pose as eth0 or eth1. i didnt blacklist any modules. my wlan is no security so i can connect. i tryed useing ifconfig wlan0 up right before i changed my modules, and for some reason it says my my interface doesnt support scanning
Offline
I guess you have wired interface on top of that, right? If the wired interface is mapped to eth0, then the wireless will map itself either on eth1 or wlan0 (so commands on eth0 are useless). What was the output of ifconfig wlan0 up before changing the modules?? Could you also print the output of "lspci -vnn | grep 14e4". After that, you'll have to try loading modules individually with modprobe (instead of changing the rc.conf and always rebooting). This way you'll be able to see which module to load.
Offline
wlan0 Link encap:Ethernet HWaddr 30:46:9A:98:2E:32
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)
also when running ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory
07:00.0 Network controller [0280]: Broadcom Corporation BCM4321 802.11b/g/n [14e4:4329] (rev 01)
and ill try loading the modules individually noq
Last edited by achingtwin21 (2011-05-15 18:17:47)
Offline
also when running ifconfig wlan0 up
SIOCSIFFLAGS: No such file or directory
I think this means you have to load manually the firmware for your wireless card (http://wiki.debian.org/bcm43xx).
The following website should help : http://linuxwireless.org/en/users/Drivers/b43 (see section on device firmware installation / other distros).
This of course is assuming udev loads the b43 module ("lsmod | grep b43" to be sure). In this case you should probably focus on working with the b43 module.
Offline
ok is succesfully got rid of the siocsiffflags now but when i iwconfig wlan0 essid Skynet then try dhcpcd wlan0 i get dhcpcd[20964]: version 5.2.12 starting
dhcpcd[20964]: wlan0: waiting for carrier
dhcpcd[20964]: timed out
Offline
Before starting dhcpcd, you have to associate your wireless card to an access point. If you don't have any encryption enabled, you must use iwconfig :
# iwconfig wlan0 essid "MyEssid"
After that, start dhcpcd. If you have WPA/WPA2 encryption enabled, you'll have to use wpa_supplicant for the association. For WEP, you only add "key YOUR_KEY" to the end of the iwconfig command. And finally, if you have a hidden network (like mine), you'll have to scan for the network with iwlist before calling wpa_supplicant/iwconfig :
iwlist wlan0 scan essid "MyEssid"
This should get it working. Personnally, I hate doing all of this manually so I've installed networkmanager wich does all of this automatically and saved all the commands I must use in a small bash script if I ever need to connect manually to my network for debugging purposes.
Offline
are you sure your wireless interface is on eth0?
Wl uses eth naming. However usually the wired card is eth0, making the wireless eth1. This page: http://linuxwireless.org/en/users/Drivers/b43 does list wl as a choice for the card. Either that, or brcm80211 with the 2.6.39 kernel. The b43 is definitely the wrong driver to use.
So, achingtwin21, if you're on 2.6.39 already, you can try the brcm80211 driver. In this case, you need the linux-firmware package, it contains firmware for use with that driver. Otherwise try the wl driver again and blacklist brcm80211. I think that one has firmware already as part of the driver, so you don't need any extra firmware packages. Then check whether eth0 or eth1 is the wireless card and go from there.
Offline
Are you using Network Manager and Gnome 3. I had the same problem and had to add groupadd network manager and add myself to the group. I did not have a problem before Gnome 3 but this worked for me.
Offline
Pages: 1