BCM4312 b/g rev 01 can't see ssid

muczy · 12-12-2008, 02:28 AM

Update:
Really strange... If I set "wext", not ndiswrapper in wicd (so in wpa-supplicant), while I'm using ndiswrapper driver, it can authenticate with the router, however it can't get an ip, from dhcp . Using Broadcom's wl driver (and wext), it connects, authenticates, and gets az ip from dhcp, with no delay.
When using ndiswrapper driver, with ndiswrapper setting in wicd/wpa-supplicant, it cannot get through the authentication...

Hangdog42 · 12-12-2008, 07:30 AM

Quote:

If I set "wext", not ndiswrapper in wicd (so in wpa-supplicant), while I'm using ndiswrapper driver, it can authenticate with the router, however it can't get an ip, from dhcp . Using Broadcom's wl driver (and wext), it connects, authenticates, and gets az ip from dhcp, with no delay.

I suspect that the wpa_supplicant devs haven't been developing the ndiswrapper driver since wext should do whatever the ndiswrapper driver does. However, that doesn't explain why it doesn't get an IP address when using ndiswrapper and wext.

I can honestly say, you're having the strangest wireless problems I've seen in a long time. I wish I had some answers as to why!

muczy · 12-12-2008, 10:47 AM

Well...
I tried again, and sometimes (perhaps once / 5 try), it gets an ip via dhcp. So sometimes ndiswrapper works...

muczy · 02-04-2009, 08:19 AM

Since kernel 2.6.28, there is a new regulatory domain setting solution, crda. If I set iw set reg EU or HU, the card only sees 11 channel, however it should see 13. I have also set "cfg80211 ieee80211_regdom=EU" in /etc/modprobe.d/options, but still no luck. Is there any other way, setting the regdom value?

Hangdog42 · 02-04-2009, 11:59 AM

I suggest you start another thread on that, I have absolutely no experience in setting regdom values, so all I could do would be to Google, which you've probably done already.

muczy · 02-04-2009, 04:36 PM

I've started a new topic because of the regdom problem:
http://www.linuxquestions.org/questi...module-702336/

muczy · 03-31-2009, 07:55 AM

JosipBroz: the ssid is not hidden, since under Vista I can see it, and also connect to it.
Update: the router seems to be an X-Micro XWL-11GRIX. I haven't found any linux-specific issues with it.

muczy · 04-26-2009, 02:13 AM

"Solved":
I have bought an Intel 4965 card, and it can see, and also connect to the AP.
The problem was, that the AP uses Channel 13 (b/g), but the broadcom wl driver simply can't change regulatory domains, so it can only operate in Channels 1-11 (b/g).
I really hate Broadcom...

With ndiswrapper, iwlist reported 14 channels, but it seems like hardware coded, or whatever. However in Vista, it can use channels 1-13...

Hangdog42 · 04-26-2009, 07:01 AM

Quote:

The problem was, that the AP uses Channel 13 (b/g), but the broadcom wl driver simply can't change regulatory domains, so it can only operate in Channels 1-11 (b/g).
I really hate Broadcom...

Wow. That is a new one. Yeah, nobody lives outside of the US, so why should their drivers support non-US standards. Thanks for posting this, you will definitely help others.