From: "John W. Linville" <linville@tuxdriver.com>
To: Rog?rio Brito <rbrito@ime.usp.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc
Date: Sat, 7 Jun 2008 10:30:51 -0400 [thread overview]
Message-ID: <20080607143051.GA3096@tuxdriver.com> (raw)
In-Reply-To: <20080607005227.GA1739@ime.usp.br>
On Fri, Jun 06, 2008 at 09:52:27PM -0300, Rog?rio Brito wrote:
> First of all, thanks John for taking the time to reply to my
> message.
>
> On Jun 06 2008, John W. Linville wrote:
> > On Sun, Jun 01, 2008 at 04:30:01PM -0300, Rogério Brito wrote:
> > > I have an iBook G3 600MHz combo (late 2001 model, powerpc) with a USB
> > > wireless card rt2x00 that doesn't work.
> > >
> > > I just compiled a fresh 2.6.26-rc4 kernel and it can't get a lease from
> > > the access point, even though it is able to see the access point.
> > >
> > > The userland here is Debian unstable (sid) and I can perform some of the
> > > steps in the direction of configuring the interface. For instance, the
> > > following works (I am using wep as the encryption system with other systems
> > > running under Linux, but, unfortunately, EVEN disabling encryption for the
> > > sake of the tests doesn't help here):
> (...)
> > > (Here, it is unable to grab an IP addess from the access point)
> >
> > You should set the key _before_ setting the essid.
>
> Thanks, but that unfortunately doesn't seem to help. :-(
>
> I have taken dmesg "snapshots" of my system together with many other
> information regarding how it is configured and I put it at my
> homepage, at <http://www.ime.usp.br/debug/>.
404
> >From what I am seeing, it looks like the bug mentioned in
> <http://bugzilla.kernel.org/show_bug.cgi?id=9388>, but I don't get the
> stack trace that is present there and I'm just trying to use WEP
> instead of WPA or anything fancier.
Did you apply this patch?
http://bugzilla.kernel.org/attachment.cgi?id=14384
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-06-07 15:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 19:30 [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito
2008-06-01 22:58 ` Rogério Brito
2008-06-06 16:23 ` John W. Linville
2008-06-07 0:52 ` Rog?rio Brito
2008-06-07 14:30 ` John W. Linville [this message]
2008-06-08 0:11 ` Rogério Brito
2008-06-08 1:02 ` Rogério Brito
2008-06-08 10:42 ` Ivo van Doorn
2008-06-08 21:35 ` Rogério Brito
2008-06-08 22:02 ` Ivo van Doorn
2008-06-08 22:09 ` Rogério Brito
2008-06-08 22:30 ` Rogério Brito
2008-06-09 0:15 ` Rogério Brito
2008-06-11 9:36 ` Rogério Brito
2008-06-11 13:43 ` John W. Linville
2008-06-12 4:15 ` Rogério Brito
2008-06-11 18:21 ` Ivo van Doorn
2008-06-12 4:23 ` Rogério Brito
2008-06-12 17:40 ` Ivo van Doorn
2008-06-13 4:06 ` Rogério Brito
2008-06-13 4:52 ` Rogério Brito
-- strict thread matches above, loose matches on Subject: below --
2008-06-20 17:57 [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd) Rogério Brito
2008-06-20 19:58 ` Rogério Brito
2008-06-25 19:49 ` Rogério Brito
2008-08-04 13:26 ` Ivo van Doorn
2008-08-07 17:01 ` [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc Rogério Brito
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=20080607143051.GA3096@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rbrito@ime.usp.br \
/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