Bertold Van den Bergh | 1 Oct 11:58 2011

Re: RT73 (and others): Beacon interval problem

Hello,

Doesn't your modification also result in hostapds configuration being
ignored? The only change would be that a more reasonable interval
would be used, not the configured value.

Sincerely,
Bertold Van den Bergh

On Mon, Sep 26, 2011 at 10:26 AM, Helmut Schaa
<helmut.schaa@...> wrote:
> Hi,
>
> On Wed, Sep 21, 2011 at 7:17 PM, Bertold Van den Bergh
> <vandenbergh@...> wrote:
>> I have tracked down the problem, and found that mac80211 does not call
>> rt2x00mac_bss_info_changed with changes set to BSS_CHANGED_BEACON_INT,
>> because the beacon interval has not changed between restarts, but the
>> interface has been disabled and reenabled by hostapd, thus executing
>> this code
>>        rt2x00_set_field32(&reg, TXRX_CSR9_BEACON_INTERVAL, 0);
>> and
>>        rt2x00usb_register_write(rt2x00dev, TXRX_CSR9, 0);
>> which sets the beacon interval to zero, causing the very fast
>> transmission. Changing the beacon interval in hostapd makes the
>> function to set the interval be called at startup and fixes the
>> problem.
>
> The same issue was present in rt2800 as well [1].
>
(Continue reading)

Gertjan van Wingerde | 1 Oct 13:32 2011
Picon

Re: Support for RT3072E ?

On 09/26/11 10:46, Helmut Schaa wrote:
> On Sun, Sep 25, 2011 at 3:08 PM, Ian Jeffray <ian@...> wrote:
>> Dear all,
>>
>> I have a SWEEX LW324 adaptor, which Sweex claim is an RT3072E device.
>>
>> The identification on the chip seems to say 'RT3072I' however the last
>> character is not very clear.  There are two Unictron AA029 chip
>> antennas and I believe the configuration is 2T2R.  The marking on the
>> PCB is 'RT3072-A  V2.1'
>>
>> The latest wireless-next driver says:
>> phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 3071, rf: 000e, rev:
>> 021c.
>>
>> And lsusb says:
>> 148f:2870 Ralink Technology, Corp. RT2870 Wireless Adapter
>>
>> This device does is not recognised by the rt2x00 driver because of
>> the unknown '000e' RF block.
> 
> That looks indeed fishy. I wasn't able to find a definition for this RF in the
> ralink legacy drivers. Maybe this is a vendor specific RF? Or the eeprom
> is somehow damaged ...
> 

Hmm, interesting. I just received my own LW324 adapter, and it indeed claims
the RF chip as reported by Ian.

Shiang, do you have some information on this RF chip identification. What does
(Continue reading)

Helmut Schaa | 4 Oct 08:40 2011

Re: RT73 (and others): Beacon interval problem

On Sat, Oct 1, 2011 at 11:58 AM, Bertold Van den Bergh
<vandenbergh@...> wrote:
> Doesn't your modification also result in hostapds configuration being
> ignored?

The requested change only affects the init code, hostapd sets the
beacon interval
later (see rt73usb_config_erp).

Thanks,
Helmut
Olivier Gandit | 6 Oct 21:12 2011

Re: Building a recent version of the driver

Hello,

it seems kernel.org is back.
Nevertheless, I'm still unable to extract the rt2x00 sources following
the instructions from the wiki.
The command
git clone git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git rt2x00
ends up with a 'fatal: The remote end hung up unexpectedly'.

Do you know how I can get these source files?

Best regards,

Olivier Gandit

2011/9/26 Ivo Van Doorn <ivdoorn@...>:
> Hi,
>
>> Is there a way to get the driver files independently from a kernel release?
>
> That would be compat-wireless, but I don't know where (and if) that package
> has moved to temporarily.
>
> Ivo
>
Ivo Van Doorn | 6 Oct 21:17 2011
Picon

Re: Building a recent version of the driver

Hi,

> it seems kernel.org is back.

Yes, but neither SSH or GIT seems to be completely back yet.

> Nevertheless, I'm still unable to extract the rt2x00 sources following
> the instructions from the wiki.
> The command
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git rt2x00
> ends up with a 'fatal: The remote end hung up unexpectedly'.
>
> Do you know how I can get these source files?

You have to wait until the servers have been fully restored I guess.

Ivo
Mark van Dijk | 7 Oct 00:17 2011
Picon

Re: Building a recent version of the driver

> > it seems kernel.org is back.
> 
> Yes, but neither SSH or GIT seems to be completely back yet.
> 
> > Nevertheless, I'm still unable to extract the rt2x00 sources
> > following the instructions from the wiki.
> > The command
> > git clone
> > git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git rt2x00
> > ends up with a 'fatal: The remote end hung up unexpectedly'.
> >
> > Do you know how I can get these source files?
> 
> You have to wait until the servers have been fully restored I guess.

Isn't there a mirror at github?
Ivo Van Doorn | 7 Oct 07:32 2011
Picon

Re: Building a recent version of the driver

Hi

> > > it seems kernel.org is back.
> >
> > Yes, but neither SSH or GIT seems to be completely back yet.
> >
> > > Nevertheless, I'm still unable to extract the rt2x00 sources
> > > following the instructions from the wiki.
> > > The command
> > > git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git rt2x00
> > > ends up with a 'fatal: The remote end hung up unexpectedly'.
> > >
> > > Do you know how I can get these source files?
> >
> > You have to wait until the servers have been fully restored I guess.
>
> Isn't there a mirror at github?

Yeah, i've pointed Olivier at that earlier, but I assume that wasn't useful.

Ivo

_______________________________________________
users mailing list
users@...
http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
Olivier Gandit | 7 Oct 13:07 2011

Re: Building a recent version of the driver

Actually, I haven't found any mirror for the rt2x00 sources only.

2011/10/7 Ivo Van Doorn <ivdoorn@...>:
> Hi
>
>> > > it seems kernel.org is back.
>> >
>> > Yes, but neither SSH or GIT seems to be completely back yet.
>> >
>> > > Nevertheless, I'm still unable to extract the rt2x00 sources
>> > > following the instructions from the wiki.
>> > > The command
>> > > git clone
>> > > git://git.kernel.org/pub/scm/linux/kernel/git/ivd/rt2x00.git rt2x00
>> > > ends up with a 'fatal: The remote end hung up unexpectedly'.
>> > >
>> > > Do you know how I can get these source files?
>> >
>> > You have to wait until the servers have been fully restored I guess.
>>
>> Isn't there a mirror at github?
>
> Yeah, i've pointed Olivier at that earlier, but I assume that wasn't useful.
>
> Ivo
>
> _______________________________________________
> users mailing list
> users@...
> http://rt2x00.serialmonkey.com/mailman/listinfo/users_rt2x00.serialmonkey.com
>
>
Ivo Van Doorn | 7 Oct 13:56 2011
Picon

Re: Building a recent version of the driver

Hi,

On Fri, Oct 7, 2011 at 1:07 PM, Olivier Gandit <ogandit@...> wrote:
> Actually, I haven't found any mirror for the rt2x00 sources only.

Well that mirror doesn't exist, that is why I pointed you to the
linux-wireless sources (that is 99% the same as rt2x00 anyway).

Ivo
Olivier Gandit | 12 Oct 18:11 2011

rt2800 usb crash with hostapd

Dear rt2x00 users,

I have built the stable release of the rt2x00 drivers for use with
hostapd on an ARM system with kernel version 2.6.35.5 and a rt2800 usb
chipset.

Everything starts fine but when a client tries to connect to the
access point, it fails with the following message:
BUG: scheduling while atomic: hostapd/1089/0x00000002
Modules linked in: rt2800usb rt2800lib rt2x00usb rt2x00lib mac80211
cfg80211 kfifo(P) compat lib80211_crypt_wep lib80211_crypt_tkip
lib80211_crypt_ccmp ppp_async ppp_generic slhc
[<c002872c>] (unwind_backtrace+0x0/0xf4) from [<c02a95b0>]
(schedule+0x274/0x34c)
[<c02a95b0>] (schedule+0x274/0x34c) from [<c02a9dc8>]
(schedule_timeout+0x13c/0x1d8)
[<c02a9dc8>] (schedule_timeout+0x13c/0x1d8) from [<c02a9af4>]
(wait_for_common+0xe8/0x1c4)
[<c02a9af4>] (wait_for_common+0xe8/0x1c4) from [<c01d6240>]
(usb_start_wait_urb+0x9c/0xc4)
[<c01d6240>] (usb_start_wait_urb+0x9c/0xc4) from [<c01d6450>]
(usb_control_msg+0xd4/0xf8)
[<c01d6450>] (usb_control_msg+0xd4/0xf8) from [<bf138de0>]
(rt2x00usb_vendor_request+0xa8/0x130 [rt2x00usb])
[<bf138de0>] (rt2x00usb_vendor_request+0xa8/0x130 [rt2x00usb]) from
[<bf138f08>] (rt2x00usb_vendor_req_buff_lock+0x68/0x114 [rt2x00usb])
[<bf138f08>] (rt2x00usb_vendor_req_buff_lock+0x68/0x114 [rt2x00usb])
from [<bf13911c>] (rt2x00usb_vendor_request_buff+0x68/0xbc
[rt2x00usb])
[<bf13911c>] (rt2x00usb_vendor_request_buff+0x68/0xbc [rt2x00usb])
from [<bf151534>] (rt2x00usb_register_multiread+0x44/0x4c [rt2800usb])
[<bf151534>] (rt2x00usb_register_multiread+0x44/0x4c [rt2800usb]) from
[<bf141148>] (rt2800_get_tkip_seq+0x34/0x4c [rt2800lib])
[<bf141148>] (rt2800_get_tkip_seq+0x34/0x4c [rt2800lib]) from
[<bf0f5c74>] (ieee80211_get_key+0x198/0x1e8 [mac80211])
[<bf0f5c74>] (ieee80211_get_key+0x198/0x1e8 [mac80211]) from
[<bf0bb79c>] (nl80211_get_key+0x284/0x328 [cfg80211])
[<bf0bb79c>] (nl80211_get_key+0x284/0x328 [cfg80211]) from
[<bf0a37ec>] (nl_doit_wrapper+0x130/0x158 [compat])
[<bf0a37ec>] (nl_doit_wrapper+0x130/0x158 [compat]) from [<c023754c>]
(genl_rcv_msg+0x1e8/0x210)
[<c023754c>] (genl_rcv_msg+0x1e8/0x210) from [<c0235bb8>]
(netlink_rcv_skb+0xbc/0xd8)
[<c0235bb8>] (netlink_rcv_skb+0xbc/0xd8) from [<c0237358>] (genl_rcv+0x18/0x24)
[<c0237358>] (genl_rcv+0x18/0x24) from [<c023579c>]
(netlink_unicast+0x2d0/0x32c)
[<c023579c>] (netlink_unicast+0x2d0/0x32c) from [<c02360dc>]
(netlink_sendmsg+0x190/0x270)
[<c02360dc>] (netlink_sendmsg+0x190/0x270) from [<c021073c>]
(sock_sendmsg+0x8c/0xb0)
[<c021073c>] (sock_sendmsg+0x8c/0xb0) from [<c0210c8c>]
(sys_sendmsg+0x130/0x254)
[<c0210c8c>] (sys_sendmsg+0x130/0x254) from [<c0022ee0>]
(ret_fast_syscall+0x0/0x2c)

Does anyone has already seen this?
Do you know any solution?

Best regards,

Olivier

Gmane