From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Simon Raffeiner (SCC)" <simon.raffeiner@kit.edu>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: Ralink RT5390/RT5370 no longer works on more recent kernels
Date: Mon, 9 Feb 2015 09:41:43 +0100 [thread overview]
Message-ID: <20150209084142.GA15797@redhat.com> (raw)
In-Reply-To: <54D81624.9070705@lwfinger.net>
On Sun, Feb 08, 2015 at 08:06:28PM -0600, Larry Finger wrote:
> On 02/07/2015 10:54 AM, Simon Raffeiner (SCC) wrote:
> The second thing to verify is that your configuration contains the line
> "CONFIG_RT2800USB_RT53XX=y". This parameter is marked as depending on
> EXPERIMENTAL, and I'm not sure that Ubuntu enables those parameters in their
> kernels. Again as the module was loaded, I think your kernel is OK, but that
> parameter is something to check.
I suggest check rfkill as well.
> Finally, if your kernel configuration is OK, you will probably need to
> bisect the problem between v3.18 and v3.16. I have a device that uses
> rt2800usb, but it is not a 53XX. FWIW, it works.
Between 3.16 and 3.18 we have only those rt2x00 changes:
cfd9167 rt2x00: do not align payload on modern H/W
664d6a7 wireless: rt2x00: add new rt2800usb device
01f7fee rt2800: correct BBP1_TX_POWER_CTRL mask
ac0372a rt2x00: support Ralink 5362.
9baa3c3 PCI: Remove DEFINE_PCI_DEVICE_TABLE macro use
6a06e55 wireless: rt2x00: add new rt2800usb devices
d4150246 drivers/net/wireless/rt2x00/rt2x00dev.c: remove null test before kfree
df6e633 rt2x00: Use dma_zalloc_coherent
19dcb76 rt2x00: do not initialize BCN_OFFSET registers
ddb4055 rt2x00: change order when stop beaconing
88ff2f4 rt2x00: change default MAC_BSSID_DW1_BSS_BCN_NUM
ba08910 rt2x00: change beaconing setup on RT2800
283dafa rt2x00: change beaconing locking
57eaeb6 net: wireless: rt2x00: rt2x00mac.c: Cleaning up uninitialized variables
They could be reverted, even on top of 3.19-rc7, instead of doing
full bisection. But this could be also mac80211 issue, then bisection
will be necessary to figure out this bug.
Stanislaw
next prev parent reply other threads:[~2015-02-09 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 16:54 Ralink RT5390/RT5370 no longer works on more recent kernels Simon Raffeiner (SCC)
2015-02-09 2:06 ` Larry Finger
2015-02-09 8:41 ` Stanislaw Gruszka [this message]
2015-02-09 8:52 ` Yegor Yefremov
2015-02-09 8:54 ` [rt2x00-users] " Jakub Kicinski
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=20150209084142.GA15797@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=simon.raffeiner@kit.edu \
--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;
as well as URLs for NNTP newsgroup(s).