Hi Max, sorry for the delay in replying but I have been re-reading this thread, which is somewhat disconcerting when all your pastebin postings have now expired!

I am not sure what you have been up to since your posting on Jan 23 but it appears that you have been playing with your wireless drivers!!!

From your latest lsmod output: you now have:
b44
b43
ssb
ndiswrapper
mac80211 loaded with: b43
cfg80211 loaded with: b43,mac80211
led_class loaded with: b43,sdhci (sdhci relates to bluetooth part of the b43 driver)

whereas on your initial post, dated December 15, your lsmod showed:

wl
lib80211_crypt_tkip
lib80211 loaded with: wl,lib80211_crypt_tkip

It appears from my reading of Hangdog42's post #119 that the wl/STA drivers that you originally had are the latest and best.

Hence I am confused as to why you are now trying the b43/b44/ssb drivers and have them installed together with the ndiswrapper driver - your wireless card can only handle 1 driver at a time.

One question I would ask - are you running any sort of firewall either on your laptop or on your "Nexus" router, which might have been blocking all the ping requests to 192.168.1.1 the were unsuccessful????

I would also note that I don't run a network manager nor WICD (which is a network manager) but only wifi-radar for when I connect with my wifi ISP. Incidentally although my Tablet PC running XP gets a dhcp assigned IP address, when I use my Debian64bit machine I have assigned a fixed IP address and my ISP's server respects my request for allocation of that fixed IP. So you needn't worry about your WICD reporting its inability to get an IP address if wifi-radar can see all the ap's in your area.

You may want to take a look at this: http://www.ubuntumini.com/2009/11/br...in-karmic.html which might help

Further reading: http://www.linuxquestions.org/questi...light=broadcom

Thanks for the input. No, I'm not running any firewalls.

First things first, I should remove all unnecessary drivers, right? If so, please tell me which ones and how to do so, thanks!

Who says it doesn't pay to be persistent?

I went to Dell, downloaded and installed an Ubuntu version compatible with Dell systems (http://linux.dell.com/files/ubuntu/hardy/iso-images/) and VOILA!!! I have wireless access to the net!!!

But, there's a catch (isn't there one always? LOL). I can access the net from other APs but not from Nexus. The weird thing is that my ethernet access is not direct to the modem but through my router, Nexus, and it works perfectly. However, despite the fact that I am able to connect to Nexus wirelessly, I am not able to send or receive data. I tried pinging an address and 0 packets were sent or received. Why am I able to access the net through my ethernet cable (connected to Nexus) but not via WiFi?

I just noticed that, while I have a WPA Supplicant folder, I don't have a wpa_supplicant.conf file. Could this be the source of the problem? If so, how do I proceed?

You only need wpa_supplicant if WEP or WPA.

What kernel are you using now? Type: uname -r

Can you look at the output of lsmod and check which driver you are using.

If you have wired but not wireless connection to Nexus, I would suggest that you check you router settings very very carefully.

Kernel: 2.6.24-27-generic

Here's my lsmod output: http://pastebin.com/m11acbc61

Here are my router's encryption protocols -
WPA: WPA-PKS (no server)
WPA Mode: WPA2
Encryption technique: TKIP

What's next?

Okay, let me first presume that in your new install you have a network manager or nm-applet running - I say this because you don't need WICD at this stage, and you appear to have a working 'wl' driver. I would suggest that you firswt try connecting with your 'Nexus' router in unencrypted mode - just to ensure that you can connect and stay connected - note: you will have to change your settings by wired connection.

Once we have that working then we can progess to setting up the encrypted connection.

Incidentally, my various wanderings in google land and specifically the ubuntu forums, lead me to believe that your problems with the karmic 9.10 kernel relate to buggy drivers and kernel. It appears that upgrading the kernel from the karmic 2.6.31 does now finally allow permanent and consistent connections in an encrypted environment. So don't think it is/was your fault.

Presumably, if you have understood any/all of the various commands such as ifconfig, iwconfig and iwlist you should be able to quickly tell whether your wireless is connected properly. Once that is done you can try setting WPA2 with TKIP using whatever network manager which should set up the (your) wpa-supplicant.conf rather than having to do it yourself.

My cable company needs to come and do some work with my internet service. I'll be back in a few days to post my results as soon as they're done, thanks!

I disabled my router's encryption protocols and am able to connect wirelessly. I was able to do the same when using Karmic Koala so the problem is definitely not my wireless card, router or modem. What's next?

assuming you have the driver broadcom sta that makes wl.ko module
Bcmwl in ubuntu.
blacklist ssb.
blacklist b43.

kernel,headers,depends updated.

if you really stuck try the linux mint 8 cd its on there.

How do I blacklist?

What does this mean "kernel,headers,depends updated."?

You should have a file /etc/modprobe.d/blacklist owned by root.root sudo into it with your favourite editor and add two lines at the end:

blacklist b43
blacklist ssb

Wrt updated kernel and headers I believe that these are only necessary if you are installing a tarball from source. However I can't rememeber what kernel you are using (uname -r) will tell you, and perhaps slackwaredanny is suggesting you might need to upgrade your kernel to the latest in the repositories - but not sure.

im sorry for not being clear sinse it such a long tread and i skimmed it and it seemed that you had it workin at some point.And since im swedish my english sometimes suffers from that.
the bcmwl package needs kernel headers updated.
maybe a clean install could benefit you and as said ive got my broadcom 43 12 going out of the box on mint,and now im running it in slackware.
b43,ssb and ndiswrapper dont work for me.
maybe ubuntu 10.4 daily has it i dont know.but its a debian pkg build of the broadcom sta you need for the 4312 on ubuntu/debian dists.
hope you get it working.