Motorsheep - 2013-11-10

I have an old Sony Viao laptop running Mint 15 Mate. I have attempted to use a Netgear WN111 wireless adapter with NDISwrapper. After installing all the necessary modules, I successfully added the driver, found the network, got online, and it worked flawlessly.

Then I rebooted, and my entire network was hosed.

This is a completely fresh install of Mint. The only thing I have done to it is run the updater, add all the NDISWrapper packages (to fix the 'ndiswrapper not found' issue common to mint), then install the driver for the adapter into NDISWrapper and connect to the wireless router.

Here are the symptoms:

  1. Booting up, the screen hangs and displays “waiting for network configuration”, then “waiting up to 60 more seconds for network configuration” (I know the 'failsafe.conf' fix for this, but include it as a symptom of the bigger issue of a broken network).

  2. After booting up, I get a “networking disabled” and “Networkmanager not running” message when I try to open the network. Prior to removing the WN111 driver, I was unable to restart Network Manager with the console. After physically removing the adapter and removing the driver from NDISwrapper, I am able to start Network Manager from the console and regain cabled access, but after reboot it is back to being disabled.

  3. Every so often, administrative functions do not work (such as “sudo” or “run as administrator”) and hangs the terminal or program. A reboot seems to fix this.

Had the adapter never worked at all, I would have chalked this up to a hardware incompatibility and moved on, but the fact that it works perfectly before I reboot the machine leads me to believe there is something else at work here.

Here are the results from running various test when I posted this issue on the Mint Forums, on which it was suggested I re-post the problem here.


$ sudo /usr/lib/linuxmint/mintWifi/mintWifi.py

-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

-------------------------
* IV. querying ifconfig...
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

-------------------------
* V. querying DHCP...
-------------------------
* VI. querying nslookup google.com...
;; connection timed out; no servers could be reached

-----------------------------------------------------------------------------------------------

$ sudo service network-manager start
network-manager start/running, process 2172

-----------------------------------------------------------------------------------------------

$ sudo /usr/lib/linuxmint/mintWifi/mintWifi.py
-------------------------
* I. scanning WIFI PCI devices...
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.

eth0 no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 08:00:46:99:ba:66
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::a00:46ff:fe99:ba66/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31 errors:0 dropped:0 overruns:0 frame:0
TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3727 (3.7 KB) TX bytes:15419 (15.4 KB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1107 (1.1 KB) TX bytes:1107 (1.1 KB)

-------------------------
* V. querying DHCP...
Rather than invoking init scripts through /etc/init.d, use the
service(8)
utility, e.g. service smbd reload

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the reload(8) utility, e.g. reload smbd
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server: 192.168.0.1
Address: 192.168.0.1#53

Non-authoritative answer:
Name: google.com
Address: 173.194.33.101
Name: google.com
Address: 173.194.33.102
Name: google.com
Address: 173.194.33.103
Name: google.com
Address: 173.194.33.104
Name: google.com
Address: 173.194.33.105
Name: google.com
Address: 173.194.33.110
Name: google.com
Address: 173.194.33.96
Name: google.com
Address: 173.194.33.97
Name: google.com
Address: 173.194.33.98
Name: google.com
Address: 173.194.33.99
Name: google.com
Address: 173.194.33.100

Results of inxi -N and ndiswrapper -l with adapter plugged in but driver not installed:

$ ndiswrapper -l
>> (no result) <<

$ inxi -N
Network: Card-1: Intel 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller driver: e100
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 08:00:46:99:ba:66
Card-2: NetGear WN111(v1) RangeMax Next Wireless [Marvell 88W8362+88W8060]
IF: N/A state: N/A mac: N/A

Results of inxi -n and ndiswrapper -l with adapter plugged in and driver installed in ndiswrapper:

$ ndiswrapper -l
netmw245 : driver installed
device (0846:9000) present

$ inxi -N
>> (terminal hangs! no result) <<

Removing the driver and unplugging the adapter does not restore network-related terminal commands, including "sudo service network-manager stop" unless system is rebooted.


$ dmesg | grep ndis
[ 1242.165501] ndiswrapper version 1.58 loaded (smp=yes, preempt=no)
[ 1242.213450] usbcore: registered new interface driver ndiswrapper
[ 1493.424796] usbcore: deregistering interface driver ndiswrapper
[ 1493.452771] ndiswrapper version 1.58 loaded (smp=yes, preempt=no)
[ 1493.743637] ndiswrapper: driver netmw245 (Netgear,11/19/2007,1.0.7.3) loaded
[ 1494.743037] usbcore: registered new interface driver ndiswrapper

(with adapter and driver installed)


I have found many threads on NDISwrapper issues, as well as the individual symptoms, but nothing has worked yet. If anyone has any suggestions on how to proceed I would greatly appreciate it. Let me know what other information I can provide.

 
Last edit: Motorsheep 2013-11-10