On Mon, Nov 19, 2007 at 04:03:02PM +0100, Johannes Berg wrote: > > > > The first noticeable problem is when using iwconfig on the device. I > > > cannot set a key for the device, and a query of the configuration always > > > claims that the "<encryption key is too long>". > > > > Likely some wireless ioctl compat layer bug in the kernel. > > Is this 32/64 interop? The kernel has never been fixed and never will > be. New wireless tools should "support" this, but imnsho you're *much* > better off compiling 64-bit wireless tools. There was a patch for this kind of issue from Masakazu Mokuno that went in 2.6.22 or 2.6.23 that was touching that part. I don't think he went in the stable series, but probably should have. There are other potential cause of problem here, and I suspect he might get the same error with 64 bits userspace. Can you give me the exact error text as reported by iwconfig ? I'll probably have to send you a test version to see what's happening under the cover. > > > If I try to scan for APs using iwlist, I get one AP listed, before a bus > > > error occurs. This of course, does not suggest that the problem is with > > > the driver, but I mention it for the record. > > > > This is an unaligned data access in the userland tools. > > Try to catch it with GDB and give us ths backtrace. > > For Jean. Definitely, it sounds familiar. This is that I need : o version of the kernel o version of the driver if not stock driver o version of Wireless Tools (iwconfig --version). Most likely, you need to upgrade your Wireless Tools to version 29 which fixes this 32/64 interop problem. With the latest kernel and the latest wireless tools, the only known bugs are the two ESSID bugs. Regards, Jean - 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
