Hi On Mon, Dec 16, 2013 at 2:45 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Mon, 2013-12-16 at 14:39 +0100, David Herrmann wrote: > >> > Can you check in a sniffer what the frame bitrates are that go out? This >> > seems suspicious: >> > >> > nl80211: Set TX rates failed: ret=-100 (Network is down) >> >> I looked at the sniffer data and all I see is a huge amount of p2p >> probe requests from my local device, the successful p2p-invitation and >> invitation response and then lots of go-negotiation requests that >> never get any response. > > Right, and I suspect they don't get a response because (as the sniffer > trace tells me) they're sent with 1 Mbps (a CCK rate), which is invalid > in the P2P spec (must use OFDM). > > Thus something is wrong with the TX bitrates stuff, but I can't tell you > where that would be ... Ok, I will try hooking into the ath9k driver then and see why setting TX rates fails. Thanks a lot! Maybe Oleksij has some more ideas on that. Thanks David -- 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
