netdev - Re: [PATCH 0/2] d80211, rt2x00: fixes

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 13 Dec 2006 17:28:58 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Ivo Van Doorn <ivdoorn@...il.com>
Cc:	Dan Williams <dcbw@...hat.com>, Jiri Benc <jbenc@...e.cz>,
	"John W. Linville" <linville@...driver.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 0/2] d80211, rt2x00: fixes

On Wed, Dec 13, 2006 at 10:28:15PM +0100, Ivo Van Doorn wrote:
> That is definately the rt2500 legacy driver and _not_ the rt2x00 driver.

Yeah I just noticed that a few minutes ago.  I had been trying out both
to see how they worked, and I left the old module loaded by accident.

> Correct, that is why those iwpriv commands are the clear evidence
> you are not using rt2x00 but rt2500 legacy. Check which driver is loaded
> rt2500 means legacy
> rt2500pci means rt2x00.

Yep I am now poking with the wpa_supplicant again, getting other
interesting messages from it.

I will try to give a report on how my system behaves with the 2x00
driver soon since apparently some of my testing was with the wrong
driver.  Oops. :)

--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html