Comment 21 for bug 662288

Thanks Wolfgang,

Ok I had trouble getting [1] the kernel-ppa daily to associate with my access-point. Eventually it worked (about 5 reboots and multiple attempts) I'm not sure if that problem is indicative of anything relevant to this bug. When it finally associated I couldn't contact any of my network so I'm not sure of the state of support in that kernel version. That being said, once I could associate I could reproduce the hang just fine so at least it is clear that the hang is present on mainline.

I'm a little uncertain as to the relationship between the kernel-ppa/mainline [1] and compat-wireless [2] with respect to the "linux-next" variant of compat-wireless. Downloaded the tar-balls from [2] but got an early compile fail when building against the kernel-ppa version (making me think the underpinnigs have changed significantly for this rev), which I don't see with the maverick package (i get further but still fails in some irrelevant drivers - I haven't spent any time getting either working yet). Should I be downloading the other (linux-next) variant of compat-wireless for use with the kernel-ppa?

Is there any reason to prefer testing wireless-compat with the kernel-ppa as the base over using the maverick kernel as the base?

I'll make sure the bug is logged upstream, although at the moment mainline is not a useful baseline for me to run day-to-day as the dkms rt3090 driver from #9 doesn't seem to work, so I'll be slow going getting progress on that.