Wirless not working, Lenovo ideapad S10e, Open Suse 11.4 Broadcom 802.11g

English Network/Internet
1

Hi guys, hope you are able to help me with my Wireless connection. i have got a Lenovo ideapad S10e and have recently installed Open Suse 11.4

Wireless is turned on have pressed the switch to turn it on and off several times but will not scan or activate, firmware is installed. the network manager displays network interface as unavailable. and i am unable to select the tick box to enable the wireless.

the following is the results i have found following previous posts

dmesg | grep firmware “get no messages”

/sbin/lspci
05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

/sbin/lspci -n
05:00.0 0280: 14e4:4315 (rev 01)

dmesg | less
13.138601] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
13.169116] ALSA patch_realtek.c:1524: SKU: Nid=0x1d sku_cfg=0x4015812d
13.169129] ALSA patch_realtek.c:1526: SKU: port_connectivity=0x1
13.169138] ALSA patch_realtek.c:1527: SKU: enable_pcbeep=0x1
13.169147] ALSA patch_realtek.c:1528: SKU: check_sum=0x00000005
13.169155] ALSA patch_realtek.c:1529: SKU: customization=0x00000081
13.169164] ALSA patch_realtek.c:1530: SKU: external_amp=0x5
13.169172] ALSA patch_realtek.c:1531: SKU: platform_type=0x1
13.169180] ALSA patch_realtek.c:1532: SKU: swap=0x0
13.169188] ALSA patch_realtek.c:1533: SKU: override=0x1

dmesg | grep Broadcom
13.138601] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
13.562149] Broadcom 43xx driver loaded Features: PMLS, Firmware-ID: FW13 ]
81.018255] usb 3-2: Manufacturer: Broadcom Corp
4005.795214] usb 3-2: Manufacturer: Broadcom Corp
4950.738256] usb 3-2: Manufacturer: Broadcom Corp

/usr/sbin/iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off

sudo /usr/sbin/iwlist scan
root’spassword:
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning. wlan0 Interface doesn’t support scanning : Network is down

hope you can help, and many thanks in advance.
d

2

I have exactly the same issue on an Ideapad S10. Hope someone can help.

Riverday

3

On 04/27/2011 10:06 AM, RiverDay wrote:
>
> I have exactly the same issue on an Ideapad S10. Hope someone can
> help.

When the “network is down”, the first thing is to check the output of
‘/usr/sbin/rfkill list’. You may have to install the rfkill package first.

If rfkill does not show anything being blocked, then try the following:


sudo /sbin/killproc NetworkManager
sudo /sbin/killproc knetworkmanager
sudo /usr/sbin/NetworkManager
sudo /usr/bin/knetworkmanager > /dev/null 2>&1 &

The above sequence assumes that you are using KDE, NetworkManager, and the
NetworkManager-KDE applet.

The reason for the above sequence is that it seems that something is not being
initialized properly, and a reload can help.

4

thank you for the quick response.
For some unknown reason, it seems to be working partly. i guess the reboot must have corrected the issue, which i dont understand because i rebooted it several times yesterday.
At least it is able to connect to the AP and is also able to scan.
however i am still unable to connect to the internet, which most likely is a configuration issue.

i have tried to configure it using the kde net mnrg and also the yast2

/usr/sbin/iwconfig
IEEE 802.11bg ESSID: “BTHOMEHUB-267”
Mode: managed Frequency: 2.44GHz Access Point: 00:1d:68:50:61:6D
bit rate= 54mb/s tx-power=20 dbm
retry long limit:7 rts thr: off fragment thr: off
power managment: off
link quality= 70/70 signal level=-21dbm
rx invalid nwid:0 rx invalid crypt:0 rx invalid frag:0
tx excessive retries:1 invalid misc: 0 missed becon:0

any idea???

thank you
D

5

Thank you for your support, i have managed to get it up and running. the problem seems to be with the WEP key,was using the pass phrase, changed to Hex and seems to be working fine.

Thanks.

6

On 04/28/2011 08:06 AM, d3mi55 wrote:
>
> Thank you for your support, i have managed to get it up and running. the
> problem seems to be with the WEP key,was using the pass phrase, changed
> to Hex and seems to be working fine.

There are 6 ways to convert a WEP pass phrase to a key, and the one used by
Windows does not work with Linux. As has been said many times in this forum,
with WEP you should always use a key.