On Mon, 2010-03-08 at 18:37 -0800, Jim Ham wrote: > What I have discovered is that if the ESSID is not active, iwconfig sets > it correctly and it sticks. If the ESSID is one that is locally present, > iwconfig seems to set it, but it almost immediately reverts to garbage. Either you have a memory corruption bug in your kernel, or you have some buggy userspace tool (it could be a misbehaving NetworkManager or wicd) that changes ESSID on the interface as soon as the driver reports association. I haven't seen any similar reports. > Kernel driver in use: ath5k ath5k is not an example of code quality, but I don't remember any memory corruption bugs in it fixed since 2.6.32. I suggest following steps: 1) Check for updates for your distribution, install updates, recheck. 2) Boot to the single user mode, make sure that wpa_supplicant and wicd are not running (kill them otherwise) and try setting up the connection manually. 3) Install the latest compat-wireless, recheck. -- Regards, Pavel Roskin -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
