Hello, first I'll provide the requested information (from the sticky)
64-bit openSuSE 11.4
uname -a output
Linux linux-mx43 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux
dmesg | grep firmware
127.965048] b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27)
lspci output:
03:08.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02)
03:08.0 0280: 14e4:4301 (rev 02)
iwconfig output:
wlan0 IEEE 802.11b ESSID:off/any
Mode:Managed Access Point: NoHello, first I'll provide the requested information (from the sticky)
64-bit openSuSE 11.4
uname -a output
Linux linux-mx43 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux
dmesg | grep firmware
127.965048] b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27)
lspci output:
03:08.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02)
03:08.0 0280: 14e4:4301 (rev 02)
iwconfig output:
wlan0 IEEE 802.11b ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
iwlist -scan output:
wlan0 Interface doesn't support scanning : Network is down
I've configured the device for my network's settings in YaST's Network Settings tool.
Is the card turned off by the kill switch? Where do I find the kill switch?t-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
iwlist -scan output:
wlan0 Interface doesn't support scanning : Network is down
I've configured the device for my network's settings in YaST's Network Settings tool.
Is the card turned off by the kill switch? Where do I find the kill switch?
Typically these steps are required
sudo /usr/sbin/install_bcm43xx_firmware
sudo /sbin/modprobe -rv b43
sudo /sbin/modprobe -v b43
nick@linux-mx43:~> sudo /sbin/modprobe -rv b43
root’s password:
nick@linux-mx43:~> sudo /sbin/modprobe -v b43
insmod /lib/modules/2.6.37.6-0.7-desktop/kernel/drivers/net/wireless/b43/b43.ko
I’m not sure if these indicate success of the commands
iwlist still indicates: wlan0 Interface doesn’t support scanning : Network is down
Thanks thus far.
On 08/17/2011 03:36 PM, ug2215 wrote:
>
> nick@linux-mx43:~> sudo /sbin/modprobe -rv b43
> root’s password:
> nick@linux-mx43:~> sudo /sbin/modprobe -v b43
> insmod
> /lib/modules/2.6.37.6-0.7-desktop/kernel/drivers/net/wireless/b43/b43.ko
>
>
> I’m not sure if these indicate success of the commands
> iwlist still indicates: wlan0 Interface doesn’t support scanning :
> Network is down
The device uses b43legacy, not b43.
The network is down usually is an rfkill problem. I think a search on the forums
would have produced many reports on what you need to do, but apparently not.
Install rfkill with
sudo zypper install rfkill
Then run rfkill to get the state
/usr/sbin/rfkill list
If you see a “hard” block, then the problem is the hardware switch. No BCM4303
that I have seen has one, so I don’t think that is the problem. You most likely
have a “soft” block, which can be cleared with
sudo /usr/sbin/rfkill unblock all
At this point, you should be able to scan.
hmmmm
nick@linux-mx43:~/StarFarer/starfarer> /usr/sbin/rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
does this mean I’m screwed?
Is it possible that there’s a jumper on the card that puts in the wrong mode
Thanks for your help diagnosing this
On 08/17/2011 06:46 PM, ug2215 wrote:
>
> hmmmm
>
> Code:
> --------------------
> nick@linux-mx43:~/StarFarer/starfarer> /usr/sbin/rfkill list
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
>
> --------------------
>
>
> does this mean I’m screwed?
Until we solve this, yes. As there is only one item in the rfkill list, that
excludes other wireless or bluetooth cards.
Check the card for a jumper.
worked flawlessly on my opensuse 11.4 x64 with broadcomm 4311 card. thanks a lot!!
Thanks for the assistance, still haven’t gotten the card working but I’ve switched to Fedora because of various problems I was having