Re: After kernel upgrade to 2.6.12 no connection anymore :-(

Ruud Linders <rkmp-qWit8jRvyhVmR6Xm/[email protected]> Thu, 18 Aug 2005 20:52:34 +0200
Newsgroups gmane.linux.drivers.atmel-wlan
Message-ID <[email protected]>
After several hours of building/rebooting cycles I finally got to
the conclusion that somewhere between kernels
  2.6.12-rc3    and
  2.6.12-rc3-git1
(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.12-rc3-git1.bz2)

the at76c503a driver got broken !

It doesn't appear to be a problem with ARP messages as Jim mentioned
since manually setting the arp table doesn't help.

What I =do= see is that the interface actually receives something
as the RX-packets/RX-bytes of the interface are incremented
when I ping it (or any other IP address in the subnet for that
matter).

Enough for today, it is now a matter of dissecting the
patch-2.6.12-rc3-git1.bz2 to see which change caused the problems
(and then finding a fix).


Ruud Linders wrote:
> Jim MacBaine wrote:
> 
>>On 8/17/05, Ruud Linders <rkmp-qWit8jRvyhVmR6Xm/[email protected]> wrote:
>>
>>
>>
>>>After upgrading my kernel from 2.6.11 to 2.6.12, I can't get a
>>>working link anymore.
>>
>>
>>Yes, we have had this topic here a few times already.  But noone here
>>has enough techical knowledge to fix the driver.  So the driver is
>>obviously unmaintained.
>> 
> 
> 
> That's too bad :-(  I've been using it for long time without problems.
> 
> 
>>>Effect is no message seems to get through.
>>
>>
>>If you'd look closer, you'd probably see that arp requests get through
>>but that they are not answered.
> 
> 
> Hmm, I'll have a look at that.
> 
> 
>>
>>>Been using this the at76c503a driver since years started back with 2.4.x.
>>>
>>>With atmelwlandriver cvs version from sourceforge I actually got
>>>a working connection on kernel 2.6.12 (although only channel 10
>>>seems to work ?!)
>>
>>
>>I have switched from the atmelwlandriver to at76c503c after I had
>>massive problems with the first one (still on 2.4), complete system
>>stalls, spontaneous reboots and often a completley unresponsive usb
>>system, which is quite bad with a usb keyboard.
>>
>>But maybe it is time to try the atmelwlandriver again.  Is it working
>>stable on 2.6.12 for you?
> 
> 
> I've been running it now for a day or 2 and I can't say that there have
> been these disastrous errors.  Building/installing was painless so it
> seems to be rather up-to-date AND it uses standard 'iwconfig' to setup
> (I have some vague memoeries it used to require strange tools to manage)
> 
> Once it is running it seems to work alright, however, it is doing weird
> things when starting up. I try to set it up in ad-hoc mode on fixed
> channel but it insists in scanning all channels/networks in the
> neighborhood to "join" something. So when I don't have my laptop powered
> on (as the other side of the wireless link) it will lock on another
> channel (with =my=  wep-key & essid) which happens to be used by some
> neighbor two appartments away !?
> 
> 
> I think it is time to switch to something newer with 802.11g support
> with Access Point functionality and proper linux(-usb) support.
> 
> 
>>Regards,
>>Jim
>>
>>_______________________________________________
>>Atmel-wlan-usb mailing list
>>Atmel-wlan-usb-ikZNBd7uB5wQUIZIPwn63sWURRETrGNnG9Ur7JDdleE@public.gmane.org
>>https://iprserv.jura.uni-leipzig.de/mailman/listinfo/atmel-wlan-usb
>>
> 
> 
>