Network-manager doesn't show any wireless network on ipw2200

Could you please attach your /etc/network/interfaces?

Also, please attach the output of `iwconfig` and `nm-tool`

Thanks.

this is the output of iwconfig and nm-tool:

dario@laptop:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11g ESSID:"linksys"
          Mode:Managed Frequency:2.462 GHz Access Point: 00:18:39:4B:DD:6F
          Bit Rate:36 Mb/s Tx-Power=20 dBm Sensitivity=8/0
          Retry limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=76/100 Signal level=-53 dBm Noise level=-89 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:3 Invalid misc:0 Missed beacon:9

dario@laptop:~$ nm-tool

NetworkManager Tool

State: disconnected

- Device: eth0 ----------------------------------------------------------------
  NM Path: /org/freedesktop/NetworkManager/Devices/eth0
  Type: Wired
  Driver: b44
  Active: no
  HW Address: 00:02:3F:16:19:6F

  Capabilities:
    Supported: yes
    Carrier Detect: yes
    Speed: 10 Mb/s

  Wired Settings
    Hardware Link: no

I have a similar problem, the only difference being that it sometimes work, sometimes does not.

/etc/network/interfaces
8<--------------------
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
8<--------------------

iwconfig
8<--------------------
lo no wireless extensions.

eth1 IEEE 802.11g ESSID:"tango"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:0D:88:EC:0A:1C
          Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
          Retry limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=90/100 Signal level=-39 dBm Noise level=-91 dBm
          Rx invalid nwid:0 Rx invalid crypt:2 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.
8<--------------------

nm-tool
8<--------------------
NetworkManager Tool

State: disconnected

- Device: eth0 ----------------------------------------------------------------
  NM Path: /org/freedesktop/NetworkManager/Devices/eth0
  Type: Wired
  Driver: tg3
  Active: no
  HW Address: 00:14:22:E0:C3:B3

  Capabilities:
    Supported: yes
    Carrier Detect: yes
    Speed: 65535 Mb/s

  Wired Settings
    Hardware Link: no

8<--------------------

This output was gathered while knetworkmanager shows no wireless network and my eth1 card had to be manually configured.

I have also experienced a few times knetworkmanager showing no network and saying "disconnected" in the system tray, but the card being automatically configured nonetheless (after resume from standby, where I resumed at a location that had different networks from the place I was when I suspended).

Same problem here for a few days, with Feisty up-to-date.

I attach the /etc/network/interfaces

And here there is the output of that commands:

emilio@kiko:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 radio off ESSID:""
          Mode:Managed Channel:0 Access Point: Not-Associated
          Bit Rate:0 kb/s Tx-Power=off 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

emilio@kiko:~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth1 ----------------------------------------------------------------
  NM Path: /org/freedesktop/NetworkManager/Devices/eth1
  Type: 802.11 Wireless
  Driver: ipw2200
  Active: no
  HW Address: 00:16:6F:A3:C2:37

  Capabilities:
    Supported: yes

  Wireless Settings
    Scanning: yes
    WEP Encryption: yes
    WPA Encryption: yes
    WPA2 Encryption: yes

  Wireless Networks (* = Current Network)

- Device: eth0 ----------------------------------------------------------------
  NM Path: /org/freedesktop/NetworkManager/Devices/eth0
  Type: Wired
  Driver: 8139too
  Active: yes
  HW Address: 00:16:36:5F:67:53

  Capabilities:
    Supported: yes
    Carrier Detect: yes
    Speed: 100 Mb/s

  Wired Settings
    Hardware Link: yes

  IP Settings:
    IP Address: 192.168.1.36
    Subnet Mask: 255.255.255.0
    Broadcast: 192.168.1.255
    Gateway: 192.168.1.1
    Primary DNS: 80.58.61.250
    Secondary DNS: 80.58.61.254

Also, this is my system:
emilio@kiko:~$ uname -a
Linux kiko 2.6.20-6-generic #2 SMP Wed Jan 31 20:53:39 UTC 2007 i686 GNU/Linux

Simon, please tell us what more info do you need.

Best regards
Emilio

This workaround works for me:
sudo rmmod ipw2200
sudo modprobe ipw2200

After reloading the module nm-tool immediately shows that NM is managing eth1, and after a while NM connects to the network.

On the other hand, restarting NetworkManager and/or knetworkmanager (without reloading the module) has no effect.

I've found that I had no problem, but I had my wireless deactivated :) So I have no bug here (which does not mean others can have it)

Here is an extract from my system log, that occured when I resumed the machine. The machine was resumed at 15:05. At first nm-tool did not list eth1 (my ipw2200). At 15:07 I did the module unload/reload trick, and NM grabbed the network. I did not find anything obviously wrong in the log file, but maybe somebody in the know can sort it out.

uname -a
Linux tadzim 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

My wired card is a Tigon3.

Is there any additional information I can provide?

The problem still appears with latest updates, is this bug on somebody's radar? I'd love to help testing!

For what it is worth, I see what appears to be the same problem with an ipw2200 on edgy- mostly it works, but sometimes after I move from one building to another, either I'm unable to connect to the networks in the new building, or worse, the card has disappeared.

Since the last few days I have not experienced the problematic behavior so it seems an update did some magic here. This bug seems to be resolved for me (crossing fingers...)

Thanks for checking this again. Please report back if it breaks again for you.