Cannot get Broadcom Corporation BCM4312 802.11b/g to connect w/ Ubuntu 9.10.
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was talk to forum about WICD and they suggest, to check if there is more then one wireless network with AUTOCONNECT option.
And another suggestion is to " it may help to switch wicd to use dBm mode". Try to find that option in settings, as well as turn off autoconnect and reconnect.
Nexus was the only wireless network with AUTOCONNECT. I have since disabled this along with reconnect.
WICD - Wireless Interface setting
Use dbM to measure signal strength is enabled.
Just a quick note to say that I am stall following this thread but don't have a positive solution - I can't see why your connection keeps dropping - but it appears that WICD is still trying to open eth0 as a wired connection right after wpa_supplicant negotiates an encrypted connection on 192.168.1.3.
I would be interested in seeing the content of your wpa_supplicant.conf IIRC it should be in your /etc/wpa_supplicant directory. If you don't find it there you could try running the command (as root):
# locate wpa | grep .conf
the line therein that I am interested in is 'scan_ssid=' which starts scanning for other access point rather arbitrarily (in my opinion), I think there is a way to stop it but I can't remember if it is setting it to zero rather than 1.
The other suggestion I would make is to turn-off/disable eth0 (your wired connection) in WICD - if that is possible [I don't and haven't ever used WICD, so don't have a clue if it is an option that you can select].
Hope this helps - if not then I might suggest that you download something called wifi-radar which requires manual set-up but doesn't use a network manager and doesn't require dchp to be running even if it is running on your router.
Cheers
Good to have you back!
From my wpa_supplicant.conf. For security purposes I masked my psk.
Ok, then find your "Nexus" in the list of available AP and click "connect", because it looks like wicd do not connecting to it by it self (which is good actually)
Re Wifi-radar - You should have a wifi-radar and a wifi-radar.conf man pages loaded, have a quick look at them.
I have it on my desktop and just click on it, then I have to enter my root pswd, it should perform a scan (if it doesn't click on the Preferences button; unselect 'Auto-detect Wireless Device' and select 'eth2' in the pulldown box (I scan_timeout set to 22 for my 14 ap's) and Click on Close button.
When it comes up, you should then select/highlight the Nexus ap, click on the configure button, and put in the following settings:
click on wifi > and select Managed and channel 11
click on No wpa > and enter wext
if you can still see the Key box enter your key (otherwise click on wifi > again)
then enter your wpa-type it should give you options: WPA-PSK (select it)
Click on Automatic network configuration DHCP >
it should change to: manual network configuration
then enter:
IP : 192.168.1.3
Netmask : 255.255.255.0
Gateway : 192.168.1.1
Domain : (I leave this blank)
DNS : 192.168.1.1
DNS : 192.168.1.1
I have nothing in my connection commands
Click on Save
Click on Disconnect, wait for it ...., scroll through the ap's and select/ highlight Nexus now click on connect wait for it ....,
If all goes well you should be connected.
However, you may need to disable dhcp and Wicd so that they don't interfere.
Re Wifi-radar - You should have a wifi-radar and a wifi-radar.conf man pages loaded, have a quick look at them.
I have it on my desktop and just click on it, then I have to enter my root pswd, it should perform a scan (if it doesn't click on the Preferences button; unselect 'Auto-detect Wireless Device' and select 'eth2' in the pulldown box (I scan_timeout set to 22 for my 14 ap's) and Click on Close button.
When it comes up, you should then select/highlight the Nexus ap, click on the configure button, and put in the following settings:
click on wifi > and select Managed and channel 11
click on No wpa > and enter wext
if you can still see the Key box enter your key (otherwise click on wifi > again)
then enter your wpa-type it should give you options: WPA-PSK (select it)
Click on Automatic network configuration DHCP >
it should change to: manual network configuration
then enter:
IP : 192.168.1.3
Netmask : 255.255.255.0
Gateway : 192.168.1.1
Domain : (I leave this blank)
DNS : 192.168.1.1
DNS : 192.168.1.1
I have nothing in my connection commands
Click on Save
Click on Disconnect, wait for it ...., scroll through the ap's and select/ highlight Nexus now click on connect wait for it ....,
If all goes well you should be connected.
However, you may need to disable dhcp and Wicd so that they don't interfere.
Hope this helps
I get an "Could not get IP Address" error message. How do I disable dhcp?
Is this a test? I am not sure that my little grey cells can recall, what my kubuntu karmic beta distro looked like exactly. I don't recall if karmic automatically defaults to runlevel 2 (you can check by running as root # runlevel (if it returns N 2 - this means its initial runlevel was none and it booted into runlevel 2).
Anyhow once you know what it is/was you can edit your /etc/rcX.d directory (full of shell scripts) where X equals your runlevel - then just delete the s24dhcpbd entry -anyway that is what mine was [its gone now and I had to look in /etc/rc3d to see what it was - incidentally if you want it back just copy the entry from a different runlevel]. I also got rid of avahi-daemon which played silly b___ers with searching for DNS servers.
If you haven't got one yet I now have S51wifi-radar linked to /etc/init.d/wifi-radar.
You may have to reboot, as I am not sure that logging out and back in reruns then runlevel scripts
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
