LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices

Reply
 
Search this Thread
Old 10-15-2003, 09:58 PM   #1
ktminc
LQ Newbie
 
Registered: Oct 2003
Posts: 6

Rep: Reputation: 0
Exclamation wireless dlink 520+


Hi ,
I have read a lot of threads on this topic and I have tried to piece all them together to get my card to work...

But No luck.


Here is what I have right now:

kernel 2.4.22

acx100_0.2.pre2 driver


I ahve added some debug statements in the ihw.c code for the driver to see if I am getting and calls to and from the card....


I have tried static ip as wlel as dhcp. They both give the same results.


Does anyone have any ideas on what I am doing wrong here

Thanks




[root@localhost scripts]# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
From 192.168.2.101 icmp_seq=1 Destination Host Unreachable
From 192.168.2.101 icmp_seq=2 Destination Host Unreachable
From 192.168.2.101 icmp_seq=3 Destination Host Unreachable
From 192.168.2.101 icmp_seq=4 Destination Host Unreachable
From 192.168.2.101 icmp_seq=5 Destination Host Unreachable
From 192.168.2.101 icmp_seq=6 Destination Host Unreachable

--- 192.168.2.1 ping statistics ---
8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7020ms
, pipe 3



iwconfig

lo no wireless extensions.

eth0 no wireless extensions.

wlan0 v0.2.0pre2 ESSID:"SMC"
Mode:Managed Channel:6 Access Point: 00:04:E2:4E:7E:FF
Bit Rate=11Mb/s Tx-Power:18 dBm
Encryption key:xxx-xxx-xx Security mode:restricted
Link Quality:100/100 Signal level:54/100 Noise level:0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

( Key is correct by x outed )

I have verifed the MAC address is the WLAN of my wireless router

Sysylog

Oct 15 22:40:38 localhost kernel: acx100: It looks like you were coaxed into buying a wireless network card
Oct 15 22:40:38 localhost kernel: acx100: that uses the mysterious ACX100 chip from Texas Instruments.
Oct 15 22:40:38 localhost kernel: acx100: You should better have bought e.g. a PRISM(R) chipset based card,
Oct 15 22:40:38 localhost kernel: acx100: since that would mean REAL vendor Linux support.
Oct 15 22:40:38 localhost kernel: acx100: Given this info, it's plain evident that this driver is EXPERIMENTAL,
Oct 15 22:40:38 localhost kernel: acx100: thus your mileage may vary.
Oct 15 22:40:38 localhost kernel: CONFIG_PCMCIA: 0
Oct 15 22:40:38 localhost kernel: Found ACX100-based wireless network card, phymem1:0xff9fe000, phymem2:0xff9e0000, irq:22, mem1:0xe08c7000, mem2:0xe09ff000
Oct 15 22:40:38 localhost kernel: Allocating 6688, 1A20h bytes for wlandevice_t
Oct 15 22:40:38 localhost kernel: Allocated 33708 bytes for firmware module loading.
Oct 15 22:40:38 localhost kernel: acx100_write_fw (firmware): 1, acx100_validate_fw: 1
Oct 15 22:40:39 localhost /etc/hotplug/net.agent: invoke ifup wlan0
Oct 15 22:40:39 localhost /etc/hotplug/net.agent: register event not handled
Oct 15 22:40:39 localhost kernel: ************ acx100_initmac_1 ************
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: Allocated 964 bytes for firmware module loading.
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd F
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 10
Oct 15 22:40:39 localhost kernel: WriteACXImage (radio): 1, ValidateACXImage: 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 18
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost kernel: writing WEP options.
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 13
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd A
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 14
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd A
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost last message repeated 2 times
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 12
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost last message repeated 2 times
Oct 15 22:40:39 localhost kernel: setting regulatory domain to 1 (0x10): FCC (USA) (1-11)
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost last message repeated 3 times
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost last message repeated 2 times
Oct 15 22:40:39 localhost kernel: setting regulatory domain to 1 (0x10): FCC (USA) (1-11)
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:39 localhost last message repeated 3 times
Oct 15 22:40:39 localhost kernel: SSID = STAAD87D8, len = 9
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 13
Oct 15 22:40:39 localhost kernel: SSID = STAAD87D8, len = 9
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 14
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 1
Oct 15 22:40:39 localhost kernel: acx100: form factor 0x00 (standard?), radio type 0x11 (RFMD), EEPROM version 0x0000. Uploaded firmware 'Rev 1.9.3.e' (0x01020505).
Oct 15 22:40:39 localhost kernel: SSID = STAAD87D8, len = 9
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 13
Oct 15 22:40:39 localhost kernel: SSID = STAAD87D8, len = 9
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 14
Oct 15 22:40:39 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:40 localhost kernel: SSID = SMC, len = 3
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 13
Oct 15 22:40:40 localhost kernel: SSID = SMC, len = 3
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 14
Oct 15 22:40:40 localhost kernel: Warning: WEP support might not be supported in Ad-Hoc mode yet!
Oct 15 22:40:40 localhost kernel: WEP 64bit
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:40 localhost kernel: firmware version >= 1.9.3.e --> using software timer
Oct 15 22:40:40 localhost kernel: <AcxSetStatus> iStatus = 0 (STARTED)
Oct 15 22:40:40 localhost kernel: Set transmit power = 1
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:40 localhost kernel: Setting antenna value: 0x8F
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:40 localhost kernel: Setting ED threshold value: 0x70
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:40 localhost kernel: Setting CCA value: 0x0D
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:40 localhost kernel: Setting regulatory domain to 0x10
Oct 15 22:40:40 localhost kernel: setting regulatory domain to 1 (0x10): FCC (USA) (1-11)
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:40 localhost kernel: Changing to channel 6
Oct 15 22:40:40 localhost kernel: <AcxSetStatus> iStatus = 1 (SCANNING)
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 8
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 4
Oct 15 22:40:40 localhost kernel: acx100_issue_cmd cmd 3
Oct 15 22:40:40 localhost kernel: ProcessProbeResponse: found and registered station 0: ESSID "SMC" on channel 6, BSSID 00 04 E2 4E 7E FF (Access Point, 11Mbps), SIR 138, SNR 0.
Oct 15 22:40:41 localhost kernel: Radio scan found 1 stations in this area.
Oct 15 22:40:41 localhost kernel: <Scan Table> 0: SSID="SMC",CH=6,SIR=138,SNR=0
Oct 15 22:40:41 localhost kernel: peer_cap 0x11, needed_cap 0x01
Oct 15 22:40:41 localhost kernel: ESSID matches: "SMC" (station), "SMC" (config)
Oct 15 22:40:41 localhost kernel: matching station found!!
Oct 15 22:40:41 localhost kernel: d11CompleteScan: matching station FOUND (idx 0), JOINING (00 04 E2 4E 7E FF).
Oct 15 22:40:41 localhost kernel: acx100_issue_cmd cmd B
Oct 15 22:40:41 localhost kernel: <acx100_join_bssid> BSS_Type = 2
Oct 15 22:40:41 localhost kernel: <acx100_join_bssid> JoinBSSID MAC:00 04 E2 4E 7E FF
Oct 15 22:40:41 localhost kernel: Sending authentication1 request, awaiting response!
Oct 15 22:40:41 localhost kernel: <AcxSetStatus> iStatus = 2 (WAIT_AUTH)
Oct 15 22:40:41 localhost kernel: process_authen: UNVERIFIED.
Oct 15 22:40:41 localhost kernel: 00.80.C8.AD.87.D8<4>00.80.C8.AD.87.D8<4><sta_list_add> sta = 00:04:E2:4E:7E:FF
Oct 15 22:40:41 localhost kernel: process_authen auth seq step 2.
Oct 15 22:40:41 localhost kernel: transmit_auth3!
Oct 15 22:40:41 localhost kernel: process_authen: UNVERIFIED.
Oct 15 22:40:41 localhost kernel: 00.80.C8.AD.87.D8<4>00.80.C8.AD.87.D8<4>process_authen auth seq step 4.
Oct 15 22:40:41 localhost kernel: <AcxSetStatus> iStatus = 3 (AUTHENTICATED)
Oct 15 22:40:41 localhost kernel: Authenticated!
Oct 15 22:40:41 localhost kernel: Sending association request, awaiting response! NOT ASSOCIATED YET.
Oct 15 22:40:41 localhost kernel: association: requesting capabilities 0x0011
Oct 15 22:40:41 localhost kernel: acx100_issue_cmd cmd 2
Oct 15 22:40:41 localhost kernel: <AcxSetStatus> iStatus = 4 (ASSOCIATED)
Oct 15 22:40:41 localhost kernel: ASSOCIATED!
Oct 15 22:40:42 localhost kernel: <acx_timer> iStatus = 4
Oct 15 22:41:20 localhost kernel: <transmit_deauthen>sta=00:02:8A:A1:A9:F8
Oct 15 22:41:20 localhost kernel: Tx error occurred (error 0x20)!! (maybe distance too high?)
Oct 15 22:41:20 localhost kernel: <transmit_deauthen>sta=00:02:8A:A1:A9:F8
Oct 15 22:41:22 localhost kernel: process_authen: UNVERIFIED.
 
Old 10-17-2003, 06:43 AM   #2
ktminc
LQ Newbie
 
Registered: Oct 2003
Posts: 6

Original Poster
Rep: Reputation: 0
I did some checking and the error
Tx error occurred (error 0x20)!! (maybe distance too high?)
is coming from my eth0 card that I am not using...

DOes the code only pick up the first nic.

Is there a way to make it use the one I want to use.

Am I correct here

Thanks

Kevin
 
Old 10-19-2003, 01:30 PM   #3
akaBeaVis
Guru
 
Registered: Apr 2003
Location: Maryland
Distribution: Slack 9.1,10 Mandrake 10,10.1, FedCore 2,3, Mepis 2004, Knoppix 3.6,3.7, SuSE 9.1, FreeBSD 5.2
Posts: 1,109

Rep: Reputation: 45
I'm sorry, I thought this was the same thread as this one:
http://www.linuxquestions.org/questi...247#post547247
please see that thread as he has his dwl-520+ working now.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DLink 520+ dns johnlittlepeap Mandriva 0 10-21-2004 04:40 AM
Dlink 520+ and RedHat EyesintheDark Linux - Wireless Networking 0 04-30-2004 04:23 PM
wireless dlink 520+ ktminc Linux - Hardware 1 10-16-2003 09:23 PM
DLink DWL 520+ and DHCP fatherus Linux - Networking 1 04-23-2003 03:25 PM
DLINK 520 Ethernet Card Cher Linux - Hardware 0 02-27-2003 10:31 PM


All times are GMT -5. The time now is 08:13 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration