> > 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. > > 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. > > Whilst the device is up, I continually get console messages like those I > > have inlined below: > > > > Kernel unaligned access at TPC[100ee4d4] do_rx+0x244/0x614 [zd1211rw] > > Kernel unaligned access at TPC[100ee4e8] do_rx+0x258/0x614 [zd1211rw] > > Kernel unaligned access at TPC[100ee4cc] do_rx+0x23c/0x614 [zd1211rw] > > These are unaligned data accesses in the kernel driver. For Daniel. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
