From: pat-lkml <pat...@er...> - 2005-10-17 05:40:48
|
I have successfully used master mode to associate and ping in the following setup(s): Master: acx111 wg311v2 on amd64 Clients: Madwifi/atheros in laptop minipci whatever wireless is in my axim x50v acx111 wg311v2 on x86 I did not turn routing on because I havn't figured out how to mac filter. Wep WAS working for some of the tests, but I stopped trying as the test client was my axim and writing in hex keys was painful at best. Pat Erley Denis Vlasenko wrote: >On Sunday 16 October 2005 23:15, Howard Young wrote: > > >>>Yes, but I also will happily take patches which fix compilation >>>along the lines of: >>> >>>#if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, n) >>>acx_e_suspend(struct pci_dev *pdev, pm_message_t state) >>>#else >>>acx_e_suspend(struct pci_dev *pdev, int state) >>>#endif >>> >>>-- >>>vda >>> >>> >>> >>[snip] >> >>So i did what you suggested above. Does this have any impact on power >>saving? >> >> > >Dunno. Andreas says that powersaving in acx is buggy - oopsable on resume. > > > >>After downloading a recent file acx-20051016.tar.bz2. I moved the the kernel >>directory deleted the src files from 57 (well moved them some place else) >>then tar -xvjf'd the file to the directory. >> >>I tested compiling it with the "make SUBDIRS=drivers/net/wireless" from the >>linux symlink. >>It compiled, but there was no acx_pci.ko so i compiled the entire kernel >>again using. >> >> > >It's acx.ko now. > > > >>make-kpkg clean >>fakeroot make-kpkg --append_to_version -hiy --initrd --revision=rev.03 >>kernel_image modules_image >> >>To recap i am 2.8.6 stable on this system. >> >>I then restarted the computer and it booted up without anything i noticed as >>out of the ordinary (i am talking about mistakes on my part there) . >> >>I have been using the system for a while doing some of the below and as the >>log has filled with messages I am now typing modprobe -r acx for which dmesg >>shows (probably you don't need to see this as it looks alright?): >>closed device >>switching off power LED to save power :-) >>removing device wlan0 >>removing /proc entry driver/acx_wlan0 >>removing /proc entry driver/acx_wlan0_diag >>removing /proc entry driver/acx_wlan0_eeprom >>removing /proc entry driver/acx_wlan0_phy >>usbcore: deregistering driver acx_usb >> >>typing modprobe acx presents: >> >>acx: this driver is still EXPERIMENTAL >>acx: reading README file and/or Craig's HOWTO is recommended, visit >>http://acx100.sf.net in case of further questions/discussion >>acx: compiled to use 32bit I/O access. I/O timing issues might occur, such >>as non-working firmware upload. Report them >>running on a little-endian CPU >>PCI module v0.3.13 initialized, waiting for cards to probe... >>ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 16 (level, low) -> IRQ 169 >>acx: found ACX100-based wireless network card at 0000:00:0c.0, irq:169, >>phymem1:0xDFFFE000, phymem2:0xDFFE0000, mem1:0xe0cd5000, mem1_size:4096, >>mem2:0xe0e6e000, mem2_size:65536 >>initial debug setting is 0x000A >>using IRQ 169 >>requesting firmware image 'tiacx100c11' >>acx: firmware image 'tiacx100c11' was not provided. Check your hotplug >>scripts >>requesting firmware image 'tiacx100' >>acx_write_fw (main/combined):0 >>acx_validate_fw (main/combined):0 >>requesting firmware image 'tiacx100r11' >>acx_write_fw (radio): 0 >>acx_validate_fw (radio): 0 >>acx100_s_init_wep: writing WEP options >>get_mask 0x00004D82, set_mask 0x00000000 >>got sensitivity value 187 >>got antenna value 0x8F >>got Energy Detect (ED) threshold 112 >>got Channel Clear Assessment (CCA) value 13 >>got regulatory domain 0x30 >>get_mask 0x00000000, set_mask 0x00000000 - after update >>new ratevector: 82 84 0B 16 2C >>setting RXconfig to 2010:0FDD >>acx: form factor 0x00 (unspecified), radio type 0x11 (RFMD), EEPROM version >>0x04, uploaded firmware 'Rev 1.9.8.b' (0x01020505) >>creating /proc entry driver/acx_wlan0 >>creating /proc entry driver/acx_wlan0_diag >>creating /proc entry driver/acx_wlan0_eeprom >>creating /proc entry driver/acx_wlan0_phy >>acx v0.3.13: net device wlan0, driver compiled against wireless extensions >>16 and Linux 2.6.8-hiy >>USB module v0.3.13 initialized, probing for devices... >>usbcore: registered new driver acx_usb >> >>I try connecting it to the ground floor WEP 128 access point using this in >>the interfaces file: >>auto wlan0 >>iface wlan0 inet static >>address 192.168.123.61 >>netmask 255.255.255.0 >>broadcast 192.168.123.255 >>gateway 192.168.123.60 >>wireless-channel 6 >>wireless-essid ... >>wireless-mode managed >>wireless-key ... >>#wireless-power 15 >>wireless-txpower 12 >> >>I then ifdown eth0 (the normal connector for this computer) so that i have >>no confusing situations with route. >>After this i type ping 192.168.123.60 (the access point) and it works just >>fine. >> >>I then ifdown wlan0 and try changing the interfaces file so that it is >>instead set to: >>wireless-key off >>wireless-rate 1M >>wireless-channel 8 >>wireless-essid FOL >>wireless-mode master >>wireless-txpower 5 >> >>I go to the second floor (nearest client) and detach it from its current >>wlan access point. It can see the FOL AP i have just created but it cannot >>connect. >> >>I need to know what information i should present to start searching for ways >>to get this working? >> >> > >Master mode was not tested extensively. > > > >>Would you like >>Ethereal data? >>kern.log acx output? >>syslog output? >> >> > >I need full log (see README) where I can see how client atempts to join acx's AP. > > > >>The new ones which i randomly selected as appearing most likely (is this a >>bad idea?) are: >> >>24a54fd30f7658fcbffc825b0dd7aa5b /usr/lib/hotplug/firmware/tiacx100 >>1c7413e7b0be4ef7d1e424a132e17fab /usr/lib/hotplug/firmware/tiacx100r0D >>a150750ad33c512edc4afee5270b37cb /usr/lib/hotplug/firmware/tiacx100r11 >>c99d01d4fcf0d6cc00441aff60690be4 /usr/lib/hotplug/firmware/tiacx100r15 >> >> > >Firmware is ok. > > > >>Hope this is useful, it is what appears in my kern.log when i type ifup >>wlan0 with the interfaces file configured for FOL (the AP mode as shown >>above). >> >>Oct 16 21:49:06 S-A kernel: acx: master mode (HostAP) is very, very >>experimental! It might work partially, but better get prepared for nasty >>surprises at any time >> >> > >Please turn off linewrapping in your mail client. > > > >>Oct 16 21:49:06 S-A kernel: new priv->mode=3 >>Oct 16 21:49:06 S-A kernel: new ratevector: 82 >>Oct 16 21:49:06 S-A kernel: module count++ >>Oct 16 21:49:06 S-A kernel: acx_set_status(4):ASSOCIATED >>Oct 16 21:49:06 S-A kernel: updating initial settings on iface activation... >>Oct 16 21:49:06 S-A kernel: get_mask 0x00000000, set_mask 0x0037EEFC >>Oct 16 21:49:06 S-A kernel: important setting has been changed. Need to >>update packet templates, too >>Oct 16 21:49:06 S-A kernel: updating packet templates >>Oct 16 21:49:06 S-A kernel: acx_s_cmd_join_bssid rates_basic 0001->01, >>rates_supported 0001->01 >>Oct 16 21:49:06 S-A kernel: BSS_Type = 3 >>Oct 16 21:49:06 S-A kernel: JoinBSSID MAC:00:00:00:00:00:00 >>Oct 16 21:49:06 S-A kernel: updating Tx fallback to 0 retries >>Oct 16 21:49:06 S-A kernel: updating transmit power: 5 dBm >>Oct 16 21:49:06 S-A kernel: wlan0: changing radio power level to 5 dBm (2) >>Oct 16 21:49:06 S-A kernel: updating antenna value: 0x8F >>Oct 16 21:49:06 S-A kernel: updating Energy Detect (ED) threshold: 112 >>Oct 16 21:49:06 S-A kernel: updating Channel Clear Assessment (CCA) value: >>0x0D >>Oct 16 21:49:06 S-A kernel: updating channel to: 8 >>Oct 16 21:49:06 S-A kernel: updating: enable Tx >>Oct 16 21:49:06 S-A kernel: updating: enable Rx on channel: 8 >>Oct 16 21:49:06 S-A kernel: updating short retry limit: 7, long retry limit: >>4 >>Oct 16 21:49:06 S-A kernel: updating tx MSDU lifetime: 4096 >>Oct 16 21:49:06 S-A kernel: updating regulatory domain: 0x30 >>Oct 16 21:49:06 S-A kernel: acx_set_status(4):ASSOCIATED >>Oct 16 21:49:06 S-A kernel: acx_s_cmd_join_bssid rates_basic 0001->01, >>rates_supported 0001->01 >>Oct 16 21:49:06 S-A kernel: BSS_Type = 3 >>Oct 16 21:49:06 S-A kernel: JoinBSSID MAC:00:80:C8:B1:88:8B >>Oct 16 21:49:06 S-A kernel: setting RXconfig to 2010:0FDD >>Oct 16 21:49:06 S-A kernel: updating WEP key settings >>Oct 16 21:49:06 S-A kernel: setting WEP key 0 as default >>Oct 16 21:49:06 S-A kernel: get_mask 0x00000000, set_mask 0x00000000 - after >>update >>Oct 16 21:49:06 S-A kernel: get_mask 0x00000000, set_mask 0x00000040 >>Oct 16 21:49:06 S-A kernel: setting RXconfig to 2010:0FDD >>Oct 16 21:49:06 S-A kernel: get_mask 0x00000000, set_mask 0x00000000 - after >>update >>Oct 16 21:49:17 S-A kernel: wlan0: no IPv6 routers present >> >>I go upstairs and try to associate with FOL, then as it does not work switch >>back to its normal connection. >> >>Oct 16 21:52:34 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:52:34 S-A kernel: algorithm is ok >>Oct 16 21:52:34 S-A kernel: sta_list_add: sta=00:0E:3B:01:6E:32 >>Oct 16 21:52:34 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:52:34 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:52:35 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:52:35 S-A kernel: algorithm is ok >>Oct 16 21:52:35 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:52:35 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:52:41 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:52:41 S-A kernel: algorithm is ok >>Oct 16 21:52:41 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:52:41 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:52:41 S-A kernel: wlan0: tx error 0x20, buf 14! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 21:52:41 S-A kernel: wlan0: tx error 0x20, buf 15! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 21:52:41 S-A kernel: wlan0: tx error 0x20, buf 00! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >> >> > >These are strange. acx says that it wasn't able to hear ACK >from the station. A wireless capture on a third box (or third wireless >card inserted in AP or STA) would be interesting to see - >will shot whether acx really sends beacons and responses, >and whether STA sends ACKs or not). > >If you can't do that, you may try joining from less distant machine >(say, machine from the same room) and try to get more detailed log >than above one. > > > >>Oct 16 21:52:41 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:52:41 S-A kernel: algorithm is ok >>Oct 16 21:52:41 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:52:41 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:52:50 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:52:50 S-A kernel: algorithm is ok >>Oct 16 21:52:50 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:52:50 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:52:51 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:52:51 S-A kernel: algorithm is ok >>Oct 16 21:52:51 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:52:51 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:52:57 S-A kernel: wlan0: several excessive Tx retry errors >>occurred, attempting to recalibrate radio. Radio drift might be caused by >>increasing card temperature, please check the card before it's too late! >>Oct 16 21:52:57 S-A kernel: wlan0: tx error 0x20, buf 01! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 21:52:57 S-A kernel: wlan0: tx error 0x20, buf 02! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 21:52:57 S-A kernel: wlan0: tx error 0x20, buf 03! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 21:52:57 S-A kernel: wlan0: successfully recalibrated radio >>Oct 16 21:53:01 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:53:01 S-A kernel: algorithm is ok >>Oct 16 21:53:01 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:53:01 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:53:01 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 21:53:01 S-A kernel: algorithm is ok >>Oct 16 21:53:01 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 21:53:01 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 21:53:52 S-A kernel: wlan0: tx error 0x20, buf 05! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 21:53:52 S-A kernel: wlan0: several excessive Tx retry errors >>occurred, attempting to recalibrate radio. Radio drift might be caused by >>increasing card temperature, please check the card before it's too late! >>Oct 16 21:53:52 S-A kernel: wlan0: tx error 0x20, buf 06! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 21:53:52 S-A kernel: wlan0: less than 5 minutes since last radio >>recalibration, not recalibrating (maybe card is too hot?) >> >> > > > >>The last few lines appeared slightly later, but now seeing them I will try >>at a higher txpower. I do not know what would be good adjustments for the >>other two and am not sure what a safe high is for txpower. >>It is worth noting that the reading on the client upstairs showed the >>quality of link to be above 44 percent (which is higher than its usual >>connection's quality). >> >> > >I do not recommend fiddling with this. Problem is somewhere else. > > > >>So I now ifdown wlan0 and the kern.log shows: >> >>Oct 16 22:05:58 S-A kernel: get_mask 0x00000000, set_mask 0x00000040 >>Oct 16 22:05:58 S-A kernel: setting RXconfig to 2010:0FDD >>Oct 16 22:05:58 S-A kernel: get_mask 0x00000000, set_mask 0x00000000 - after >>update >>Oct 16 22:05:58 S-A kernel: acx_set_status(0):STOPPED >>Oct 16 22:05:58 S-A kernel: module count-- >>Oct 16 22:05:58 S-A kernel: closed device >> >>I update the interfaces file to use: >> >>txpower 18 >> >>The kern.log shows (sorry this is getting verbose): >> >>Oct 16 22:07:28 S-A kernel: acx: master mode (HostAP) is very, very >>experimental! It might work partially, but better get prepared for nasty >>surprises at any time >>Oct 16 22:07:28 S-A kernel: new priv->mode=3 >>Oct 16 22:07:28 S-A kernel: new ratevector: 82 >>Oct 16 22:07:28 S-A kernel: module count++ >>Oct 16 22:07:28 S-A kernel: acx_set_status(4):ASSOCIATED >>Oct 16 22:07:28 S-A kernel: updating initial settings on iface activation... >>Oct 16 22:07:28 S-A kernel: get_mask 0x00000000, set_mask 0x0027CEBC >>Oct 16 22:07:28 S-A kernel: important setting has been changed. Need to >>update packet templates, too >>Oct 16 22:07:28 S-A kernel: updating packet templates >>Oct 16 22:07:28 S-A kernel: acx_s_cmd_join_bssid rates_basic 0001->01, >>rates_supported 0001->01 >>Oct 16 22:07:29 S-A kernel: BSS_Type = 3 >>Oct 16 22:07:29 S-A kernel: JoinBSSID MAC:00:80:C8:B1:88:8B >>Oct 16 22:07:29 S-A kernel: updating Tx fallback to 0 retries >>Oct 16 22:07:29 S-A kernel: updating transmit power: 18 dBm >>Oct 16 22:07:29 S-A kernel: wlan0: changing radio power level to 18 dBm (41) >>Oct 16 22:07:29 S-A kernel: updating antenna value: 0x8F >>Oct 16 22:07:29 S-A kernel: updating Energy Detect (ED) threshold: 112 >>Oct 16 22:07:29 S-A kernel: updating Channel Clear Assessment (CCA) value: >>0x0D >>Oct 16 22:07:29 S-A kernel: updating channel to: 8 >>Oct 16 22:07:29 S-A kernel: updating: enable Tx >>Oct 16 22:07:29 S-A kernel: updating: enable Rx on channel: 8 >>Oct 16 22:07:29 S-A kernel: updating regulatory domain: 0x30 >>Oct 16 22:07:29 S-A kernel: acx_set_status(4):ASSOCIATED >>Oct 16 22:07:29 S-A kernel: acx_s_cmd_join_bssid rates_basic 0001->01, >>rates_supported 0001->01 >>Oct 16 22:07:29 S-A kernel: BSS_Type = 3 >>Oct 16 22:07:29 S-A kernel: JoinBSSID MAC:00:80:C8:B1:88:8B >>Oct 16 22:07:29 S-A kernel: updating WEP key settings >>Oct 16 22:07:29 S-A kernel: setting WEP key 0 as default >>Oct 16 22:07:29 S-A kernel: get_mask 0x00000000, set_mask 0x00000000 - after >>update >>Oct 16 22:07:29 S-A kernel: get_mask 0x00000000, set_mask 0x00000040 >>Oct 16 22:07:29 S-A kernel: setting RXconfig to 2010:0FDD >>Oct 16 22:07:29 S-A kernel: get_mask 0x00000000, set_mask 0x00000000 - after >>update >>Oct 16 22:07:39 S-A kernel: wlan0: no IPv6 routers present >> >>I go to the client and try to associate it then when it does not work as >>before return it to its normal network. Here is the information in the >>kern.log >> >>Oct 16 22:09:18 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 22:09:18 S-A kernel: algorithm is ok >>Oct 16 22:09:18 S-A kernel: sta_list_add: sta=00:0E:3B:01:6E:32 >>Oct 16 22:09:18 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 22:09:18 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 22:09:18 S-A kernel: wlan0: tx error 0x20, buf 01! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 22:09:18 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 22:09:18 S-A kernel: algorithm is ok >>Oct 16 22:09:18 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 22:09:18 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 22:09:19 S-A kernel: wlan0: tx error 0x20, buf 02! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 22:09:24 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 22:09:24 S-A kernel: algorithm is ok >>Oct 16 22:09:24 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 22:09:24 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 22:09:24 S-A kernel: wlan0: tx error 0x20, buf 02! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 22:09:24 S-A kernel: AUTHEN priv->addr=00:80:C8:B1:88:8B >>a1=00:80:C8:B1:88:8B a2=00:0E:3B:01:6E:32 a3=00:80:C8:B1:88:8B >>priv->bssid=00:80:C8:B1:88:8B >>Oct 16 22:09:24 S-A kernel: algorithm is ok >>Oct 16 22:09:24 S-A kernel: acx_process_authen auth seq step 1 >>Oct 16 22:09:24 S-A kernel: transmit_auth2: BSSID=00:80:C8:B1:88:8B >>Oct 16 22:11:16 S-A kernel: wlan0: several excessive Tx retry errors >>occurred, attempting to recalibrate radio. Radio drift might be caused by >>increasing card temperature, please check the card before it's too late! >>Oct 16 22:11:16 S-A kernel: wlan0: tx error 0x20, buf 03! (excessive Tx >>retries due to either distance too high or unable to Tx or Tx >>frame error - try changing 'iwconfig txpower XXX' or 'sens'itivity or >>'retry') >>Oct 16 22:11:16 S-A kernel: wlan0: successfully recalibrated radio >> >>And that is it. >>No doubt i should experiment with the settings and read peoples posts to see >>what is thought to work best I will see if i can find anything on lunch >>breaks. >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: >Power Architecture Resource Center: Free content, downloads, discussions, >and more. http://solutions.newsforge.com/ibmarch.tmpl >_______________________________________________ >Acx100-devel mailing list >Acx...@li... >https://lists.sourceforge.net/lists/listinfo/acx100-devel > > |