On Thu, Jun 19, 2008 at 4:41 PM, Mike Kershaw <dragorn@xxxxxxxxxxxxxxxxxx> wrote: > On Wed, Jun 18, 2008 at 11:41:10AM -0400, Mike Kershaw wrote: >> On Wed, Jun 18, 2008 at 05:28:14PM +0800, Zhu Yi wrote: >> > On Tue, 2008-06-17 at 09:24 -0400, Mike Kershaw wrote: >> > > 1 - Inability to associate to a network on 5ghz. Same AP on 2.4ghz >> > > works fine, scanning shows the AP fine. Sniffing with an additional >> > > card shows no frames at all being sent by the 4965. AP is on a >> > > channel >> > > the 4965 should be able to talk to according to iwlist channel (logs >> > > attached) >> > >> > >From the log, you are trying to use channel 56 which is under radar >> > detection. The card must hear from the AP first in order to send. Can >> > you try 36? >> >> Must hear from the AP? Like, beacons? If beacons aren't enough, how is >> something ever supposed to associate? >> >> The AP is detected normally via scanning (wpa_supplicant 'scan' and >> iwlist scan) so the card is seeing beacons fine. >> >> I'll reboot into the git kernel later today and redo the test on another >> channel. > > On channel 36 things appear to work (well, as much as they do otherwise, > packet hanging still makes the device unusable). I'm still confused as > to why the card can report it works on that channel, scan that channel, > see beacons, but then refuse to transmit. There is a bug in the firmware. the fix is on the way. Unfortunately I cannot currently commit to to any particular day it will be published yet. What AP do you use I don't see such bad behviour on A band. Thanks Tomas -- 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
