The only reason my Intel card would not work was that I forgot to add it to the wireless MAC list – and the other reason was that I even forgot that I had activated that list. So now I can savely remove the Ralink chip card and passs it on.
Not much sense to read the rest as I could solve the problem by adding my internal card to the wireless MAC filter of my router. stupid me!
This is what bothers me on the new Ubuntu 8.10 beta on my Thinkpad R52:
- Now with a Ralink card (RT61) also this connection is resetted all the time. On reconnection every time the card that never worked with WPA (Intel 2200 BG) is used. The bug has expired (I set it to ‘new’ again) and it was always just commented to update the driver. So nobody at Canonical seems to care if Intel 2200 BG works or not?
- Related is the fact that I mentioned above that Network Manager never remebers which card and connection works. So if there is a internal card which cant connect he will ALWAYS use this, even if that has never worked. I reported this months ago and nobody cared., too. What the people working on wireless network do not seem to realize is that not every hardware works with every access point. So remembering what works and what not is so essential! Actually I alwys thoght that was what NM was all about. But it seems they only remember the password/key which has worked and not how it worked. I guess this is trivial feature to add so again I dont understand why this has not been changed. Or why a card that never worked is even displayed and takes 80% of all entries, while the working card always switches its position (upper or lower end of the other card) – I would guess it would be important to display the most used and working connections at the top – also depending on the location. Come on guys, NM is not that new any more. So please fix those minor issues – I dont see any sense in listing 30 wireless networks in my range that I never use and will never use. What exactly am i supposed to do with them? This is only a distraction.
So my situation now is that not only the internal card is still not working but now the external PCMCIA card is resetted every five minutes or so. Which makes Ubuntu quite unusable for me – and its already Beta time. I had thought ipw2200 drivers would become really much better with newer kernel > 2.6.26, but 2.6.27 I still have the same bugs. So everybody having same type of hardware should stay back from Ubuntu till I can report that things are working.
Here is an example log. As you see wlan0 (rt61) comes up and then eth2 (ipw2200) interferes:
Oct 7 14:44:02 cine avahi-daemon: Registering new address record for 192.168.200.102 on wlan0.IPv4.
Oct 7 14:44:02 cine dhclient: bound to 192.168.200.102 — renewal in 32910 seconds.
Oct 7 14:44:03 cine NetworkManager: (wlan0): device state change: 7 -> 8
Oct 7 14:44:03 cine NetworkManager: (wlan0): writing resolv.conf to /sbin/resolvconf
Oct 7 14:44:03 cine NetworkManager: Policy set (wlan0) as default device for routing and DNS.
Oct 7 14:44:03 cine NetworkManager: Activation (wlan0) successful, device activated.
Oct 7 14:44:03 cine NetworkManager: Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 7 14:44:03 cine ntpdate: adjust time server 220.127.116.11 offset 0.000279 sec
Oct 7 14:44:07 cine NetworkManager: (eth2): supplicant connection state change: 0 -> 3
Oct 7 14:44:07 cine NetworkManager: (eth2): supplicant connection state change: 3 -> 0
Oct 7 14:44:09 cine NetworkManager: eth2: link timed out.
Oct 7 14:44:12 cine NetworkManager: (eth2): supplicant connection state change: 0 -> 3
Oct 7 14:44:12 cine NetworkManager: (eth2): supplicant connection state change: 3 -> 0