airo-linux-general — General questions/comment about using the airo linux driver.

RE: [Airo-linux-general] Promisc mode doesn't work

[Ben C. <BCr...@An...>]

Johnny,
This driver will not report that it is in promisc mode thru the /proc
sub-system.  if you do an ifconfig -a you'll see that once the card is =
in
promisc mode the MAC changes to a really long string.  You can't miss =
it.
One thing to be aware of is that if you suspend the machine, when it =
wakes
back up the card will be back in ESS mode.  enjoy and hope that helps!

-Ben

-----Original Message-----
From: Johnny Choque [mailto:jc...@tl...]
Sent: Monday, July 22, 2002 7:55 AM
To: air...@li...
Subject: [Airo-linux-general] Promisc mode doesn't work


Hi all,

Following the Kevin's suggests of his last e-mail I put
the variation of the airo-linux driver of Airtraf software within
pcmcia-cs-3.1.34/wireless directory and did the makes. After that,
I tried to use the promisc mode in several way :

echo "Mode: rfmon" > /proc/driver/aironet/eth1/Config
echo "Mode: r" > /proc/driver/aironet/eth1/Config
echo "Mode: y" > /proc/driver/aironet/eth1/Config
echo 'Mode: rfmon' > /proc/driver/aironet/eth1/Config
echo 'Mode: r' > /proc/driver/aironet/eth1/Config
echo 'Mode: y' > /proc/driver/aironet/eth1/Config

but the /proc/driver/aironet/eth1/Config file don=B4t change and
the Mode parameter always is ESS. Only accept the "ad-hoc" or "ESS" =
values.

Someone have any idea about this problem?

Thanks in advance.

Johnny



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Airo-linux-general mailing list
Air...@li...
https://lists.sourceforge.net/lists/listinfo/airo-linux-general

Re: [Airo-linux-general] Promisc mode doesn't work

[Nick D. <ni...@me...>]

On Mon, Jul 22, 2002 at 01:55:23PM +0200, Johnny Choque wrote:

<snip>

> echo "Mode: rfmon" > /proc/driver/aironet/eth1/Config
> echo "Mode: r" > /proc/driver/aironet/eth1/Config
> echo "Mode: y" > /proc/driver/aironet/eth1/Config
> echo 'Mode: rfmon' > /proc/driver/aironet/eth1/Config
> echo 'Mode: r' > /proc/driver/aironet/eth1/Config
> echo 'Mode: y' > /proc/driver/aironet/eth1/Config
>=20
> but the /proc/driver/aironet/eth1/Config file don=B4t change and
> the Mode parameter always is ESS. Only accept the "ad-hoc" or "ESS" value=
s.

Apologies if this is out of step, I haven't played with my wireless card for
ages, but have you tried picking up traffic regardless of the mode that
/proc tells you the card is in.  IIRC you may find yourself able to pick up
traffic anyway.

--=20
plumped disaffection saltiest being=20

[Airo-linux-general] Promisc mode doesn't work

[Johnny C. <jc...@tl...>]

Hi all,

Following the Kevin's suggests of his last e-mail I put
the variation of the airo-linux driver of Airtraf software within
pcmcia-cs-3.1.34/wireless directory and did the makes. After that,
I tried to use the promisc mode in several way :

echo "Mode: rfmon" > /proc/driver/aironet/eth1/Config
echo "Mode: r" > /proc/driver/aironet/eth1/Config
echo "Mode: y" > /proc/driver/aironet/eth1/Config
echo 'Mode: rfmon' > /proc/driver/aironet/eth1/Config
echo 'Mode: r' > /proc/driver/aironet/eth1/Config
echo 'Mode: y' > /proc/driver/aironet/eth1/Config

but the /proc/driver/aironet/eth1/Config file don=B4t change and
the Mode parameter always is ESS. Only accept the "ad-hoc" or "ESS" value=
s.

Someone have any idea about this problem?

Thanks in advance.

Johnny

[Airo-linux-general] RE: Aironet 340 and Redhat 7.3 woes

[Ben C. <BCr...@An...>]

Howdy All!
I was able to compile the modified airtraf (from Peter Lee) driver and it
all works.  Is there going to be a fix for the CVS to allow it to compile
against the newer kernels?  I'm interested in the wifi0 interface.  Thanks!

-Ben

>  -----Original Message-----
> From: 	Ben Cranston  
> Sent:	Thursday, June 27, 2002 3:56 PM
> To:	'air...@li...'
> Subject:	Aironet 340 and Redhat 7.3 woes
> 
> Hello All!
> 
> I'm working with the following:
> Stock Redhat 7.3 on HP omnibook laptop (Kernel 2.4.18-3)
> airo.c driver version 1.5.2 2001/01/22 
> aironet 340 card 
> aironet firmware 4.25.30 
> 
> I cannot get the card to go into promisc mode.  I've tried the echo 'Mode:
> r' command to the Config file, but it still will not go into rfmon mode.
> The best I can get is after I've assoicated to an AP I can then see
> broadcast and my traffic.  Not good ehough if you're trying to audit
> someone. anyway.  
> 
> At this point I believe that the stock driver just won't go into promisc
> mode.  So I went the cvs path and grabbed the latest airo-linux code from
> sourceforge.  I've copied over the airo.c and airo_cs.c code into the
> kernel tree and did the makes.  I get all the way to make bzImage and then
> die in a flurry of "invalid type argument of '->'" errors near line 7635.
> ugh.. So I cannot compile the latest version.  Does anyone have any
> pointers on how to get this going, or how to get the 1.5.2 version to
> actually bump into promisc mode?  I'm really at a loss. Thanks in advance!
> 
> -Ben

Re: [Airo-linux-general] Aironet 340 and Redhat 7.3 woes

[Kevin <lei...@ne...>]

Hi,

I just went through a lot of this on Mandrake 8.2 with 2.4.18 and later 
kernels, I have the 350 card, I'll tell you what I know.  

My experience was, when compiling w/o kernel pcmcia, and using pcmcia-cs 
instead (which is supposed to work per readme)  the airo-linux driver 
appears not to compile correctly on the current stable kernel 2.4.18,
and the project maintainer hasn't communicated if he intends to resolve 
this.

I tried on 3 different systems and 2 distributions, serveral versions of 
pcmcia-cs, same problems throughout.

Anyway, it appears that promisc mode is only available once the wifi 
interface was introduced.

You'll notice on the CVS that the wifi interface wasn't introduced in 
airo.c until CVS rev 1.35

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/airo-linux/airo-linux/kernel/airo.c

When I try to compile CVS rev 1.35-1.37 it will compile, but depmod 
complains of unresloved symbols, and promisc mode doesn't work if I 
actually use the driver.

When I try to compile airo.c CVS rev 1.38-1.41 I get errors complaining 
about the EXPORT_SYMBOL( ) macros introduced in 1.38+.

The good news is I discovered a gentleman who's made a variation of the 
airo-linux driver for his Airtraf software.  Promisc mode DOES work for 
me using that driver, though it does
complain of unresolved symbols from depmod, the driver works fine for me.

http://prdownloads.sourceforge.net/airtraf/airo-linux-mod-airtraf.tar.gz

I've read in some places that one has to listen on wifi0 once the card 
is in promisc mode.  I don't know if that's true with other variations 
of the driver but for me using airtraf I have listen on eth1 (eth0 being
my land line) , wifi0 doesn't seem to work.

Post back if you discover anything more on this if you would, this list 
isn't real active it's hard to dig up info on these. I think they're 
great cards, I hope the support base grows.  
I'm hoping we see a way to put these in AP mode at some point as well.

A couple links that may be useful though some info is out of date
http://www.goonda.org/wireless/aironet/
http://www.cs.umd.edu/~npetroni/airo.html

hope that helps.

Kevin


BCr...@An... wrote:

>Hello All!
>
>I'm working with the following:
>Stock Redhat 7.3 on HP omnibook laptop (Kernel 2.4.18-3)
>airo.c driver version 1.5.2 2001/01/22 
>aironet 340 card 
>aironet firmware 4.25.30 
>
>I cannot get the card to go into promisc mode.  I've tried the echo 'Mode:
>r' command to the Config file, but it still will not go into rfmon mode.
>The best I can get is after I've assoicated to an AP I can then see
>broadcast and my traffic.  Not good ehough if you're trying to audit
>someone. anyway.  
>
>At this point I believe that the stock driver just won't go into promisc
>mode.  So I went the cvs path and grabbed the latest airo-linux code from
>sourceforge.  I've copied over the airo.c and airo_cs.c code into the kernel
>tree and did the makes.  I get all the way to make bzImage and then die in a
>flurry of "invalid type argument of '->'" errors near line 7635.  ugh.. So I
>cannot compile the latest version.  Does anyone have any pointers on how to
>get this going, or how to get the 1.5.2 version to actually bump into
>promisc mode?  I'm really at a loss. Thanks in advance!
>
>-Ben
>
>
>-------------------------------------------------------
>Sponsored by:
>ThinkGeek at http://www.ThinkGeek.com/
>_______________________________________________
>Airo-linux-general mailing list
>Air...@li...
>https://lists.sourceforge.net/lists/listinfo/airo-linux-general
>

[Airo-linux-general] Aironet 340 and Redhat 7.3 woes

[Ben C. <BCr...@An...>]

Hello All!

I'm working with the following:
Stock Redhat 7.3 on HP omnibook laptop (Kernel 2.4.18-3)
airo.c driver version 1.5.2 2001/01/22 
aironet 340 card 
aironet firmware 4.25.30 

I cannot get the card to go into promisc mode.  I've tried the echo 'Mode:
r' command to the Config file, but it still will not go into rfmon mode.
The best I can get is after I've assoicated to an AP I can then see
broadcast and my traffic.  Not good ehough if you're trying to audit
someone. anyway.  

At this point I believe that the stock driver just won't go into promisc
mode.  So I went the cvs path and grabbed the latest airo-linux code from
sourceforge.  I've copied over the airo.c and airo_cs.c code into the kernel
tree and did the makes.  I get all the way to make bzImage and then die in a
flurry of "invalid type argument of '->'" errors near line 7635.  ugh.. So I
cannot compile the latest version.  Does anyone have any pointers on how to
get this going, or how to get the 1.5.2 version to actually bump into
promisc mode?  I'm really at a loss. Thanks in advance!

-Ben

[Airo-linux-general] Re: [Airo-linux-gen80211] error 'this_object_must_be_defined_as_export_objs_in_the_Makefile'

[Kevin <lei...@ne...>]

In case anyone else has this problem, I just solved it duh.    I added 
-DEXPORT_SYMTAB to CFLAGS in the Makefile residing in the /wireless dir 
containing airo* files.

CFLAGS = -O3 -Wall -Wstrict-prototypes -pipe -DEXPORT_SYMTAB

regards


lei...@ne... wrote:

> Hello,
>
> I just pulled the latest airo-linux module off cvs, copied airo* to 
> pcmcia-cs-3.1.33/wireless/
>
> did a make config and then make all and I get the error listed above 
> (full text at bottom). grep shows that the error it's complaining 
> about is in:
>
> /usr/src/linux/include/linux/module.h:#define 
> __EXPORT_SYMBOL(sym,str)   error 
> this_object_must_be_defined_as_export_objs_in_the_Makefile
>
> Previously I had no problem compiling the cicso airo* and the native 
> pcmcia-cs airo* drivers.  I'm using Kernel 2.4.18-6  with latest  
> pcmcia-cs-3.1.33.  In current kernel and .config pcmcia is disabled as 
> is the kernel supplied airo driver.
>
> Any suggestions appreciated I'm stuck on how to fix this error.  I 
> think i sent this to the wrong list last time, sorry if anyone got a 
> dupe on this.
> thank you and best regards,
> Kevin
>
> cc   -MD -O3 -Wall -Wstrict-prototypes -pipe -I../include 
> -I/usr/src/linux/include  -D__KERNEL__ -DMODULE -c airo_cs.c
> In file included from airo_cs.c:34:
> /usr/src/linux/include/linux/malloc.h:4:2: warning: #warning 
> linux/malloc.h is deprecated, use linux/slab.h instead.
> cc   -MD -O3 -Wall -Wstrict-prototypes -pipe -I../include 
> -I/usr/src/linux/include  -D__KERNEL__ -DMODULE -c airo.c
> airo.c:1456: parse error before 
> `this_object_must_be_defined_as_export_objs_in_the_Makefile'
> airo.c:1456: warning: type defaults to `int' in declaration of 
> `this_object_must_be_defined_as_export_objs_in_the_Makefile'
> airo.c:1456: warning: data definition has no type or storage class
> airo.c:1626: parse error before 
> `this_object_must_be_defined_as_export_objs_in_the_Makefile'
> airo.c:1626: warning: type defaults to `int' in declaration of 
> `this_object_must_be_defined_as_export_objs_in_the_Makefile'
> airo.c:1626: warning: data definition has no type or storage class
> airo.c:1671: parse error before 
> `this_object_must_be_defined_as_export_objs_in_the_Makefile'
> airo.c:1671: warning: type defaults to `int' in declaration of 
> `this_object_must_be_defined_as_export_objs_in_the_Makefile'
> airo.c:1671: warning: data definition has no type or storage class
> airo.c: In function `airo_interrupt':
> airo.c:1821: warning: `buffer' might be used uninitialized in this 
> function
> make[1]: *** [airo.o] Error 1
> make[1]: Leaving directory `/home/anh/pcmcia-cs-3.1.33/wireless'
> make: *** [all] Error 2
>
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> Airo-linux-general mailing list
> Air...@li...
> https://lists.sourceforge.net/lists/listinfo/airo-linux-general
>
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> Airo-linux-gen80211 mailing list
> Air...@li...
> https://lists.sourceforge.net/lists/listinfo/airo-linux-gen80211

[Airo-linux-general] compile error 'this_object_must_be_defined_as_export_objs_in_the_Makefile'

[Kevin <lei...@ne...>]

Hello,

I just pulled the latest airo-linux module off cvs, copied airo* to 
 pcmcia-cs-3.1.33/wireless/

did a make config and then make all and I get the error listed above 
(full text at bottom). grep shows that the error it's complaining about 
is in:

/usr/src/linux/include/linux/module.h:#define __EXPORT_SYMBOL(sym,str)   
error this_object_must_be_defined_as_export_objs_in_the_Makefile

Previously I had no problem compiling the cicso airo* and the native 
pcmcia-cs airo* drivers.  I'm using Kernel 2.4.18-6  with latest  
pcmcia-cs-3.1.33.  In current kernel and .config pcmcia is disabled as 
is the kernel supplied airo driver.

Any suggestions appreciated I'm stuck on how to fix this error.

thanks!

cc   -MD -O3 -Wall -Wstrict-prototypes -pipe -I../include 
-I/usr/src/linux/include  -D__KERNEL__ -DMODULE -c airo_cs.c
In file included from airo_cs.c:34:
/usr/src/linux/include/linux/malloc.h:4:2: warning: #warning 
linux/malloc.h is deprecated, use linux/slab.h instead.
cc   -MD -O3 -Wall -Wstrict-prototypes -pipe -I../include 
-I/usr/src/linux/include  -D__KERNEL__ -DMODULE -c airo.c
airo.c:1456: parse error before 
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
airo.c:1456: warning: type defaults to `int' in declaration of 
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
airo.c:1456: warning: data definition has no type or storage class
airo.c:1626: parse error before 
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
airo.c:1626: warning: type defaults to `int' in declaration of 
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
airo.c:1626: warning: data definition has no type or storage class
airo.c:1671: parse error before 
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
airo.c:1671: warning: type defaults to `int' in declaration of 
`this_object_must_be_defined_as_export_objs_in_the_Makefile'
airo.c:1671: warning: data definition has no type or storage class
airo.c: In function `airo_interrupt':
airo.c:1821: warning: `buffer' might be used uninitialized in this function
make[1]: *** [airo.o] Error 1
make[1]: Leaving directory `/home/anh/pcmcia-cs-3.1.33/wireless'
make: *** [all] Error 2

[Airo-linux-general] firmware checksum error - unable to recover

[<pcg( Marc)@goof(A.).(L. )com>]

[lists.sf.net seems to be down right now, so I couldn't subscribe to the
list. Please send me a CC of any replies, thanks a lot!]

Hi!

After starting to flash a new firmware using ACU, my machine immediately
froze. Now the card gives me a "firmware checksum error" (2 second pause,
3 blinks), and the linux driver says "can't enable MAC".

The cisco docs say that one should re-flash the firmware in that case,
however, since the driver doesn't load properly under linux, I can't start
acu.

Under windows, the symptoms are the same: the driver detects the card,
installs itself but acu says "no radio found".

I then downloaded the dos utilities (as recommended by previous posts) and
tried:

   pflashv~1 -bisa -p2000 fw.img
 
This outputs a single "3" every two seconds, but otherwise doesn't do
anything (other values of -p give me "no card found", under windows 98,
the card is registered to ports 0x2000-0x203f).

Is there a way to resurrect this card? The bootblock seems to be ok
(differnet blink code?), so...

Thanks a lot in advance.

-- 
      -----==-                                             |
      ----==-- _                                           |
      ---==---(_)__  __ ____  __       Marc Lehmann      +--
      --==---/ / _ \/ // /\ \/ /       pc...@go...      |e|
      -=====/_/_//_/\_,_/ /_/\_\       XX11-RIPE         --+
    The choice of a GNU generation                       |
                                                         |

[Airo-linux-general] State of wifi device development?

[Haebler, M. (Marcus) <ha...@lu...>]

I installed the latest airo-linux CVS today and 
saw the new wifi device. Is that device supposed 
to work? I could not capture any packet in tcpdump 
or ethereal with this device. 

In general, is my understanding correct that the 
wifi device is supposed to implement rfmon mode 
while eth0 is up and running "normally"? 

Thanks, 

Marcus  

[Airo-linux-general] Aironet 350 and Ipaq on Familiar

[darren <teo...@ya...>]

Hi all,

I just got a Ipaq and installed Linux onto it (Familiar 2.4.18).

I have installed the Aironet modules but cannot seem to get the Cisco
card started: "Unrecognized Card in slot 1" - it says.

Any one managed to get the cisco 350 working on Ipaq + Linux?

Please advise
Darren


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[Airo-linux-general] why alloc_etherdev for wireless LAN card ?

[rakesh u. <rak...@bl...>]

Hello All,

I was just going through the source code of airo.c and was wondering for
usage of "alloc_etherdev". It is supposed to initialize the parameters for
the default ethernet card, here we want to initialize the parameters
specific to 802.11.

also I came across one macro ARPHRD_IEEE80211, we need to setup the device
type to this type, which we are not doing any where, but we are checking the
device type while receiving the packet, so who will set this device type ??

probably my questions are too primary or very basic, but I have just started
reading on wireless LAN drivers so I need to clear it before proceeding.

Regards
Rakesh

[Airo-linux-general] temporarily loading different drivers

[Nick D. <ni...@me...>]

Hi,

I currently use the airo drivers that come with the kernel, however I'd like
to temporary load the "official" Cisco drivers so I can upgrade the firmware
on my Cisco 340.

However I'm unsure how to do this, and really don't want to break anything,
does anyone have any suggestions or URLs to help me achieve this?

-- 
crocks 

[Airo-linux-general] help with /proc output

[Nick D. <ni...@me...>]

Hi,

From various sources I've learnt that I should try echoing "adhoc", "rfmon",
"ess", "y" and "i" to /proc/driver/aironet/ethN/Config.  However I only ever
see "Mode: ESS" or "Mode: adhoc".  Where can I find out which modes my Cisco
340 supports?

Also I'd like to understand what the contents of the "Status: " and "Mode: "
lines mean, I've tried reading the documentation and, with almost no
knowledge of c, the source code, but I can't see anything revealing.

Can anyone point me at a URL, or something I've missed?

-- 
notifier graced blurs 

Re: [Airo-linux-general] problem with Aironet 4800 PCMCIA on Strongarm

[Robert K. J. <joh...@ll...>]

ADS just sent me a zImage and ramdisk.gz which they used to successfully
exercise a Cisco 340 PCMCIA card.  They provided console output
demonstrating a successful load and use with ping.  However, using this
same zImage and ramdisk.gz on my system results in the same errors
and kernel oops that I obtained previously.  I was under the impression that
the Cisco 340 and the Aironet PC4800 were essentially the same cards,
but there must be a difference.  Please let me know if anyone has any
suggestions of what to try.  Also, please let me know if anyone is aware
of a successful use of the Aironet PC4800 PCMCIA card on a Strongarm
based system.

At 11:26 AM 3/27/2002 -0800, you wrote:
>I am having trouble getting an Aironet 4800 PCMCIA card working with
>an Applied Data Systems (ADS) Graphics Client Plus Strongarm embedded
>system.  ADS claims to have successfully tested the Cisco 340 card which
>I thought was essentially the same as the Aironet 4800.  The latest patched
>Linux kernel available for this board is 2.4.9-ac10-rmk2-np1-ads3.  When I 
>tried
>a kernel using standard sources and everything compiled into the kernel,
>I got a kernel OOPS shown below as run through ksymoops on another
>system.  When I tried replacing the kernel airo.c and airo_cs.c (also adding
>airo.h) from the CVS repo (airo.c version 1.36), the system went off looking
>for modules even though it was still compiled into the kernel.  I then 
>compiled
>with the CVS code as modules (airo.o and airo_cs.o), and I obtained the
>following error messages when plugging the card in:
>
>Jan  1 00:50:30 Linux daemon.info cardmgr[112]: socket 0: Aironet PC4800
>Jan  1 00:50:30 Linux daemon.info cardmgr[112]: executing: 'insmod 
>/lib/modules/
>2.4.9-ac10-rmk2-np1-ads3/pcmcia/airo.o'
>Jan  1 00:50:31 Linux daemon.info cardmgr[112]: executing: 'insmod 
>/lib/modules/
>2.4.9-ac10-rmk2-np1-ads3/pcmcia/airo_cs.o'
>Jan  1 00:50:32 Linux kern.err airo: Max tries exceeded waiting for command
><3>airo: MAC could not be enabled
><5>airo_cs: RequestConfiguration: Operation succeeded
>Jan  1 00:50:33 Linux daemon.info cardmgr[112]: get dev info on socket 0 
>failed:
>  Resource temporarily unavailable
>Jan  1 00:50:33 Linux daemon.info cardmgr[112]: wrong module 'airo_cs' for 
>devic
>e 'airo_cs'?
>
>I was thinking of trying the external PCMCIA card services, but I am not 
>sure whether
>it will support the Strongarm and this device in particular.  Any 
>information and/or
>suggestions would be greatly appreciated.
>
>Here is the output from ksymoops for the first configuration:
>
>ksymoops 2.4.0 on i686 2.4.4.  Options used
>      -V (specified)
>      -K (specified)
>      -L (specified)
>      -O (specified)
>      -m ./System.map (specified)
>      -a arm
>
>Unable to handle kernel NULL pointer dereference at virtual address 00000000
>*pgd = 00000000, *pmd = 00000000
>Internal error: Oops: 0
>CPU: 0
>pc : [<00000000>]    lr : [<c01019d4>]
>Using defaults from ksymoops -t elf32-i386
>sp : c8b47664  ip : 0000001f  fp : c8b476c4
>r10: c8b4773c  r9 : c0bb8c00  r8 : 0000004c
>Warning (Oops_set_i370_regs): garbage 'r9 : c0bb8c00  r8 : 0000004c' at 
>end of i370 register line ignored
>r7 : 00000000  r6 : 24000000  r5 : c0bb8d40  r4 : 00000000
>r3 : 00000000  r2 : 00000004  r1 : c8b47696  r0 : c0bb8d40
>Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  Segment user
>Control: C8B4317F  Table: C8B4317F  DAC: 00000015
>Process cardmgr (pid: 112, stackpage=c8b47000)
>c8b47640:                                               c01019d4 00000000 
>600000
>c8b47660: ffffffff 00000004 c8b47694 c8b476ac  c01aeb04 00000000 60000093 
>000001
>c8b47680: 00001515 00000000 00000000 00000000  c0037c20 c8b476ac c0251f8c 
>c8bc83
>c8b476a0: 00000037 24000000 c01bc9d8 c01bc2f8  c01cab80 c8b4773c c8b476f0 
>c8b476
>c8b476c0: c001e0e8 c0101808 00000006 00000040  c8b4773c c01bc2f8 c01bc2f8 
>c01cab
>c8b476e0: c8b4773c c8b4770c c8b476f4 c0025b74  c001e034 c01adb70 00000000 
>200000
>c8b47700: c8b47738 c8b47710 c001e0e8 c0025b3c  fa050000 c8b47784 00000001 
>c001e3
>c8b47720: 60000013 ffffffff c0bb8c00 c8b477ac  c8b4773c c001d4c0 c001e034 
>000000
>c8b47740: f0080008 00000001 000000d0 c8bc83e0  00000000 00000037 c01017fc 
>240000
>c8b47760: c0bb8c00 c0bb8c00 c8b477ac c8b47764  c8b47784 c001e258 c001e314 
>600000
>c8b47780: ffffffff c0bb8c00 f6000000 c0bb8d40  00000037 00000001 d1b71759 
>c8b47b
>c8b477a0: c8b477e0 c8b477b0 c0101460 c001e274  c0bb8c00 c8b477e0 c8b477c4 
>c00f81
>c8b477c0: c8b479bc 00000000 c0270d60 0000002b  c0270a60 c8b47b78 c8b477e4 
>c01004
>c8b477e0: c010137c c00331d4 c8b477f8 c024eda0  c8b477fc c002f354 00010005 
>000003
>c8b47800: 00000009 0007a120 00000000 00000000  005b8d80 c003b11c c8b47b5c 
>000000
>c8b47820: 00000001 0007a120 0000004e 00000001  c0271800 c8b47a38 c8b47a08 
>c00f06
>c8b47840: c00f0400 c8b47a10 00000000 0000ffff  c8b47b5c c0270a60 c0270a60 
>000000
>c8b47860: 00000000 00000000 00000000 c8b47a3c  00000000 c00f05c0 c8b40146 
>000000
>c8b47880: 00000040 00000000 c8b47b94 c8b47a5c  c00f1d30 c00f032c c8b47a68 
>c00efb
>c8b478a0: c00ef9e0 c0271800 c0271800 00000002  c0271b6a 0000000c 0000004e 
>c8b47a
>c8b478c0: c8b47ac0 c8b47a94 c00f01c8 c016d14c  c8b47acc c8b47c6c 0000004e 
>000000
>c8b478e0: c8b47c6c 0000004e 00000001 c0271800  c8b47af4 c8b47ac4 c00f067c 
>000000
>c8b47900: 0000ffff 00000000 0000ffff c8b47af8  c0270660 c8b47cbc 00000001 
>000000
>c8b47920: 00000001 c8b47cb4 c8b47af8 c00f1eec  c00f05c0 0007015f 0000012c 
>c8b47b
>c8b47940: c8b47b10 c0119450 c014570c 0000012b  00006677 c01ac0d0 00000001 
>c01cab
>c8b47960: fffffffa c01ac0c0 c01cab00 c00f01c8  c016d14c c8b479bc 00000004 
>091a01
>c8b47980: 55016655 ffff3046 00000000 c8b47c6c  00000001 c8b479b8 c8b479a4 
>c8b479
>c8b479a0: c8b479ac c00f1c8c c00f0e30 c8b47af4  c0271800 00000002 c0271b6a 
>000100
>c8b479c0: 00000301 00000009 0007a120 00000000  00000000 005b8d80 c003b11c 
>c8b47b
>c8b479e0: 0000004e 00000001 0007a120 0000004e  00000001 c0271800 c8b47a38 
>c8b47a
>c8b47a00: c00f067c c00f0400 c8b47a10 00000000  0000ffff c8b47b5c c0270a60 
>c0270a
>c8b47a20: 00000000 00000000 00000000 00000000  c8b47a3c 00000000 c00f05c0 
>c8b401
>c8b47a40: 00000000 00000040 00000000 c8b47b94  c8b47a5c c00f1d30 c00f032c 
>c8b47a
>c8b47a60: c00efb44 c00ef9e0 c0271800 c0271800  00000002 c0271b6a 0000000c 
>000000
>c8b47a80: c8b47acc c8b47ac0 c8b47a94 c00f01c8  c016d14c c8b47acc c8b47c6c 
>000000
>c8b47aa0: 00000001 c8b47c6c 0000004e 00000001  c0271800 c8b47af4 c8b47ac4 
>c00f06
>c8b47ac0: 00000030 0000ffff 00000000 0000ffff  c8b47af8 c0270660 c8b47cbc 
>000000
>c8b47ae0: 00000000 00000001 c8b47cb4 c8b47af8  c00f1eec c00f05c0 0007015f 
>000001
>c8b47b00: c8b47b40 c8b47b10 c0119450 c014570c  0000012b 00006677 c01ac0d0 
>000000
>c8b47b20: c01cab80 fffffffa c01ac0c0 c01cab00  00000000 c8b47b1b 00000100 
>000000
>c8b47b40: 00000042 40000c1b 0000000c c8b4797c  c0270d60 c024eda0 c0270a9c 
>000000
>c8b47b60: c0270d8c c01fd73c 00000000 c8b47b94  c8b47b7c c0100738 c01000d0 
>c02718
>c8b47b80: c0270a60 c0270a9c c8b47c08 c8b47b98  c00f6c04 c0100678 cb84e000 
>000000
>c8b47ba0: 00000000 cb84e000 c8b47c00 c8b47bb8  c0024148 c003b11c 000000a3 
>0004f0
>c8b47bc0: 27fb2000 cb84f000 c00072e4 00000000  00000000 5c7b2000 28000000 
>000010
>c8b47be0: c0270d8c c0270d60 00000000 c0270d8c  c8b47c2c c01b7f9c c01b7fbc 
>c8b47c
>c8b47c00: c8b47c0c c00f8114 c00f69b0 c0270d60  00000000 c0270d8c c024eda0 
>c8b47c
>c8b47c20: c8b47c2c c00fff94 c00f7ec4 c01b7f9c  00000012 0000660c c010066c 
>c8b47c
>c8b47c40: c00f8600 c00f91c0 00000000 c8b47c88  c0270d60 00000000 00000210 
>c8bc83
>c8b47c60: c024e6e0 c8b47cbc 00000000 00000000  02024fc8 c8076440 c8b47cb4 
>c8b47c
>c8b47c80: c00f3ed4 c00ffe64 c0000000 c024e6e0  c050643c c8076440 00000000 
>000000
>c8b47ca0: 00000000 00000050 c8b47f78 c8b47cb8  c00f4b54 c00f3d38 80000000 
>6f7269
>c8b47cc0: 0073635f 00000000 00000000 00000000  00000000 00000000 00000000 
>000000
>c8b47ce0: 00000000 00000000 00000000 00000000  00000000 00000000 00000000 
>000000
>c8b47d00: 00000000 00000000 00000000 bffffa54  bffffa54 bffffa54 bffffa54 
>c8b47d
>c8b47d20: 00000000 00000001 c8b15540 00000400  00000001 00000000 c8b47dc8 
>000004
>c8b47d40: c8e3dea0 c0ae1b00 c8e3dea0 20000013  c01ace64 c01ad0a4 00000000 
>000000
>c8b47d60: c0af2458 c0af2458 c01ad0a0 c8b47da8  c8b47d7c c004726c c0046e3c 
>000000
>c8b47d80: c01ace64 c01ace64 00000000 000000d2  c0af2458 c0af2458 00000000 
>c8b47d
>c8b47da0: 00000025 c8b47e0c 00000000 00000000  ffffffff c8b47ea0 c8b47dc4 
>c016f8
>c8b47dc0: c016d14c 00000002 00000000 00000000  00000000 c8b47e0c 00000000 
>000000
>c8b47de0: ffffffff 33323130 37363534 42413938  46454443 4a494847 4e4d4c4b 
>525150
>c8b47e00: 56555453 5a595857 c0014600 33323130  37363534 62613938 66656463 
>6a6968
>c8b47e20: 6e6d6c6b 7271706f 76757473 7a797877  c0af2400 c8b47e30 c0014620 
>c8b460
>c8b47e40: ffffffff 40016000 ffffffff ffffffff  c00157a0 c8b47e88 c8b47e64 
>c0022e
>c8b47e60: c003af8c c00157bc c8b46000 c8b47ee4  c00157a0 40016000 00000000 
>000000
>c8b47e80: 00000000 00000000 00000000 ffffffff  c8af7072 c8b47ef4 c8b47ea4 
>c01702
>c8b47ea0: c016f83c c020703c 60000013 c023446c  c0234454 00000000 00001000 
>c0af24
>c8b47ec0: c8b41004 00000001 c8b47ee4 c8b47ed8  c0047564 c0046ab4 c8b47efc 
>c8b47e
>c8b47ee0: c0047d98 c0047518 c0234454 c0aa60bf  c8b47f50 c8b47f00 c0039828 
>c0047c
>c8b47f00: 40116000 c8b41004 40116000 c8b46000  00000001 c0014620 00000001 
>400160
>c8b47f20: c8b47f50 c8b47f30 c003c08c c00438a8  40016000 c0014620 40016000 
>400160
>c8b47f40: 00000000 c8b47f8c c8b47f54 c003c554  00000003 c050643c 02011438 
>ffffff
>c8b47f60: c001d9a4 c8bf9f20 02024fc8 c8b47fac  c8b47f7c c005cd58 c00f45bc 
>400160
>c8b47f80: c8b47fac 00000002 02024fc8 02011438  00000036 c001d9a4 c8b46000 
>0201dc
>c8b47fa0: 00000000 c8b47fb0 c001d820 c005ca60  00000002 c0027224 00000003 
>c05064
>c8b47fc0: 02024fc8 02011438 00000002 02024fc8  02011438 00000003 00000000 
>0201dc
>c8b47fe0: 0201dc28 bffffc14 0201134c bffffbe4  02002dac 400b54c4 a0000010 
>000000
>Backtrace:
>Function entered at [<c01017fc>] from [<c001e0e8>]
>Function entered at [<c001e028>] from [<c0025b74>]
>Function entered at [<c0025b30>] from [<c001e0e8>]
>  r6 = 20000000  r5 = 00000000  r4 = C01ADB70
>Function entered at [<c001e028>] from [<c001d4c0>]
>Function entered at [<c001e268>] from [<c0101460>]
>Function entered at [<c0101370>] from [<c0100470>]
>  r8 = C0270A60  r7 = 0000002B  r6 = C0270D60  r5 = 00000000
>  r4 = C8B479BC
>Function entered at [<c01000c4>] from [<c0100738>]
>Function entered at [<c010066c>] from [<c00f6c04>]
>  r6 = C0270A9C  r5 = C0270A60  r4 = C0271800
>Function entered at [<c00f69a4>] from [<c00f8114>]
>Function entered at [<c00f7eb8>] from [<c00fff94>]
>  r4 = C024EDA0
>Function entered at [<c00ffe58>] from [<c00f3ed4>]
>Function entered at [<c00f3d2c>] from [<c00f4b54>]
>Function entered at [<c00f45b0>] from [<c005cd58>]
>Function entered at [<c005ca54>] from [<c001d820>]
>Code: bad PC value.
>Kernel panic: Aiee, killing interrupt handler!
>Warning (Oops_read): Code line not seen, dumping what data is available
>
> >>EIP; 00000000 Before first symbol
> >>r10; c8b4773c <END_OF_CODE+89430ac/????>
>Trace; c01017fc <airo_interrupt+0/7e8>
>Trace; c001e0e8 <do_IRQ+c0/164>
>Trace; c001e028 <do_IRQ+0/164>
>Trace; c0025b74 <ADS_IRQ_demux+44/74>
>Trace; c0025b30 <ADS_IRQ_demux+0/74>
>Trace; c001e0e8 <do_IRQ+c0/164>
>Trace; c001e028 <do_IRQ+0/164>
>Trace; c001d4c0 <__irq_svc+20/a0>
>Trace; c001e268 <request_irq+0/c8>
>Trace; c0101460 <init_airo_card+f0/268>
>Trace; c0101370 <init_airo_card+0/268>
>Trace; c0100470 <airo_config+3ac/510>
>Trace; c01000c4 <airo_config+0/510>
>Trace; c0100738 <airo_event+cc/1ec>
>Trace; c010066c <airo_event+0/1ec>
>Trace; c00f6c04 <pcmcia_register_client+260/284>
>Trace; c00f69a4 <pcmcia_register_client+0/284>
>Trace; c00f8114 <CardServices+25c/3a0>
>Trace; c00f7eb8 <CardServices+0/3a0>
>Trace; c00fff94 <airo_attach+13c/188>
>Trace; c00ffe58 <airo_attach+0/188>
>Trace; c00f3ed4 <bind_request+1a8/1e4>
>Trace; c00f3d2c <bind_request+0/1e4>
>Trace; c00f4b54 <ds_ioctl+5a4/7f0>
>Trace; c00f45b0 <ds_ioctl+0/7f0>
>Trace; c005cd58 <sys_ioctl+304/318>
>Trace; c005ca54 <sys_ioctl+0/318>
>Trace; c001d820 <ret_fast_syscall+0/38>
>
>
>_______________________________________________
>Airo-linux-general mailing list
>Air...@li...
>https://lists.sourceforge.net/lists/listinfo/airo-linux-general

[Airo-linux-general] problem with Aironet 4800 PCMCIA on Strongarm

[Robert K. J. <joh...@ll...>]

I am having trouble getting an Aironet 4800 PCMCIA card working with
an Applied Data Systems (ADS) Graphics Client Plus Strongarm embedded
system.  ADS claims to have successfully tested the Cisco 340 card which
I thought was essentially the same as the Aironet 4800.  The latest patched
Linux kernel available for this board is 2.4.9-ac10-rmk2-np1-ads3.  When I 
tried
a kernel using standard sources and everything compiled into the kernel,
I got a kernel OOPS shown below as run through ksymoops on another
system.  When I tried replacing the kernel airo.c and airo_cs.c (also adding
airo.h) from the CVS repo (airo.c version 1.36), the system went off looking
for modules even though it was still compiled into the kernel.  I then compiled
with the CVS code as modules (airo.o and airo_cs.o), and I obtained the
following error messages when plugging the card in:

Jan  1 00:50:30 Linux daemon.info cardmgr[112]: socket 0: Aironet PC4800
Jan  1 00:50:30 Linux daemon.info cardmgr[112]: executing: 'insmod 
/lib/modules/
2.4.9-ac10-rmk2-np1-ads3/pcmcia/airo.o'
Jan  1 00:50:31 Linux daemon.info cardmgr[112]: executing: 'insmod 
/lib/modules/
2.4.9-ac10-rmk2-np1-ads3/pcmcia/airo_cs.o'
Jan  1 00:50:32 Linux kern.err airo: Max tries exceeded waiting for command
<3>airo: MAC could not be enabled
<5>airo_cs: RequestConfiguration: Operation succeeded
Jan  1 00:50:33 Linux daemon.info cardmgr[112]: get dev info on socket 0 
failed:
  Resource temporarily unavailable
Jan  1 00:50:33 Linux daemon.info cardmgr[112]: wrong module 'airo_cs' for 
devic
e 'airo_cs'?

I was thinking of trying the external PCMCIA card services, but I am not 
sure whether
it will support the Strongarm and this device in particular.  Any 
information and/or
suggestions would be greatly appreciated.

Here is the output from ksymoops for the first configuration:

ksymoops 2.4.0 on i686 2.4.4.  Options used
      -V (specified)
      -K (specified)
      -L (specified)
      -O (specified)
      -m ./System.map (specified)
      -a arm

Unable to handle kernel NULL pointer dereference at virtual address 00000000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 0
CPU: 0
pc : [<00000000>]    lr : [<c01019d4>]
Using defaults from ksymoops -t elf32-i386
sp : c8b47664  ip : 0000001f  fp : c8b476c4
r10: c8b4773c  r9 : c0bb8c00  r8 : 0000004c
Warning (Oops_set_i370_regs): garbage 'r9 : c0bb8c00  r8 : 0000004c' at end 
of i370 register line ignored
r7 : 00000000  r6 : 24000000  r5 : c0bb8d40  r4 : 00000000
r3 : 00000000  r2 : 00000004  r1 : c8b47696  r0 : c0bb8d40
Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  Segment user
Control: C8B4317F  Table: C8B4317F  DAC: 00000015
Process cardmgr (pid: 112, stackpage=c8b47000)
c8b47640:                                               c01019d4 00000000 
600000
c8b47660: ffffffff 00000004 c8b47694 c8b476ac  c01aeb04 00000000 60000093 
000001
c8b47680: 00001515 00000000 00000000 00000000  c0037c20 c8b476ac c0251f8c 
c8bc83
c8b476a0: 00000037 24000000 c01bc9d8 c01bc2f8  c01cab80 c8b4773c c8b476f0 
c8b476
c8b476c0: c001e0e8 c0101808 00000006 00000040  c8b4773c c01bc2f8 c01bc2f8 
c01cab
c8b476e0: c8b4773c c8b4770c c8b476f4 c0025b74  c001e034 c01adb70 00000000 
200000
c8b47700: c8b47738 c8b47710 c001e0e8 c0025b3c  fa050000 c8b47784 00000001 
c001e3
c8b47720: 60000013 ffffffff c0bb8c00 c8b477ac  c8b4773c c001d4c0 c001e034 
000000
c8b47740: f0080008 00000001 000000d0 c8bc83e0  00000000 00000037 c01017fc 
240000
c8b47760: c0bb8c00 c0bb8c00 c8b477ac c8b47764  c8b47784 c001e258 c001e314 
600000
c8b47780: ffffffff c0bb8c00 f6000000 c0bb8d40  00000037 00000001 d1b71759 
c8b47b
c8b477a0: c8b477e0 c8b477b0 c0101460 c001e274  c0bb8c00 c8b477e0 c8b477c4 
c00f81
c8b477c0: c8b479bc 00000000 c0270d60 0000002b  c0270a60 c8b47b78 c8b477e4 
c01004
c8b477e0: c010137c c00331d4 c8b477f8 c024eda0  c8b477fc c002f354 00010005 
000003
c8b47800: 00000009 0007a120 00000000 00000000  005b8d80 c003b11c c8b47b5c 
000000
c8b47820: 00000001 0007a120 0000004e 00000001  c0271800 c8b47a38 c8b47a08 
c00f06
c8b47840: c00f0400 c8b47a10 00000000 0000ffff  c8b47b5c c0270a60 c0270a60 
000000
c8b47860: 00000000 00000000 00000000 c8b47a3c  00000000 c00f05c0 c8b40146 
000000
c8b47880: 00000040 00000000 c8b47b94 c8b47a5c  c00f1d30 c00f032c c8b47a68 
c00efb
c8b478a0: c00ef9e0 c0271800 c0271800 00000002  c0271b6a 0000000c 0000004e 
c8b47a
c8b478c0: c8b47ac0 c8b47a94 c00f01c8 c016d14c  c8b47acc c8b47c6c 0000004e 
000000
c8b478e0: c8b47c6c 0000004e 00000001 c0271800  c8b47af4 c8b47ac4 c00f067c 
000000
c8b47900: 0000ffff 00000000 0000ffff c8b47af8  c0270660 c8b47cbc 00000001 
000000
c8b47920: 00000001 c8b47cb4 c8b47af8 c00f1eec  c00f05c0 0007015f 0000012c 
c8b47b
c8b47940: c8b47b10 c0119450 c014570c 0000012b  00006677 c01ac0d0 00000001 
c01cab
c8b47960: fffffffa c01ac0c0 c01cab00 c00f01c8  c016d14c c8b479bc 00000004 
091a01
c8b47980: 55016655 ffff3046 00000000 c8b47c6c  00000001 c8b479b8 c8b479a4 
c8b479
c8b479a0: c8b479ac c00f1c8c c00f0e30 c8b47af4  c0271800 00000002 c0271b6a 
000100
c8b479c0: 00000301 00000009 0007a120 00000000  00000000 005b8d80 c003b11c 
c8b47b
c8b479e0: 0000004e 00000001 0007a120 0000004e  00000001 c0271800 c8b47a38 
c8b47a
c8b47a00: c00f067c c00f0400 c8b47a10 00000000  0000ffff c8b47b5c c0270a60 
c0270a
c8b47a20: 00000000 00000000 00000000 00000000  c8b47a3c 00000000 c00f05c0 
c8b401
c8b47a40: 00000000 00000040 00000000 c8b47b94  c8b47a5c c00f1d30 c00f032c 
c8b47a
c8b47a60: c00efb44 c00ef9e0 c0271800 c0271800  00000002 c0271b6a 0000000c 
000000
c8b47a80: c8b47acc c8b47ac0 c8b47a94 c00f01c8  c016d14c c8b47acc c8b47c6c 
000000
c8b47aa0: 00000001 c8b47c6c 0000004e 00000001  c0271800 c8b47af4 c8b47ac4 
c00f06
c8b47ac0: 00000030 0000ffff 00000000 0000ffff  c8b47af8 c0270660 c8b47cbc 
000000
c8b47ae0: 00000000 00000001 c8b47cb4 c8b47af8  c00f1eec c00f05c0 0007015f 
000001
c8b47b00: c8b47b40 c8b47b10 c0119450 c014570c  0000012b 00006677 c01ac0d0 
000000
c8b47b20: c01cab80 fffffffa c01ac0c0 c01cab00  00000000 c8b47b1b 00000100 
000000
c8b47b40: 00000042 40000c1b 0000000c c8b4797c  c0270d60 c024eda0 c0270a9c 
000000
c8b47b60: c0270d8c c01fd73c 00000000 c8b47b94  c8b47b7c c0100738 c01000d0 
c02718
c8b47b80: c0270a60 c0270a9c c8b47c08 c8b47b98  c00f6c04 c0100678 cb84e000 
000000
c8b47ba0: 00000000 cb84e000 c8b47c00 c8b47bb8  c0024148 c003b11c 000000a3 
0004f0
c8b47bc0: 27fb2000 cb84f000 c00072e4 00000000  00000000 5c7b2000 28000000 
000010
c8b47be0: c0270d8c c0270d60 00000000 c0270d8c  c8b47c2c c01b7f9c c01b7fbc 
c8b47c
c8b47c00: c8b47c0c c00f8114 c00f69b0 c0270d60  00000000 c0270d8c c024eda0 
c8b47c
c8b47c20: c8b47c2c c00fff94 c00f7ec4 c01b7f9c  00000012 0000660c c010066c 
c8b47c
c8b47c40: c00f8600 c00f91c0 00000000 c8b47c88  c0270d60 00000000 00000210 
c8bc83
c8b47c60: c024e6e0 c8b47cbc 00000000 00000000  02024fc8 c8076440 c8b47cb4 
c8b47c
c8b47c80: c00f3ed4 c00ffe64 c0000000 c024e6e0  c050643c c8076440 00000000 
000000
c8b47ca0: 00000000 00000050 c8b47f78 c8b47cb8  c00f4b54 c00f3d38 80000000 
6f7269
c8b47cc0: 0073635f 00000000 00000000 00000000  00000000 00000000 00000000 
000000
c8b47ce0: 00000000 00000000 00000000 00000000  00000000 00000000 00000000 
000000
c8b47d00: 00000000 00000000 00000000 bffffa54  bffffa54 bffffa54 bffffa54 
c8b47d
c8b47d20: 00000000 00000001 c8b15540 00000400  00000001 00000000 c8b47dc8 
000004
c8b47d40: c8e3dea0 c0ae1b00 c8e3dea0 20000013  c01ace64 c01ad0a4 00000000 
000000
c8b47d60: c0af2458 c0af2458 c01ad0a0 c8b47da8  c8b47d7c c004726c c0046e3c 
000000
c8b47d80: c01ace64 c01ace64 00000000 000000d2  c0af2458 c0af2458 00000000 
c8b47d
c8b47da0: 00000025 c8b47e0c 00000000 00000000  ffffffff c8b47ea0 c8b47dc4 
c016f8
c8b47dc0: c016d14c 00000002 00000000 00000000  00000000 c8b47e0c 00000000 
000000
c8b47de0: ffffffff 33323130 37363534 42413938  46454443 4a494847 4e4d4c4b 
525150
c8b47e00: 56555453 5a595857 c0014600 33323130  37363534 62613938 66656463 
6a6968
c8b47e20: 6e6d6c6b 7271706f 76757473 7a797877  c0af2400 c8b47e30 c0014620 
c8b460
c8b47e40: ffffffff 40016000 ffffffff ffffffff  c00157a0 c8b47e88 c8b47e64 
c0022e
c8b47e60: c003af8c c00157bc c8b46000 c8b47ee4  c00157a0 40016000 00000000 
000000
c8b47e80: 00000000 00000000 00000000 ffffffff  c8af7072 c8b47ef4 c8b47ea4 
c01702
c8b47ea0: c016f83c c020703c 60000013 c023446c  c0234454 00000000 00001000 
c0af24
c8b47ec0: c8b41004 00000001 c8b47ee4 c8b47ed8  c0047564 c0046ab4 c8b47efc 
c8b47e
c8b47ee0: c0047d98 c0047518 c0234454 c0aa60bf  c8b47f50 c8b47f00 c0039828 
c0047c
c8b47f00: 40116000 c8b41004 40116000 c8b46000  00000001 c0014620 00000001 
400160
c8b47f20: c8b47f50 c8b47f30 c003c08c c00438a8  40016000 c0014620 40016000 
400160
c8b47f40: 00000000 c8b47f8c c8b47f54 c003c554  00000003 c050643c 02011438 
ffffff
c8b47f60: c001d9a4 c8bf9f20 02024fc8 c8b47fac  c8b47f7c c005cd58 c00f45bc 
400160
c8b47f80: c8b47fac 00000002 02024fc8 02011438  00000036 c001d9a4 c8b46000 
0201dc
c8b47fa0: 00000000 c8b47fb0 c001d820 c005ca60  00000002 c0027224 00000003 
c05064
c8b47fc0: 02024fc8 02011438 00000002 02024fc8  02011438 00000003 00000000 
0201dc
c8b47fe0: 0201dc28 bffffc14 0201134c bffffbe4  02002dac 400b54c4 a0000010 
000000
Backtrace:
Function entered at [<c01017fc>] from [<c001e0e8>]
Function entered at [<c001e028>] from [<c0025b74>]
Function entered at [<c0025b30>] from [<c001e0e8>]
  r6 = 20000000  r5 = 00000000  r4 = C01ADB70
Function entered at [<c001e028>] from [<c001d4c0>]
Function entered at [<c001e268>] from [<c0101460>]
Function entered at [<c0101370>] from [<c0100470>]
  r8 = C0270A60  r7 = 0000002B  r6 = C0270D60  r5 = 00000000
  r4 = C8B479BC
Function entered at [<c01000c4>] from [<c0100738>]
Function entered at [<c010066c>] from [<c00f6c04>]
  r6 = C0270A9C  r5 = C0270A60  r4 = C0271800
Function entered at [<c00f69a4>] from [<c00f8114>]
Function entered at [<c00f7eb8>] from [<c00fff94>]
  r4 = C024EDA0
Function entered at [<c00ffe58>] from [<c00f3ed4>]
Function entered at [<c00f3d2c>] from [<c00f4b54>]
Function entered at [<c00f45b0>] from [<c005cd58>]
Function entered at [<c005ca54>] from [<c001d820>]
Code: bad PC value.
Kernel panic: Aiee, killing interrupt handler!
Warning (Oops_read): Code line not seen, dumping what data is available

 >>EIP; 00000000 Before first symbol
 >>r10; c8b4773c <END_OF_CODE+89430ac/????>
Trace; c01017fc <airo_interrupt+0/7e8>
Trace; c001e0e8 <do_IRQ+c0/164>
Trace; c001e028 <do_IRQ+0/164>
Trace; c0025b74 <ADS_IRQ_demux+44/74>
Trace; c0025b30 <ADS_IRQ_demux+0/74>
Trace; c001e0e8 <do_IRQ+c0/164>
Trace; c001e028 <do_IRQ+0/164>
Trace; c001d4c0 <__irq_svc+20/a0>
Trace; c001e268 <request_irq+0/c8>
Trace; c0101460 <init_airo_card+f0/268>
Trace; c0101370 <init_airo_card+0/268>
Trace; c0100470 <airo_config+3ac/510>
Trace; c01000c4 <airo_config+0/510>
Trace; c0100738 <airo_event+cc/1ec>
Trace; c010066c <airo_event+0/1ec>
Trace; c00f6c04 <pcmcia_register_client+260/284>
Trace; c00f69a4 <pcmcia_register_client+0/284>
Trace; c00f8114 <CardServices+25c/3a0>
Trace; c00f7eb8 <CardServices+0/3a0>
Trace; c00fff94 <airo_attach+13c/188>
Trace; c00ffe58 <airo_attach+0/188>
Trace; c00f3ed4 <bind_request+1a8/1e4>
Trace; c00f3d2c <bind_request+0/1e4>
Trace; c00f4b54 <ds_ioctl+5a4/7f0>
Trace; c00f45b0 <ds_ioctl+0/7f0>
Trace; c005cd58 <sys_ioctl+304/318>
Trace; c005ca54 <sys_ioctl+0/318>
Trace; c001d820 <ret_fast_syscall+0/38>

[Airo-linux-general] WEP safe in Cisco APs??

[darren <teo...@ya...>]

Hi all,

I read that the WEP and its IVs generated by a Cisco setup is safe from
Airsnort and WEPCrack.

Are there any utilities currently that can compromise the Cisco APs?

Otherwise, are they totally safe to use?

Darren


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[Airo-linux-general] Re: More descriptive Mode: in Config

[Cory S. <co...@st...>]

    Do these modes correspond at all with modes of network cards like 
promiscuous mode etc.?  Just curious.  I think snort might be causing 
problems with my card.  Didn't know if I just can't run snort on a box 
with a wireless card, or if I needed to switch the mode of the card.

Thanks,
Cory

[Airo-linux-general] Re: [Aironet] Aironet in ANYBSS and AP mode?

[Peter K. L. <pk...@du...>]

darren wrote:

> Dear All,
> 
> I have asked this question before but somehow it was not posted (or did
> I miss it??)
> 
> 1) Does 'echo "Mode: y" >> /proc/driver/aironet/eth1/Config' really
> work?


Okay, I can attest to the validity of ANYBSS working.  ANYBSS mode was a 
crucial part in developing AirTraf, and when I ran AirTraf in an 
environment with multiple access points, I was able to pick up beacon 
frames of access points operating at different channels, although I 
don't quite remember whether those were of different SSID or not.  But I 
don't really think that should matter...  It would just not make sense 
why having different SSID would cause ANYBSS *not* to work, since to 
make that happen, you have to explicitly "cause" it to happen in the 
driver level (or firmware), and I don't see *any* benefit to having it 
operate that way.  So I assume that it works properly.


> 
> I have done this step and was able to go into "rfmon", but it does not
> seem to be picking up beacon frames other then those of the same SSID.
> Am I doing anything wrong here??
> 


First of all, if you are picking up beacon frames, and are able to 
extract the SSID info of the beacon frames, make sure you also pick up 
the channel info, because chances are, the access points share the same 
SSID.  Also, make sure you *Can* get the beacon frames of other access 
points, it might just well be that the signals are too weak for you to 
pick up.


> 2) Can I make a normal Aironet card work as an AP in linux?
>


Sorry I don't know anything about running aironet as an AP...

-Peter K. Lee

[Airo-linux-general] More descriptive Mode: in Config

[Benjamin R. <br...@ya...>]

I committed a small change to reflect more accurately
the mode of the card.  Before the rfmon, lanmon, and
any bss rfmon modes were reported as ESS.  So now
there
are 5 modes:
adhoc
ESS - infrastructure mode
rfmon - monitors all the 802.11 packets for the
current BSS
yna bss rfmon - monitors all 802.11 packets
lanmon - grabs all the 802.11 packets for the current
BSS

enjoy
ben

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/

[Airo-linux-general] Re: [Aironet] Aironet in ANYBSS and AP mode?

[Ken A. <ka...@pa...>]

See http://people.ssh.com/jkm/Prism2/
Ken


darren wrote:
> 
> Dear All,
> 
> I have asked this question before but somehow it was not posted (or did
> I miss it??)
> 
> 1) Does 'echo "Mode: y" >> /proc/driver/aironet/eth1/Config' really
> work?
> 
> I have done this step and was able to go into "rfmon", but it does not
> seem to be picking up beacon frames other then those of the same SSID.
> Am I doing anything wrong here??
> 
> 2) Can I make a normal Aironet card work as an AP in linux?
> 
> Any help will be great!
> Darren
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> _______________________________________________
> Aironet mailing list  -  Ai...@cs...
> http://csl.cse.ucsc.edu/mailman/listinfo/aironet

[Airo-linux-general] Aironet in ANYBSS and AP mode?

[darren <teo...@ya...>]

Dear All,

I have asked this question before but somehow it was not posted (or did
I miss it??)

1) Does 'echo "Mode: y" >> /proc/driver/aironet/eth1/Config' really
work?

I have done this step and was able to go into "rfmon", but it does not
seem to be picking up beacon frames other then those of the same SSID.
Am I doing anything wrong here??

2) Can I make a normal Aironet card work as an AP in linux?

Any help will be great!
Darren


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[Airo-linux-general] Aironet PCI 350 distance problem

[Arben A. <ar...@te...>]

Hi to all,

=20

I have been truing to deploy a wireless network in Kosovo (former
Yugoslavia =96 better known for many recent wars then technology).

=20

For this, I used PCI 352 cards on a Linux machine. The cards are put in
Ad-hoc mode and we use parabolic antennas with RP-TNC connectors to
increase the effective distance of transmission for the cards.

=20

I have placed up to four PCI cards on one Linux machine and installed
routing software (OSPF)

=20

The problem is the distance. Every time the link spreads for more than 4
=96 5 Km, the packed drops are enormous leaving only about 50-60 Kbps
available. All is working fine on short distances but the after this
limit, all hell breaks lose. The signal strength is not a problem. Both
the indicator on the Status utility of the ACU and measurements with
spectrum analyzer indicate excellent signal quality.

=20

What seems to be the problem? Is the problem in the driver or firmware?
I tried to download new firmwares but it seems like the problem is
getting worse with ever new release of firmware? Do you have any
suggestions how to alleviate this problem?=20

=20

Any comments are very highly appreciated.=20

=20

=20

=20

Arben Abdullahu

=20

Re: [Airo-linux-general] compiling problems with CVS

[Cory S. <co...@st...>]

    My mistake.  The "compiling with linux 2.4" page under docs says to 
"apply the 2.4.3 patch (should work with most versions of 2.4)".  I took 
that too literally.

Perhaps I should be more specific about my situatoin.  I purchased DTN 
Speed Net's (www.dtnspeed.net) wireless internet access.  It's currently 
my only non-dialup option.  I have a Cisco 350 PCI card for a desktop, 
50 ft. of RG8 coax cable, and a yagi style (spelling?) directional antenna.

    With a 2.4.17 kernel compile using the airo code that comes with it 
(1/01 timeframe I think), I've had the following problems:

- at best, throughput, signal strength, and signal quality are lower 
than with the same wireless hardware (different PC) on Windows XP.
- the throughput, strength and quality eventually degrades to loss of 
assoctiation with the access point all together (i.e. no connectivity). 
 This appears to only be rectified by taking the card out and re-seating 
it (perhaps powering system down for a few secons/minuts would suffice).

Next, I did as you suggested ... copied the airo source and heaers into 
the 2.4.17 source tree and recompiled.  This didn't appear to aleviate 
the above problems, and additionally introduced some kernal instability 
such as:

- hung once during boot up at time of airo card discovery
- no longer powers itself off at shutdown.  Instead makes loud beeping 
noices, and can only be stopped by disconecting the power at the wall.
- it's possible that it was the cause of a mysterious system reboot, but 
I can't confirm that it wasn't just a brief power outage or something 
instead.

In short, for this solutoin to meet all of my needs, I have to have an 
internet routable IP address on my Linux gateway (meaning the wireless 
card has to be in my linux box, or it has to be replaced with some kind 
of external access point).  I only have 2 more weeks, at most, left 
before my money back guarantee time of 30 days runs out.

    I'm looking for any and all suggestion/things to try to get this 
working stable.

Thanks,
Cory

Benjamin Reed wrote:

>That patch was only for 2.4.3.  In later kernels you
>just need to copy airo.c, airo.h, and airo_cs.c over
>the existing files in the kernel sources.
>
>ben
>
>--- Cory Steers <co...@st...> wrote:
>
>>  I'm having some trouble compiling my kernel after
>>patching it with CVS 
>>code.  I've tried this with a 2.4.7 and 2.4.17
>>kernel.  If my kernel 
>>source is in /usr/src/linux and my CVS patches are
>>in 
>>/usr/src/airo-linux, I cd to /usr/src/ and type
>>"patch -p0 < airo-linux/kernel/patches/2.4.3.patch"
>>and get the 
>>following errors:
>>
>>
>>patching file linux/drivers/net/Config.in
>>Hunk #1 FAILED at 254.
>>1 out of 1 hunk FAILED -- saving rejects to file 
>>linux/drivers/net/Config.in.rej
>>patching file linux/drivers/net/Makefile
>>Hunk #1 succeeded at 94 (offset 5 lines).
>>patching file linux/drivers/net/pcmcia/Config.in
>>Hunk #1 succeeded at 31 (offset 1 line).
>>Hunk #2 FAILED at 40.
>>1 out of 2 hunks FAILED -- saving rejects to file 
>>linux/drivers/net/pcmcia/Config.in.rej
>>patching file linux/drivers/net/pcmcia/Makefile
>>patching file linux/Documentation/Configure.help
>>Hunk #1 succeeded at 8650 with fuzz 1 (offset 1340
>>lines).
>>
>>After looking at linux/drivers/net/Config.in.rej it
>>appears that ~ ling 
>>290 something is where it wants to put the code.  I
>>don't think it's 
>>necessary anyway, because Config.in sources 
>>drivers/net/wireless/Config.in which has a spot for
>>CONFIG_AIRO.
>>
>>I have no idea what
>>linux/drivers/net/pcmcia/Config.in.rej wants to do. 
>> I can't match the rej stuff to anything in that
>>Config file.  I decided 
>>to not worry about it, because I'm not running on a
>>laptop, and 
>>therefore not using pcmcia.
>>
>>Next, I move linux/drivers/net/wireless/airo.c and
>>airo_cs.c to 
>>airo-old.c and airo_cs-old.c respectively.  I copy 
>>airo-linux/kernel/airo.c airo.h and airo_cs.c to 
>>linux/drivers/net/wireless.  I run "make
>>menuconfig", configure the 
>>kernel, and then successfully run "make dep".  When
>>I run "make bzImage" 
>>I get the following errors:
>>
>>
>>gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
>>-Wstrict-prototypes 
>>-Wno-trigraphs -O2 -fomit-frame-pointer
>>-fno-strict-aliasing -fno-common 
>>-pipe -mpreferred-stack-boundary=2 -march=i586   
>>-DEXPORT_SYMTAB -c 
>>auto_irq.c
>>rm -f net.o
>>ld -m elf_i386  -r -o net.o tulip/tulip.o airo.o
>>Space.o setup.o 
>>net_init.o loopback.o ppp_generic.o slhc.o
>>ppp_async.o ppp_synctty.o 
>>ppp_deflate.o bsd_comp.o auto_irq.o
>>ld: cannot open airo.o: No such file or directory
>>make[3]: *** [net.o] Error 1
>>make[3]: Leaving directory
>>`/usr/src/linux/drivers/net'
>>make[2]: *** [first_rule] Error 2
>>make[2]: Leaving directory
>>`/usr/src/linux/drivers/net'
>>make[1]: *** [_subdir_net] Error 2
>>make[1]: Leaving directory `/usr/src/linux/drivers'
>>make: *** [_dir_drivers] Error 2
>>
>>
>>Any help would be greatly appreciated.
>>
>>Thanks,
>>Cory
>>
>>
>>_______________________________________________
>>Airo-linux-general mailing list
>>Air...@li...
>>https://lists.sourceforge.net/lists/listinfo/airo-linux-general
>>
>
>__________________________________________________
>Do You Yahoo!?
>Send FREE video emails in Yahoo! Mail!
>http://promo.yahoo.com/videomail/
>

Re: [Airo-linux-general] compiling problems with CVS

[Benjamin R. <br...@ya...>]

That patch was only for 2.4.3.  In later kernels you
just need to copy airo.c, airo.h, and airo_cs.c over
the existing files in the kernel sources.

ben

--- Cory Steers <co...@st...> wrote:
>   I'm having some trouble compiling my kernel after
> patching it with CVS 
> code.  I've tried this with a 2.4.7 and 2.4.17
> kernel.  If my kernel 
> source is in /usr/src/linux and my CVS patches are
> in 
> /usr/src/airo-linux, I cd to /usr/src/ and type
> "patch -p0 < airo-linux/kernel/patches/2.4.3.patch"
> and get the 
> following errors:
> 
> 
> patching file linux/drivers/net/Config.in
> Hunk #1 FAILED at 254.
> 1 out of 1 hunk FAILED -- saving rejects to file 
> linux/drivers/net/Config.in.rej
> patching file linux/drivers/net/Makefile
> Hunk #1 succeeded at 94 (offset 5 lines).
> patching file linux/drivers/net/pcmcia/Config.in
> Hunk #1 succeeded at 31 (offset 1 line).
> Hunk #2 FAILED at 40.
> 1 out of 2 hunks FAILED -- saving rejects to file 
> linux/drivers/net/pcmcia/Config.in.rej
> patching file linux/drivers/net/pcmcia/Makefile
> patching file linux/Documentation/Configure.help
> Hunk #1 succeeded at 8650 with fuzz 1 (offset 1340
> lines).
> 
> After looking at linux/drivers/net/Config.in.rej it
> appears that ~ ling 
> 290 something is where it wants to put the code.  I
> don't think it's 
> necessary anyway, because Config.in sources 
> drivers/net/wireless/Config.in which has a spot for
> CONFIG_AIRO.
> 
> I have no idea what
> linux/drivers/net/pcmcia/Config.in.rej wants to do. 
>  I can't match the rej stuff to anything in that
> Config file.  I decided 
> to not worry about it, because I'm not running on a
> laptop, and 
> therefore not using pcmcia.
> 
> Next, I move linux/drivers/net/wireless/airo.c and
> airo_cs.c to 
> airo-old.c and airo_cs-old.c respectively.  I copy 
> airo-linux/kernel/airo.c airo.h and airo_cs.c to 
> linux/drivers/net/wireless.  I run "make
> menuconfig", configure the 
> kernel, and then successfully run "make dep".  When
> I run "make bzImage" 
> I get the following errors:
> 
> 
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
> -Wstrict-prototypes 
> -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common 
> -pipe -mpreferred-stack-boundary=2 -march=i586   
> -DEXPORT_SYMTAB -c 
> auto_irq.c
> rm -f net.o
> ld -m elf_i386  -r -o net.o tulip/tulip.o airo.o
> Space.o setup.o 
> net_init.o loopback.o ppp_generic.o slhc.o
> ppp_async.o ppp_synctty.o 
> ppp_deflate.o bsd_comp.o auto_irq.o
> ld: cannot open airo.o: No such file or directory
> make[3]: *** [net.o] Error 1
> make[3]: Leaving directory
> `/usr/src/linux/drivers/net'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory
> `/usr/src/linux/drivers/net'
> make[1]: *** [_subdir_net] Error 2
> make[1]: Leaving directory `/usr/src/linux/drivers'
> make: *** [_dir_drivers] Error 2
> 
> 
> Any help would be greatly appreciated.
> 
> Thanks,
> Cory
> 
> 
> _______________________________________________
> Airo-linux-general mailing list
> Air...@li...
> https://lists.sourceforge.net/lists/listinfo/airo-linux-general

__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/