From: Matthew Richards (matt_at_richardsfamily.net)
Date: 2002-02-28 07:31:19 UTC
Thanks for the help.. I've done that and now seem to have AP mode running
(the Win2k WL100 says its connected to the AP with 100% strength).. but I've
run into another similar error message..
Feb 28 18:22:21 shakesbeare kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS
failed (res=-110)
Feb 28 18:22:21 shakesbeare kernel: wlan0: hfa384x_cmd - timeout -
reg=0x8002
Feb 28 18:22:21 shakesbeare kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS
failed (res=-110)
Feb 28 18:22:21 shakesbeare kernel: wlan0: hfa384x_cmd - timeout -
reg=0x8002
Feb 28 18:22:21 shakesbeare kernel: wlan0: hfa384x_cmd - timeout -
reg=0x8002
Feb 28 18:22:21 shakesbeare kernel: wlan0: hfa384x_get_rid: CMDCODE_ACCESS
failed (res=-110)
Feb 28 18:22:35 shakesbeare kernel: wlan0: hfa384x_cmd - timeout -
reg=0x8000
Feb 28 18:22:35 shakesbeare kernel: wlan0: hfa384x_set_rid:
CMDCODE_ACCESS_WRITE failed (res=-110)
Feb 28 18:22:35 shakesbeare kernel: prism2: wlan0: resetting card
and when I try to ping the other end.. it says:
ping: sendto: Operation not permitted
Any ideas?
Matt.
-----Original Message-----
From: Kurthy Lorant [mailto:lorant_at_real-net.sk]
Sent: Wednesday, 27 February 2002 9:33 PM
To: Matthew Richards
Subject: Re: Trouble with Compaq WL200
Hi!
Try to modify the HFA384X_BAP_BUSY_TIMEOUT to 5000 in the prism2.c file.
Lorant.
> Hi all,
>
> I'm trying to get my RH 7.2 gateway box to work as an AP using a WL200
> to a
> Win2k/WL100 laptop.. I did get the 2 to link up in Ad-Hoc mode, but I
> couldnt get any traffic between them. One thing that might be a
> problem..
> they both had their firemware flashed to 0.8.0 - would that be a
> problem?
>
> Any help would be greatly appreciated.
>
> Thanks,
> Matt
>
> Feb 27 20:48:51 shakesbeare kernel: Linux PCMCIA Card Services 3.1.31
> Feb 27 20:48:51 shakesbeare kernel: kernel build: 2.4.18 #4 Tue Feb
> 26
> 21:58:37 EST 2002
> Feb 27 20:48:51 shakesbeare kernel: options: [pci] [cardbus]
> Feb 27 20:48:51 shakesbeare kernel: Intel ISA/PCI/CardBus PCIC probe:
> Feb 27 20:48:51 shakesbeare kernel: PCI: Found IRQ 11 for device
> 00:0d.0
> Feb 27 20:48:51 shakesbeare kernel: PCI: Sharing IRQ 11 with 00:07.2
> Feb 27 20:48:51 shakesbeare kernel: Cirrus PD6729 rev 00 PCI-to-PCMCIA
> at
> slot 00:0d, port 0x9800
> Feb 27 20:48:51 shakesbeare kernel: host opts [0]: [ring] [pci irq
> 11]
> [1/5/0] [1/20/0]
> Feb 27 20:48:51 shakesbeare kernel: host opts [1]: [ring] [pci irq
> 11]
> [1/5/0] [1/20/0]
> Feb 27 20:48:51 shakesbeare kernel: PCI card interrupts, PCI
> status
> changes
> Feb 27 20:48:51 shakesbeare cardmgr[5060]: starting, version is 3.1.31
> Feb 27 20:48:51 shakesbeare cardmgr[5060]: watching 2 sockets
> Feb 27 20:48:51 shakesbeare kernel: cs: memory probe
> 0x0d0000-0x0dffff:
> clean.
> Feb 27 20:48:51 shakesbeare cardmgr[5060]: socket 0: Compaq WL200
> Feb 27 20:48:51 shakesbeare cardmgr[5060]: executing: 'modprobe
> prism2'
> Feb 27 20:48:51 shakesbeare cardmgr[5060]: + modprobe: Can't locate
> module
> prism2
> Feb 27 20:48:51 shakesbeare cardmgr[5060]: modprobe exited with status
> 255
> Feb 27 20:48:51 shakesbeare cardmgr[5060]: executing: 'insmod
> /lib/modules/2.4.18/pcmcia/prism2.o'
> Feb 27 20:48:51 shakesbeare kernel: prism2: prism2.c 0.0.0 2002-02-13
> (SSH
> Communications Security Corp, Jouni Malinen)
> Feb 27 20:48:51 shakesbeare kernel: prism2: (c) SSH Communications
> Security
> Corp <jkm_at_ssh.com>
> Feb 27 20:48:51 shakesbeare kernel: Config has no IRQ info, but trying
> to
> enable IRQ anyway..
> Feb 27 20:48:51 shakesbeare kernel: cs: IO port probe 0x0100-0x04ff:
> excluding 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7
> Feb 27 20:48:52 shakesbeare kernel: cs: IO port probe 0x0380-0x03bf:
> clean.
> Feb 27 20:48:52 shakesbeare kernel: cs: IO port probe 0x03e0-0x04cf:
> clean.
> Feb 27 20:48:52 shakesbeare kernel: cs: IO port probe 0x04d8-0x04ff:
> clean.
> Feb 27 20:48:52 shakesbeare kernel: cs: IO port probe 0x0a00-0x0aff:
> clean.
> Feb 27 20:48:52 shakesbeare kernel: cs: IO port probe 0x0c00-0x0cff:
> clean.
> Feb 27 20:48:52 shakesbeare kernel: prism2: index 0x01: Vcc 3.3, irq 11,
> io
> 0x0100-0x013f
> Feb 27 20:48:52 shakesbeare kernel: prism2: Registered netdevice wlan0
> Feb 27 20:48:52 shakesbeare kernel: wlan0: NIC: id=0x8002 v1.0.1
> Feb 27 20:48:52 shakesbeare kernel: wlan0: PRI: id=0x15 v0.3.0
> Feb 27 20:48:52 shakesbeare kernel: wlan0: STA: id=0x1f v0.8.0
> Feb 27 20:48:52 shakesbeare cardmgr[5060]: executing: './network start
> wlan0'
> Feb 27 20:48:52 shakesbeare cardmgr[5060]: + /usr/local/sbin/iwconfig
> wlan0
> essid "matt"
> Feb 27 20:48:52 shakesbeare kernel: wlan0: hfa384x_setup_bap -
> timeout3
> Feb 27 20:48:52 shakesbeare kernel: wlan0: hfa384x_set_rid - to BAP0
> failed
> Feb 27 20:48:52 shakesbeare kernel: prism2: wlan0: resetting card
> Feb 27 20:48:52 shakesbeare cardmgr[5060]: + Error for wireless request
> "Set
> ESSID" (8B1A) :
> Feb 27 20:48:52 shakesbeare kernel: wlan0: TXRateControl setting to 15
> failed
> Feb 27 20:48:52 shakesbeare kernel: wlan0: hfa384x_setup_bap -
> timeout3
> Feb 27 20:48:52 shakesbeare kernel: wlan0: hfa384x_set_rid - to BAP0
> failed
> Feb 27 20:48:52 shakesbeare kernel: prism2: wlan0: resetting card
> Feb 27 20:48:52 shakesbeare cardmgr[5060]: + SET failed on device
> wlan0
> ; Invalid argument.
>
> # iwconfig wlan0
> Warning : Device wlan0 has been compiled with version 12
> of Wireless Extension, while we are using version 11.
> Some things may be broken...
>
> wlan0 IEEE 802.11-DS ESSID:"matt"
> Mode:Managed Frequency:2.412GHz Access Point:
> 44:44:44:44:44:44
> Bit Rate:2Mb/s Tx-Power:10 dBm Sensitivity=1/3
> Retry min limit:8 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 invalid crypt:0 invalid misc:0
>
>