"For advanced users: There is a known bug in these Debian packages, detailed in this thread ( http://forums.debian.net/viewtopic.php?p=100586&sid=f09bad1b17b5f4c62f1c4e68d044b8bf ). If you are having issues after installing from these packages, the kernel module may not have installed, so you may get the error FATAL: Module ndiswrapper not found when you run modprobe ndiswrapper in the terminal. To avoid this problem, it's best to compile from the source available at http://ndiswrapper.sourceforge.net/. This is fairly simple but requires the build-essential package to be installed. You can install this offline using apt-cdrom from the command line or the synaptic package manager with the ubuntu install CD."
I consider myself an advanced user, but not a linux developer and I don't have a clue how to workaround this bug following those "official" instructions.
I want to mention again that this bug may be a regression occurred in Ubuntu 12.04. Expecting users to workaround a bug by compiling source by themselves is a serious issue to me.
This bug is now mentioned here:
https:/ /help.ubuntu. com/community/ WifiDocs/ Driver/ Ndiswrapper
"For advanced users: There is a known bug in these Debian packages, detailed in this thread ( http:// forums. debian. net/viewtopic. php?p=100586& sid=f09bad1b17b 5f4c62f1c4e68d0 44b8bf ). If you are having issues after installing from these packages, the kernel module may not have installed, so you may get the error FATAL: Module ndiswrapper not found when you run modprobe ndiswrapper in the terminal. To avoid this problem, it's best to compile from the source available at http:// ndiswrapper. sourceforge. net/. This is fairly simple but requires the build-essential package to be installed. You can install this offline using apt-cdrom from the command line or the synaptic package manager with the ubuntu install CD."
I consider myself an advanced user, but not a linux developer and I don't have a clue how to workaround this bug following those "official" instructions.
I want to mention again that this bug may be a regression occurred in Ubuntu 12.04. Expecting users to workaround a bug by compiling source by themselves is a serious issue to me.