Send users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
Today's Topics:
1. Re: problem with rt2800usb module on Linksys NSLU2 running
Debian (Helmut Schaa)
2. Re: problem with rt2800usb module on Linksys NSLU2 running
Debian (mick)
3. Re: problem with rt2800usb module on Linksys NSLU2 running
Debian (David Joshua Geary)
4. Re: 7 more packets after each beacon frame (Ivo Van Doorn)
5. Re: 7 more packets after each beacon frame (Helmut Schaa)
6. Re: [PATCH] rt2x00: Add USB device ID of Buffalo WLI-UC-GNHP.
(Ivo Van Doorn)
7. Re: 7 more packets after each beacon frame (Ivo Van Doorn)
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Nov 2011 10:31:17 +0100
From: Helmut Schaa <[email protected]>
To: mick <[email protected]>
Cc: [email protected]
Subject: Re: [rt2x00-users] problem with rt2800usb module on Linksys
NSLU2 running Debian
Message-ID:
<CAGXE3d8U=hYgE27pZWV=agpj9gbqcd8hdy7uxbsp1g-l5kr...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Sun, Nov 13, 2011 at 8:40 PM, mick <[email protected]> wrote:
> Firstly, I hope this the right list to post to. According to the
> Debian wiki, the rt2800usb module is provided by this project. Modinfo
> also suggests that this is the right place.
Yup, it is.
> I have a problem with the rt2800usb module on my Linksys NSLU2
> which has been reflashed to run Debian 6 (squeeze). The NSLU2 is a
> small ARM architecture machine. I am using the default module and
> firmware provided by Debian for this architecture.
big or little endian? There might be an endian bug in rt2x00 somewhere as
others also had problems with this ...
Helmut
------------------------------
Message: 2
Date: Mon, 14 Nov 2011 10:37:58 +0000
From: mick <[email protected]>
To: Helmut Schaa <[email protected]>
Cc: [email protected]
Subject: Re: [rt2x00-users] problem with rt2800usb module on Linksys
NSLU2 running Debian
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
On Mon, 14 Nov 2011 10:31:17 +0100
Helmut Schaa <[email protected]> allegedly wrote:
> On Sun, Nov 13, 2011 at 8:40 PM, mick <[email protected]> wrote:
> > Firstly, I hope this the right list to post to. According to the
> > Debian wiki, the rt2800usb module is provided by this project.
> > Modinfo also suggests that this is the right place.
>
> Yup, it is.
Excellent. Thank you.
> > I have a problem with the rt2800usb module on my Linksys NSLU2
> > which has been reflashed to run Debian 6 (squeeze). The NSLU2 is a
> > small ARM architecture machine. I am using the default module and
> > firmware provided by Debian for this architecture.
>
> big or little endian? There might be an endian bug in rt2x00
> somewhere as others also had problems with this ...
>
I believe it is natively big-endian though the debian install is little
endian. See http://www.nslu2-linux.org/wiki/Info/EndianNess and the
discussion on wireless at
http://www.nslu2-linux.org/wiki/Peripherals/WirelessNetworkAdapter
Regards
Mick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL:
<http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/attachments/20111114/31a0c79c/attachment-0001.bin>
------------------------------
Message: 3
Date: Tue, 15 Nov 2011 00:26:29 +1100
From: David Joshua Geary <[email protected]>
To: [email protected]
Subject: Re: [rt2x00-users] problem with rt2800usb module on Linksys
NSLU2 running Debian
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Firstly, I hope this the right list to post to. According to the
> Debian wiki, the rt2800usb module is provided by this project. Modinfo
> also suggests that this is the right place.
You are correct.
> I have a problem with the rt2800usb module on my Linksys NSLU2
> which has been reflashed to run Debian 6 (squeeze). The NSLU2 is a
> small ARM architecture machine. I am using the default module and
> firmware provided by Debian for this architecture.
I assumed that the module shipped with Debian is too old and does not
support the device (evidenced by the phy error below). This assumption
directly conflicts with your evidence below of it working on an x86
architecture machine. I am beginning to suspect endianness issues,
however your `uname -a` suggests your ARM machine is little endian (like
an x86 and unlike a PowerPC).
I have downloaded and compiled Linux 3.1.0 in an effort to utilise a
device with the same chipset on a PowerPC architecture machine. I had
the same symptoms as you on the stock Debian Squeeze on PowerPC.
However, with Linux 3.1.0, my symptoms are that the phy is allocated but
the link never becomes ready and very rarely are there any results from
scans.
> The USB device I have is made by Addon and is apparently an RT3072
> adapter. On insertion of the adapter, the rt2800usb module (version
> 2.3.0) loads (dmesg details below) but is followed by the error
> messages:
Please state all of the branding on the device.
> phy0 -> rt2800usb_init_eeprom: Error - Invalid RT chipset detected.
> phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
>
> and no wifi interface is created.
>
> I have confirmed that the device works by plugging it into my x86
> architecture desktop running Debian 6 and to a netbook also running
> Debian 6. The problem only occurs on my NSLU2.
I never even thought of trying this. Good idea. I'll check it out next
weekend.
Please post `uname -a` for your x86 machines. I'm wondering if they are
different kernel versions (and therefore different driver revisions).
Please also post `lsmod` for your x86 machines. They may be using a
different driver (a driver not developed or supported by the rt2x00
project).
> lsusb reports the following:
>
> Bus 003 Device 005: ID 148f:3072 Ralink Technology, Corp. RT3072
> Wireless Adapter
This is the same ID as reported by my Tenda W322Uv2.0.
> kernel details (uname -a)
>
> Linux mug 2.6.32-5-ixp4xx #1 Mon Oct 3 12:19:10 UTC 2011 armv5tel
> GNU/Linux
> any suggestions as to what I should do to get this to work would be most
> welcome.
Perhaps also try the kernel in Debian Backports.
Another source of information is /var/log/syslog
Any other ideas are welcome.
In conclusion, I have no idea what the problem is nor how to go about
identifying and fixing it.
You may also want to see my blog entry on the matter which I update as I
learn more about my particular problem with this chipset:
http://perditauranus.dyndns.org/tdiary/?date=20111105
- --
David Joshua Geary
UNE Linux User Group: [email protected] <http://lugune.dyndns.org>
I don't care what software you use so long as
we only exchange files in open data formats
Open-Document <http://en.wikipedia.org/wiki/Open_Document>
Ogg <http://en.wikipedia.org/wiki/Ogg>
PDF <http://en.wikipedia.org/wiki/Pdf>
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.10 (GNU/Linux)
mQINBE0JY54BEAD2D3ckM+FTElSG6w89L1PkeB+m8+8K5ZJZKfLJXWv7NNTRS5DC
uJd/OrlQwC4Ecwkp4HqmjF8jYzCeLEnC7SR6VU3j05l1vR7pZvphUx7lYBbhXbV/
ykBQBK9AWQwf1ve3G2+hGRAeYmhSzen3Px06aBq4/nr3adF1JFekV5CyCuHxDriT
p7HMqEwCvRExnaJD45VKzCQiCYLDYkgVc5u+yBWHd92Jk0DHtm6T/CuoLsoYPIgU
Jy8sNFdGE9cC3Nb6Ay/Je4FUlKqu9xNej7KGF0SNVjfD7+bMlB37uaDSk1vLGkmg
rhnR78YTdZ2iE2hcbae8l/N9aFWUHfxnuHEew/imTJgaBOMOp6k3FGIFG+1qznnG
UlXBMR7gY5jyPKTLe0iJo5MCylKeS56uyDgGv8FtGD73MRqGxktR5b8Zv4Wjv0cz
S4yBT8dvAYohw8UeRF4EKQlmxX7rusaipXCe/lGyuytfNFJ77EHMESzVkM/da0qk
Zt2sotf83XXE+h6lsUDee1whNDtNvaYmTziKZVHJ3olP3kg+FglgoWKG/y5QQHtW
ASa4tnlnNFVGJaOBVnVOq5RsrmQ+YSmYsm/OfjzAthc3QM5BhQhB381y4lKtFo1S
G7qChNSpA29ea1Muqgz3fDlP3m4iHo1AFvBTgpvEIh/Eb8MXSmeHxmEk0QARAQAB
tD9EYXZpZCBHZWFyeSAoR01haWwgRW1haWwgU2lnbmluZyBLZXkpIDxiaWFuY2Eu
dXJhbnVzQGdtYWlsLmNvbT6JAjgEEwECACIFAk0JY54CGyMGCwkIBwMCBhUIAgkK
CwQWAgMBAh4BAheAAAoJEMR6DgDuR4IfvsUQALCnZfpyz39BQT609n0m+wLZg8CX
uTnCf1m+oZj5W11oqqZd0XcHc1o4n6F6VNvSULHCgNYP6kOnJHliBX53Qdr7muJz
qQSwtywaS6oQUHWJk++youkvBqV/A4tiggEsXKzdQx/F+o2sIWQ4VGR3NlLkOJa4
xddVAGLuYHmOt1OenwfFXUFodmcPSWwnyVu9E8cm7iZxdg66u/fEraY4pC2yI2Zi
T0c1NRVA6ytqo/t4V2wmysZLj9r+O3q88ncUTg1qcVNS32eEVxZJS1R0y7MyM+Gr
lh6OI+VrhkfQ/DawvsAqHxxgMWMrzBQUa9ss7mPlawZWOSBiBLtckYHpPJje21ze
EPzhPub7EnXfenLWIHG2+O0FIkPIu5OSRwHtAgkTXBXtrzzyMIU/cFsuI0D2Da6m
w4QSlEAb8hWGS5LqaM/8i+eaTDL7XgZ9Z7OibS4lzcUnZZOW5dzHIqDVK77c57If
rG2cin/GChsYrlckN1XrvlulSXYu08D/xL4f39sUZexiyYZtLoWas+MvOboGgc8o
MfE7U92gXb1l4hm3iKXHzaYdBC1YqxMdgy9RBDaSbHq3n0pFpCGW8SURtuOlkVbq
kgwPq6v1obb0ZvpE3cLPN8PhqSWxbM4sEYYo6jDAaTRkv/Cy/faEQuCJ+wmVT2bu
deYspeWy73rGANavuQINBE0JY54BEADD+h4XyQmbyfNrsmPjHlqJtmZHojtiZZKZ
nKoawdLex/L7XJBXfNhTu1kwCV2fW1HibyUW/a5m41H9ked5gScR8bEn02liXc6c
Ad6rAMSY9H2/5+FXcGPJqV/9VJTNC8FTEADmJzHzENLDcpil1jXkYDwSn5wYYsmS
1GtT4jsRkGZYzXerPs3JfpxTFuVQWTsodyzfs+YwnNVIcAX4yBrg5WSRPlbHC0WP
VQxqFVdDDq0RN11+2sM6BYVvnL1fX69TN4MAPhBjbYalIt0Ls9dGjn/aiB0E1nEn
QfRcQb939gJQV5LLKxICc9Qa/GfMFjt6OYArZ8RzMvIs7WGdFXG0GuU/DjHRI65U
f7Ed7bGZw9S0ZAjawH8q1/JeUkNtbMCz5oRvvhYTXOw3WLXCeTPALJ6XU7fRTY48
rIDxpvoxyE4mMoNnn1ZE5rcIbCza0tDD3FUPae6i6Mixnk0hXGirwnwPuJyFi3Io
zibtMzuoju7l2gKzhZVcp4HlERhGTcEPfCaVIGy3j0k0nfc+hCySA59fXfs6UK5T
URhSKLb8+R/Ne0Fyiyg8ASdS8HPIs8Njw4CppfWX5Ds5NgwF5OALlYHkIKjn07Kc
+bGO+WWJvnZfo2fdjgPPs4ECaJL7L5RuVuy26QnPMLgAUNJLgGjugGoE0pOLSwmj
f3xOB4GlowARAQABiQIfBBgBAgAJBQJNCWOeAhsMAAoJEMR6DgDuR4If6LAQAIAx
WHngmPZ1vzraRVadFnQrYr4bpBT+Hznwm91HtAup8HgutSiulOY1Kbpra1avjmQi
MYCRQqDeOsFGirOomterbU18sXX7YBFbAT0c+rHoSdtFP2JTkSzN0Ocs1mZZuLfu
Dw/DSAaxlpkKQUJ5xn+qAOPr0fX2HbNcTc9kKYPNJJ9n7WtPhG6hC7ehjHis2jSz
Am3Ik+5gNZjaNkHsanaGTfx3mo/jf2AUGydB2quYPz8DFyTYN6q+VZ6+Vzy08RGz
MLWwM/SSMhT+GXrhSeuAiO26a70T0XTbhliccUDlG6ORPQ+ydzkffNQB35OfIkbA
+SoiDf1txduWDeJxblZ3feYqwBcjBBJU/ofEigH32z0ZOsFpWcJTsXSB2RyoJT+Y
Pb426uZYYTi2ZtWGcDtwRzK2lXM3WIHnoduFY5LIXq51c+cP2u8a461pmrlTvixE
y+IfX/zHfvSUnJDpnO4sA770oCHBUsbmU14oPdr+Kla67jqpjujap1ITRA96bcNm
K7O3vOKqbkAoy4w9ogCbBHrH1/8M+iRWA+0Iim+zhYSeEmjLszeecII9MH3u8CS0
DjLhpLrX6WG7F9fr0xAnc3Dui+qBm/q1dKenCKauUYWRgDPUXzP32oIiw/bXBp/4
qKbhUOJTXVVns4OnvPNzFoCvcNS6G/3ZGlX/6duU
=kv+y
- -----END PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOwRcBAAoJEMR6DgDuR4IfLiEP/j+Xa15UZ4jdXF2/R/jEiJwi
LBfa892SkpttrDxkwGv4P8/aQz7LzA9qyvQpzoiQGNXT2vXwF0C5RPY/rjGH17l9
QrCgZqdjzmehYKHOX1UTeMfWPCj+6pWKaHLLkAp8ZqKf7iLCIkXqYLyaBHbaD/aQ
ZuuILxhbUW+ozVFEDue/n9LJiJs7zRQy553+UhLgo7v4wJkgK3fm8TvI1Wia5oKB
mW/IHQ2T7vfz25Sq3X9/EuuQETmS2FttHV7tOkHbOYIpa6HMKne5wh9fxfvIo04p
FnqZnTTrPVfpWyGEQ0IaO7uBHxIwPpKErhTbOizupFKUZDhL9U4FCEatLyD6CtxK
o2Rm8ceKlP/qdt/8B130yC4ThxJ3pMJqj6OWHa0XyWiNF5JBd6tBTvkxUZ40abcr
FMfix30hw8D7g7PITnTknJUa+NfDrrYC/BZgSf7ycJRfrFIqvi6/R3dTjfS5jMrq
dCDdpIVxehB3IYpFrCmtgPCkIsRg4JVAcaLLNWTUNigcQiKiDVyRtmBkJLbQi5AB
8ZlT6ICfsjEuUYrPErZbsnmtZ2X/6ZzlG6Ye5IKUHRVkG+2tphz/vMLPOKUqb3u1
VJas5h60MahCyyhNOuq24rJp++AjwjcAF155t0H6tm5n4n43gTPtpAPAfJiSNM8l
b7hp4iu4Rd38tzpuH4lF
=QK66
-----END PGP SIGNATURE-----
------------------------------
Message: 4
Date: Mon, 14 Nov 2011 15:38:48 +0100
From: Ivo Van Doorn <[email protected]>
To: Helmut Schaa <[email protected]>
Cc: Andreas Hartmann <[email protected]>,
[email protected]
Subject: Re: [rt2x00-users] 7 more packets after each beacon frame
Message-ID:
<caozox0uxmpkfwa1nkt6moady4fboh5fycvxxgu62qqjfxsb...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
>> Can't we just "program" the card with the right amount of BSSIDs as we
>> need them?
>> I.e. just set it to one at the start and change it later when more
>> BSSIDs are added.
>
> Sure, would be possible but if we remove an interface that might leave
> a hole in the beacon buffers. So, we would have to shift following
> beacons such that we don't have holes between any beacons ...
>
> I'm just thinking about a way to implement this without much management
> overhead.
Another issue is that this solution will only reduce the number of extra
beacons. Basically you can program the driver to have:
1, 2 or 8 beacons. So when you have 3 interfaces you will still have
the extra beacons. Furthermore you have to change both the BSSID and
unicode_to_me mask. And I am not sure if that will show any side effects.
Ivo
------------------------------
Message: 5
Date: Mon, 14 Nov 2011 15:44:29 +0100
From: Helmut Schaa <[email protected]>
To: Ivo Van Doorn <[email protected]>
Cc: Andreas Hartmann <[email protected]>,
[email protected]
Subject: Re: [rt2x00-users] 7 more packets after each beacon frame
Message-ID:
<CAGXE3d_MMZvikf3Q=b6TbPcJbb2H=pq3o3rtwbechnku8to...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Nov 14, 2011 at 3:38 PM, Ivo Van Doorn <[email protected]> wrote:
> Hi,
>
>>> Can't we just "program" the card with the right amount of BSSIDs as we
>>> need them?
>>> I.e. just set it to one at the start and change it later when more
>>> BSSIDs are added.
>>
>> Sure, would be possible but if we remove an interface that might leave
>> a hole in the beacon buffers. So, we would have to shift following
>> beacons such that we don't have holes between any beacons ...
>>
>> I'm just thinking about a way to implement this without much management
>> overhead.
>
> Another issue is that this solution will only reduce the number of extra
> beacons. Basically you can program the driver to have:
> 1, 2 or 8 beacons. So when you have 3 interfaces you will still have
> the extra beacons. Furthermore you have to change both the BSSID and
> unicode_to_me mask. And I am not sure if that will show any side effects.
Hmm, not sure, we could just leave the MAC_BSSID_DW1_BSS_ID_MASK as "8"
and just initialize MAC_BSSID_DW1_BSS_BCN_NUM with the actual number of
beaconing interfaces. I don't think the BSSID needs to have a specific value
depending on the used beacon slot ...
So, I think it is possible but quite some changes are required.
Helmut
------------------------------
Message: 6
Date: Mon, 14 Nov 2011 15:44:54 +0100
From: Ivo Van Doorn <[email protected]>
To: Gertjan van Wingerde <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [rt2x00-users] [PATCH] rt2x00: Add USB device ID of
Buffalo WLI-UC-GNHP.
Message-ID:
<caozox0uue5j9q7cv8161fi-smdu+trws3wxekrhghvzu1k4...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Sat, Nov 12, 2011 at 7:10 PM, Gertjan van Wingerde
<[email protected]> wrote:
> This is reported to be an RT3070 based device.
>
> Reported-by: Teika Kazura <[email protected]>
> Signed-off-by: Gertjan van Wingerde <[email protected]>
Acked-by: Ivo van Doorn <[email protected]>
> ---
> ?drivers/net/wireless/rt2x00/rt2800usb.c | ? ?1 +
> ?1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800usb.c
> b/drivers/net/wireless/rt2x00/rt2800usb.c
> index f156579..3778763 100644
> --- a/drivers/net/wireless/rt2x00/rt2800usb.c
> +++ b/drivers/net/wireless/rt2x00/rt2800usb.c
> @@ -919,6 +919,7 @@ static struct usb_device_id rt2800usb_device_table[] = {
> ? ? ? ?{ USB_DEVICE(0x050d, 0x935b) },
> ? ? ? ?/* Buffalo */
> ? ? ? ?{ USB_DEVICE(0x0411, 0x00e8) },
> + ? ? ? { USB_DEVICE(0x0411, 0x0158) },
> ? ? ? ?{ USB_DEVICE(0x0411, 0x016f) },
> ? ? ? ?{ USB_DEVICE(0x0411, 0x01a2) },
> ? ? ? ?/* Corega */
> --
> 1.7.7
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
>
------------------------------
Message: 7
Date: Mon, 14 Nov 2011 15:51:24 +0100
From: Ivo Van Doorn <[email protected]>
To: Helmut Schaa <[email protected]>
Cc: Andreas Hartmann <[email protected]>,
[email protected]
Subject: Re: [rt2x00-users] 7 more packets after each beacon frame
Message-ID:
<CAOZOX0UbE+R4W=WEHgNtq=crtcx8z+uhcd0vyezuf11+tnu...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
On Mon, Nov 14, 2011 at 3:44 PM, Helmut Schaa
<[email protected]> wrote:
> On Mon, Nov 14, 2011 at 3:38 PM, Ivo Van Doorn <[email protected]> wrote:
>> Hi,
>>
>>>> Can't we just "program" the card with the right amount of BSSIDs as we
>>>> need them?
>>>> I.e. just set it to one at the start and change it later when more
>>>> BSSIDs are added.
>>>
>>> Sure, would be possible but if we remove an interface that might leave
>>> a hole in the beacon buffers. So, we would have to shift following
>>> beacons such that we don't have holes between any beacons ...
>>>
>>> I'm just thinking about a way to implement this without much management
>>> overhead.
>>
>> Another issue is that this solution will only reduce the number of extra
>> beacons. Basically you can program the driver to have:
>> 1, 2 or 8 beacons. So when you have 3 interfaces you will still have
>> the extra beacons. Furthermore you have to change both the BSSID and
>> unicode_to_me mask. And I am not sure if that will show any side effects.
>
> Hmm, not sure, we could just leave the MAC_BSSID_DW1_BSS_ID_MASK as "8"
> and just initialize MAC_BSSID_DW1_BSS_BCN_NUM ?with the actual number of
> beaconing interfaces. I don't think the BSSID needs to have a specific value
> depending on the used beacon slot ...
>
> So, I think it is possible but quite some changes are required.
Yeah, especially since it means you have to constantly ensure that all enabled
beacons are placed right after each other in the registers.. I would
say that would
add a lot of complexity which we don't want. So can we detect which drivers are
broken and disable multi-BSSID for those?
Ivo
------------------------------
_______________________________________________
users mailing list
[email protected]
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
End of users Digest, Vol 33, Issue 13
*************************************
