List Info

Thread: DLINK DWL-122 on ARM platform not stable, why?
DLINK DWL-122 on ARM platform not stable, why?
user name
 2006-09-21 08:59:42 
The dlink dwl-122 dongle i used on my ARM(XScale270)
platform seemed
not stable, the linux is 2.6.10. USB driver used OHCI mode.

1. opensystem without WEP
After a set of wlanctl-ng command and iwconfig, ifconfig,
route...,
the output listed below:
/ # linkstatus=CONNECTED
hfa384x_usbctlx_complete_sync: CTLX[3] error: state(Request
failed)
prism2sta_commsqual_defer: error fetching commsqual

Around 2 seconds after "linkstatus=CONNECTED",
the first error appeared.
And when i ping the gateway, another error come out like
below:

/ # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=127 time=9.9 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=127 time=3.6 ms
hfa384x_usbctlx_complete_sync: CTLX[3] error: state(Request
failed)
prism2sta_commsqual_defer: error fetching commsqual

Sometime, this error appeared:
skb_p80211_to_ether: OTHER frame too large (-4 > 1500)
hfa384x_usbctlx_complete_sync: CTLX[3] error: state(Request
failed)
prism2sta_commsqual_defer: error fetching commsqual

Will you please give me some guide? How could I make it
stable? What's
the reason of those errors?

2. Opensystem with WEP(64bits)
When i set WEP(64bits) on AP, the dongle also could connect
to the AP,
and i could see the dongle's information on AP's trace.
But even i set
IP address and route of the dongle, no host could i ping to.
Some
error info like this:
... ...
message=lnxreq_autojoin
  ssid='mobot'
  authtype=opensystem
  resultcode=success
/usr/lib # linkstatus=CONNECTED

error message shown below:
hfa384x_usbctlx_complete_sync: CTLX[3] error: state(Request
failed)
prism2sta_commsqual_defer: error fetching commsqual
... ...
I never really connected to LAN when my AP set WEP.

I need some guide on these problems, thank you very much!

Tiger.Yin
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user
DLINK DWL-122 on ARM platform not stable, why?
user name
 2006-09-21 14:32:09 
On Thu, Sep 21, 2006 at 04:59:42PM +0800, Tiger.Yin wrote:
> The dlink dwl-122 dongle i used on my ARM(XScale270)
platform seemed
> not stable, the linux is 2.6.10. USB driver used OHCI
mode.

What driver version?   What firmware version?

> Sometime, this error appeared:
> skb_p80211_to_ether: OTHER frame too large (-4 >
1500)

This is interesting.  

> 2. Opensystem with WEP(64bits)
> When i set WEP(64bits) on AP, the dongle also could
connect to the AP,
> and i could see the dongle's information on AP's
trace. But even i set
> IP address and route of the dongle, no host could i
ping to. Some
> error info like this:
> ... ...
> message=lnxreq_autojoin
>   ssid='mobot'
>   authtype=opensystem
>   resultcode=success
> /usr/lib # linkstatus=CONNECTED

Are you sure you don't need 'authtype=sharedkey'?

Is the WEP key known to be identical/correct?

Finally, despite many heroic efforts from many contributors
(Especially Chris Rankin), prism2 USB hardware is inherently

flaky.  Newer firmawre helps a lot, as do newer driver revs.
 
 - Solomon
-- 
Solomon Peachy                        solomonlinux-wlan.com
AbsoluteValue Systems                 http://www.linux-wlan.com
721-D North Drive                     +1 (321) 259-0737 
(office)
Melbourne, FL 32934                   +1 (321) 259-0286 
(fax)
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user
DLINK DWL-122 on ARM platform not stable, why?
user name
 2006-09-22 01:05:04 
Thank you, Solomon!
The driver version I tried is 0.2.2, 0.2.3 and 0.2.5.
Firmware
information like below:
ident: nic: id=0x8026 1.0.0
ident: pri: id=0x15 1.1.3
ident: sta: id=0x15 1.7.1
But I couldn't find suitable firmware for my dongle because
I found no
firmware is used for nic id=0x8026. I'm not sure if those
firmware
could used on my dongle?

I tried WEP with "sharedkey", but the result is
the same. So will you
please give me some idea on firmware updating? Thanks a lot!

Tiger.Yin


On 9/21/06, Solomon Peachy <solomonlinux-wlan.com> wrote:
> On Thu, Sep 21, 2006 at 04:59:42PM +0800, Tiger.Yin
wrote:
> > The dlink dwl-122 dongle i used on my
ARM(XScale270) platform seemed
> > not stable, the linux is 2.6.10. USB driver used
OHCI mode.
>
> What driver version?   What firmware version?
>
> > Sometime, this error appeared:
> > skb_p80211_to_ether: OTHER frame too large (-4
> 1500)
>
> This is interesting.
>
> > 2. Opensystem with WEP(64bits)
> > When i set WEP(64bits) on AP, the dongle also
could connect to the AP,
> > and i could see the dongle's information on AP's
trace. But even i set
> > IP address and route of the dongle, no host could
i ping to. Some
> > error info like this:
> > ... ...
> > message=lnxreq_autojoin
> >   ssid='mobot'
> >   authtype=opensystem
> >   resultcode=success
> > /usr/lib # linkstatus=CONNECTED
>
> Are you sure you don't need 'authtype=sharedkey'?
>
> Is the WEP key known to be identical/correct?
>
> Finally, despite many heroic efforts from many
contributors
> (Especially Chris Rankin), prism2 USB hardware is
inherently
> flaky.  Newer firmawre helps a lot, as do newer driver
revs.
>
>  - Solomon
> --
> Solomon Peachy                        solomonlinux-wlan.com
> AbsoluteValue Systems                 http://www.linux-wlan.com
> 721-D North Drive                     +1 (321) 259-0737
 (office)
> Melbourne, FL 32934                   +1 (321) 259-0286
 (fax)
>
>
>
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user
DLINK DWL-122 on ARM platform not stable, why?
user name
 2006-09-25 06:02:22 
The driver version I tried is 0.2.2, 0.2.3 and 0.2.5.
Firmware
information like below:
ident: nic: id=0x8026 1.0.0
ident: pri: id=0x15 1.1.3
ident: sta: id=0x15 1.7.1
But I couldn't find suitable firmware for my dongle because
I found no
firmware is used for nic id=0x8026. I'm not sure if those
firmware
could used on my dongle?

I tried WEP with "sharedkey", but the result is
the same. So will you
please give me some idea on firmware updating? Thanks a lot!


On 9/21/06, Solomon Peachy <solomonlinux-wlan.com> wrote:
> On Thu, Sep 21, 2006 at 04:59:42PM +0800, Tiger.Yin
wrote:
> > The dlink dwl-122 dongle i used on my
ARM(XScale270) platform seemed
> > not stable, the linux is 2.6.10. USB driver used
OHCI mode.
>
> What driver version?   What firmware version?
>
> > Sometime, this error appeared:
> > skb_p80211_to_ether: OTHER frame too large (-4
> 1500)
>
> This is interesting.
>
> > 2. Opensystem with WEP(64bits)
> > When i set WEP(64bits) on AP, the dongle also
could connect to the AP,
> > and i could see the dongle's information on AP's
trace. But even i set
> > IP address and route of the dongle, no host could
i ping to. Some
> > error info like this:
> > ... ...
> > message=lnxreq_autojoin
> >   ssid='mobot'
> >   authtype=opensystem
> >   resultcode=success
> > /usr/lib # linkstatus=CONNECTED
>
> Are you sure you don't need 'authtype=sharedkey'?
>
> Is the WEP key known to be identical/correct?
>
> Finally, despite many heroic efforts from many
contributors
> (Especially Chris Rankin), prism2 USB hardware is
inherently
> flaky.  Newer firmawre helps a lot, as do newer driver
revs.
>
>  - Solomon
> --
> Solomon Peachy                        solomonlinux-wlan.com
> AbsoluteValue Systems                 http://www.linux-wlan.com
> 721-D North Drive                     +1 (321) 259-0737
 (office)
> Melbourne, FL 32934                   +1 (321) 259-0286
 (fax)
>
>
>
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user
fwloading USB prism2 devices (Was Re: DLINK DWL-122 on ARM platform not stable, why?)
user name
 2006-09-28 11:38:41 

  


  

    
Tiger.Yin wrote:

mail.gmail.com"
 type="cite">
  
The driver version I tried is 0.2.2, 0.2.3 and 0.2.5. Firmware
information like below:
ident: nic: id=0x8026 1.0.0
ident: pri: id=0x15 1.1.3
ident: sta: id=0x15 1.7.1
But I couldn't find suitable firmware for my dongle because I found no
firmware is used for nic id=0x8026. I'm not sure if those firmware
could used on my dongle?
  



I have both of the devices you mentioned, though my DWL-122 has
succumbed to what I think is a loose internal connection. (Probably
from it falling to the floor one too many times, so that's my fault -
it no longer works under Windows either.) I'm currently writing this
mail on a laptop connected over the MA111 wireless, tho, as I had been
meaning to install and test 0.2.5 anyway. The firmware loading process
I remember from the D-Link is virtually identical to what follows, and
I found both ran well with the latest sta firmware in RAM.



The latest sta firmware
that's included with linux-wlan-ng is newer than what's displayed in
your proc output, and seems to ram-load fine on 0x8026 USB devices.
With 0.2.5 installed on my Fedora Core 5 box using the make config /
make / make install rules, the ram-load is run via udev rules on insert
of either device, so this process "normally" is automatic (for those
with udev support, at least). The results of the load show up in dmesg
output:



[immediately after device is physically inserted into USB port]

----dmesg----

usb 1-1: new full speed USB device using uhci_hcd and address 4

usb 1-1: configuration #1 chosen from 1 choice

PDA Read from 0x007f0000 in EXTDS space.

PDA Read from 0x007f0000 in EXTDS space.

Writing 4096 bytes to ram 0x7e2ffe

Writing 4096 bytes to ram 0x7e3ffe

Writing 4096 bytes to ram 0x7e4ffe

Writing 4096 bytes to ram 0x7e5ffe

Writing 4096 bytes to ram 0x7e6ffe

Writing 4096 bytes to ram 0x7e7ffe

Writing 4096 bytes to ram 0x7e8ffe

Writing 4096 bytes to ram 0x7e9ffe

Writing 4096 bytes to ram 0x7eaffe

Writing 4096 bytes to ram 0x7ebffe

Writing 4096 bytes to ram 0x7ecffe

Writing 4096 bytes to ram 0x7edffe

Writing 3010 bytes to ram 0x7eeffe

Writing 416 bytes to ram 0x7efc20

Writing 16 bytes to ram 0x7efdd0

Writing 4044 bytes to ram 0x7f0800

Writing 3288 bytes to ram 0x7fe000

hfa384x_usbctlx_complete_sync: CTLX[1] error: state(Request failed)

hfa384x_drvr_start: cmd_initialize() failed, result=-5

prism2sta_ifstate: hfa384x_drvr_start() failed,result=-5

----dmesg----



The last lines there seem to be a quirk in the MA111 (at least the
one I'm using) -- the error either indicates or results in it failing
to "come to life" properly after it's fwloaded and re-enabled by the
driver scripts, which I found can be fixed by disabling and re-enabling
it again by hand. If you decide to update the firmware on the MA111,
you may have to issue additional "wlanctl-ng wlan0 lnxreq_ifstate
ifstate=disable" and then "... ifstate=enable" commands afterwards to
bring it to life. I don't know if there's a way to script the process
so that it succeeds. (But if so please let us know, I don't mind having
to hand-enable so I've never experimented with mods to the automation
scripts. Maybe a short sleep between the prism2dl and the enable would
work.)



Since I'm guessing with an ARM platform and a 2.6.10 kernel version,
udev isn't in the picture (plus the driver install should've set things
up if it was), it's easiest to do the firmware load by hand, at least
initially. I followed along with the /etc/wlan/shared script to make
sure I did the right steps, and loaded my MA111 with the latest STA
1.8.3 the same way it does, since it seems to work well for me when
udev fwloads via /etc/wlan/shared.



/etc/wlan/shared.prism2 contains a function prism2_fwload() which maps
(on lines 82-83) NIC type 0x8026 to the "prism2_ru.hex" firmware file,
and then loads it with the following commands (minus the sudo for root
privileges, of course):



% sudo /sbin/wlanctl-ng wlan0 lnxreq_ifstate ifstate=fwload

message=lnxreq_ifstate

  ifstate=fwload

  resultcode=success



% sudo /sbin/prism2dl -r /etc/wlan/prism2_ru.hex wlan0

Reading S-record file /etc/wlan/prism2_ru.hex...

NIC ID: 0x8026 v1.0.0

MFI ID: 0x1 v1 1->1

CFI ID: 0x2 v2 1->1

PRI ID: 0x3 v1 1->4

Version:  ID 0x1f 1.8.3

Compat: Role 0 Id 0x4 v3 1->15

Compat: Role 0x1 Id 0x1 v1 1->1

Compat: Role 0x1 Id 0x2 v2 1->1

Compat: Role 0x1 Id 0x3 v1 4->4

Seq: 0

Platform:  ID 0x800a 1.0.0

Platform:  ID 0x800f 1.0.0

Platform:  ID 0x8010 1.0.0

Platform:  ID 0x8011 1.0.0

Platform:  ID 0x801e 1.0.0

Platform:  ID 0x801f 1.0.0

Platform:  ID 0x8020 1.0.0

Platform:  ID 0x8025 1.0.0

Platform:  ID 0x8026 1.0.0

Platform:  ID 0x8027 1.0.0

prism2dl: warning: Failed to find PDR for plugrec 0x0406.

prism2dl: warning: Failed to find PDR for plugrec 0x0302.

prism2dl: warning: Failed to find PDR for plugrec 0x0414.

prism2dl: finished.



The failed PDR warnings seem to be harmless (like I said, my MA111
functions with 1.8.3 firmware loaded), and /proc/net/p80211/wlan0/nsd
now shows 0.0.0 for all versions, which is "correct" until I re-enable
the device using:



% sudo wlanctl-ng wlan0 lnxreq_ifstate ifstate=disable

message=lnxreq_ifstate

  ifstate=disable

  resultcode=success

% sudo wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable

message=lnxreq_ifstate

  ifstate=enable

  resultcode=success



(Again, the disable prior to enable may be my paranoia and
unnecessary. I also tend to issue a disable before "ifstate=fwload".
The /etc/wlan scripts see ifstate as a tristate, and move into any
state from either other state... I make no claim to superior knowledge
-- in fact I assume the script developers' understanding is better than
mine -- how it should best be done. I just got into the habit of not
going between fwload and enable directly while fiddling with this
MA111, and I can't say if anything is really affected by the extra
steps. YMMV.)



...After this, dmesg reports the proper hardware setup and iwconfig
sees that the interface is ready for config:



----dmesg----

ident: nic h/w: id=0x8026 1.0.0

ident: pri f/w: id=0x15 1.1.3

ident: sta f/w: id=0x1f 1.8.3

MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1

CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1

PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4

STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/15

PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1

STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1

STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1

Prism2 card SN: x00x00x00x00x00x00x00x00x00x00x00x00

----dmesg----



% iwconfig wlan0

Warning: Driver for device wlan0 has been compiled with version 20

of Wireless Extension, while this program supports up to version 19.

Some things may be broken...



wlan0     IEEE 802.11-DS  ESSID:off/any

          Mode:Auto  Channel:0  Access Point: Not-Associated

          Bit Rate:2 Mb/s   Tx-Power:18 dBm

          Retry min limit:8   RTS thr:off   Fragment thr: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





Good luck!



  -FeRD


mail.gmail.com"
 type="cite">
  
I tried WEP with "sharedkey", but the result is the same. So will you
please give me some idea on firmware updating? Thanks a lot!


On 9/21/06, Solomon Peachy linux-wlan.com"><solomonlinux-wlan.com> wrote:
  

  

    
On Thu, Sep 21, 2006 at 04:59:42PM +0800, Tiger.Yin wrote:
    

    

      
The dlink dwl-122 dongle i used on my ARM(XScale270) platform seemed
not stable, the linux is 2.6.10. USB driver used OHCI mode.
      

    

    
What driver version?   What firmware version?

    

    

      
Sometime, this error appeared:
skb_p80211_to_ether: OTHER frame too large (-4 > 1500)
      

    

    
This is interesting.

    

    

      
2. Opensystem with WEP(64bits)
When i set WEP(64bits) on AP, the dongle also could connect to the AP,
and i could see the dongle's information on AP's trace. But even i set
IP address and route of the dongle, no host could i ping to. Some
error info like this:
... ...
message=lnxreq_autojoin
  ssid='mobot'
  authtype=opensystem
  resultcode=success
/usr/lib # linkstatus=CONNECTED
      

    

    
Are you sure you don't need 'authtype=sharedkey'?

Is the WEP key known to be identical/correct?

Finally, despite many heroic efforts from many contributors
(Especially Chris Rankin), prism2 USB hardware is inherently
flaky.  Newer firmawre helps a lot, as do newer driver revs.

 - Solomon
--
Solomon Peachy                        linux-wlan.com">solomonlinux-wlan.com
AbsoluteValue Systems                 http://www.linux-wlan.com
721-D North Drive                     +1 (321) 259-0737  (office)
Melbourne, FL 32934                   +1 (321) 259-0286  (fax)



    

  

  
_______________________________________________
Linux-wlan-user mailing list
lists.linux-wlan.com">Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user

  




  

  
  
   
     
    






 [1-5]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )