public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: users@rt2x00.serialmonkey.com
Cc: Luis Correia <buga@loide.net>, linux-kernel@vger.kernel.org
Subject: Re: [rt2x00-users] rt2500usb broken since 2.6.29
Date: Fri, 19 Mar 2010 22:31:48 +0100	[thread overview]
Message-ID: <201003192231.50287.linux@rainbow-software.org> (raw)
In-Reply-To: <201003191601.48405.linux@rainbow-software.org>

On Friday 19 March 2010 16:01:47 Ondrej Zary wrote:
> On Thursday 18 March 2010, Luis Correia wrote:
> > Hi,
> >
> > On Thu, Mar 18, 2010 at 22:04, Ondrej Zary <linux@rainbow-software.org>
>
> wrote:
> > > On Thursday 18 March 2010 22:51:18 Luis Correia wrote:
> > >> Hi,
> > >>
> > >> On Thu, Mar 18, 2010 at 21:46, Ondrej Zary
> > >
> > > <linux@rainbow-software.org>wrote:
> > >> > Hello,
> > >> > rt2500usb is broken since kernel 2.6.29. It has been discussed
> > >> > before but never solved:
> > >> > http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=4&t=4834
> > >> > https://bugzilla.redhat.com/show_bug.cgi?id=484888
> > >> >
> > >> > I have Asus WL-167G and it really does not work. Scanning works,
> > >> > association
> > >> > too but no packets can be sent (looks like receive works because
> > >> > tcpdump shows packets from other machines). DHCP fails (No
> > >> > DHCPOFFERS received).
> > >> >
> > >> > The problem is caused by this patch:
> > >> >
> > >> > rt2x00: Implement HW encryption (rt2500usb)
> > >> >
> > >> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
> > >> >om mit ;h=dddfb478b26e29a2b47f655ec219e743b8111015
> > >> >
> > >> > Removing it from 2.6.29 restores the functionality.
> > >> >
> > >> > --
> > >> > Ondrej Zary
> > >>
> > >> you can prevent hardware encryption by supplying "nohwcrypt=1" to the
> > >> driver.
> > >> (modinfo rt2500usb)
> > >
> > > That did not work. Maybe that was because I just unloaded the rt2500usb
> > > module and loaded it again with nohwcrypt=1 without rebooting the
> > > machine. Then I removed the HW encryption, recompiled and reloaded and
> > > it did not work either. It started to work only after reboot.
> >
> > did you actually remove the usb module and unloaded the module as well?
> >
> > you then need to load the module with the option, wait one sec and
> > then plug the device back in.
> >
> > > Does the HW encryption really work with any rt2500usb hardware? How can
> > > I help to fix it? Or maybe it should be disabled by default.
> >
> > I think the HW encription did work in the past, but I'm unsure of the
> > proper timeline.
>
> HW encryption was added in 2.6.29 and it does not work there. In 2.6.30,
> the driver is broken even more - it does not work even with HW encryption
> disabled. I'm going to bisect it.

Bisection revealed this commit:
ac7f9cfa2c3b810e0adfb889ad407a8c79a84dbe
cfg80211: accept no-op interface mode changes

Removing it from 2.6.30 (and disabling HW encryption) makes rt2500usb work in 
2.6.30. There are more changes to that code in next kernels so the patch 
cannot be removed from newer kernels. However, disabling it (by changing "if 
(change)" to "if (1)" in net/wireless/nl80211.c) and disabling HW encryption 
makes rt2500usb work even in 2.6.34-rc1.

There seems to be another (third!) problem. With 2.6.29, DHCP works on the 
first DHCPDISCOVER. With 2.6.30, it takes two to three DHCPDISCOVERs to get a 
reply. With 2.6.34-rc1, it takes three to five. After one reboot with 
2.6.34-rc1, it did not work at all with this in log:
phy0 -> rt2500usb_set_device_state: Error - Device failed to enter state 3 
(-16).

-- 
Ondrej Zary

      reply	other threads:[~2010-03-19 21:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 21:46 rt2500usb broken since 2.6.29 Ondrej Zary
     [not found] ` <880c1631003181451r7669428ctee7adc867979bc25@mail.gmail.com>
2010-03-18 21:52   ` [rt2x00-users] " Luis Correia
2010-03-18 22:04   ` Ondrej Zary
2010-03-18 22:10     ` Luis Correia
2010-03-19 15:01       ` Ondrej Zary
2010-03-19 21:31         ` Ondrej Zary [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201003192231.50287.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=buga@loide.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox