I think my problem may not be the same as the one described in this bug -- I wondered about this after posting, since I saw the same behavior with NM as well as WICD.
Yes, my problem was with the wireless driver (iwlagn). I thought this bug had to do with it because my wireless access point was not getting recognized. Further research led me to the following bugs, which are more relevant -- I learned of the compat-wireless drivers from this comment: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/313854/comments/6
James,
I think my problem may not be the same as the one described in this bug -- I wondered about this after posting, since I saw the same behavior with NM as well as WICD.
Yes, my problem was with the wireless driver (iwlagn). I thought this bug had to do with it because my wireless access point was not getting recognized. Further research led me to the following bugs, which are more relevant -- I learned of the compat-wireless drivers from this comment: https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/313854/ comments/ 6
https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/348275 /bugs.launchpad .net/ubuntu/ +source/ linux-ubuntu- modules- 2.6.24/ +bug/193970
https:/
HTH.
--aslam