Re: regression on BWU613SB

On Sat Apr 10, 2004 at 12:00:05PM +0200, [email protected] wrote:
> --__--__--
> 
> Hi,
> 
> On Thu, 8 Apr 2004, The Anarcat wrote:
> 
> > I've noticed a regression in the support for the chipset inside my
> > BWU613SB USB wifi. I got it to work in January and the modifications I
> > suggested got committed into the main tree by around then, however, I
> > never checked to see if the CVS code was actually working.
> >
> > One thing is for sure now, it's not working anymore. The symptom is that
> > when plugging the device in, gkrellm crashes, ifconfig segfaults, as cat
> > /proc/net/wireless. I appended a typical crash dump below.
> >
> > I've tried to pinpoint the date at which the regression got into the
> > tree, so I tried the following dates, in order:
> >
> > 1 feb: works
> > 1 mar: crash
> > 15 feb: works
> > 25 feb: crash
> > 20 feb: works
> 
> > 23 feb: crash while compiling (!)
> IMHO hard to blame the driver for this (unless it was loaded before
> compilation time).

You are probably right. I was just mentionning that to underline why I
stopped there. :)

> There were only a few updates to at76c503.c during that time
> (from "cvs log at76c503.c"):
> 
...
> ----------------------------
> revision 1.43
> date: 2004/02/20 22:14:42;  author: jal2;  state: Exp;  lines: +2 -10
> branches:  1.43.2;
> 0.12beta7: un-done the workaround for 2.4.x kernels and usb-uhci calling
> disconn
> ect during resetting the device (it didn't work)
> ----------------------------
...
> version 1.43 removed a work-around for usb-uhci on 2.4.x problems which
> didn't work here (but I guess it worked for you :-|

Not sure. I don't remember exactly, but maybe I was running the gizmo
with the other usb driver (uhci) then.

> > I'm a little hesitant to try to debug this on an old version, so I'd
> > rather wait for input on how to solve the first problem with the current
> > tree (segfaulting ifconfig on connection) and the attack the second
> > problem rather than trying to fix problems with the old code.
> 
> I'd suggest trying the latest cvs version and take uhci instead of
> usb-uhci (if possible). Maybe your re-installing of the system swapped
> uhci for usb-uhci?

Indeed it did. I installed this OS using the Knoppix CD and it seems it
setup usb-uhci. Knoppix, by the way, uses the other atmel driver and
therefore doesn't detect the card.

> The current cvs has a problem with 2.4.x and usb-uhci due to different
> behaviour of the USB subsys at USB device reset calls (but it works with
> uhci, ohci and ehci).

I've sucessfully setup my system using uhci, through modconf, and the
latest CVS.  IMHO, it should be made clearer on the website and the doc
that usb-uhci is not supported, it would solve many headaches. :)

Thanks again for tracking this down,

A.

PS: any chance of seeing this wonderful driver being merged into the
main kernel tree or something? Just dreaming here. ;)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAfCOLttcWHAnWiGcRAswKAJ0VsFKv+LjXMH+x52+V+buLlwtzMACfeUEn
QVrzc+Oj6U1mGbF9BONYyaY=
=IoPA
-----END PGP SIGNATURE-----