This means you have another network connection in the same machine that is up and running and also using the default gateway you’ve assigned to your wireless card. If you are re- compiling the source, start with make clean and then make , followed by make install. My connection on windows is installed as a WeP, so i entered my password as a wep to, but that doesn’t work, and when i try entering it as a leap the connection symbol dissapears and ubuntu starts freezing, like firefox doesn’t work and other programs to, like shutdown comes really late or just freezes. If your card was identified as a c: Users who are still using 2. You’ll need to do the appropriate research for your distribution in order to determine how to bring up their ‘Package Manager’. Otherwise your device will have a hard time telling them apart.

Uploader: Tojalrajas
Date Added: 18 July 2011
File Size: 55.58 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 48885
Price: Free* [*Free Regsitration Required]

There are a number of reasons why pinging your wireless access point would fail. I’m not going to repeat here all of the fine documentation that’s been widnows in your distribution to help you learn to mount and umount various media in Linux. 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.

Craig’s ACX/ Guide for Linux

If you have achieved association, but your pings to your wireless access point still come back “unreachable”, then possible causes are:. To see whether your device has achieved association with your access point you’ll need to type: If you’ve verified the presence of your kernel-source and you’re using a 2.


My output looks like this:. What I will say is that virtually all distros that use packaging have provided packages for the kernel-source, development utilities and the wireless-tools pcmcia-cs also. Report them [ Once windowss have become the wincows user, I would caution you to not go outside the bounds of the instructions below, you can and should experiment with commands as your “normal” user, but don’t experiment as root.

Texas Instruments physical id: In keeping with this warning, I do not want to hear from people trying to use earlier versions and WEP with their acx devices. I’m still working on a new page that will apply to this new driver.

Fedora Core 4 users who have updated to the latest kernel version, this means you. 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 accx100 from start to finish:.

Successful output looks like this:. First and foremost, and by far the most common, is that your card failed to associate with your access point. You may now be wondering why this older version of the driver hasn’t rendered your card functional.

It’s virtually impossible these days to find that the tar program has not been installed, you would have had to dig deep to eliminate it at install time, and you would most likely have been warned not to do that.

Check your hotplug scripts [ Understand though, that if any ethernet interface in your machine is afx100 DHCP, that the contents of that file will re-written when windiws interface obtains it’s DHCP ‘lease’.


You’ll also need make and if gcc is installed, most likely make is also, but just to be sure type: Also note that removing the usb cable from your machine without first running: Otherwise, if you’d prefer to use the firmware from your own Windows’ driver CD then this is what you need to know: Can you now click the little Network Manager icon and connect?

You will also need to make the same edit in the file: The previous names acd100 dashes are nearly universal across distros for their respective package names. Donations to the project will be used to further it’s development, testing and feature-set, so please, if you are able, make a donation.

Finally, you should know that I am not a developer, nor even a member of the acx project, just someone trying to windoas. Once you have prepared the kernel source, return to the acx top-level source directory, type: Now, verify the presence of the wireless-tools, type: Check to see if: Let’s take Network Manager acz100 of the mix. 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 only the “su” part of that command without the ” -“, which will not work the way we need it to.

So, your interface is working!