Announcement

**Buddlespit** · Aug 22, 2013, 04:02 PM

Read: http://askubuntu.com/questions/48563...reless-adapter

**Tooky** · Aug 23, 2013, 06:35 AM

on writing lsusb i get:

Bus 002 Device 003: ID 0846:9020 NetGear, Inc. WNA3100(v1) Wireless-N 300 [Broadcom BCM43231]

Unfortunately the links there are 404'd and 403'd.

On the bright side, i've now how to make folders.

**Tooky** · Aug 23, 2013, 06:39 AM

the link you posted had comments asking for the following info, maybe it's useful:

@tooky-desktop:~$ sudo lshw -C network
[sudo] password for mel:
SCSI
*-network
description: Ethernet interface
product: 82579V Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 05
serial: e0:69:95:62:f3:4f
size: 100Mbit/s
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=2.1.4-k duplex=full firmware=0.13-4 ip=192.168.0.7 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
resources: irq:51 memory:fe700000-fe71ffff memory:fe728000-fe728fff ioport:f040(size=32)

the iwconfig gives:

eth0 no wireless extensions.
lo no wireless extensions.

**Tooky** · Aug 23, 2013, 12:06 PM

Progress so far:

i've downloaded the ndiswrapper 1.58 from http://sourceforge.net/projects/ndiswrapper/

i've compiled it using the instructions http://askubuntu.com/questions/20608...le-ndiswrapper

then i've used post #98 http://ubuntuforums.org/showthread.p...549190&page=10

first trying to use bcmwlhigh6.inf bcmwlhigh6.sys bcmwlhigh664.sys
which i found in C:\Program Files (x86)\NETGEAR\WNDA3100v2\Driver\WIN764\ like the post said

then i tried again with bcmwlhigh5.inf bcmwlhigh5.sys bcmwlhigh564.sys

For a while i was in a position where ndiswrapper -l would show the driver was installed but device wasn't present, on checking lsusb my device wasn't even present there! To sort this I uninstalled bcmwlhigh6.inf, recompiled the ndiswrapper and rebooted (for good measure).

Now i'm in a better position:

root@mel-desktop:/home/mel/wifi/ndis_bcmwl# ndiswrapper -l
bcmwlhigh5 : driver installed
device (0846:9020) present

and:

root@mel-desktop:/home/mel/wifi/ndis_bcmwl# iwconfig
eth0 no wireless extensions.

lo no wireless extensions.

wlan0 IEEE 802.11g ESSID

ff/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:300 Mb/s Tx-Power:32 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key

ff
Power Management

ff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

My adapter is half working. I'm able to see networks and a KDE deamon promted me for a password for a KDE wallet which i created, and my network has prompted me for the wifi password.

The current issue is that the WLAN interface hangs on "setting network address" before going back to not connected.
There's also a red circle with a white x on it when this occurs, but there's one on my wired connection which has been working fine.

edit: it's a wpa/wpa2 network

**Tooky** · Aug 24, 2013, 04:37 AM

on each reboot i need to load the ndiswrapper again using

#ndiswrapper modprobe

otherwise my adapter shan't even detect networks and the iwconfig command will just show

#root@mel-desktop:/home/mel/wifi/ndis_bcmwl# iwconfig
#eth0 no wireless extensions.

#lo no wireless extensions.

**Tooky** · Aug 24, 2013, 05:47 AM

IT WORKS!

following http://sourceforge.net/apps/mediawik...etgear_WNA3100
I had already done everything in this post apart from

#root@mel-desktop:/# iwconfig wlan0 tx 15

then checked with

#root@mel-desktop:/# nm-tool

and got similar results to the post.

now i'm wirelessly connected!

**Tooky** · Aug 24, 2013, 06:58 AM

Ahh it doesn't anymore. After a reboot i had to reload the ndiswrapper and reset the tx power to 15, even after doing that though i'm hanging on setting network address.

root@mel-desktop:/home/mel# iwconfig
eth0 no wireless extensions.

lo no wireless extensions.

wlan0 IEEE 802.11g ESSID:"SKY0ED87"
Mode:Managed Frequency:2.462 GHz Access Point: 7C:03:4C:90:ED:88
Bit Rate=117 Mb/s Tx-Power:16 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:A573-AF66-2F0A-151F-7CEE-929B-03EA-B14C Security mode:restricted
Power Management

ff
Link Quality:62/100 Signal level:-56 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:31 Invalid misc:4208 Missed beacon:0

nm-tools show's my network state as oscillating between connecting and disconnected:

root@mel-desktop:/home/mel# nm-tool

NetworkManager Tool

State: connected (global)

- Device: wlan0 ----------------------------------------------------------------
Type: 802.11 WiFi
Driver: ndiswrapper
State: disconnected
Default: no
HW Address: C4:3D:C7:C8:2C:6F

Capabilities:

Wireless Properties
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes

Wireless Access Points
BTHub3-2Z2G: Infra, 00:AC:54:CF:B2:E2, Freq 2412 MHz, Rate 54 Mb/s, Strength 37 WPA WPA2
Mshome: Infra, 00:11:50:82:26:B2, Freq 2412 MHz, Rate 54 Mb/s, Strength 60 WEP
BTWiFi-with-FON: Infra, 12:AC:54:CF:B2:E2, Freq 2412 MHz, Rate 54 Mb/s, Strength 35
BTWiFi: Infra, 02:AC:54:CF:B2:E2, Freq 2412 MHz, Rate 54 Mb/s, Strength 35
SKY0ED87: Infra, 7C:03:4C:90:ED:88, Freq 2462 MHz, Rate 54 Mb/s, Strength 72 WPA WPA2

**Tooky** · Aug 24, 2013, 12:51 PM

it seems to fail at ip configuration

**Tooky** · Aug 24, 2013, 02:14 PM

i've installed network-config and run a test, i got the following:

Configuring device wlan0 :

$ iwconfig wlan0 mode managed

$ iwconfig wlan0 essid "SKY0ED87"

$ iwconfig wlan0 rate auto

$ iwconfig wlan0 key off

$ pkill wpa_supplicant

$ wpa_supplicant -B -Dndiswrapper -iwlan0 -c/etc/wpa_supplicant/wpa_psk.conf
wlan0: Unsupported driver 'ndiswrapper'

$ ifconfig wlan0 up

DHCP may take a while, please wait...
$ dhclient wlan0

Configuring device eth0 :

$ ifconfig eth0 down

**Tooky** · Aug 24, 2013, 03:05 PM

i've now set the ip address by c&ping the details from nm-tool into the network maanger. This enabled me to connect according to nm-tools but i didn't get anything on the browser.

pinging my ip address was fine but pinging 8.8.8.8 was not, so maybe a DNS problem?

did the following using https://answers.launchpad.net/ubuntu...estion/208504:

echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf > /dev/null
sudo apt-get update
sudo apt-get upgrade

got some updates.

**vinnywright** · Aug 24, 2013, 03:27 PM

ndiswrapper can be tricky at times ,,,,,,the last time I had to use it , it required 3 comands to be run ,,,,not just the "ndiswrapper -i somefile.inf" thare are 2 others that must be ran to insure proper function ,,,,,,,I do not remember what thay are at the moment (it's installed in a diferent system than I am in right now ) but if you check in a console "man ndiswrapper" you should find them ,,,,,or post it hear and I'll try to help.

VINNY

**Teunis** · Aug 24, 2013, 04:07 PM

My compliments for your perseverance.
This should work but I think I'd have gone shopping for a different wifi adapter...

**Tooky** · Aug 26, 2013, 05:18 AM

Cheers Tenuis... i wish it was paying off though.

Vinny, i hope this means something to you:

#NDISWRAPPER(8) System Manager's Manual NDISWRAPPER(8)

NAME
ndiswrapper - Linux kernel module and user space tool to load and run Windows XP drivers for wireless cards

SYNOPSIS
ndiswrapper

DESCRIPTION
ndiswrapper is two parts: user space tool that is used to install Windows XP drivers and kernel module to load the Windows
XP drivers. Both are called ndiswrapper.

ndiswrapper - tool
The user space tool (/usr/sbin/ndiswrapper) is used whenever a new Windows XP driver is to be installed. This program
takes the following options:

OPTIONS

-i <inf file>
installs new Windows XP driver, where <inf file> is full path to INF file for that driver.

-l lists the currently installed drivers.

-e <driver>
removes an installed Windows XP driver named <driver>.

-m writes an alias for wlan0 (default wireless device) into module configuration file so that ndiswrapper kernel mod‐
ule is loaded automatically when this interface is used.

ndiswrapper - kernel module
The kernel module loads the installed Windows drivers and executes them so that the wireless cards can be used in Linux.
The module takes the following options:

OPTIONS

if_name=<basename>
The default basename for the interface is wlan%d, so that the wireless cards will be configured as wlan0, wlan1,
... (%d is replaced with lowest available number). You may use any other basename or fixed name, such as eth%d,
ndis2 etc.

proc_uid=<uid>
The module creates files in /proc/net/ndiswrapper that provide some useful information. These files are created so
that they can be read only by root by default. If some other user needs to access these files without having to
login as root, then replace <uid> with the user ID of that user.

proc_gid=<gid>
The module creates files in /proc/net/ndiswrapper that provide some useful information. These files are created so
that they can be read only by people in root group by default. If users from other groups need to access these
files, then replace <gid> with the group ID of those users.

ndiswrapper kernel module uses loadndisdriver user space tool to load all the Windows drivers. This tool is not to
be used under normal circumstances. Only when ndiswrapper module is already loaded and a new Windows XP driver is
installed (by ndiswrapper user space tool) and you want the kernel module to load that driver without having to
unload the module that you need to use it.

**vinnywright** · Aug 26, 2013, 03:35 PM

it dose ,,,,,,it looks like you are using a newer ver than I had/have in this system .........so the commands may be different , but first lets see the output of

Code:

ndiswrapper -h

hear is mine

Code:

vinny@Vinnys-HP-G62:~$ ndiswrapper -h
install/manage Windows drivers for ndiswrapper

usage: ndiswrapper OPTION
-i inffile       install driver described by 'inffile'
-a devid driver  use installed 'driver' for 'devid' (dangerous)
-r driver        remove 'driver'
-l               list installed drivers
-m               write configuration for modprobe
-ma              write module alias configuration for all devices
-mi              write module install configuration for all devices
-v               report version information

where 'devid' is either PCIID or USBID of the form XXXX:XXXX,
as reported by 'lspci -n' or 'lsusb' for the card

as we see hear their are 4 comands to be ran whin installing the windows driver (by the way it likes XP drivers best I think your using a win7 one,,yes/no) first the -i option (ndiswrapper -i someinffile.inf) then the -m (ndiswrapper -m ) then the -ma and last the -mi ,,,,,,your newer ver may not take all these so check with the -h option ...

plus their are 2 parts to the ndiswrapper program , ndiswrapper-utils & ndiswrapper-common you nead both (unless the source you compiled had both in it IDK.
was their a reason you compiled from source instead of using the one in your package manager ?

anyway if you have both the -utils & the -common installed lets have a look at "ndiswrapper -h " and I'll walk you through the hole mess

VINNY

Announcement

Driver issues

Driver issues

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment