03-21-2014, 10:55 PM
Hi, SkylineR34
You might try adding the following to /etc/modules (this is from the Ubuntu wireless wiki, available at: https://help.ubuntu.com/community/WifiDo...#autostart ):
If you are using the nm-applet to configure Wireless Network, ndiswrapper will not be started by the network manager alias setting. In order to ensure the ndiswrapper module is loaded at system startup. First, make a backup copy of the file:
/etc/modules
before manually editing it. Then, edit the /etc/modules file to add an entry for ndiswrapper at the end of the file. In Ubuntu:
gksudo gedit /etc/modules
In Kubuntu:
kdesu kate /etc/modules
and add the word ndiswrapper to the end of this file and save it.
The basic problem is that ndiswrapper is linking to the driver file, and this link needs to be unloaded for "proper" shutdown, otherwise the process will hang as the kernel does not know how to proceed.
I don't know whether this will work but it is worth a try.
You might try adding the following to /etc/modules (this is from the Ubuntu wireless wiki, available at: https://help.ubuntu.com/community/WifiDo...#autostart ):
If you are using the nm-applet to configure Wireless Network, ndiswrapper will not be started by the network manager alias setting. In order to ensure the ndiswrapper module is loaded at system startup. First, make a backup copy of the file:
/etc/modules
before manually editing it. Then, edit the /etc/modules file to add an entry for ndiswrapper at the end of the file. In Ubuntu:
gksudo gedit /etc/modules
In Kubuntu:
kdesu kate /etc/modules
and add the word ndiswrapper to the end of this file and save it.
The basic problem is that ndiswrapper is linking to the driver file, and this link needs to be unloaded for "proper" shutdown, otherwise the process will hang as the kernel does not know how to proceed.
I don't know whether this will work but it is worth a try.