Bug#593183: broken rt2860 support after upgrade to 2.6.32-18 from -16
- To: Raphael Geissert <geissert@debian.org>
- Cc: 593183@bugs.debian.org
- Subject: Bug#593183: broken rt2860 support after upgrade to 2.6.32-18 from -16
- From: Moritz Muehlenhoff <jmm@inutil.org>
- Date: Thu, 18 Jul 2013 18:49:50 +0200
- Message-id: <[🔎] 20130718164950.GB24907@inutil.org>
- Reply-to: Moritz Muehlenhoff <jmm@inutil.org>, 593183@bugs.debian.org
- In-reply-to: <CAA7hUgEcTFtQPwCMR9AMXH2WpHznsBsD4VWUUq+TdJggTJz0jA@mail.gmail.com>
- References: <AANLkTinPaCrEZ1BP_wOf7LWR8JkuQEetbA=v1NJvdZEN@mail.gmail.com> <1283683983.5323.464.camel@localhost> <201009051009.31132.geissert@debian.org> <201009271418.06283.geissert@debian.org> <20111127070904.GA14891@elie.hsd1.il.comcast.net> <CAA7hUgEcTFtQPwCMR9AMXH2WpHznsBsD4VWUUq+TdJggTJz0jA@mail.gmail.com>
On Thu, Jan 19, 2012 at 01:23:31AM -0600, Raphael Geissert wrote:
> Hi Jonathan,
>
> On 27 November 2011 01:09, Jonathan Nieder <jrnieder@gmail.com> wrote:
> > Raphael Geissert wrote:
> >> I just tried with a visible AP (using the same crypto settings) and it works.
> >> So, the changes to the module appear to only break support for hidden APs.
> >
> > Thanks for finding this. As Ben mentioned, Realtek's original
> > rt2860sta driver was abandoned in favor of rt2800pci from the rt2x00
> > project[*] (the usual risk of using a staging driver).
>
> Indeed, the rt2800 driver works like a charm compared to the rt2860sta :)
>
> > However, many people still use squeeze. So I would be happy to see
> > the regression you discovered fixed. Some questions in that vein:
> >
> > 1. Just to check, can you still reproduce the trouble with the
> > latest squeeze kernel?
> >
> > 2. Can you bisect? The squeeze kernel is on the "squeeze" branch
> > of git://git.debian.org/kernel/linux-2.6.git; the usual
> > "make silentoldconfig; make; fakeroot -u make deb-pkg" should work
> > to build each revision one wants to test.
>
> I currently don't have enough disk space to accommodate such a setup,
> but will at least try with a live image or something similar.
> Back when I was affected I remember checking the different changes
> made to the driver, but they were all made in one big patchset that
> was added in a single commit, IIRC.
>
> HTH. I will anyway try to free up some space.
>
> Cheers, and thanks for picking up such an old bug :)
Has this been tracked down or shall we go ahead and close the bug?
Cheers,
Moritz
Reply to: