ndiswrapper wpa2 eap-tls does not work

[ra]

Binary package hint: linux-image-2.6.20-16-386

Using feisty fawn on a MSI S270 laptop (the one with the AMD Turion cpu) I got a problem with the wireless lan network card (02:09.0 Ethernet controller: Linksys, A Division of Cisco Systems [AirConn] INPROCOMM IPN 2220 Wireless LAN Adapter (rev 01)) using ndiswrapper (1.38 from the feisty repository):
wpa2 psk works. wpa2 eap-tls fails during ie 3/4 authentication but it works with the vanilla ndiswrapper (1.38).
The vanilla version does not compile with USE_OWN_WQ (called CONFIG_NDISWRAPPER_WQ in the ubuntu kernel). If I compile the vanilla version with USE_OWN_WQ it fails the same way.
Is there a special reason ubuntu does not use the default ndiswrapper compile options? It would be very nice if the ubuntu kernel worked ootb on this machine.

[ra (r.a)]

5 weeks later the problem is still persistent - same problem and same (trivial) fix even with the gutsy release and 2.6.22 kernel.

maybe someone from the kernel/ndiswrapper team could be so kind and tell me why CONFIG_NDISWRAPPER_WQ is used...

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[ra (r.a)]

there is a automated reaction _one year_ after i posted a bug and the source to the problem with a simple question (why USE_OWN_WQ/CONFIG_NDISWRAPPER_WQ is used). i have a work around (since one year) and i'm not willing to test (any more) your 2.6.27 pre-release.

handling bug reports imho is a way of making a distribution better (from a user pov). this wont happen if you simply ignore bug reports.

[Leann Ogasawara (leannogasawara)]

Hi Robert,

Thank you for your response. First I apologize for the lack of response you've received with the bug report you filed. This is an area where we are constantly trying to improve. Regarding the automated call for testing that was sent, we needed to get as much feedback about the 2.6.27 kernel as quickly as possible. It by no means excuses the lack of response you had received prior, but it is still an update we felt you should have been notified of and given a chance to test and note any regressions before it is decided to move to 2.6.27 prior to Intrepid's release. We have been trying to closely monitor any feedback we receive.

I can't comment specifically why CONFIG_NDISWRAPPER_WQ was enabled for the 2.6.20 kernels as I was not involved at that point in time. I can however tell you that with the Intrepid kernel this option does not appear to exist any longer. It's hard to say though if your bug is really fixed unless you'd be willing to test. Since you've already voiced that this is something you are unwilling to do, I'll unfortunately just go ahead and close this report. If you do have a change of heart and feel like testing we would still appreciate your feedback. Again, I apologize for the lack of attention you had received prior. We will continue to try to improve on this in the future. Thanks.