try using Yast - Network and deselect ]Manage by Networkmanager. Make sure ipv6 is disabled and configure your essid and key through Yast and with luck you will be up. I make this loose assumption since it appears to recognize your wifi but without the needed configs
kulket wrote:
> Hi,
>
> I installed OpenSuse 11.1 recently & been trying to setup wireless. I
> have gone through the primer “Getting Your Wireless to Work”.
>
> Based on that, here are the details:
>
> I have BCM4311 as the pci wireless device:
>
> 1. #lspci
> 0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g
> WLAN (rev 01)
>
> 2.# /sbin/lspci -n
> 03:00.0 0200: 14e4:170c (rev 02)
> 0b:00.0 0280: 14e4:4311 (rev 01)
>
> 3. # iwfconfig
> wlan0 IEEE 802.11bg ESSID:""
> Mode:Managed Frequency:2.412 GHz Access Point:
> Not-Associated
> Tx-Power=0 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> 4. I see I am missing ESSID & access point is missing. How do I set up
> those ? When I do ‘iwlist scan’ I get following message:
>
> wlan0 Interface doesn’t support scanning : Network is down
Have you installed the firmware? Please post the output of
kulket wrote:
> First ofall thanks to Larry & ‘techwiz03’ for trying to help me.
> Based on the primer/stickies I have been able to make a little
> progress.
>
> Yes I have installed the firmware. When I had installed it I remember
> recieving output after dmesg | grep b43.
> However, if I doit now, I get nothing.
>
> # dmesg | grep -i broadcom
> ndiswrapper: driver bcmwl5 (Broadcom,10/12/2006, 4.100.15.5) loaded
> eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:15:c5:b1:5c:d3
You get no output from ‘dmesg | grep b43’ because you don’t have b43
loaded - you are using ndiswrapper. The two are mutually incompatible.
You also have a problem with your BCM44xx. It needs the driver ssb,
which will grab the wireless device and may prevent proper loading of
ndiswrapper.
> Now I when I do iwlist scan I can see my network along with the other
> networks. However, I cannot connect to it.
>
> Cell 02 - Address: 00:1C:DF:BC:FC:75
> ESSID:“MySSID”
>
> Protocol:IEEE 802.11g
> Mode:Managed
>
> Frequency:2.437 GHz (Channel 6)
> Quality:100/100 Signal level:-30 dBm Noise level:-96 dBm
> Encryption key:on
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
> 12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
> 48 Mb/s; 54 Mb/s
> Extra:bcn_int=100
> Extra:atim=0
>
> IE: WPA Version 1
> Group Cipher : TKIP
> Pairwise Ciphers (2) : TKIP CCMP
> Authentication Suites (1) : PSK
>
>
> I have tried connecting to it using YAST-Network manager and also ifup.
> Both ways I see its trying to connect to my wirless network, but fails.
>
>
> Please let me know if I need to provide any output/info. I have
> dual-boot system, with Dell 1390 WLAN card.
Your first post said that you have a BCM4311. Why are you using
ndiswrapper? You do know that that approach runs a Windows driver in
the innermost level. Furthermore, the BCM4311 works very well with b43.
kulket wrote:
> Although I am not a newbie to Linux, I am a novice when it comes to
> networking/wireless. Thanks all for your help.
>
> Larry, from the link posted above, I found your reply to similar
> questions: I am gonna install b43 firmware again & activate it.
>
> /usr/sbin/install_bcm43xx_firmware
> /sbin/modprobe -rv b43
> /sbin/modprobe -v b43
>
> What should I do about BCM44xx which needs ssb currently ?
> Also, should I uninstall ndiswrapper ?
As Akeollh said, do not worry about BCM44xx. The driver ssb was
created so that a single copy could be shared between 44xx and 43xx
devices. It will work without any difficulty as long as you get rid of
ndiswrapper.