The future of Auto-NDISWrapper

Asked by Björgvin Ragnarsson

Canonical is developing a distribution and desktop agnostic tool for installing third-party-drivers called jockey, It does not currently support ndiswrapper drivers but jockey's architecture is very modular so adding support would not be too hard. could become a webservice for jockey to locate the ndiswrapper drivers.

Have you had a look at Jockey and do you think it should replace Auto-NDISWrapper?

Question information

English Edit question
Auto-NDISwrapper Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
climatewarrior (gabrieljoel) said :


Yes, I'm aware of jockey. I believe that integrating ndiswrapper into jockey would be a great step forward. I wish jockey could replace auto-ndiswrapper entirely but I think that at the moment that is not possible for several reasons. Auto-ndis in some cases needs to the user to do several things which I believe would be unacceptable for something like jockey. For example for some drivers we tell the users to go fetch the driver at a specified url and then copy the file to a specified directory. This is due to the fact that many driver providers do not offer a direct link to the downloads. Maybe we could jump over this hoop but I really don't see it ever working in a reliable manner. As jockey needs to be absolutely reliable and robust. What I think would be feasible and highly beneficial would be to automate the installation of several hand picked drivers that are known to work 100% of the time in some determined wireless cards. And all of this integrated into jockey.

Can you help with this problem?

Provide an answer of your own, or ask Björgvin Ragnarsson for more information if necessary.

To post a message you must log in.