Menu
▾
▴
[Acx100-devel] [ acx100-Support Requests-847834 ] Unknown radio type/Tx error 0x10 (MSDU lifetime)
|
From: SourceForge.net <no...@so...> - 2003-12-02 12:15:35
|
Support Requests item #847834, was opened at 2003-11-23 22:26 Message generated for change (Settings changed) made by andim2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=543746&aid=847834&group_id=75380 Category: None Group: None Status: Open Priority: 5 Submitted By: Attila (hat418) Assigned to: Nobody/Anonymous (nobody) >Summary: Unknown radio type/Tx error 0x10 (MSDU lifetime) Initial Comment: I have a D-LINK DWL-520+ card. I use Debian/Woody with kernel 2.4.20. I have compiled pre6 driver succesfully using firmware from original windows driver. The driver starts and I can ping through the radio link but I have the following suspicious message in the log: ... Nov 23 21:44:50 server kernel: FIXME: unknown/unsupported radio type, cannot modify Tx power level yet! ... And also there are several messages (almost after every packet sent) in the log: Nov 23 22:08:52 server kernel: Tx error occurred (error 0x10)!! (maybe distance too high?) The full log of starting the driver is below: Nov 23 21:44:48 server kernel: acx100: It looks like you were coaxed into buying a wireless network card Nov 23 21:44:48 server kernel: acx100: that uses the mysterious ACX100 chip from Texas Instruments. Nov 23 21:44:48 server kernel: acx100: You should better have bought e.g. a PRISM(R) chipset based card, Nov 23 21:44:48 server kernel: acx100: since that would mean REAL vendor Linux support. Nov 23 21:44:48 server kernel: acx100: Given this info, it's plain evident that this driver is EXPERIMENTAL, Nov 23 21:44:48 server kernel: acx100: thus your mileage may vary. Visit http://acx100.sf.net for support. Nov 23 21:44:48 server kernel: acx100_init_module: TI acx100_pci.o: Ver 0.2.0pre6 Loaded Nov 23 21:44:49 server kernel: PCI: Found IRQ 10 for device 00:10.0 Nov 23 21:44:49 server kernel: Found ACX100-based wireless network card, phymem1:0xdffdf000, phymem2:0xdffc0000, irq:10, mem1:0xc285c000, mem2:0xc285e000 Nov 23 21:44:49 server kernel: Allocating 6596, 19C4h bytes for wlandevice_t Nov 23 21:44:49 server kernel: hw_unavailable = 1 Nov 23 21:44:49 server kernel: reset hw_unavailable++ Nov 23 21:44:49 server kernel: Allocated 33708 bytes for firmware module loading. Nov 23 21:44:49 server kernel: acx100_write_fw (firmware): 1, acx100_validate_fw: 1 Nov 23 21:44:49 server kernel: reset hw_unavailable-- Nov 23 21:44:50 server kernel: ************ acx100_initmac_1 ************ Nov 23 21:44:50 server kernel: Allocated 920 bytes for firmware module loading. Nov 23 21:44:50 server kernel: WriteACXImage (radio): 1, ValidateACXImage: 1 Nov 23 21:44:50 server kernel: writing WEP options. Nov 23 21:44:50 server kernel: get_mask 0x00002004, set_mask 0x00000000 Nov 23 21:44:50 server kernel: Got antenna value 0x8d. Nov 23 21:44:50 server kernel: get_mask 0x00000000, set_mask 0x00000000 - after update Nov 23 21:44:50 server kernel: Regulatory domain ID as read from EEPROM: 0x30 Nov 23 21:44:50 server kernel: SSID = STA1E3B9D, len = 9 Nov 23 21:44:50 server kernel: SSID = STA1E3B9D, len = 9 Nov 23 21:44:50 server kernel: hw_unavailable-- Nov 23 21:44:50 server kernel: acx100: form factor 0x01 (D-Link DWL-520+/650+/Planet WL-8305?), radio type 0x0d (Maxim), EEPROM version 0x0005. Uploaded firmware 'Rev 1.9.3.e' (0x01020505). Nov 23 21:44:50 server kernel: firmware version >= 1.9.3.e --> using software timer Nov 23 21:44:50 server kernel: acx100_set_status: Setting iStatus = 0 (STARTED) Nov 23 21:44:50 server kernel: initial settings update on iface activation. Nov 23 21:44:50 server kernel: get_mask 0x00000000, set_mask 0x0000dfff Nov 23 21:44:50 server kernel: acx100_set_status: Setting iStatus = 0 (STARTED) Nov 23 21:44:50 server kernel: Updating WEP key settings Nov 23 21:44:50 server kernel: Updating transmit power: 20 dBm Nov 23 21:44:50 server kernel: FIXME: unknown/unsupported radio type, cannot modify Tx power level yet! Nov 23 21:44:50 server kernel: Updating antenna value: 0x8F Nov 23 21:44:50 server kernel: Updating energy detect threshold: 112 Nov 23 21:44:50 server kernel: Updating Channel Clear Assessment value: 0x0D Nov 23 21:44:50 server kernel: Updating: enable Tx Nov 23 21:44:50 server kernel: Updating: enable Rx Nov 23 21:44:50 server kernel: Updating short retry limit: 5, long retry limit: 3 Nov 23 21:44:50 server kernel: Updating xmt MSDU lifetime: 2048 Nov 23 21:44:50 server kernel: Updating regulatory domain: 0x30 Nov 23 21:44:50 server kernel: Updating channel: 5 Nov 23 21:44:50 server kernel: acx100_set_status: Setting iStatus = 1 (SCANNING) Nov 23 21:44:50 server kernel: get_mask 0x00000000, set_mask 0x00000000 - after update Nov 23 21:44:50 server kernel: acx100_process_probe_response: found and registered station 0: ESSID "DI-614+" on channel 5, BSSID 00 0A 09 00 00 0A (Access Point, 11Mbps), SIR 110, SNR 0. Nov 23 21:44:52 server kernel: Radio scan found 1 stations in this area. Nov 23 21:44:52 server kernel: <Scan Table> 0: SSID="DI-614+",CH=5,SIR=110,SNR=0 Nov 23 21:44:52 server kernel: peer_cap 0x01, needed_cap 0x01 Nov 23 21:44:52 server kernel: ESSID matches: "DI- 614+" (station), "[any]" (config) Nov 23 21:44:52 server kernel: matching station found!! Nov 23 21:44:52 server kernel: d11CompleteScan: matching station FOUND (idx 0), JOINING (00 0A 09 00 00 0A). Nov 23 21:44:52 server kernel: <acx100_join_bssid> BSS_Type = 2 Nov 23 21:44:52 server kernel: <acx100_join_bssid> JoinBSSID MAC:00 0A 09 00 00 0A Nov 23 21:44:52 server kernel: Sending authentication1 request, awaiting response! Nov 23 21:44:52 server kernel: acx100_set_status: Setting iStatus = 2 (WAIT_AUTH) Nov 23 21:44:52 server kernel: Tx error occurred (error 0x10)!! (maybe distance too high?) Nov 23 21:44:53 server kernel: <acx_timer> iStatus = 2 Nov 23 21:44:53 server kernel: resend authen1 request (attempt 2). Nov 23 21:44:53 server kernel: Sending authentication1 request, awaiting response! Nov 23 21:44:54 server kernel: process_authen: UNVERIFIED. Nov 23 21:44:54 server kernel: 00.80.C8.1E.3B.9D<4>00.80.C8.1E.3B.9D<4>00.0A.09.00. 00.0A<4>00.0A.09.00.00.0A<4>00.0A.09.00.00.0A<4>Alg orithm is ok Nov 23 21:44:54 server kernel: Got current client for sta hash tab Nov 23 21:44:54 server kernel: Found acceptable client Nov 23 21:44:54 server kernel: <sta_list_add> sta = 00:0A:09:00:00:0A Nov 23 21:44:54 server kernel: process_authen auth seq step 2. Nov 23 21:44:54 server kernel: acx100_set_status: Setting iStatus = 3 (AUTHENTICATED) Nov 23 21:44:54 server kernel: Sending association request, awaiting response! NOT ASSOCIATED YET. Nov 23 21:44:54 server kernel: association: requesting capabilities 0x0001 Nov 23 21:44:54 server kernel: acx100_set_status: Setting iStatus = 4 (ASSOCIATED) Nov 23 21:44:54 server kernel: ASSOCIATED! Nov 23 21:44:54 server kernel: <acx_timer> iStatus = 4 ---------------------------------------------------------------------- Comment By: Attila (hat418) Date: 2003-11-25 00:31 Message: Logged In: YES user_id=915983 Where can I download pre6_plus_fixes_4 from? I did not find it. I tried "iwconfig wlan0 retry lifetime XXX" but I always get the rror message: Error for wireless request "Set Retry Limit" (8B28) : SET failed on device wlan0 ; Invalid argument. I have tried different values for XXX. And one more thing: as the link works (I can ping) I tried to use it but the performance is very poor. I could ftp at 5- 7kBps at bitrate set to 11M. ---------------------------------------------------------------------- Comment By: Andreas Mohr (andim2) Date: 2003-11-24 17:56 Message: Logged In: YES user_id=132674 Please download the pre6_plus_fixes_4 tar and test it, this should fix the 0x10 MSDU lifetime issues. Also try fiddling with "iwconfig wlan0 retry lifetime XXX" values and tell me when it fails again. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=543746&aid=847834&group_id=75380 |