[rt2x00-users] problem with rt2800usb module on Linksys NSLU2 running Debian

[Gertjan van Wingerde]

Hi Mick,

On Tue, Nov 15, 2011 at 4:47 PM, mick <mbm at rlogin.net> wrote:
> On Mon, 14 Nov 2011 22:55:51 +0100
> Gertjan van Wingerde <gwingerde at gmail.com> allegedly wrote:
>> I'm afraid that you might be hit with an interesting endian-issue,
>> perhaps caused by running the ARM in little-endian mode, while the
>> rt2x00 modules might be thinking it is big-endian mode. Could you try
>> the attached diagnostics patch and report the output in dmesg when
>> loading the module?
>>
>> This should at least show us if my suspicion is right, and as well if
>> there may be other endianness issues.
>>
>> ---
>
> Gertjan
>
> Thank you. But I now have another difficulty - I can't find the source
> for rt2x00lib.c to patch.
>
> It is entirely possible of course that I am being incredibly stupid
> here. After all, I spent some silly amount of time today searching for
> the debian source for the /module/ rt2800usb before I it sank in
> that it is no longer a separate module but part of the mainline kernel.
>
> So having installed the kernel source to my NSLU2 I find that the
> contents of linux-source-2.6.32/drivers/net/wireless/rt2x00 are:
>
> Kconfig
> Makefile
> rt2400pci.c
> rt2400pci.h
> rt2500pci.c
> rt2500pci.h
> rt2500usb.c
> rt2500usb.h
> rt2800usb.c
> rt2800usb.h
> rt2x00.h
> rt2x00config.c
> rt2x00crypto.c
> rt2x00debug.c
> rt2x00debug.h
> rt2x00dev.c
> rt2x00dump.h
> rt2x00firmware.c
> rt2x00ht.c
> rt2x00leds.c
> rt2x00leds.h
> rt2x00lib.h
> rt2x00link.c
> rt2x00mac.c
> rt2x00pci.c
> rt2x00pci.h
> rt2x00queue.c
> rt2x00queue.h
> rt2x00reg.h
> rt2x00usb.c
> rt2x00usb.h
> rt61pci.c
> rt61pci.h
> rt73usb.c
> rt73usb.h
>
> no rt2800lib.c
>

OK. This already shows that the rt2x00 version that you are running is
very old, and
it is not surprising it is not working at all.

> I then tried to fetch the source from your git repository as outlined
> at
> http://rt2x00.serialmonkey.com/wiki/index.php?title=Rt2x00_GIT_instructions
> but received the error
> "fatal: The remote end hung up unexpectedly" - which suggests some
> authentication issue.
>
> I'm not having a good day.
>

Yeah, we have not resurrected the git repository after the kernel.org
hacking issues, and
we may never resurrect it.
Basically you can choose to use the wireless-testing git tree to get
the latest rt2x00 sources,
or, and this is usually easier, use a recent compat-wireless package
to get the latest rt2x00.

---
Gertjan