linux-kernel - Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080625194937.GA13636@ime.usp.br>
Date:	Wed, 25 Jun 2008 16:49:38 -0300
From:	Rogério Brito <rbrito@....usp.br>
To:	Ivo van Doorn <ivdoorn@...il.com>
Cc:	"John W. Linville" <linville@...driver.com>,
	linux-kernel@...r.kernel.org, rbrito@....usp.br
Subject: Re: [2.6.26-rc4] Problems with rt2x00 USB interface on powerpc (fwd)

Hi, Ivo and John (again).

On Jun 20 2008, Rogério Brito wrote:
> On Jun 20 2008, Ivo van Doorn wrote:
> > 
> > > Did you receive my earlier message (attached here for reference)? I'm
> > > willing to experiment with the driver a little bit and I hope that the
> > > information that I have provided so far is helpful to chase the reason
> > > why the driver doesn't work on PowerPC.
> > 
> > Sorry I have been quite busy with other things.
> 
> I'm terribly sorry for that, since I would like the driver to work with
> the USB stick still in the 2.6.26 release (since that's what some
> distributions will probably use).

Just for your information, I just compiled the -rc7 kernel on x86-64 (where
rt2500usb works if I boot with kernel 2.6.25) and still doesn't work (I'm
not even mentioning here PowerPC).

The "doesn't work" part means that the usual procedure of bringing the
interface up, setting the key (I'm using WEP), setting the essid (at which
point it should already be associated with the AP) and then using a dchp
client on the interface doesn't get a DHCP lease.

The DHCP client just sits there trying to send a broadcast message and
there is no response. After the key is set and after the essid is set, I
see that it is not associated with the AP, even though I get messages on
dmesg that it has associated and then the association was lost (I don't
have the dmesg log here on this computer).

Interestingly, I can see the AP if I do an "iwlist wlan0 scan" command.

I would really like to help with this problem (and have it fixed) before
the actual release of 2.6.26. Since I saw that you had some activity in
your git tree.

To John: would you like me to test any other tree with my hardware, like
the wireless-next tree? Would it make any difference?

Regards, Rogério Brito.

-- 
Rogério Brito : rbrito@...ckenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/