BCM4328 - Can't set ESSID or iwlist scan doesn't find any

My wireless card (BCM4328 on the MacBook Pro) doesn’t set the ESSID when I used the command:

iwconfig eth1 essid spnet

It looks like this command doesn’t have any effect.

eth1      IEEE 802.11abgn  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Bit Rate:14 Mb/s   Tx-Power:32 dBm
          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=-87 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

I’m trying the latest “wl” driver.
It can be connected to “spnet” from the Mac OS.
I tried setting up using Yast but since it was not working, I used the iwconfig command.
Also, “iwlist eth1 scan” doesn’t return any result.

What could be the problem?

#uname -r
2.6.27.25-0.1-default
#modinfo wl
filename:       /lib/modules/2.6.27.25-0.1-default/updates/wl.ko
srcversion:     562B1ECA508CC3E2D48DBE6
alias:          pci:v000014E4d00004357sv*sd*bc*sc*i*
alias:          pci:v000014E4d00004353sv*sd*bc*sc*i*
alias:          pci:v000014E4d0000432Dsv*sd*bc*sc*i*
alias:          pci:v000014E4d0000432Csv*sd*bc*sc*i*
alias:          pci:v000014E4d0000432Bsv*sd*bc*sc*i*
alias:          pci:v000014E4d0000432Asv*sd*bc*sc*i*
alias:          pci:v000014E4d00004329sv*sd*bc*sc*i*
alias:          pci:v000014E4d00004328sv*sd*bc*sc*i*
alias:          pci:v000014E4d00004315sv*sd*bc*sc*i*
alias:          pci:v000014E4d00004313sv*sd*bc*sc*i*
alias:          pci:v000014E4d00004312sv*sd*bc*sc*i*
alias:          pci:v000014E4d00004311sv*sd*bc*sc*i*
depends:        ieee80211_crypt
vermagic:       2.6.27.25-0.1-default SMP mod_unload modversions
parm:           oneonly:int
parm:           piomode:int
parm:           nompc:int
parm:           name:string

Tried using network manager ? Also, IIRC, if using broadcoms wl driver, you may need to disable/blacklist ssb, did you do this ?

Andy

Sorry for the delayed response, I am still on vacation :slight_smile:

I have ssb blacklisted and tried networkmanager too. No difference :frowning:

i have basically the same issue - after s/w update today, the wireless card (cisco 350) doesn’t connect. i removed the conn in the ntwk mgr and put it back in. no help.

i’m using suse11.1, kde4.

iwconfig eth2 shows

eth2 IEEE 802.11-DS ESSID:“;pd$\x11\x9E\x09\xDC\xAA\xD4\xAC\xF2\x1B\x10\xAF;3\xCD\xE3PHG\x15\xBBo”\x19\xBA\x9B}\xF5"
Mode:Managed Frequency: 2.437 GHz Access Point: Invalid
Bit Rate: 11 Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thr: off Fragment thr: off
Power Management: off
Link Quality=92/100 Signal level=-50 dBm Noise level=-92 dBm
Rx invalid nwid:15554 Rx invalid crypt: 0 Rx invalid frag: 0
Tx excessive retries:0 Invalid misc:108231 Missed beacon: 0

note no mention of Encryption. further note “rx invalid nwid”
also note all other boxes working fine wirelessly.

so i set the essid using iwconfig eth2 essid myessid, iwconfig eth2 then showed the correct essid and a new line saying Encryption key: off

then i set the key using iwconfig eth2 key 1234567812346789…

iwconfig eth2 continues to show encryption off, even after iwconfig eth2 key on.

if i put in the key before changing the essid, it appears to turn on the encryption and shows the usual Encryption : -… line, but then the essid appears whacked.

iwlist scanning shows the wireless router with what appears to be the correct info.

am i correct in thinking the ntwk mgr database is in the gconf db? if so, it doesn’t show up with gconf-editor.

thoughts?

hmmm… can’t edit posts after 10 minutes. so, a new post it is.

in the ensuing time, i used yast to config eth2 (use traditional instead of ntwk mgr). all is well, if you don’t mind not using the ntwk mgr. for me, thats ok, but i’d still like to know how to get ntwk mgr to work properly.

tnx

In my case, I tried the traditional way first but that too didn’t work. (See the opening post).

Finally, after updating the system with latest broadcom-wl driver, it started working!