Re: [Acx100-devel] tests

[<an...@bi...>]

Hi Howard,

Howard Young schrieb:
>=20
> Hello which messages should I show you.

The part of syslog related to acx .. ;)

> Is there any way that I can redirect most of the acx output to a file b=
y
> default so that I can easily submit all information to this list.

Well, the output of acx-driver are kernel-log-messages, all of them go
to /var/log/syslog ..

I usually do the reporting this way:

first run this script, it modprobe, configure card, do traffic and rmmod
plus tagging the output with logger.

---8<---
#!/bin/sh
# test script

#global variable, the place where the testbuild resides
_PATH=3D/home/andreas/source/kernel/acx
_current=3D`file $_PATH/test-build | cut -f 5 -d" "`

# tag the test to find it in syslog
logger -t "acx100 tests" Now using $_current snapshot

# stop existing connection
# this is only for me, i use waproamd ...
/etc/init.d/waproamd stop
# remove old module
modprobe -r acx_pci
sleep 1

# load necessary module
logger -t "acx100 tests" LOADING firmeware_class!
# firmwareclass is needed since about 20050807
# therefore you have to provide firmware_image at 'hotplug firmware
upload dir', /lib/firmware for me
modprobe firmware_class
sleep 1

# load module with debugging
logger -t "acx100 tests" Now loading acx_pci !
# insmod with debug output ...
insmod $_PATH/test-build/acx_pci.ko debug=3D0xffff
sleep 1

# configure wlan connection
logger -t "acx100 tests" iwconfig wlan0
# andreas at home !
iwconfig wlan0 mode managed essid biessmann key <my_key>
sleep 1

# get a ip
# i have not defined wireless konfig at /etc/network/interfaces ...
logger -t "acx100 tests" ifup wlan0
ifup wlan0

# make some traffic
# test the connection
sleep 1
logger -t "acx100 tests" "ping -c 10 heise.de"
ping -c 10 heise.de
sleep 1

# stop the connection
logger -t "acx100 tests" starting _stop_ script
logger -t "acx100 tests" unloading acx_pci module in 5 sec

echo "unloading in 5 sec!!"

sleep 5

logger -t "acx100 tests" STOPPING IFACE
ifdown wlan0

---8<---

After that i copy the syslog to my working directory to find the acx_stuf=
f.
First run a 'cat -n syslog | grep "acx100 tests"' so i can see the first
and last line number related to acx.

after that i use the following script that way:
=2E/fromTo.sh syslog acx_test <first line of test> <last line of test>

---8<---
#!/bin/sh
# fromTo.sh

function usage() {
        echo "$0 <filename> <new Filename> <from first Line> <to last Lin=
e>"
        exit 0
}

if [ $# !=3D 4 ]; then
        usage
fi

file=3D"$1"
newFile=3D"$2"
from=3D"$3"
to=3D"$4"

length=3D`echo $to-$from +1 | bc`

head -$to $file | tail -$length - > $newFile

exit 0

---8<---

so you have acx related syslog and can bzip the file. That file should
be about 100K max size. It has another benefit, you can better grep it ..=
=2E

>=20
> There seem to be messages logged in several files.=20

really?

> I am not sure what is
> important but don't want to spend all evening copying text files around=

> just to find most of it is useless.
>=20

I understand .... therefor use the described way ...
First of all, find a working version for yor acx111, acx100 seemed to
work. After that you can test newer versions and help the developers by
sending detailed debug. Afterwards you can switch back to the working
version ..

> I had quite a nasty crash after rebooting. I have not before had a cras=
h
> like that. It was on the Server. Alas i do not know where the error was=

> logged and foolishly turned off the pc so I could get up for work...
> without having made a note of the error. It was something to do with a
> kernel module error near the end of the boot up (it seemed odd that it
> was severe at that stage in the boot... sorry i do not have more detail=
s).
>=20
> Remember server is an acx111.

Well, i think the pre_XY are in a early stage regarding to acx111.
Better use the newer snapshots at:
http://195.66.192.167/linux/acx_patches/

>=20
> Howard
>=20

kind regards
Andrea Bie=DFmann