OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Stuck With Wpa On Cacko 1.23, Can not make WPA work on my Zaurus 3100
DReymann
post May 16 2006, 08:40 AM
Post #1





Group: Members
Posts: 30
Joined: 10-January 04
Member No.: 1,407



Hi,

although reading all informations available on oesf-forums and on different sites on the net I still have problems getting wpa to work on my zaurus 3100 with cacko 1.23.

Recently I changed my access point from wep-encryption to wpa-psk. The change was succesful - I am able to connect my laptop using wpa.

With wep it was no problem to connect my zaurus with the access point. On the zaurus I use Cacko-ROM 1.23, the Wifi-Card is a SanDisk Connect CompactFlash 802.11b.

According to some hints on forum-postings I upgraded the flash to 1.8.4, since the card has a prism chipset.

After insertion of the card it seems to be recognized correctly. For example dmesg containd the following lines:
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.4

This is my /etc/wpa_supplicant.conf
CODE
#######################
# Begin /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
# change to:
# ctrl_interface=/home/root/usr/bin/wpa_supplicant
# does not change anything
# I thought it has to be the path to the binary
ctrl_interface_group=0 # what does that mean?
eapol_version=1    # what does that mean?
ap_scan=1 # because my Access-Point does not broadcast the SSID
network={
    ssid="SSID-OF-MY-ACCESS-POINT"
    #psk="psk in plain text"
    psk=verysecretverxsecretverysecretverysecret
    scan_ssid=1
    key_mgmt=WPA-PSK
    proto=WPA
}
# End of /etc/wpa_supplicant.conf
#####################

I modified my /etc/pcmcia/wlan-ng.conf:
CODE
############################
######## begin /etc/pcmcia/wlan-ng.conf:
#! /bin/sh

WLAN_VERSION=0
WLAN_PATCHLEVEL=1
WLAN_SUBLEVEL=12
WLAN_EXTRAVERSION=-shp

case "$ADDRESS" in
# [snip several lines ...]
qpewlan0,*,*,*)
   INFO="Wpa REYMANN" # the name which was used within qtopia the config tool
   WLAN_ENABLE=y
   WPA=y # added following several post
   dot11PrivacyInvoked=false
   dot11WEPDefaultKeyID=0
   PRIV_KEY128=false
   dot11WEPDefaultKey0=
   dot11WEPDefaultKey1=
   dot11WEPDefaultKey2=
   dot11WEPDefaultKey3=
   IS_ADHOC=n
   AuthType=opensystem
   DesiredSSID="SSID-OF-MY-ACCESS-POINT"
  ;;
*,*,*,*)
    WLAN_ENABLE=n
  ;;
esac
###### end /etc/pcmcia/wlan-ng.conf ##
############################

When hitting the connection-applet the light of the Wifi card flickers for a while but at the end no connection is established.

I did not find any possibilty to send information to a log file. The only information I get is the output of dmesg but this does not help (at least not me).

Some of the possibly relevant parts of dmesg output:
CODE
########################
##### dmesg-output: #########
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.3.7 - 2005-02-12 (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_crypt: registered algorithm 'WEP'
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 135, io 0xf6000000-0xf600003f
prism2_hw_init: initialized in 210 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.4
wifi0: registered netdevice wlan0
prism2: wlan0: operating mode changed 3 -> 2
hostap_cs: CS_EVENT_PM_SUSPEND
hostap_cs: CS_EVENT_RESET_PHYSICAL
pxa_pcmcia_suspend(0)
BlueZ Core ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
wifi0: hfa384x_cmd_issue: cmd reg was busy for 5000 usec
wifi0: hfa384x_cmd_issue - timeout - reg=0x8888
wifi0: hfa384x_cmd: entry still in list? (entry=c38cdf20, type=0, res=-1)
wifi0: hfa384x_cmd: interrupted; err=-110
wifi0: hfa384x_get_rid: CMDCODE_ACCESS failed (res=-110, rid=fd51, len=6)
# the above repeated several times
Could not read current WEP flags.
wifi0: encryption setup failed
wlan0: set_encryption failed
wlan0: hfa384x_setup_bap - timeout before
wlan0: hfa384x_set_rid (rid=fc02, len=34) - failed - res=-110
hostap_cs: CS_EVENT_PM_RESUME
hostap_cs: CS_EVENT_CARD_RESET
prism2_hw_init: initialized in 190 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.4
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
  retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
  A1=00:00:00:00:00:00 A2=00:60:b3:6b:cf:d3 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
  retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
  A1=00:00:00:00:00:00 A2=00:60:b3:6b:cf:d3 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
  retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
  A1=00:00:00:00:00:00 A2=00:60:b3:6b:cf:d3 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
  retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
  A1=00:00:00:00:00:00 A2=00:60:b3:6b:cf:d3 A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
hostap_cs: CS_EVENT_PM_SUSPEND
hostap_cs: CS_EVENT_RESET_PHYSICAL
pxa_pcmcia_suspend(0)
wlan0: hfa384x_setup_bap - timeout before
######## end of dmesg-output ################

Any advice or hint what to to or how to find the reason for my problems. For security reasons I would not like to switch back to WEP-encryption.

Thanks for help in advance

Detlev

Sorry for the long post ...
Go to the top of the page
 
+Quote Post
DRDR
post May 16 2006, 01:09 PM
Post #2





Group: Members
Posts: 46
Joined: 3-September 04
Member No.: 4,448



I had to update the card's firmware to get it work. Try to search for prism firmware update on the forum and you should find some hard to understand stuff which workd in my case...
Go to the top of the page
 
+Quote Post
DReymann
post May 16 2006, 11:55 PM
Post #3





Group: Members
Posts: 30
Joined: 10-January 04
Member No.: 1,407



Hi,

QUOTE(DRDR @ May 16 2006, 10:09 PM)
I had to update the card's firmware to get it work. Try to search for prism firmware update on the forum and you should find some hard to understand stuff which workd in my case...
*


As already mentioned in my post, upgrade has been done. I think
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.8.4

is the latest available firmware.

Detlev
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 23rd October 2014 - 10:37 AM