Comment 7 for bug 72925

Hi Carthik,

sorry for the delay. Here are the steps to reproduce the problem:

1. Save some money and buy a Lenovo ThinkPad Z61m 9453-A11 (which includes an Intel 802.11abg wireless card).
   The problem will probably occur on other laptops with the same card, though.

2. Install "Kubuntu Edgy 6.10" with the latest updates.

3. Get a (decent ?) WLAN router, set it up to use WPA2-PSK and install the packages "wireless-tools" and
   "wpasupplicant".

4. Edit "/etc/wpa_supplicant/wpa_supplicant.conf" as recommended by the man pages:

      ctrl_interface=/var/run/wpa_supplicant
      eapol_version=1
      ap_scan=0

      network={
         ssid="..." # enter ssid here
         scan_ssid=0
         proto=RSN
         key_mgmt=WPA-PSK
         pairwise=CCMP
         group=TKIP CCMP
         psk="..." # enter psk here
      }

5. Run the following commands:

      sudo modprobe ipw3945
      sudo ipup eth1

6. If you're lucky, the connection will come up and will work for a long (or even very long...) time. If you're not,
   the WLAN LED will start to flicker, and nothing will work until you run the following commands:

      sudo ipdown eth1
      sudo modprobe -r ipw3945

   The flickering will *always* start when you run "ipdown eth1", and it of course ends when you unload the driver.

7. If everthing works fine, repeat steps 5 and 6 until it doesn't... ;)

8. If you cannot connect to the WLAN network at all, set "ap_scan" in "wpa_supplicant.conf" to 2 and repeat
   steps 5 and 6.

I just found out today that if you remove "ap_scan=..." from "wpa_supplicant.conf", you can always connect to the
network, even if the WLAN LED flickers. I stay with my parents for a few days, though, so it may be different when
I return home (fingers crossed...).

Another thing to take into account: I didn't upgrade Kubuntu to "Edgy", but did a fresh install. "/etc/hostname"
was empty until I noticed and entered my hostname today.

Have a nice Christmas (if you celebrate it), and thanks a lot!

Martin