On Thu, 2010-06-03 at 23:48 -0700, Johannes Berg wrote: > On Thu, 2010-06-03 at 17:56 +0200, Christian P. Schmidt wrote: > > > > Maybe try the rfkill tool: > > > http://wireless.kernel.org/en/users/Documentation/rfkill > > > > Yes, it was the rfkill tool that caused my attempts to fail. However, > > this didn't change my association attempt problems. > > I also took my time to look at the PCIe port - steady 3.3V on the RFKILL > > pin, which means "no RFKILL". > > > > Any further ideas? > > Unfortunately not. It would seem that something is causing your frames > not to be transmitted correctly, but I see no reason for that right now. The logs provided contains a lot of useful information. Among this is that the device is unable to transmit data with the firmware returning a "TX_LOCKED" status. From what I understand this is a regulatory check failure based on the channel type, which does not make sense in this regard since from what I can tell channel 8, which is an active channel, is used. I passed this question to our firmware folks and now waiting for an answer. Reinette -- 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
