Oh no... I wish I'd noticed that post! Those definately don't work... I got one a few months back that was branded as an N-Gear product, but exactly the same thing... blue transparent plastic, round-sh shaped plastic box that it came in... yea, it's a piece of junk. In my experiments I needed a powered USB hub to even get it recognized... then it turns out that the manufacturer ID is actually invalid, so the only way to get the driver to actually recognize it is to modify the original kernel driver source code and add in the manufacturer and unit ID's to the list that's there... and after all of that, the stupid thing still only worked about 50% of the time... it would cut in and out, do randomly odd things... in general I came to the conclusion that instead of paying 10 bucks for a piece of... I'd just pay 30 and get a proper Linksys one. Well worth it in my mind. Not sure what that other poster was talking about, and maybe they've legitimately fixed the chip ID problem, but this is yet another one of those "you get what you pay for" scenarios as far as I'm concerned.

Check your dmesg outputs though and see... perhaps it's not the same problems that I ran into... but it does sound awfully familiar...

-Rob