Re: Problem with Atmel drivers

Hi Prezes,

On Mon, 6 Sep 2004, Prezes wrote:

>   I went to page:
>
>   http://at76c503a.berlios.de/
>
>   and I downloaded via CVS the last driver source. I have got Knoppix
>   (installed in HDD in "knoppix' way) with kernel 2.4.26. I compiled
>   and I installed the driver. When I do "iwconfig" everything is OK.
>   but if I would like to do "ifconfig wlan0 10.0.0.1 netmask
>   255.255.255.0 up" or simply "ifconfig wlan0 10.0.0.1" system hang
>   with error: "segmentation fault". If I do "ifconfig wlan0" or
>   "ifconfig -a" everything is displayed properly, but I can't
>   configure this device. Could you help me? This device is Planet
>   wl-u350 usb. I use Wireless Tools version 27-pre26 (beta), with
>   version pre23 the same. I must add, that I have also wl-8305 in
>   another computer and the same system and everything is OK (with
>   acx100 packet).
>
>   I attach my kernel .config file.

I need more info about the hang. Please try these steps:

1) attach device and load the Berlios drivers (latest cvs version)
2) check the syslog for the display of the MAC address (indicating a
   normal initialization).
3) set debug in at76c503 to max:
	iwpriv wlan0 set_debug -1
4) Open the network interface, this starts the driver which in turn
   seems to hang your system: do it delayed and switch to the
   tty where your syslog is displayed (here tty10, check your
   /etc/syslog.conf for a line like
	*.*                             /dev/tty10
   Execute on the shell prompt:
	sleep 5; ifconfig wlan0 X.Y.Z.A
   and switch to the syslog tty in the next 5 seconds
5) Any more info about the crash in the syslog there? If you don't feel
   like writing down the info and have got a digital camera, take a
   picture and send it to me in a personal mail. You may also redirect
   syslog to the serial port and capture it with a second computer (PDA).

6) Any crash info in syslog is almost useless with 2.4.x
   kernels without kernel symbol postprocessing. You need to store the
   kernel symbols after step 1 and run ksymoops after a reboot on the
   syslog.

/Jörg