Yeah, sorry to hear. I guess you should think about getting a different cheap wireless card and check if it is supported first. I find that a lot are these days. Anyway, netcfg: I was a bit skeptical about this whole idea of non-automatic wireless via command line and specifically configuration files, but I must say, it's pretty nice overall. There are occasionally a couple glitches here and there (like just now, it didn't notice that my connection dropped and the profile stayed on. Solved by just turning it off/on manually.), but in the whole, this is the most solid, most automatic network system I've used. Setting up profiles, it turns out, is pretty much as simple as typing in your network information into your normal network manager. netcfg is also conveniently tied into rc.conf, so you can just dump your common networks in there in order of preference and you're done. I love this -- networkmanager still frequently connects to the neighbours' wireless rather than my own. Also, just as something to get you started maybe, attached is a small script that scans for networks in the area and returns you their names + encryption status. This script could certainly use some improvement, but maybe you'll find some use for it if you decide to go the netcfg way eventually. Cheers, -AT On Wed, Apr 29, 2009 at 8:53 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
Thomas Bächler wrote:
David C. Rankin schrieb:
Listmates,
My second Arch box is now complete (well almost:-) This time a desktop box with a zytel wireless lan adapter using the TI acx chipset and its firmware 2 is the acx111_2.3.1.31/tiacx111c16 firmware slice. The card is detected and works fine it think... I can open kwifimanager and it has my access point associated and I can watch the generic packets blip by and watch the strength meter do its thing, but I cannot authenticate :-(
Short answer: Throw that thing away!
Thomas, all,
I think I may be dead in the water with this card using WPA under Linux. The problem is that there isn't a *single* windows driver that provides WPA capabilities for the card. Specifically, in order to provide wpa access, this wireless card relies on the following files for basic wireless with WEP:
FwRad16.bin FwRad17.bin FwRad19.bin TNET1130.INF TNET1130.sys
And then requires the following for WPA access:
odysseyIM3.inf odysseyIM3.sys
The odyssey driver is a separate add-on driver that windows uses as a "wrapper" for the tnet1130 driver to provide added WPA capabilities.
ndiswrapper will load the tnet1130 driver without complaint, and the ndiswrapper -l show the driver properly installed. The odyssey driver will load, but ndiswrapper -l shows the driver is "not a valid driver". Further, even though the tnet1130 driver loads, the essid cannot be manipulated with iwconfig, so I'm doubtful that even the basic wireless will work under ndiswrapper.
Unless somebody has a stroke of genius and can let me know "hey, Rankin, you are going about this all wrong!" I think the case is pretty much closed on this one...
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com