From: Diego B. <di...@bi...> - 2003-09-29 21:59:30
|
Hello! I just bought a D-Link AirPlus DWL-650+ in the hopes that this driver would support it. Unfortunately this is not the case, my notebook hangs after loading the acx100_pci module. I tried acx100 version 0.2.0-pre2, 0.2.0-pre1, 0.1h and CVS. I used firmware revision 1.50 from the Linux driver as well as 1.9.3 from my Windows driver CD, all with no success. I've read all the docs, spent some time in Google, but still I cannot find a solution. Thus I'm hoping that someone here might help me out... My setup: Toshiba Satellite 320CDT with a homebrewed 2.4.22 kernel and latest wireless tools. At first I had problems with the wrong regulatory domain being set, I resolved this by hardcoding 0x30 into src/acx100_helper.c. Here is part of the output that happens after insmod, sorry I cannot give you the full output, the machine hangs, I'm copying this from the screen by hand.. Changing to channel 6 <AcxSetStatus> iStatus = 1 (SCANNING) <acx100_set_timer> Elapse = 3000000 When I tried again with the AP shut down, I get the following additional output and the machine does not hang anymore: Radio scan found 0 stations in this area. d11CompleteScan: no matching station found in range and not in Ad-Hoc mode --> giving up scanning. <AcxSetStatus> iStatus = 0 (STARTED) <acx100_set_timer> Elapse = 1500000 <acx_timer> iStatus = 0 NETDEV WATCHDOG: wlan0: transmit timed out NETDEV WATCHDOG: wlan0: transmit timed out NETDEV WATCHDOG: wlan0: transmit timed out NETDEV WATCHDOG: wlan0: transmit timed out The last message is repeated ad infinitum. When I start up the AP again and issue an iwconfig command, I get the following message and the machine hangs again: <AcxSetStatus> iStatus = 1 (SCANNING) <acx100_set_timer> Elapse = 3000000 After a few minutes I get NETDEV WATCHDOG: wlan0: transmit timed out ad infinitum again. Any clues what else I could try, test, patch, whatever? I also get this message Warning: Driver for device wlan0 has been compiled with version 15 of Wireless Extension, while this program is using version 12. Some things may be broken... although I am using kernel 2.4.22 and latest wireless tools from sourceforge. What must I update? Thanks in advance Diego P.S.: I'm having trouble subscribing to this mailing list, I get a confirmation email, but never seem to get subscribed after answering to this mail... >From diego Mon Sep 29 19:00:05 +0200 2003 To: acx...@li... Subject: D-Link AirPlus DWL-650+ hangs machine X-Mailer: VM 7.17 under Emacs 21.2.1 Hello! I just bought a D-Link AirPlus DWL-650+ in the hopes that this driver would support it. Unfortunately this is not the case, my notebook loads the acx100_pci module but hangs after ifconfig. I tried acx100 version 0.2.0-pre2, 0.2.0-pre1, 0.1h and CVS. I used firmware revision 1.50 from the Linux driver as well as 1.9.3 from my Windows driver CD, all with no success. I've read all the docs, spent some time in Google, but still I cannot find a solution. Thus I'm hoping that someone here might help me out... My setup: Toshiba Satellite 320CDT with a homebrewed 2.4.22 kernel and latest wireless tools. At first I had problems with the wrong regulatory domain being set, I resolved this by hardcoding 0x30 into src/acx100_helper.c. Here is the output after insmod: acx100: It looks like you were coaxed into buying a wireless network card acx100: that uses the mysterious ACX100 chip from Texas Instruments. acx100: You should better have bought e.g. a PRISM(R) chipset based card, acx100: since that would mean REAL vendor Linux support. acx100: Given this info, it's plain evident that this driver is EXPERIMENTAL, acx100: thus your mileage may vary. Visit http://acx100.sf.net for support. init_module: TI acx100_pci.o: Ver 0.2.0pre2 Loaded init_module: dev_info is: TI acx100_pci CONFIG_PCMCIA: 0 Found ACX100-based wireless network card, phymem1:0x11000000, phymem2:0x11010000, irq:5, mem1:0xc7228000, mem2:0xc722a000 Allocating 6688, 1A20h bytes for wlandevice_t stop queue after setup. Allocated 33708 bytes for firmware module loading. acx100_write_fw (firmware): 1, acx100_validate_fw: 1 ****************************************** ************ acx100_initmac_1 ************ ****************************************** ==> Get the mailbox pointers from the scratch pad registers CmdMailboxOffset = fdc8 InfoMailboxOffset = ff4c <== Get the mailbox pointers from the scratch pad registers CommandParameters = [ 0xC7239DCC ] InfoParameters = [ 0xC7239F50 ] Allocated 920 bytes for firmware module loading. WriteACXImage (radio): 1, ValidateACXImage: 1 CodeEnd:8730 writing WEP options. <== Initialize the Queue Indicator pDc->pFrameHdrQPool = 0xc02e6000 pDc->pFrameHdrQPoolPhyAddr = 0x 2e6000 pDc->TxBufferPool = 0xc0020000 pDc->TxBufferPoolPhyAddr = 0x 20000 pDc->pTxHostDescQPool = 0xc009e000 pDc->TxHostDescQPoolPhyAddr = 0x 9e000 pAdapter->rHWInfo.pvMemBaseAddr2 = 0xc722a000 pDc->ui32ACXTxQueueStart = 0x00008ad8 pDc->pTxDescQPool = 0xc7232ad8 pDc->pRxHostDescQPool = 0xc02b5000 pDc->RxHostDescQPoolPhyAddr = 0x 2b5000 pDc->pRxBufferPool = 0xc0060000 pDc->RxBufferPoolPhyAddr = 0x 60000 setting regulatory domain to 3 (0x30): ETSI (Europe) (1-13) setting regulatory domain to 3 (0x30): ETSI (Europe) (1-13) SSID = STA1882BC, len = 9 Beacon length:61 SSID = STA1882BC, len = 9 SetProberTemp: cb = 61 acx100: form factor 0x01 (D-Link DWL-650+/Planet WL-8305?), radio type 0x0d (Maxim), EEPROM version 0x0000. Uploaded firmware 'Rev 1.9.3.e' (0x01020505). This is further information that turns up in /var/log/messages after I make all iwconfig settings: SSID = STA1882BC, len = 9 Beacon length:61 SSID = STA1882BC, len = 9 SetProberTemp: cb = 61 SSID = familia, len = 7 Beacon length:59 SSID = familia, len = 7 SetProberTemp: cb = 59 Warning: WEP support might not be supported in Ad-Hoc mode yet! Warning: WEP support might not be supported in Ad-Hoc mode yet! Then I do 'ifconfig wlan0 192.168.0.23': firmware version >= 1.9.3.e --> using software timer <AcxSetStatus> iStatus = 0 (STARTED) Set transmit power = 1 Setting antenna value: 0x8F Setting ED threshold value: 0x70 Setting CCA value: 0x0D Setting regulatory domain to 0x30 setting regulatory domain to 3 (0x30): ETSI (Europe) (1-13) Changing to channel 6 <AcxSetStatus> iStatus = 1 (SCANNING) <acx_timer> iStatus = 1 and the machine hangs. When I eject the card, I sometimes get an oops, sometimes the machine recovers. I cannot really reproduce it reliably. On my last try after a few seconds I get the following output Rx packet 00 (MGMT/Beacon): time 236115156, len 64, signal 99, SNR 0, mode 2, iStatus 1 ProcessProbeResponse: found and registered station 0: ESSID "familia" on channel 6, BSSID 00 90 4B 2E D0 A5 (Access Point, 11Mbps), SIR 99, SNR 0. Rx packet 01 (MGMT/Beacon): time 237446525, len 64, signal 96, SNR 64, mode 2, iStatus 1 Rx packet 02 (MGMT/Beacon): time 237549066, len 64, signal 88, SNR 0, mode 2, iStatus 1 Rx packet 03 (MGMT/Beacon): time 237651447, len 64, signal 89, SNR 0, mode 2, iStatus 1 Rx packet 04 (MGMT/Beacon): time 237754068, len 64, signal 104, SNR 0, mode 2, iStatus 1 Rx packet 05 (MGMT/Beacon): time 237856369, len 64, signal 107, SNR 0, mode 2, iStatus 1 Rx packet 06 (MGMT/Beacon): time 237958791, len 64, signal 106, SNR 0, mode 2, iStatus 1 Rx packet 07 (MGMT/Beacon): time 238060812, len 64, signal 107, SNR 0, mode 2, iStatus 1 Rx packet 08 (MGMT/Beacon): time 238163553, len 64, signal 108, SNR 0, mode 2, iStatus 1 Rx packet 09 (MGMT/Beacon): time 238266074, len 64, signal 105, SNR 0, mode 2, iStatus 1 Rx packet 10 (MGMT/Beacon): time 238368135, len 64, signal 107, SNR 0, mode 2, iStatus 1 Rx packet 11 (MGMT/Beacon): time 238470413, len 64, signal 100, SNR 0, mode 2, iStatus 1 Rx packet 12 (MGMT/Beacon): time 238572816, len 64, signal 101, SNR 0, mode 2, iStatus 1 Rx packet 13 (MGMT/Beacon): time 238675458, len 64, signal 98, SNR 0, mode 2, iStatus 1 Rx packet 14 (MGMT/Beacon): time 238777939, len 64, signal 97, SNR 0, mode 2, iStatus 1 Rx packet 15 (MGMT/Beacon): time 238880080, len 64, signal 95, SNR 0, mode 2, iStatus 1 Rx packet 16 (MGMT/Beacon): time 238982821, len 64, signal 94, SNR 0, mode 2, iStatus 1 Rx packet 17 (MGMT/Beacon): time 239084942, len 64, signal 90, SNR 0, mode 2, iStatus 1 Rx packet 18 (MGMT/Beacon): time 239187703, len 64, signal 91, SNR 0, mode 2, iStatus 1 Rx packet 19 (MGMT/Beacon): time 239289644, len 64, signal 91, SNR 0, mode 2, iStatus 1 Rx packet 20 (MGMT/Beacon): time 239392125, len 64, signal 89, SNR 0, mode 2, iStatus 1 Rx packet 21 (MGMT/Beacon): time 239494507, len 64, signal 94, SNR 0, mode 2, iStatus 1 Rx packet 22 (MGMT/Beacon): time 239597228, len 64, signal 100, SNR 0, mode 2, iStatus 1 Rx packet 23 (MGMT/Beacon): time 239699509, len 64, signal 108, SNR 0, mode 2, iStatus 1 Rx packet 24 (MGMT/Beacon): time 239802110, len 64, signal 105, SNR 0, mode 2, iStatus 1 Rx packet 25 (MGMT/Beacon): time 239904331, len 64, signal 100, SNR 0, mode 2, iStatus 1 Rx packet 26 (MGMT/Beacon): time 240006552, len 64, signal 103, SNR 0, mode 2, iStatus 1 Rx packet 27 (MGMT/Beacon): time 240108913, len 64, signal 106, SNR 0, mode 2, iStatus 1 Rx packet 28 (MGMT/Beacon): time 240211715, len 64, signal 111, SNR 0, mode 2, iStatus 1 Rx packet 29 (MGMT/Beacon): time 240313876, len 64, signal 114, SNR 0, mode 2, iStatus 1 Rx packet 30 (MGMT/Beacon): time 240416064, len 64, signal 110, SNR 0, mode 2, iStatus 1 Rx packet 31 (MGMT/Beacon): time 240518626, len 64, signal 76, SNR 0, mode 2, iStatus 1 Rx packet 00 (MGMT/Beacon): time 275540281, len 64, signal 89, SNR 0, mode 2, iStatus 1 Rx packet 01 (MGMT/Beacon): time 275642982, len 64, signal 94, SNR 0, mode 2, iStatus 1 Rx packet 02 (MGMT/Beacon): time 275744991, len 64, signal 90, SNR 0, mode 2, iStatus 1 Rx packet 03 (MGMT/Beacon): time 275847432, len 64, signal 88, SNR 0, mode 2, iStatus 1 Radio scan found 1 stations in this area. <Scan Table> 0: SSID="familia",CH=6,SIR=99,SNR=0 peer_cap 0x01, needed_cap 0x01 ESSID matches: "familia" (station), "familia" (config) matching station found!! d11CompleteScan: matching station FOUND (idx 0), JOINING (00 90 4B 2E D0 A5). <acx100_join_bssid> BSS_Type = 2 <acx100_join_bssid> JoinBSSID MAC:00 90 4B 2E D0 A5 Sending authentication1 request, awaiting response! Tx packet (MGMT/Authen): len 30, hdr_len 24, pyld_len 6, mode 2, iStatus 1 <AcxSetStatus> iStatus = 2 (WAIT_AUTH) Rx packet 04 (MGMT/Beacon): time 275950273, len 64, signal 92, SNR 0, mode 2, iStatus 2 Rx packet 05 (CTL/Ack): time 275959688, len 14, signal 94, SNR 0, mode 2, iStatus 2 Rx packet 06 (MGMT/Authen): time 275960159, len 34, signal 93, SNR 0, mode 2, iStatus 2 process_authen: UNVERIFIED. 00.80.C8.18.82.BC<4>00.80.C8.18.82.BC<4><sta_list_add> sta = 00:90:4B:2E:D0:A5 process_authen auth seq step 2. <AcxSetStatus> iStatus = 3 (AUTHENTICATED) Sending association request, awaiting response! NOT ASSOCIATED YET. association: requesting capabilities 0x0001 Tx packet (MGMT/AssocReq): len 44, hdr_len 24, pyld_len 20, mode 2, iStatus 3 Rx packet 07 (MGMT/Beacon): time 276052563, len 64, signal 94, SNR 0, mode 2, iStatus 3 Rx packet 08 (CTL/Ack): time 276094152, len 14, signal 92, SNR 0, mode 2, iStatus 3 Rx packet 09 (MGMT/AssocResp): time 276095144, len 40, signal 96, SNR 0, mode 2, iStatus 3 <AcxSetStatus> iStatus = 4 (ASSOCIATED) wake queue after association. ASSOCIATED! Rx packet 10 (MGMT/Beacon): time 276154872, len 64, signal 88, SNR 0, mode 2, iStatus 4 <acx_timer> iStatus = 4 and then the machine hangs again until I eject the card. I'm stuck at this point, I've run through all the steps many times and read all the docs. Any clues what else I could try, test, patch, whatever? When I remove the card manually I sometimes get a kernel oops and my system freezes hard, only magic sysrq still works, sometimes, sometimes not. Are you guys interested in me decoding the oops? Thanks in advance Diego |