Where do I put a new module?

timm · 2006-11-21 02:51:06

I am installing wireless networking on an Asus P5B Deluxe WiFi motherboard. It uses a realtek 8187L. I got the linux driver off of the realtek site and built it; now I have a file named r8187.ko. Where do I put it so I can use it at boot?

FUBAR · 2006-11-21 11:49:06

Isn't there a "make install" command to run?

timm · 2006-11-21 17:59:12

Duh....why didn't I think of that? :oops:

Can't do a make install in the main directory. This thing sets up a directory that's a bit different after a build, but in the beta-8187 subdirectory I was able to do a make install; unfortunately it threw a lot of errors about ieee80211-etc-etc undefined. It does however, put the module in its place; but it cannot be started as I get all of the ieee80211 errors when I try.

I know there's an issue about the stack that is used with this driver, so that's probably related.. but that's stuff that's over my head. I'll do some more research.

RobF · 2006-11-21 23:45:57

timm wrote:

Duh....why didn't I think of that? :oops:
Can't do a make install in the main directory. This thing sets up a directory that's a bit different after a build, but in the beta-8187 subdirectory I was able to do a make install; unfortunately it threw a lot of errors about ieee80211-etc-etc undefined. It does however, put the module in its place; but it cannot be started as I get all of the ieee80211 errors when I try.
I know there's an issue about the stack that is used with this driver, so that's probably related.. but that's stuff that's over my head. I'll do some more research.

FWIW, I compiled the RTL8187 driver in Debian a while ago, and it worked fine. The following are my notes from the compile and install. Loading the driver could be automated, e.g. by putting the script in /etc/rc.local. Also, the r8187 and ieee80111 modules should probably be put in /lib/modules/2.6.18-ARCH/kernel/drivers/net/wireless.

=================================

Compiling native Linux driver for RTL8187 chipset in Netgear WG111v2 USB adapter:

Downloaded linux26x-8187(110).zip from http://www.realtek.com.tw/downloads/dow … yword=8187
Unpacked it to folder rtl8187_linuxdrv_V1.1

Unpacked source code:
tar -zxvf stack.tar.gz
tar -zxvf drv.tar.gz

Built and inserted modules:
cd ieee80211/
make clean;make (in user console)
(got 4 warnings related to softmac.c)

In root console executed:
insmod ieee80211_crypt-rtl.ko
insmod ieee80211_crypt_wep-rtl.ko
insmod ieee80211_crypt_tkip-rtl.ko
insmod ieee80211_crypt_ccmp-rtl.ko
insmod ieee80211-rtl.ko

cd ..
cd beta-8187/
make clean;make (still in root console)
(got 6 warnings)

insmod r8187.ko

lsmod shows that all of these modules have been installed, and the adapter is functional (but LED is not).

Wrote a script "load":

#!/bin/sh

insmod ieee80211_crypt-rtl.ko
insmod ieee80211_crypt_wep-rtl.ko
insmod ieee80211_crypt_tkip-rtl.ko
insmod ieee80211_crypt_ccmp-rtl.ko
insmod ieee80211-rtl.ko
insmod r8187.ko
#ifconfig wlan0 up

Wrote a script "unload":

#!/bin/sh

ifconfig wlan0 down
rmmod r8187.ko
rmmod ieee80211-rtl.ko
rmmod ieee80211_crypt_ccmp-rtl.ko
rmmod ieee80211_crypt_tkip-rtl.ko
rmmod ieee80211_crypt_wep-rtl.ko
rmmod ieee80211_crypt-rtl.ko

Put the ieeexxxxxxx.ko modules, the r8187.ko module and the scripts "load" and "unload" in a folder RTLmodules.
To bring up the wireless interface wlan0, run the script "load", to bring it down, run "unload".

timm · 2006-11-25 18:34:10

Thanks.

I've worked through the steps, and although I haven't set up the scripts yet, I have the radio up. Unfortunately, now I can't connect to the network.

I used iwconfig to set the essid; it shows everything lined up with the ap; but signal remains at 0 and the network is unreachable.

What's the trick to getting it to connect?

RobF · 2006-11-25 19:58:07

After you've loaded the IEEE and r8187 modules, you still have to configure the wlan0 interface (it might also be named eth1) as follows:

1. To bring up the wireless interface wlan0 run
# iwconfig wlan0 essid name_of_your_wireless_access_point channel number_of_your_channel
key your_WEP_key_in_hexadecimal open

2. To get an IP address via DHCP run
# dhcpcd wlan0

3. To set up a route to the internet gateway run
# route add default gw 192.168.0.1 (substitute you gateway's IP address here)

You may already have done #1, and #2 may also take care of #3.

To check the connection run
# ifconfig (do you have an IP address?)
# iwconfig (does everything look all right?)
# ping google.com (can you connect to Google?)

If you did succeed in getting a connection to the Internet, you then would want to automate the setup at boot time. To that effect edit /etc/rc.conf and /etc/conf.d/wireless along the lines described in these posts

http://bbs.archlinux.org/viewtopic.php?t=27055 (RobF's post from 11/25)
http://bbs.archlinux.org/viewtopic.php?t=26986

I'd kept the RTLmodules folder on my Desktop and ran the scripts manually whenever I wanted to experiment with that adapter in promiscuous mode in Kismet. Otherwise, for ordinary use, I use a Windows driver via ndiswrapper with this chipset; it's a little easier to handle that way.

If you want to use the native driver for this chipset for good, I'd think it would be best to put all the modules in /lib/modules/2.6.18-ARCH/kernel/drivers/net/wireless; Arch should find them there. Rather than running the "load" script explicitly to load the modules from there, you may also want to try simply putting the modules in MODULES in /etc/rc.conf in the correct order to autoload them at boot time, i.e. (all on one line):

MODULES=(ieee80211_crypt-rtl.ko ieee80211_crypt_wep-rtl.ko ieee80211_crypt_tkip-rtl.ko ieee80211_crypt_ccmp-rtl.ko ieee80211-rtl.ko r8187.ko)

Robert

timm · 2006-11-26 01:56:17

I think I've gone through it, step by step, without connection success. Hopefully another set of eyes will see what I cannot. I have tried it unencrypted and with a wep key; I cannot ping my network.

iwconfig wlan0 yields:

wlan0 802.11b/g linked ESSID:"B53566A"
Mode:Managed Channel=11 Access Point: 00:13:49:79:BF:2B
Bit Rate=54 Mb/s
Retry:on Fragment thr:off
Encryption key:off
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

ifconfig wlan0 yields:

wlan0 Link encap:Ethernet HWaddr 00:15:AF:04:32:DF
inet addr:192.168.27.8 Bcast:192.168.27.255 Mask:255.255.255.0
inet6 addr: fe80::215:afff:fe04:32df/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:185 errors:3 dropped:48 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20264 (19.7 Kb) TX bytes:696 (696.0 b)

iwlist wlan0 scanning yields:

wlan0 Scan completed :
Cell 01 - Address: 00:13:49:79:BF:2B
ESSID:"B53566A"
Protocol:IEEE 802.11g
Mode:Master
Channel:11
Encryption key:off
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 11 6 9 12 18 24 36 48 54
Quality:16 Signal level:0 Noise level:15
Extra: Last beacon: 16ms ago
Cell 02 - Address: 00:0F:B3:B1:C1:AA
ESSID:"ACTIONTEC"
Protocol:IEEE 802.11bg
Mode:Master
Channel:9
Encryption key:off
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
Quality:17 Signal level:0 Noise level:27
Extra: Last beacon: 298ms ago

My message.log has this for the last bit:

Nov 25 17:37:49 tvbox rtl8187: Card MAC address is 00:15:af:04:32:df
Nov 25 17:37:49 tvbox rtl8187: Card reports RF frontend Realtek 8225
Nov 25 17:37:49 tvbox rtl8187: WW:This driver has EXPERIMENTAL support for this chipset.
Nov 25 17:37:49 tvbox rtl8187: WW:use it with care and at your own risk and
Nov 25 17:37:49 tvbox rtl8187: WW:**PLEASE** REPORT SUCCESS/INSUCCESS TO andreamrl@tiscali.it
Nov 25 17:37:49 tvbox rtl8187: This seems a new V2 radio
Nov 25 17:37:49 tvbox rtl8187: PAPE from CONFIG2: 0
Nov 25 17:37:49 tvbox rtl8187: Driver probe completed
Nov 25 17:37:49 tvbox
Nov 25 17:37:49 tvbox usbcore: registered new driver rtl8187
Nov 25 17:37:49 tvbox rtl8187: Card successfully reset
Nov 25 17:37:53 tvbox ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 25 17:41:43 tvbox Linking with B53566A
Nov 25 17:41:43 tvbox Associated successfully
Nov 25 17:41:43 tvbox Using G rates
Nov 25 17:41:43 tvbox ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Nov 25 17:43:24 tvbox rtl8187: Setting SW wep key
Nov 25 17:51:53 tvbox Associated successfully
Nov 25 17:51:53 tvbox Using G rates
Nov 25 18:01:54 tvbox Associated successfully
Nov 25 18:01:54 tvbox Using G rates
Nov 25 18:11:55 tvbox Associated successfully
Nov 25 18:11:55 tvbox Using G rates
Nov 25 18:41:17 tvbox rtl8187: Setting SW wep key
Nov 25 18:56:16 tvbox rtl8187: Setting SW wep key
Nov 25 19:02:55 tvbox rtl8187: Setting SW wep key
Nov 25 19:03:34 tvbox rtl8187: Setting SW wep key
Nov 25 19:05:36 tvbox rtl8187: Setting SW wep key
Nov 25 19:06:49 tvbox Associated successfully
Nov 25 19:06:49 tvbox Using G rates

rayjgu3 · 2006-11-26 02:12:26

try
iwconfig wlan0 essid any
this should let you connect to any ap thats not encrypted
or figure out which is yours on your scan you got 2 listed

iwlist wlan0 scanning yields:
wlan0 Scan completed :
Cell 01 - Address: 00:13:49:79:BF:2B
ESSID:"B53566A"
Protocol:IEEE 802.11g
Mode:Master
Channel:11
Encryption key:off
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 11 6 9 12 18 24 36 48 54
Quality:16 Signal level:0 Noise level:15
Extra: Last beacon: 16ms ago

Cell 02 - Address: 00:0F:B3:B1:C1:AA
ESSID:"ACTIONTEC"
Protocol:IEEE 802.11bg
Mode:Master
Channel:9
Encryption key:off
Bit Rates:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 22 24 36 48 54
Quality:17 Signal level:0 Noise level:27
Extra: Last beacon: 298ms ago

im guessing 1 is your neighbor but neither is encrypted

timm · 2006-11-26 02:19:02

Yes, the ACTIONTEC one isn't mine.

Tried any, no change.

rayjgu3 · 2006-11-26 02:27:40

not positive but ill try from memory

in the network section of /etc/rc.conf put this in
wlan_wlan0="wlan0 essid B53566A channel 11 "

then run
/etc/rc.d/network restart

timm · 2006-11-26 02:38:19

Nice. That does it.

I entered

wlan_wlan0="wlan0 essid B53566A channel 11 "

from the command line and restarted the network as you indicated. I don't have the radio starting automatically yet. I had this line (and a couple of others) in my rc.conf, but they kept flinging errors because I haven't managed to get these modules to load automatically yet; I suppose the radio wasn't up at boot, so these lines were ignored, and since rc.conf isn't reprocessed after I did get the radio up, it didn't know these were there.

Now to get it set up to start automatically

And on to wpa-supplicant......

Thanks to all who helped.

timm · 2006-11-26 16:34:44

This morning I went to go through the automation part of this; I tried moving things around and loading them through rc.conf; lots of errors.

I tried through rc.local; one error shuts things down; when it tries to insmod ieee80211_crypt-rtl.ko it reports -1 "Invalid module format"

I did a pacman update last night when the network was up, maybe I downloaded something that caused a change, so I started from scratch with the driver source; once I have build everything and I try to insmod ieee80211_crypt-rtl.ko, I still get -1 "Invalid module format"

errors.log contains this entry a couple of times:

ieee80211_crypt_rtl: exports duplicate symbol ieee80211_crypt_deinit_entries (owned by ieee80211_crypt)

I removed all references to the ieee80211 modules in rc.conf and rc.local; so it shouldn't be trying to load anything. If I dmesg |grep 8187, I see lots of errors beginning with r8187. I did a depmod while I was trying to get the modules in /lib/etc to be recognized by the system at boot, I have since removed those since it didn't help to have them there. I'm wondering if I messed something up with that. (Yes, I know, children running around with dangerous toys)

I otherwise have no idea what I've done to mess up a working system and no idea how to undo it. How do I fix this one?

RobF · 2006-11-26 18:21:02

The "invalid module format" error message is familiar to me, e.g. I've seen it when trying to load various versions of ndiswrapper in various Linux distros. I've usually gotten around it by wildly hacking around, trying other versions of the software or putting the module in a different path etc. but I've never figured out what is invalid about the format. When I compiled and ran the RTL8187 driver in Debian, I didn't come across these problems. I might be interested in installing this driver in Arch on my system but I wouldn't get around to it immediately. Sorry that I can't help you there.

However, unless you're interested in using raw monitoring (rfmon) mode, why not take the easy way out and use a Windows driver via ndiswrapper? Quite frankly, often these drivers work better than reverse engineered buggy native Linux drivers that aren't supported by the manufacturers.

If you want to do that, see these posts

http://bbs.archlinux.org/viewtopic.php?t=27055 (RobF's post from 11/25)
http://bbs.archlinux.org/viewtopic.php?t=26986

For Windows drivers check here (e.g. search for the pciid of your adapter):

http://ndiswrapper.sourceforge.net/medi … x.php/List

In Arch I've used the RTL8187 in a Netgear WG111v2 wireless USB adapter with the Windows driver pair net111v2.inf and wg111v2.sys which I got from the Netgear support CD. It works very well, certainly with 128-bit WEP encryption. Haven't tried WPA as yet but will soon.

Robert

timm · 2006-11-27 04:25:32

I tried the ndiswrapper approach, but was stymied; couldn't get an iwlist scanning result.

I tried blacklisting the r8187 module, which got rid of the r8187 errors in dmesg. I did a locate for r8187.ko, and found one in the modules directory. This is not the one my script pointed to, but I deleted it anyway. Took the blacklist entry out, rebooted, and got no more messages. Apparently Arch was using that module for some reason; what was wrong with it is unknown.

I then rebuilt the r8187 modules from scratch from the instructions in this thread, this time the wireless interface came right up with no errors. I then moved the modules into /opt/rtl-modules, and since there was a script named wlan0up in the module directory, put that there as well. Added the additional lines to assign an IP address, etc, as discussed above, and rebooted the system. It now comes up automatically on boot.

RobF · 2006-11-27 07:44:07

I'm surprised you couldn't get a Windows driver to work with ndiswrapper. What is the make of your wireless NIC that contains the RTL8187 and which Windows driver did you use?

But I'm glad you eventually got the native Linux driver to work. Is it working with wpa-supplicant? If you can't get it to work with wpa-supplicant (it may not support that as yet) you may need to try the ndiswrapper route again, e.g. with a different Windows driver.

Robert

Mr Green · 2006-11-27 08:51:26

@timm I tried to run wlan0up from rc.local but it cannot find directories ... etc .. would not run from /home either

Yeah its complicated but a script will soon sort that ..

lock your network down if you have not already

Will test this stuff soon maybe you guys will help with a wiki page?

8)

Mr Green · 2006-11-27 11:00:22

Started a wiki page

Wireless_r8187

will need editing & adding to will have a look later

rather than adding modules .. why not use wlan0up ? script

RobF · 2006-11-27 17:56:43

I'm certainly willing to help with a wiki page but not until I've gone through compiling and installing the native driver in Arch myself which won't be until next weekend. The part about running the RTL8187 with a Windows driver & ndiswrapper I could do sooner, I just would like to get that going also for WPA rather than only WEP 128-bit.

The background info on Andrea Merello's native r8187 driver is here:

http://rtl8180-sa2400.sourceforge.net/
http://www.hpl.hp.com/personal/Jean_Tou … lTek80211g
(section 4.10)

Robert

timm · 2006-11-28 03:36:20

With the ndiswrapper I used the latest Windows XP driver from the RealTek site; it may not be supported, I suppose. I couldn't find the pci id of this card, it's on an Asus P5B Deluxe WiFi motherboard, and uses a USB connection. It identifies as the RTL8187L, but nothing more than that that I have seen. I didn't find it on the ndiswrapper wiki page.

Here is the lspci output:

00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82P965/G965 PCI Express Root Port (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) 6 port SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 4364 (rev 12)
03:00.0 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)
03:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)
04:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS] (rev a1)
05:00.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
05:01.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 11)
05:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
05:04.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
06:08.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
06:09.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
--------------------

The rest of this may well be a complete waste of time. In reading the links provided to the native drivers, I'm not finding wpa support mentioned; but I may be wrong. Anyway, here's what I did with the native drivers............

I have (again) run into a brick wall while configuring wpa_supplicant under the native driver. This should be supported, since there is a version included with the driver. I tried that, gave up on that and downloaded the Arch package and have been playing with it.

I bring my network up with this script:

#!/bin/sh

cd /opt/rtl-modules/ieee80211/
insmod ieee80211_crypt-rtl.ko
insmod ieee80211_crypt_wep-rtl.ko
insmod ieee80211_crypt_tkip-rtl.ko
insmod ieee80211_crypt_ccmp-rtl.ko
insmod ieee80211-rtl.ko

cd ../beta-8187/
insmod r8187.ko

cd /

ifconfig wlan0 up

iwconfig wlan0 ap 00:13:49:79:BF:2B
#iwconfig wlan0 ap 00:0D:88:FA:1B:7E
iwconfig wlan0 essid B88888A
ifconfig wlan0 192.168.27.8

cd /

/etc/rc.d/network restart
--------------
The 2B ap is my open one that I use for testing; when I am trying to use wpa it is commented out and the 7E ap, which uses wpa, is uncommented.

My wpa_supplicant file is this:

######
#
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="B88888A"
#scan_ssid=1
psk="aphrasenothererightnow"
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
priority=9
}

when I run this using

wpa_supplicant -D ipw -c /etc/wpa_supplicant.conf -i wlan0 -dddd

I get:

ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'ipw' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=7):
42 35 33 35 36 36 41 B88888A
PSK (ASCII passphrase) - hexdump_ascii(len=20): [REMOVED]
key_mgmt: 0x2
proto: 0x1
pairwise: 0x8
group: 0x8
priority=9 (0x9)
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 9
id=0 ssid='B88888A'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_ipw_init is called
SIOCGIWRANGE: WE(compiled)=20 WE(source)=16 enc_capa=0x0
capabilities: key_mgmt 0x0 enc 0x3
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:15:af:04:32:df
wpa_driver_ipw_set_wpa: enabled=1
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_countermeasures: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=1
Setting scan request: 0 sec 100000 usec
Added interface wlan0
Wireless event: cmd=0x8b06 len=8
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 251 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 9
0: 00:0d:88:fa:1b:7e ssid='B88888A' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
selected based on WPA IE
Trying to associate with 00:0d:88:fa:1b:7e (SSID='B88888A' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_ipw_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
WEXT: Operstate: linkmode=-1, operstate=5
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:0d:88:fa:1b:7e into blacklist
State: ASSOCIATING -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Added BSSID 00:00:00:00:00:00 into blacklist
State: DISCONNECTED -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wioctl[IPW_IOCTL_WPA_SUPPLICANT]: Operation not supported
pa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
Wireless event: cmd=0x8b1a len=16
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
State: DISCONNECTED -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 3
State: DISCONNECTED -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan timeout - try to get results
Received 251 bytes of scan results (1 BSSes)
Scan results: 1
Selecting BSS from priority group 9
0: 00:0d:88:fa:1b:7e ssid='B88888A' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
selected based on WPA IE
Trying to associate with 00:0d:88:fa:1b:7e (SSID='B88888A' freq=0 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
wpa_driver_ipw_set_auth_alg: auth_alg=0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_ipw_set_drop_unencrypted: enabled=1
State: SCANNING -> ASSOCIATING
WEXT: Operstate: linkmode=-1, operstate=5
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:0d:88:fa:1b:7e blacklist count incremented to 2
State: ASSOCIATING -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:00:00:00:00:00 blacklist count incremented to 4
State: DISCONNECTED -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
Wireless event: cmd=0x8b1a len=16
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:00:00:00:00:00 blacklist count incremented to 5
State: DISCONNECTED -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_ipw_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: DISCONNECTED -> DISCONNECTED
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_ipw_set_wpa: enabled=0
wpa_driver_ipw_set_drop_unencrypted: enabled=0
wpa_driver_ipw_set_countermeasures: enabled=0
No keys have been configured - skip key clearing
WEXT: Operstate: linkmode=0, operstate=6
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Removed BSSID 00:0d:88:fa:1b:7e from blacklist (clear)
Cancelling scan request

That's about 30 seconds worth of output. It seems to be finding the ap that is running, but rejects it for some reason. Any ideas?

RobF · 2006-11-28 06:42:16

You could get the usbid of this device with lsusb and then search http://ndiswrapper.sourceforge.net/medi … x.php/List with that string. Perhaps you'll find some comments about which Windows drivers work with that device.

I've downloaded the RealTek WinXP driver that you've been using and will try it tomorrow with my Netgear WG111v2 USB adapter (usbid: 0846:6a00) with ndiswrapper. The Netgear WinXP driver (04/21/2005,5.112.05.0421) that works for me for WEP-128 with the Netgear WG111v2 adapter looks similar to the most recent RealTek driver (07/19/2006,5.1234.0719.2006), or at least the readable .inf file does. This Netgear driver supposedly supports WPA-PSK and WPA2-PSK.

I've never used WPA encryption and therefore cannot comment on the output you're getting when you're running the wpa_supplicant command. I'm not at all sure that WPA is fully supported in the native driver. You could ask Andrea Merello about this (andreamrl _REMOVE_THIS_ *at* tiscali.it) although you may not get an answer. I contacted him a year ago and never received a reply.

Robert

RobF · 2006-11-28 21:23:38

I tried a couple of Windows drivers with ndiswrapper 1.26-1 with my Netgear WG111v2 adapter. Here are the results.

The following didn't work:

1. Realtek driver v.1.234 (2kxp-8187(1234).zip from http://www.realtek.com): neither the WINXP nor the WIN2000 drivers work, i.e. Netrtuw.inf & RTL8187.sys
2. Realtek driver v.1.234 (me98se-8187(1234).zip from http://www.realtek.com): neither the WINME nor the WIN98 drivers work, i.e. Netrtuw.inf & RTL8187.sys
3. Netgear driver v.2.0.1beta (wg111v2_2_0_1_beta_crn.zip from http://kbserver.netgear.com/products/wg111v2.asp): the WinXP_2K driver doesn't work (the Win98se_ME driver does)

The following do work (for WEP-128):

1. The WinXP driver from the support CD that came with the adapter (v.5.112.05.0421 from 04/21/2005)
2. Netgear driver v.2.0.1beta (wg111v2_2_0_1_beta_crn.zip from http://kbserver.netgear.com/products/wg111v2.asp): the Win98se_ME driver works (net111v2.inf & wg111v2.sys), the WinXP_2K driver doesn't

The non-working drivers don't properly initialize the hardware. Even with the drivers that work, I still had to unplug and then reinsert the USB adapter everytime after I had uninstalled one driver (ndiswrapper -e xxxxxxxx <- don't use the .inf extension here) and installed another (ndiswrapper -i xxxxxxxx) and then run /etc/rc.d/network restart. When the Netgear adapter was connected at bootup (and my internal BCM4311 mini-pci wireless adapter disabled and turned off), the system would freeze at : Loading UDev uevents [BUSY]. A hard reboot was required.

Netgear at http://kbserver.netgear.com/products/wg111v2.asp also have a bunch of earlier versions of these drivers but they are not as easy to extract.

One peculiar thing: ndiswrapper -l produced the following (lsusb says 0846:6a00)
using Netgear driver .......... net111v2 driver installed, hardware (0846:6A00) present
using Realtek driver .......... netrtuw driver installed, hardware (13D1:ABE6) present

Two different usbid's for the same hardware?

Robert

Arch Linux

#1 2006-11-21 02:51:06

Where do I put a new module?

#2 2006-11-21 11:49:06

Re: Where do I put a new module?

#3 2006-11-21 17:59:12

Re: Where do I put a new module?

#4 2006-11-21 23:45:57

Re: Where do I put a new module?

#5 2006-11-25 18:34:10

Re: Where do I put a new module?

#6 2006-11-25 19:58:07

Re: Where do I put a new module?

#7 2006-11-26 01:56:17

Re: Where do I put a new module?

#8 2006-11-26 02:12:26

Re: Where do I put a new module?

#9 2006-11-26 02:19:02

Re: Where do I put a new module?

#10 2006-11-26 02:27:40

Re: Where do I put a new module?

#11 2006-11-26 02:38:19

Re: Where do I put a new module?

#12 2006-11-26 16:34:44

Re: Where do I put a new module?

#13 2006-11-26 18:21:02

Re: Where do I put a new module?

#14 2006-11-27 04:25:32

Re: Where do I put a new module?

#15 2006-11-27 07:44:07

Re: Where do I put a new module?

#16 2006-11-27 08:51:26

Re: Where do I put a new module?

#17 2006-11-27 11:00:22

Re: Where do I put a new module?

#18 2006-11-27 17:56:43

Re: Where do I put a new module?

#19 2006-11-28 03:36:20

Re: Where do I put a new module?

#20 2006-11-28 06:42:16

Re: Where do I put a new module?

#21 2006-11-28 21:23:38

Re: Where do I put a new module?

Board footer