Wireless can see essid but makes no effort to connect

English Network/Internet
1

Hi there and thanks in advance. I just upgraded and then re-downgraded kde and wireless has stopped connecting (it still seems to be working, just not the way it should).
Here’s some info:

/sbin/lspci -v

06:05.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)                                                                 
        Subsystem: Intel Corporation Device 2702                                     
        Flags: bus master, medium devsel, latency 32, IRQ 20                         
        Memory at b8006000 (32-bit, non-prefetchable) [size=4]                      
        Capabilities: <access denied>                                                
        Kernel driver in use: ipw2200                                                
        Kernel modules: ipw2200           



/sbin/lspci -n

06:05.0 0280: 8086:4220 (rev 05)



dmesg | less

ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
Yenta: ISA IRQ mask 0x0cf8, PCI irq 22
Socket status: 30000006
Yenta: Raising subordinate bus# of parent bus (#06) from #07 to #0a
pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
cs: IO port probe 0x3000-0x3fff: clean.
pcmcia: parent PCI bridge Memory window: 0xb8000000 - 0xb80fffff
pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x8dffffff
vendor=8086 device=2448
ipw2200 0000:06:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
firmware: requesting ipw2200-bss.fw
ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)
eth0 renamed to eth0_rename by udevd [1238]



/usr/sbin/iwconfig

lo        no wireless extensions.

eth1      no wireless extensions.

eth0      unassociated  ESSID:off/any
          Mode:Managed  Channel=0  Access Point: Not-Associated
          Bit Rate:0 kb/s   Tx-Power=20 dBm   Sensitivity=8/0
          Retry limit:7   RTS thr:off   Fragment thr: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



sudo /usr/sbin/iwlist scan

root's password:
lo        Interface doesn't support scanning.

eth1      Interface doesn't support scanning.

eth0      Scan completed :
          Cell 01 - Address: 00:1B:2F:E4:25:54
                    ESSID:"swbc52"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.462 GHz (Channel 11)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=97/100  Signal level=-28 dBm
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    Extra: Last beacon: 24ms ago

Hardware profile tells me the kernel driver is ipw2200.
So it obviously knows the wireless signal is there, and can read it. Just when I try to connect it just does nothing, no whirly cogs in the system tray icon.
I’ve read the stickies but I can’t really see what the problem is to go further.
Any help appreciated.[/size]

2

oo, forgot:
OS: Linux 2.6.27.42-0.1-default i686
System: openSUSE 11.1 (i586)
KDE: 4.1.3 (KDE 4.1.3) “release 4.11.1”

3

Hi there,

I noticed you last line in dmesge is:

eth0 renamed to eth0_rename by udevd

Yet your interface shows up as eth0 in ifconfig. That is interesting.

You might want to check out:

cat /etc/udev/rules.d/70-persistent-net.rules

What happens when you manually try to associate to the AP with iwconfig in the command line? Any specific errors returned?

Cheers,
LewsTherin

4 
cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single line.
# PCI device 0x8086:0x4220 (ipw2200)
# PCI device 0x10ec:0x8169 (r8169)
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single line.
# PCI device 0x8086:0x4220 (ipw2200)
# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:ce:4c:56:6d", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0a:e4:b0:81:cf", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# USB device 0x03f0:0x1c1d (rndis_host)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="80:00:60:0f:e8:00", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

I don’t know to manually associate the Ap…

5

OK, found out howto do that.
I tried changing the essid in iwconfig. It seemed to change it to the right name, but the other settings obviously didn’t change. It wouldn’t connect either. Maybe then connected or not after trying ‘any’ and then back to ‘swbc52’ my computer crashed.
On reload I’v gone into GNOME and wireless is working fine here, but it did say KNetwork manager wanted the default keyring which was locked?? I don’t know any keyring so I deny-ed it and it connected anyway.
Just going back into kde to see if it works there now.

6

KDE still doesn’t connect wireless.

7

I’ve switched to ifup and it seems to be working fine. I do like knetwork manager but this’ll do.

8

Hey there,

Glad you got it working. I’ve had similar weird issues with Knetwork manager in the past too. Previously, when I was on 11.1 I realized I actually had some pretty old packages from the 10.x days. You might want to see if you have any updates available, but I assume that is not the case.

Also, you might want to just upgrade to 11.2 I found this fix all manner of nebulous issues I had. The on line dist upgrade to 11.2 worked flawlessly for me.

Cheers,
LewsTherin

9

Yeah, the online update worked well on another machine for me. I’m not that fussed about upgrading for some reason. I probably should be, but there you go. AFAIK I’m uptodate with what I’ve got, will check though, thanks.