On 1/29/07, Mick <[EMAIL PROTECTED]> wrote:
My only consolation is that this fault is not intermittent. :-(
Here's what happened. I emerged a different (to my tried & tested rt2x00-9999
wireless driver). Then I uninstalled rt2x00-9999, but I couldn't get the new
driver to work. So, I unmerged it, remerged rt2x00-9999 (this is a CVS
package)
Bingo. :)
Since this is a CVS package, the version that you just now installed
is different than the one that you did have installed - CVS packages
go out to the live development tree, pull the latest and greatest
version of the development source code (never, ever, ever guaranteed
to work), and use that.
So - possible solutions:
1. Figure out the date/time of the emerge of the *successful*
rt2x00-9999 package using genlop, then check out the CVS source tree
as of that date, and build/install by hand
2. Work with the rt2x00 developers to figure out the problem and get
it corrected in the current version
3. Try what I'm currently doing with my rt2500 card (using the
rt2x00-999 package compiled from CVS on Wed Jan 3 20:39:53 2007,
according to genlop) - manually set the ESSID, AP, and encryption
settings on the card, then issue a /etc/init.d/net.ra0 start/restart
command.
BTW - If you do figure out the date/time of the successful CVS
package, let me know, and I'll try that one on my laptop, see if it
fixes my problems. :)
HTH
-James
--
gentoo-user@gentoo.org mailing list
