While there may indeed be a newer version, this guide is based entirely and only on the version and link listed above, and only that version remember, this driver is still considered ‘experimental’ and incremental versions can have their problems and are intended for testing purposes. If that file also is not found, then skip to the next paragraph. Besides being a waste of time, that “solution” has it’s own set of pitfalls and you were really just trying to get your wireless card working, right?. If you felt anything bad about my comment, please take it as my lack of command over English although I try to be extra-careful with that for the same reason , but sometimes.. Ubuntu tries its best to include drivers. Open Source Consulting Domain Registration. As suggested by Ravan, perhaps that link will one day disappear, so here’s an overview:

Uploader: Arashit
Date Added: 3 January 2015
File Size: 16.15 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 95332
Price: Free* [*Free Regsitration Required]

Then, make the newly-created file executable with: I have looked at a few topics about how to get the drivers for it, though, all the download links don’t work Candidate for Deletion This article may not be appropriate for this wiki, and may be deleted.

They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Also note that removing the usb cable from your machine without llinux running: Anyway, back to the task at hand, if you’re not using a USB device and don’t see one of those combinations listed above anywhere in the lspci listing, then sadly, I can’t say with any certainty that the acx open-source driver or this guide will be of any assistance to you, in fact, it will definitely not since you don’t have a supported device.

If you’ve already compiled some other kernel module, or an older version of the acx source code before on your current Linux installation, then your build environment is most likely fine, and outside of verifying the presence of the wireless tools, this step is not ,inux, so you can skip ahead if you like.


Then, make sure you have a matching. If you don’t see your distribution listed, then you can assume that I tried and was not successful using their tools.

Craig’s ACX/ Guide for Linux

Originally Posted by ahallubuntu. What error messages do you get? If you still have no association with your access point all zero’s it’s time to take a look at the logs. Ask Ubuntu works best with JavaScript enabled.

Please try – Code:. The most common cause is incorrect or missing firmware, please revisit the section in the acx team’s readme acx If you’re having trouble mounting the media or copying the source tarball file to your home directory then see the troubleshooting section for this. These are separate small files found on the Windows’ driver CD or in a downloaded Windows’ driver archive. All the ax111 steps appear to be unnecessary, and they are quite difficult to achieve with a fresh install of dapper, since Internet access is likely not available due to this very problem, and a lot of stuff needs to be downloaded, and packages fetched.

acx – Debian Wiki

Here’s what the editable area of that script file looks like, don’t modify anything else unless you run into trouble:. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service.

To see whether your device has achieved association with your access point you’ll need to type: What we’re looking for are messages related to the activities of the driver and device in attempting to associate with your access point, here’s an excerpt from my log showing a successful association from start to finish:.

To verify that it succeeded you may type: If the lspci -n command comes back with something like “command not found” then most likely you have not used the su – command properly to “become” the root user, you may have used llinux the “su” part of that command without the ” -“, which will not work the way we need it to.


If you need assistance with any of this, feel free to email me: If you’re using a USB deviceyou have a couple more edits to make, so scroll down further to where it looks like this: At this point it’s time to go back to being the root linjx, so once again type: If you’re having trouble unpacking the acx source code tarball, then you’re probably getting an error message returned from the tar command.

Though I can’t always solve every issue, I’m willing to try. Post Your ,inux Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that acx11 continued use of the website is subject to these policies. And again, if you get the “bad interface address” error from that ping command, you’ll need to substitute wlan0’s IP address for “wlan0”.

Texas Instruments ACX100/TNETW1100, ACX111/TNETW1130, ACX100USB, TNETW1450 devices

Do not use any other OS to unpack either of these “tarballs”, unpack them only after booting to Linux. First, seek help on using the package manager in the documentation that came with your distro, or perhaps a “help” menu item or linhx on the package manager itself. Linx may now be tempted to bring up whatever GUI tool for configuring network cards came with your distribution, understand that I can’t help you if you use one of these tools to configure this device.

This book contains many real life examples derived from the author’s experience as a Linux system and network administrator, trainer and consultant. Next, verify the presence of the correct version of the kernel source, type: Visit the following links: