Yes, the drivers were from the ndis5 folder and I extracted the 2.1 files by part-installing the drive on a Windoze machine and copied them from the program folder.
You said it appeared to accept the 2.1 driver before … so use ndiswrapper to install the 2.1 driver, then unplug the USB wireless card and replug it … then send the output from:
dmesg | tail -n 50
and
sudo lshw -C network
Does your adapter have a version number on it, such as WG111T v1 ?
netwg11t.inf (strangely not ‘netwg111t’) is the v.1.2 driver. (the v.2.1 driver is the ‘WG111tv.inf’)
So, I have done as you suggested and:
Installed the netwg11t.inf driver (v.1.2)
Unplugged / replugged the adapter
ndisgtk now reports netgw11t driver installed and Hardware Present: Yes
This is now the only driver present in the ndisgtk (Note that ar5523 is still visible in ‘Hardware/ Additional Drivers’ but reporting ‘not currently in use’)
dmesg | tail -n 50
[ 19.597350] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 19.597608] input: HDA Intel Line-Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 19.814687] Bluetooth: Core ver 2.16
[ 19.814727] NET: Registered protocol family 31
[ 19.814731] Bluetooth: HCI device and connection manager initialized
[ 19.814734] Bluetooth: HCI socket layer initialized
[ 19.814737] Bluetooth: L2CAP socket layer initialized
[ 19.814998] Bluetooth: SCO socket layer initialized
[ 19.951920] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.951925] Bluetooth: BNEP filters: protocol multicast
[ 19.992337] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
[ 20.048092] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X
[ 20.048307] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 20.048777] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 20.216110] Bluetooth: RFCOMM TTY layer initialized
[ 20.216118] Bluetooth: RFCOMM socket layer initialized
[ 20.216121] Bluetooth: RFCOMM ver 1.11
[ 20.547279] init: plymouth-stop pre-start process (1134) terminated with status 1
[ 21.310701] Adding 2603004k swap on /dev/mapper/cryptswap1. Priority:-1 extents:1 across:2603004k
[ 505.364167] usbcore: deregistering interface driver ndiswrapper
[ 505.375771] ndiswrapper version 1.57 loaded (smp=yes, preempt=no)
[ 505.383082] usbcore: registered new interface driver ndiswrapper
[ 512.393193] usb 2-2: USB disconnect, device number 2
[ 526.188038] usb 2-2: new high-speed USB device number 3 using ehci_hcd
[ 526.445454] cfg80211: Calling CRDA to update world regulatory domain
[ 526.619013] cfg80211: World regulatory domain updated:
[ 526.619020] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_ga in, max_eirp)
[ 526.619026] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 526.619031] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 526.619036] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 526.619041] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 526.619046] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 526.749084] usbcore: registered new interface driver ar5523
[ 526.895160] usb 2-2: USB disconnect, device number 3
[ 527.164044] usb 2-2: new high-speed USB device number 4 using ehci_hcd
[ 527.416050] usb 2-2: reset high-speed USB device number 4 using ehci_hcd
[ 527.552311] ndiswrapper: driver netwg11t (NETGEAR,01/07/2005,1.0.1.1007) loaded
[ 537.576587] ndiswrapper (NdisWriteError LogEntry:188): log: C0001389, count: 4, return_address: f94cdc6b
[ 537.576595] ndiswrapper (NdisWriteError LogEntry:191): code: 0xf2113800
[ 537.576600] ndiswrapper (NdisWriteError LogEntry:191): code: 0x28
[ 537.576604] ndiswrapper (NdisWriteError LogEntry:191): code: 0xf9277000
[ 537.576608] ndiswrapper (NdisWriteError LogEntry:191): code: 0xf9277000
[ 537.576901] ndiswrapper (mp_init:211): couldn’t initialize device: C0000001
[ 537.576909] ndiswrapper (pnp_start_devi ce:395): Windows driver couldn’t initialize the device (C0000001)
[ 537.576921] ndiswrapper (mp_halt:254): device f1e66480 is not initialized - not halting
[ 537.576927] ndiswrapper: device eth%d removed
[ 537.577005] ndiswrapper: probe of 2-2:1.0 failed with error -22
[ 542.576025] usb 2-2: failed to reset device - initialization timeout
[ 542.576034] usb 2-2: could not initialize adapter
[ 542.579780] ar5523: probe of 2-2:1.0 failed with error -5
Yes I’ve tested it in Windows and it works. One thing I did notice, which may not be important: When I inserted the adapter into a Windows machine, the blue light illuminates brightly. When I inserted it into my Linux machine, the blue light only very faintly lit then immediately went out. however, I have tested it in other USB ports on the same Linux machine and the same happens. I’ve also used other USB devices (mouse/keyboard) and they all work fine in all Linux USB ports.
Mark, I don’t know how but it’s working!
Currently, there are no ndiswrapper drivers installed but the ar5523 driver reports that it is installed and in use.
I can only guess that actually turning the system off as opposed to restarting made a difference - which I only did as I need a power cable!
It’s not 100%; it crashed once (black screen/white text, no usb working) and the screen has strangely gone blank a couple of times (screen auto-detect reported no input) but at least we’re getting somewhere. Seems the ar5523 is definitely the way to go.
Thank you very much thus far
ps: I’m using it now.
But up to you … you can always change it back … ndiswrapper shouldn’t be being loaded now, so that line isn’t needed, and those 3 lines allowed the WG111T to be hotplugged if/when necessary.
I will do that now. However, I’ve just come up against an issue. I had a look at the wireless connections and it seems I was connected with an SSID which looked corrupt (name wasn’t exactly correct) and that the connection type was WEP (when in fact my wireless is WPA2). There was also an SSID with the correct name so I removed the incorrect one and now cannot connect using the correct, WPA2 SSID.
I’ll let you know how it goes after I’ve edited /etc/modules/
Oh, also, there are of course other (neighbour’s) SSID’s which have unusual characters - not English keyboard characters - so clearly something is awry.