Comments on: Using the Linksys WPC54G (v2) and WPA with Ubuntu Gutsy http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/ Dave puts the "Ek" in "Geek" Wed, 19 Nov 2008 11:34:29 +0000 http://wordpress.org/?v=2.6.3 By: bOnE http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-837 bOnE Sun, 30 Mar 2008 16:34:21 +0000 http://blog.eksfiles.net/?p=24#comment-837 I little comment. I've seen several posts in other forums using this and a few other tutes and I see this problem a lot: ndiswrapper reporting invalid driver. This is a simple step but one I missed myself so I felt the need to post it here. Go back through LSTINDS.INF and triple check that you got all tnet1130 and tnet1130x instances changed to uppercase. Post 5 from Steve sums it up perfectly. If you miss even one, you'll get 'LSTIND.INDS: Invalid Driver'. Other than that, perfect! Many, many thanks Dave for the hard work. It saved me a ton of time and work! bOnE I little comment. I’ve seen several posts in other forums using this and a few other tutes and I see this problem a lot: ndiswrapper reporting invalid driver.
This is a simple step but one I missed myself so I felt the need to post it here. Go back through LSTINDS.INF and triple check that you got all tnet1130 and tnet1130x instances changed to uppercase. Post 5 from Steve sums it up perfectly.
If you miss even one, you’ll get ‘LSTIND.INDS: Invalid Driver’.
Other than that, perfect! Many, many thanks Dave for the hard work. It saved me a ton of time and work!
bOnE

]]> By: Aaron http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-426 Aaron Sat, 08 Mar 2008 23:22:46 +0000 http://blog.eksfiles.net/?p=24#comment-426 Thank you so much.... I have been struggling for hours getting my Linksys WPC54G Ver2 running with WPA on Ubuntu 7.10. Followed instructions to the letter and worked perfectly Thank you so much…. I have been struggling for hours getting my Linksys WPC54G Ver2 running with WPA on Ubuntu 7.10. Followed instructions to the letter and worked perfectly

]]> By: Dave http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-384 Dave Thu, 06 Mar 2008 03:47:01 +0000 http://blog.eksfiles.net/?p=24#comment-384 Good point, Steve. I updated the instructions. Thanks! Good point, Steve. I updated the instructions. Thanks!

]]> By: steve http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-383 steve Thu, 06 Mar 2008 03:19:38 +0000 http://blog.eksfiles.net/?p=24#comment-383 Wow, fast work Dave! one more slight change and I think it will be perfect -- the appearance of the tnet1130 references in the LSTINDS.INF file isn't always to a .sys extension. So I actually just did a search on "tnet1130" and made the changes to uppercase for all references. Therefore: "Then edit the LSTINDS.INF file and change all instances of “tnet1130” to “TNET1130”, and all instances of “tnet1130x” to “TNET1130X”. Thanks again! Wow, fast work Dave!

one more slight change and I think it will be perfect — the appearance of the tnet1130 references in the LSTINDS.INF file isn’t always to a .sys extension. So I actually just did a search on “tnet1130″ and made the changes to uppercase for all references. Therefore:

“Then edit the LSTINDS.INF file and change all instances of “tnet1130” to “TNET1130”, and all instances of “tnet1130x” to “TNET1130X”.

Thanks again!

]]> By: Dave http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-379 Dave Wed, 05 Mar 2008 20:05:18 +0000 http://blog.eksfiles.net/?p=24#comment-379 Steve - thanks for the corrections. Changing the name of tnet1130x.sys to uppercase was't necessary for me, but it certainly doesn't hurt to make that change, and I added it to the instructions. As for your other comment, my (poor) assumption when I wrote these instructions was that you'd already changed to the directory containing your driver files before trying to execute that command. I've now clarified that instruction. Thanks again for your comments. Glad the instructions were helpful. Steve -

thanks for the corrections. Changing the name of tnet1130x.sys to uppercase was’t necessary for me, but it certainly doesn’t hurt to make that change, and I added it to the instructions. As for your other comment, my (poor) assumption when I wrote these instructions was that you’d already changed to the directory containing your driver files before trying to execute that command. I’ve now clarified that instruction.

Thanks again for your comments. Glad the instructions were helpful.

]]> By: steve http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-377 steve Wed, 05 Mar 2008 19:20:49 +0000 http://blog.eksfiles.net/?p=24#comment-377 I found that the mixed case problem applied to tnet1130x as well as tnet1130, so I applied the same process: renamed tnet1130x.sys to TNET1130X.sys and changed all locations to match in LSTINS.INF. Also had a problem with the instructions: sudo ndiswrapper -i LSTINDS.INF since you suggest putting the flies in /home/yourusername/linksys, it should read: sudo ndiswrapper -i /home/yourusername/linksys/LSTINDS.INF Unfortunately if you didn't make that correction, ndiswrapper does a partial installation and won't accept retyping it correctly. In that case you need to do a: sudo ndiswrapper -r lstinds Then retype correctly and install again. This wasn't easy to figure out because the ndiswrapper man page in Ubuntu is pathetic. I guessed at the -r , and it happened to work! Thanks however for puting these instructions up there -- it worked for me! I found that the mixed case problem applied to tnet1130x as well as tnet1130, so I applied the same process:

renamed tnet1130x.sys to TNET1130X.sys and changed all locations to match in LSTINS.INF.

Also had a problem with the instructions:

sudo ndiswrapper -i LSTINDS.INF

since you suggest putting the flies in /home/yourusername/linksys, it should read:

sudo ndiswrapper -i /home/yourusername/linksys/LSTINDS.INF

Unfortunately if you didn’t make that correction, ndiswrapper does a partial installation and won’t accept retyping it correctly.

In that case you need to do a:

sudo ndiswrapper -r lstinds

Then retype correctly and install again. This wasn’t easy to figure out because the ndiswrapper man page in Ubuntu is pathetic. I guessed at the -r , and it happened to work!

Thanks however for puting these instructions up there — it worked for me!

]]> By: Dave http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-10 Dave Sun, 20 Jan 2008 22:25:26 +0000 http://blog.eksfiles.net/?p=24#comment-10 After consulting this <a href="https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper" rel="nofollow">how-to</a>, I realized that I may have omitted a step--one that I didn't realize was required. Try typing this at a command line: sudo ndiswrapper -m Supposedly, this adds an Alias to associate wlan0 to ndiswrapper in modprobe.d. After consulting this how-to, I realized that I may have omitted a step–one that I didn’t realize was required. Try typing this at a command line:

sudo ndiswrapper -m

Supposedly, this adds an Alias to associate wlan0 to ndiswrapper in modprobe.d.

]]> By: daytimer045 http://blog.eksfiles.net/2007/12/30/using-the-linksys-wpc54g-v2-and-wpa-with-ubuntu-gutsy/#comment-9 daytimer045 Sun, 20 Jan 2008 19:40:41 +0000 http://blog.eksfiles.net/?p=24#comment-9 Made it through Ndiswrapper, thank you and can make a connection manually. However, it won't persist after reboot. What should be in the /etc/network/interfaces file? Made it through Ndiswrapper, thank you and can make a connection manually. However, it won’t persist after reboot.

What should be in the /etc/network/interfaces file?

]]>