Comment 53 for bug 525902

Revision history for this message
Brandon Williams (opensource-subakutty) wrote :

I just installed 64-bit 10.04 onto an IBM ThinkPad W500, and I was having the same network-manager related problem, which was resolved by switching to wicd as suggested in comment #46.

The important snippet from lspci -v is:

03:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
        Subsystem: Intel Corporation Device 1211
        Flags: bus master, fast devsel, latency 0, IRQ 30
        Memory at f4300000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [c8] Power Management version 3
        Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
        Capabilities: [e0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting <?>
        Capabilities: [140] Device Serial Number b6-df-4d-ff-ff-5d-21-00
        Kernel driver in use: iwlagn
        Kernel modules: iwlagn

Also, here are the details from iwconfig in case they matter:

wlan0 IEEE 802.11abgn ESSID:<ESSID>
          Mode:Managed Frequency:2.462 GHz Access Point: 00:1A:1E:64:20:62
          Bit Rate=54 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=67/70 Signal level=-43 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I'd like to switch back to network-manager, since it has 802.1X support for wired connections that wicd lacks, so it would be nice to see some activity on this bug. What information is required at this point in order to proceed? I am very willing to try to help outside of work hours.