headers
Oliver G. | 2 Jun 2005 17:17

Lost in configuring driverloader with wpa_supplicant

Hello all,

For days I have been trying to get wpa_supplicant working on my D-Link
GWL-G520+ (TI ACX111 chipset). Without wpa, the connection is working fine
in ad-hoc mode connected to a ipw2100.
However, things look different when enabling WPA: I just cannot get a
working connection. Attached are some log files and the output of
wpa_supplicant after starting up.

dmesg:
eth2: prism2_param: unknown param 15
driverloader: ndisWrapParseWPAInformationElements: unknown authentication 0
eth2: prism2_param: unknown param 23

wpa_supplicant -i eth2 -c /etc/wpa_supplicant.conf -dd -Dhostap:
Initializing interface 'eth2' conf '/etc/wpa_supplicant.conf' driver 'hostap'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group=0
eapol_version=1
ap_scan=2
fast_reauth=1
Line: 290 - start of a new network block
ssid - hexdump_ascii(len=10):
     74 65 73 74 20 61 64 68 6f 63                     test adhoc
mode=1 (0x1)
proto: 0x1
key_mgmt: 0x10
pairwise: 0x1
(Continue reading)

Permalink | Reply | 1 comment |
headers
Linuxant support (Jonathan | 2 Jun 2005 15:18
Favicon

Re: Lost in configuring driverloader with wpa_supplicant

Hi,

it seems that the DriverLoader module have a problem to deal with the 
WPA encryption according to:

---
driverloader: ndisWrapParseWPAInformationElements: unknown authentication 0
---

Can you please try to connect to an access point with WPA support 
(Managed mode) instead of Ad-Hoc mode to see if there is a difference?

Regards,

Jonathan
Technical specialist / Linuxant
www.linuxant.com
support <at> linuxant.com

Oliver G. wrote:
> Hello all,
> 
> For days I have been trying to get wpa_supplicant working on my D-Link
> GWL-G520+ (TI ACX111 chipset). Without wpa, the connection is working fine
> in ad-hoc mode connected to a ipw2100.
> However, things look different when enabling WPA: I just cannot get a
> working connection. Attached are some log files and the output of
> wpa_supplicant after starting up.
> 
> dmesg:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sune Mølgaard | 7 Jun 2005 10:58

USR5410 and wpa

Hi.

I would like to enable wpa with the amovementiened card, but the win32 
drivers v.4.0q offered on the site doesn't support that.

Thus, I tried to load the v.6.0b15 drivers from USR's website, and this 
snippet from dmesg shows that it wasn't successful:

driverloader: stack=8192/1448/1
driverloader: usr11g.sys: 0xc3a10000..0xc3a6e800 entry = c3a6bc80 (pbase 
= 0x10000)
eth0: New link status: Disconnected (0002)
__alloc_pages: 6-order allocation failed (gfp=0x20/0)
driverloader: NdisMAllocateSharedMemory: FAILED: 
MiniportAdapterHandle=c1827808 Length=204800 Cached=0 
VirtualAddress=00000000
eth0: failed to initialize adapter (err = -5)
eth0: Failed to register net device (-5)
usb.c: registered new driver driverloader
usb.c: deregistering driver driverloader
driverloader: stack=8192/1448/1
driverloader: usr11g.sys: 0xc3a10000..0xc3a6e800 entry = c3a6bc80 (pbase 
= 0x10000)
eth0: New link status: Disconnected (0002)
__alloc_pages: 6-order allocation failed (gfp=0x20/0)
driverloader: NdisMAllocateSharedMemory: FAILED: 
MiniportAdapterHandle=c1827808 Length=204800 Cached=0 
VirtualAddress=00000000
eth0: failed to initialize adapter (err = -5)
eth0: Failed to register net device (-5)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Oliver G. | 7 Jun 2005 13:30

Re: Re: Lost in configuring driverloader with wpa_supplicant

Hello Jonathan,

Unfortunately, I don't have a WPA capable access point at hand. I have
tried switching the DWL-G520+ to master mode, but iwconfig just told me
this is not supported. I could, however, try to switch my ipw2100 to
master mode, but don't know if this is possible at all.
Do you know of another way to find the issue?

Thanks,
Oliver
Permalink | Reply | 501 comments |
headers
Linuxant support (Jonathan | 7 Jun 2005 12:34
Favicon

Re: USR5410 and wpa

Hi,

it seems that the kernel have a problem to allocated to the installed 
Windows XP driver all the DMA memory it needs. You could try to load the 
DriverLoader module as soon as possible as the machine boots with the 
init. scripts. This workaround is likely to fix this problem.

Regards,

Jonathan
Technical specialist / Linuxant
www.linuxant.com
support <at> linuxant.com

Sune Mølgaard wrote:
> Hi.
> 
> I would like to enable wpa with the amovementiened card, but the win32 
> drivers v.4.0q offered on the site doesn't support that.
> 
> Thus, I tried to load the v.6.0b15 drivers from USR's website, and this 
> snippet from dmesg shows that it wasn't successful:
> 
> driverloader: stack=8192/1448/1
> driverloader: usr11g.sys: 0xc3a10000..0xc3a6e800 entry = c3a6bc80 (pbase 
> = 0x10000)
> eth0: New link status: Disconnected (0002)
> __alloc_pages: 6-order allocation failed (gfp=0x20/0)
> driverloader: NdisMAllocateSharedMemory: FAILED: 
> MiniportAdapterHandle=c1827808 Length=204800 Cached=0
(Continue reading)

Permalink | Reply | 0 comments |
headers
Linuxant support (Jonathan | 7 Jun 2005 12:42
Favicon

Re: Lost in configuring driverloader with wpa_supplicant

Hi,

master mode is not currently supported by DriverLoader.

If you have an access point but it doesn't support WPA, it is possible 
that simply upgrading the firmware of the access point to it's latest 
version will enable WPA support.

You could also try with multiple versions of the Windows XP driver to 
see if there is a difference.

If you require more assistance, please send at support <at> linuxant.com the 
output of 'dumpdiag'. Type the following in a root shell:

---
dldrconfig --dumpdiag
---

Just send us the generated file located in /tmp 
('driverloaderdiag.txt'). It'll help us solve the problem.

Regards,

Jonathan
Technical specialist / Linuxant
www.linuxant.com
support <at> linuxant.com

Oliver G. wrote:
> Hello Jonathan,
(Continue reading)

Permalink | Reply | 501 comments |
headers
Justin Rosander | 11 Jun 2005 00:15
Picon
Favicon

NETDEV WATCHDOG error

Hello,
I get an error message that says:

NETDEV WATCHDOG: eth1: transmit timed out

I have been running this card fine without any
problems until now.  It works great under XP as well.

I read your response to another person with this
problem in this post:
http://www.linuxant.com/pipermail/driverloader/2005q1/001989.html

I updated the driver to the latest XP driver, still
with no success.
I ran 'dldrconfig --dumpdiag', if there is someone I
should send that to, let me know.

My wireless card is a D-Link DWL-G510.  I'm running
AGNULA DeMuDi 1.2, kernel 2.4.25.  If there's anything
else you need to know, please inform me.

Many thanks in advance!
--Justin

		
__________________________________ 
Yahoo! Mail 
Stay connected, organized, and protected. Take the tour: 
http://tour.mail.yahoo.com/mailtour.html
(Continue reading)

Permalink | Reply | 1 comment |
headers
Patrick de Brabander | 11 Jun 2005 14:58
Picon

Can't get WEP enabled.

I've an USR8054 accespoint with and USR8056 NIC. When i enable a 64-bit WEp open key, i can't access it with the driverloader. Every other wireless computer can acces the accesspoint.
 
I've set in redhat-network-config the key and i tried it with "iwconfig eth0 key s:12345 open"
i've set this same key 12345 in my accespoint in ASCII.
 
what am i doing wrong
 
or is there an other way to secure my wireless lan
 
 
thanks
 
Patrick
 
 
_______________________________________________
driverloader mailing list
driverloader <at> lists.linuxant.com
https://www.linuxant.com/mailman/listinfo/driverloader
Permalink | Reply | 1 comment |
headers
John Durant | 11 Jun 2005 17:39
Favicon

D-Link DWL-650 Rev.P1

Hi...Anyone had any luck with this card?  Tnx, John
Permalink | Reply | 2 comments |
headers
Verner Kjærsgaard | 11 Jun 2005 19:49
Picon

SuSE9.3, wlan0 doesn't start, but may be started...

Hi list,

My wireless on my SuSE9.3 with driverloader works fine, I know how to get it 
on-air, but of course, if it could work automatically... Initially this is 
what happens when I do (as root) "rcnetwork restart".

**********************************************''
Setting up network interfaces:
    lo
    lo        IP address: 127.0.0.1/8                                 done
    eth0      device: Intel Corporation 82540EP Gigabit Ethernet Controller 
(Mobile) (rev 03)
    eth0      No configuration found for eth0                         unused
    wlan0     device: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI 
Adapter (rev 04)
    wlan0     Startmode is 'manual'                                   skipped
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  done
IBM93:/home/vk # ifup wlan0
    wlan0     device: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI 
Adapter (rev 04)
ERROR: command 'iwconfig wlan0 key off' returned
       Error for wireless request "Set Encode" (8B2A) :
       SET failed on device wlan0 ; Operation not supported.
ERROR: command 'iwconfig wlan0 key open 20B41AF4F3' returned
       Error for wireless request "Set Encode" (8B2A) :
       SET failed on device wlan0 ; Operation not supported.
Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... 
backgrounding.
IBM93:/home/vk # 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:16436  Metric:1
          RX packets:122 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9352 (9.1 Kb)  TX bytes:9352 (9.1 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:0C:F1:0C:6B:67
          inet6 addr: fe80::20c:f1ff:fe0c:6b67/64 Scope:Link
          UP BROADCAST NOTRAILERS MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:18 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
**********************************************''

As you can see, I get errors and no DHCP and so forth. I remedy this situation 
by launching my browser and goes into http://localhost:18020 - I then select 
reload from the web-site. I then do a (as root) "ifup wlan0". This causes no 
errors and gives me an adress and all. Like this:

IBM93:/home/vk # ifup wlan0
    wlan0     device: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI 
Adapter (rev 04)
Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... 
backgrounding.
IBM93:/home/vk # 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:16436  Metric:1
          RX packets:315 errors:0 dropped:0 overruns:0 frame:0
          TX packets:315 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:86128 (84.1 Kb)  TX bytes:86128 (84.1 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:0C:F1:0C:6B:67
          inet addr:172.16.12.201  Bcast:172.16.12.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:f1ff:fe0c:6b67/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:2 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:784 (784.0 b)  TX bytes:1553 (1.5 Kb)

IBM93:/home/vk #

So, as you can see, all is ok and life is good :-)
Only, of course, if it could be brought to work in the first place, it'd be 
great. And, changing "manuel" to "auto" doesn't work...

Any hints?

--

-- 
------------------------------
Med venlig hilsen/Best regards
Verner Kjærsgaard
Open Source Academy
www.os-academy.dk
Denmark
+45 56964223
+45 2014 5551
------------------------------
Permalink | Reply | 1 comment |

Gmane