Craig's ACX100 HowTo

The latest version of this document can always be found here: http://www.houseofcraig.net/acx100_howto.php

Commentary and suggestions about this howto go here:

Everyone, please read the Updates

Quick Links: Downloads• Installing• Testing• Configuring• Compiling• Knoppix 3.3 Live CD• Removing the 'Leaked' binary driver

Introduction

Updates

Firmware

Directions

Downloading and unpacking the module and firmware

1. Go to the downloads area and right-click the correct file for your running kernel version, choosing a 'save as' option and remembering where you put the file(s), from windows I suggest c:\windows\temp or from linux use /usr/local, repeat this process for the firmware as well
2. If you're using a CardBus (pcmcia) card, remove it at this time. If you're using a PCI card and you've been mucking around with other modules for this card trying to make it work, be aware this document assumes no other modules are loaded or are even present on the machine for this card, so it's time to undo any of that business that you've done.
3. If need be, exit windows and boot up Linux. I'm assuming that when you boot Linux, you end up with a nice graphical interface with menus, icons and the like. Once there, you'll need to open a shell (also called terminal, or in kde a Konsole) window from the main menu and switch to the root user: type su -, the "-" in there is important. You'll be asked for the root password, and you'll have to type it "blind" as no characters will show up as you type, then hit enter, you should now see the name "root" in the prompt, or when you type whoami it should say root. When this saga finally ends for you, type exit to return to your normal user name, or just close the shell window. If you're not using a graphical interface then I'm assuming you will know what to substitute for the tasks below. I'm also assuming that if you downloaded these files to c:\windows\temp that your windows partition is going to be available to you in Linux, these days that's normally set up for you during the Linux install automatically
4. Now, change the current working directory, using the example directories from above you would type: cd /mnt/windows/windows/temp or cd /usr/local
5. Unpack the module, type tar zxf acx100_pci-v0.2.0pre7-`uname -r`.tar.gz, obviously, if you downloaded an older version other than 0.2.0pre7 then replace the 0.2.0pre7 with the version you downloaded, eg: 0.2.0pre3, 0.2.0pre2, etc. The ` character surrounding "uname -r", is called a "backtick" it's the key to left of the "1" key. If this command generates several lines of output, one of which contains "cannot open", and you're sure you don't have any typos, you have the wrong module for your setup and must start over
6. Unpack the firmware, type: tar zxf acx100_firmware.tar.gz
7. If all the above completes without error, proceed to installing the module and firmware

Installing the module and firmware

1. Move the module to a typical place for networking modules, type: mv acx100_pci.o /lib/modules/`uname -r`/kernel/drivers/net, notice the backtick surrounds "uname -r" again here.
2. Create a directory for the firmware to live in, type: mkdir /lib/modules/acx100_fmwe
3. Whether you're using the firmware downloaded from here or your own re-named firmware, move it to that directory, type: mv *.BIN /lib/modules/acx100_fmwe
4. (Knoppix users: skip this step)Using a text-editor like gedit, kedit, or kate, open the file /etc/modules.conf, type: kedit /etc/modules.conf &, substitute your editor of choice for kedit, if you're not using a windowing system, then type: vi /etc/modules.conf, hit the "i" key to go to edit mode, do your editing and when finished, hit esc to go back to command mode, and then type :x to save the file and exit vi, if you feel that you've hopelessly screwed things up, type esc for command mode and :q! to quit without saving, then start over. Add this line: options acx100_pci use_eth_name=1 debug=0x01 firmware_dir=/lib/modules/acx100_fmwe to the end of the file and save it. If you're using a PCI card, you'll need to add this line as well: alias eth0 acx100_pci, if there is already an alias there for eth0 and you're sure you have another ethernet/lan card in your machine, use eth1 instead and use eth1 as your devicename in all instructions that follow!. CardBus (pcmcia) users don't need or want this line, the hotplug system will load the module
5. Knoppix users: instead of the step above, you'll need to create the file /etc/modutils/acx100_pci, type: kedit /etc/modutils/acx100_pci then add this line: options acx100_pci use_eth_name=1 debug=0x01 firmware_dir=/lib/modules/acx100_fmwe to the file and save it. If you're using a PCI card, you'll need to open /etc/modutils/aliases and add this line to the end of it: alias eth0 acx100_pci, if you're sure you have another active ethernet/lan card in your machine, use alias eth1 acx100_pci instead and use eth1 as your devicename in all instructions that follow!. CardBus (pcmcia) users don't need or want this line, the hotplug system will load the module, either way you must type: update-modules when you finish creating that file.
6. Update your module dependencies file, type: depmod -a, this may take a while to complete depending on your machine's cpu/disk speed, be patient. Some distros will return an error with something like "not an ELF file" and pointing at the *.BIN firmware files, this is ok and will not hurt anything. If that bothers you create your "acx100_fmwe" directory somewhere else, like under /usr and be sure to substitute that path in both the commands above and in the commands that follow. Important: If you get unresolved symbol errors pointing to the acx100_pci.o module, you *may* need to compile the module on your own machine, it's possible that the downloaded module will not work for you, I now recommend you continue on and see what happens. Otherwise, see the compiling section and go from there, you don't need to undo anything that you've already done. When finished the compiling section return here and start over with step #1 and answer "y" if you are asked if you want to overwrite anything
7. Check for the presence of a reference to this module in your module dependencies file, type: grep -i acx100 /lib/modules/`uname -r`/modules.pcimap, three lines, all beginning with "acx100_pci" should be returned, again, note the backticks in this command. The correct output will look like this (pre7 and later, earlier versions may not have the 3rd line identified by the "0x00009066" in it):

   acx100_pci           0x0000104c 0x00008400 0xffffffff 0xffffffff 0x00000000 0x00000000 0x00000000
   acx100_pci           0x0000104c 0x00008401 0xffffffff 0xffffffff 0x00000000 0x00000000 0x00000000
   acx100_pci           0x0000104c 0x00009066 0xffffffff 0xffffffff 0x00000000 0x00000000 0x00000000
   

   Note that if other lines are returned from this command and they don't begin with "acx100_pci", but something else with acx100 and "sta" in it, you have installed the leaked binary at some point and need to find and move it and repeat the depmod -a before continuing, see appendix a for how to do that and then return here and continue, if duplicate lines are returned from this command and you just happen to be running Mandrake 9.2 (or later?), you'll need to move their built-in v0.1h module out of the modules tree, I suggest this, type: mv /lib/modules/`uname -r`/kernel/3rdparty/acx100/acx100_pci.o.gz /root. Then, repeat step #6 above
8. If you're using a CardBus card (pcmcia), insert the card now, the module should be automatically loaded by the hotplug system. If you're using a PCI card, insert the module by hand, type: modprobe acx100_pci. Either way if you get errors to the effect that acx100_pci can't be found, and you're sure there's been no typos, then first try repeating the depmod -a command, if you still don't have those 2 lines, then your distro may require all modules to be gzipped, type: gzip /lib/modules/`uname -r`/kernel/drivers/net/acx100_pci.o and repeat the previous 2 steps
9. Check if the module got loaded, type: lsmod | grep acx100_pci, the | character is called a "pipe" and is uppercase on the backslash key on my machine. One line should be returned beginning with acx100_pci, if not, check the log for clues as to why, type: tail -n 20 /var/log/messages, there are myriad reasons outside the scope of this document as to why this would fail, chief among them being that you don't actually have an acx100 card, and perhaps the second most popular reason being your firmware was "not found" which is usually caused by incorrect naming of firmware files in the /lib/modules/acx100_fmwe directory, see the section in the readme about what files may need to be renamed if you are using your own firmware. "no such device" errors should not be ignored, try searching/posting on LinuxQuestions.org to see if your card is indeed an acx100-based card
10. If all the above completes without error, proceed to testing the module

Compiling your own module and/or using your own firmware

1. You'll need to have the kernel source installed for your distribution, from a root console type: ls -L /lib/modules/`uname -r`/build/include/linux. If a large number of files show up, you're good. If you get an error, use your distro's package management to install the kernel source, do not download what appears to be a match from kernel.org, virtually all distros modify the kernel source in some way, use your distro's source package only.
2. Note: I no longer recommend using cvs for this project.Next, you'll need to have cvs installed, to see if it is, type cvs in a root console, if you get an error of the "not found" variety, you'll need to install the cvs package for your particular distribution.
3. Change to the /usr/local directory: type cd /usr/local
4. Download the latest source tarball (bz2) from Andreas' page (<< this opens a new window in your browser), follow his instructions for unpacking it: tar jxf filename.tar.bz2, and make sure to use the source directory created by unpacking the file in place of "acx100" below, eg: acx100-0.2.0pre7_plus_fixes_14 instead of acx100). Do not unpack the source code using Windows, the end-of-line characters are different in Windows than Linux, and are not compatible. (thanks to Jakob Rohde for that tip)
5. If you're going use your own firmware, you'll need to get/open the windows driver (usually a .zip file) for your card and find/copy the *.BIN firmware files to the firmware directory under acx100 making sure to rename the files if necessary, as indicated in this section of the readme, more than likely your radio is the rfmd. The files (version 1.9.3.e) found on my SMC card's windows' driver cd were RADIO0d.BIN, RADIO11.BIN and WLANGEN.BIN, they were already named correctly and these are the files in the firmware download at the end of this document.
6. Note: If you're downloading anything newer than 0.2.0pre6_plus_fixes_10, you'll need to use the 1.9.8.b firmware instead. The older firmware just simply refuses to connect with the later versions of the driver.
7. Change to the acx100 source directory, type cd acx100
8. Compile the source, type: make
9. In preparation for installation, change to the firmware directory, type cd firmware
10. Copy those firmware files to the src directory, type: cp *.BIN ../src
11. In preparation for installation, change to the src directory, type: cd ../src
12. If all the above completes without error, proceed to installing the module and firmware

Testing the module

1. Check if the wireless device exists, type: ifconfig -a, at least 2 devices should be listed, one is always going to be "lo", one may be your wired ethernet card and the other should be your wireless card, eth0 or eth1, it will look something like this:

   eth0    Link encap:Ethernet  HWaddr 00:03:2F:05:44:D2
             ... other lines will appear  here ...
   	Interrupt:11 Base address:0x4800
   

   The only things of importance at this point are that the card has an interrupt and a base address and that the HWaddr on the first line matches the MAC address of your card which is printed somewhere on the card or it's packaging or is viewable from windows.
2. Give the wireless card some life, type: ifconfig eth0 192.168.2.10 mtu 576 substituting your device name, eth0 or eth1 and substituting a valid address for your router or access point, for instance if your router's address is 192.168.1.1, use 192.168.1.10 and so forth.
3. Check wireless extensions, type iwconfig, a listing for your wireless device should be returned and should look something like this:

   eth0      v0.1g  ESSID:""
             Mode:Ad-Hoc  Channel:1  Cell: 54:57:7B:51:10:86
             Bit Rate=11Mb/s   Tx-Power:18 dBm
             Encryption key:off
             Link Quality:34/0  Signal level:-191 dBm  Noise level:-225 dBm
             Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
             Tx excessive retries:0  Invalid misc:0   Missed beacon:0

   Don't worry about the details here, if iwconfig returns something like the above, you're good, if it returns something with "eth0 no wireless extensions", and your wireless card is eth0, you've got kernel problems, most likely caused by compiling your own kernel and leaving out something rather important, in any case, the solution to that problem is outside the scope of this document. If you get something like "command not found" when you type iwconfig, then you'll need to install the wireless-tools package for your distro (this is likely to happen to Mandrake 9.1 and 9.2 users as the wireless tools don't appear to be a default package). Using your distro's 'software installer', search on the string: "wireless-tools" and install the package that is found. Every distro I have installed (except FreeBSD 5.2) has an already-compiled package for the wireless-tools, so it's highly likely that it is on one of your CD's, do not download and compile the wireless-tools package from sourceforge.net, it's very likely the version will not match correctly to your distro and this will cause all sorts of problems that others will have a difficult time diagnosing, again, you have been warned: use your distro's wireless-tools package only.
4. Set up the wireless parameters for your particular environment, type: iwconfig eth0 mode managed channel x essid xxxxxxxx, replacing if necessary, "eth0" with eth1, and using your router's ssid name and channel # in place of the x's
5. If you're using WEP, set up the key, type: iwconfig eth0 key xxxx-xxxx-xx essid xxxxxx for a 64bit hex key, or use iwconfig eth0 key s:yourkeyhere essid xxxxxxxx for an ascii key, the essid parameter needs to be repeated at the end of most iwconfig commands.
6. Check if the config "sticks", type: iwconfig, and the output should be similar to this, with your router's ESSID and Channel displayed and the Access Point being your router's MAC address. The correct Encryption key should be displayed as well.

   eth0    v0.1g  ESSID:"wireless_hoc"  Nickname:"Thinkpad"
             Mode:Managed  Channel:8  Access Point: 00:03:2F:06:F4:13
             Bit Rate=22Mb/s   Tx-Power:18 dBm
             Encryption key:0ACD-41AF-22
             Link Quality:104/0  Signal level:-139 dBm  Noise level:-243 dBm
             Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
             Tx excessive retries:0  Invalid misc:0   Missed beacon:0
   

   If you've got "Access Point: 00:00:00:00:00:00" then something's wrong, I suggest setting encryption on the router to a 64bit hex key and repeating the previous step using the new key. Also, try a couple more iwconfig eth0 essid xxxxxxxxx commands about a second or two apart, this is a quirk of the card/driver, and I theorize, turns on the radio. You should see the "DATA" light blink once about a half-second or so after each command.
7. Set up a route to your router from this device, type: route add default gw 192.168.2.1 eth0, substituting your router's ip address and if need be, your device's name (eth0 or eth1).
8. Try to ping your router, type: ping -c 4 192.168.2.1 substituting your router's ip address for the 192.168.2.1. Output will look like this:

   PING 192.168.2.1 from 192.168.2.98 : 56(84) bytes of data.
   64 bytes from wrouter (192.168.2.1): icmp_seq=1 ttl=127 time=2.71 ms
   64 bytes from wrouter (192.168.2.1): icmp_seq=2 ttl=127 time=0.601 ms
   64 bytes from wrouter (192.168.2.1): icmp_seq=3 ttl=127 time=0.609 ms
   64 bytes from wrouter (192.168.2.1): icmp_seq=4 ttl=127 time=0.723 ms
   64 bytes from wrouter (192.168.2.1): icmp_seq=5 ttl=127 time=0.569 ms

   If you get errors with "unreachable" in them, you most likely used the wrong address for your router in either this command or the previous route command, or your encryption key is wrong, or you need to type: iwconfig eth0 essid xxxxxx again, waiting a moment before attempting the ping, this is a quirk of the card.
9. Using a text-editor as described above, open the file /etc/resolv.conf. Make this: nameserver 192.168.2.1 the first line, substituting in your router's ip address, and save the file.
10. Now, here's the big one, try to ping a host on the internet, type: ping -c 4 www.yahoo.com, or some other host of your choice.
11. If all the above completes without error, proceed to configuring the interface

Configuring the Interface

Until then, here's yet-another list to follow for getting the card setup automagically at boot and on a return from suspend, if applicable.

1. Using a text editor as described above, open /etc/sysconfig/network-scripts/ifcfg-eth0, susbstituting eth1 if need be. Here's what mine looks like for this card:

   DEVICE=eth0
   BOOTPROTO=static
   IPADDR=192.168.2.98
   NETMASK=255.255.255.0
   NETWORK=192.168.2.0
   BROADCAST=192.168.2.255
   MTU=576
   ONBOOT=no
   MODE=Managed
   CHANNEL=8
   RATE=22M
   KEY=xxxx-xxxx-xx
   ESSID=myessid_name
   #IWPRIV='set_debug 0x00'
   

   Lines beginning with a "#" are comments and ignored, I left "#IWPRIV" in there as an example of how to use iwpriv for a particular interface, the line works, but the line we added to /etc/modules.conf takes care of setting the debug level, so it's superfluous. You may also have noticed that the ONBOOT setting is "no", this prevents the attempted configuring of the device before the PCMCIA sub-system has loaded, the hotplug system should take care of loading the module when it detects the card. If you're using a PCI card, you'll want to set ONBOOT to yes.
2. You'll also need to verify the contents of your /etc/sysconfig/network file, here's what mine looks like:

   	NETWORKING=yes
   	FORWARD_IPV4=false
   	HOSTNAME=Thinkpad
   	DOMAINNAME=localdomain
   	GATEWAY=192.168.2.1
   

   Of most importance in this file is the GATEWAY setting which should match the IP address of your wireless access point or router. One more thing, on my notebook, an IBM Thinkpad 600, I had to modify the line in /etc/sysconfig/apmd to read "PCMCIARESTART=yes", in order to for a resume from suspend to work as expected.
3. That's it! Yep, that should be all you need to do to bring this card up at boot, although remember the quirk, additional iwconfig eth0 essid xxxxxx commands may be required, even when iwconfig returns all correct info, until you see "Associated!" in your /var/log/messages, you're not associated, again it's my theory that this kicks the radio on.

1. Using a text editor as described above, open /etc/rc.d/rc.inet1. Here's what you should setup for this card, if your device ended up being eth1, then scroll down a bit furthur to the same section for eth1, be careful which devicename you're editing, you don't want to screw up eth0's settings if your acx100 device is eth1:

   # Edit these values to set up your first Ethernet card (eth0):
   IPADDR="192.168.2.98"  # REPLACE with YOUR IP address!
   NETMASK="255.255.255.0" # REPLACE with YOUR netmask!
   ...
   ...
   ...
   # Edit the next line to point to your gateway:
   GATEWAY="192.168.2.1" # REPLACE with YOUR gateway!

2. I must admit, I'm still looking for the "proper" place to put the wireless settings in Slackware, until I find it, I'm using the work-around that follows for both CardBus and PCI cards:
3. Open (again) your /etc/modules.conf file in a text editor, and add this line: post-install acx100_pci /usr/sbin/setup_acx100
4. You guessed it, /usr/sbin/setup_acx100 is going to be a shell-script that gets executed after the module is loaded, so in your text editor, create a new file and add these lines to it

   #!/bin/sh
   iwconfig eth0 mode Managed rate 22M key xxxxxxxxxx essid xxxxxxxx
   sleep 2
   iwconfig eth0 essid xxxxxxx
   

   the sleep and extra essid command seem to be necessary, as time marches on, this will probably not be true, for now, you should probably use them.
5. Save the file as /usr/sbin/setup_acx100
6. Make the file executable, type: chmod u+x /usr/sbin/setup_acx100
7. Before you ask: yes, I'm aware of the /etc/rc.d/rc.netdevice file that can get created, and I'm also aware of /etc/rc.d/rc.inet1 being another possible place to issue iwconfig's from. So far, these have not been working and the post-install line in /etc/modules.conf has, I'll update when I get it all figured out

1. First, login as the root user
2. Next, you'll need to create a file in /etc/sysconfig/network-scripts named ifcfg-eth0 (or ifcfg-eth1 if this is your 2nd ethernet device) Knoppix 3.3 users, do not allow this device to become wlan0, there will be all sorts of conflicts and confusion created due to Knoppix 3.3's native support of wlan-ng devices, you have been warned, if your acx100 device is wlan0 (as reported by iwconfig or ifconfig), then double-check the contents of your /etc/modutils/acx100_pci file, making sure use_eth_name=1 is there.
3. in that file(ifcfg-eth0 or eth1) you'll need the following lines, heed the comments beginning with "#":

   	DEVICE=eth0 # if your acx100 is the 2nd ethernet device, use "eth1" instead
   	IPADDR=192.168.2.98 # use an ip address appropriate for your access point's ip range
   	NETMASK=255.255.255.0 # you shouldn't need to change this
   	NETWORK=192.168.2.0 # should be IPADDR (above) with 0 as the last number
   	BROADCAST=192.168.2.255 # should be IPADDR (above) with 255 as the last number
   	ONBOOT=no # set to "no" for CardBus cards and "yes" for PCI cards
   	

4. Next, you'll need to open your /etc/network/interfaces file and add your acx100 into it like this:

   	# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
   
   	# The loopback interface
   	# automatically added when upgrading
   	auto lo eth0 #note the addition of eth0 here, it's the acx100 card
   	iface lo inet loopback
   
   	# this is your acx100 card
   	iface eth0 inet static # if your acx100 is the 2nd ethernet device, use "eth1" instead
   		address 192.168.2.98 # see IPADDR above in step #3
   		netmask 255.255.255.0 # ditto
   		network 192.168.2.0 # ditto
   		broadcast 192.168.2.255 # ditto
   		gateway 192.168.2.1 # should be the ip address of your wireless access point or router
   		mtu 576 # this is still necessary
   
   		# these are the wireless settings for your acx100 card
   		wireless-mode Managed
   		wireless-rate 22M
   		wireless-channel 8 # use your own channel #
   		wireless-key xxxx-xxxx-xx # use your own WEP key here, or "off"
   		wireless-essid myessidname # use your own ssid name here, enclose in quotes if it contains any spaces
   	

5. You'll also need to verify that the file: /etc/modutils/acx100_pci exists,and contains this one line:

   		options acx100_pci firmware_dir=/lib/modules/acx100_fmwe debug=0x01 use_eth_name=1
   	

6. After all the above is accomplished, run update-modules as root from a console

Downloads

Essential Firmware

• Firmware (v1.9.8.b)

Pre-Compiled Kernel Modules

Fedora Core 1

• uname -r: 2.4.22-1.2115.nptl
• gcc -v: 3.3.2

• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

Red Hat 9.0

• uname -r: 2.4.20-8
• gcc -v: 3.2.2

• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

Mandrake 9.2

• please read this first
• uname -r: 2.4.22-10mdk
• gcc -v: 3.3.1

• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

Mandrake 9.1

• uname -r: 2.4.21-0.13mdk
• gcc -v: 3.2.2

• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

Mandrake 9.0

• uname -r: 2.4.19-16mdk
• gcc -v: 3.2

• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

Slackware 9.1

• uname -r: 2.4.22
• gcc -v: 3.2.3

• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

Slackware 9.0

• uname -r: 2.4.20
• gcc -v: 3.2

• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

SuSE 9.0 - Contributed by Rudi Pittman

Here's his site for the absolute latest acx100 project's SuSE 9.0 RPM's: SuSE 9.0 RPM's, be sure to read any documentation there before downloading and installing the RPMs and enjoy.

Knoppix 3.3 dated 2-9-2004(Debian testing/unstable)

• uname -r: 2.4.24-xfs

• "Live CD" users, this is the Knoppix 3.3 Live CD download for the release dated 2-9-2004: acx100-0.2.0pre7-knoppix-3.3-2.4.24-xfs.tar.gz please see Appendix B for instructions, substituting the correct filename: acx100-0.2.0pre7-knoppix-3.3-2.4.24-xfs.tar.gz where appropriate
• 0.2.0pre7 for Knoppix 3.3 (2-9-2004) installed to the hard drive

Knoppix 3.3 dated 11-19-2003 or 11-14-2003(Debian testing/unstable)

• uname -r: 2.4.22-xfs
• gcc -v: 3.3

• "Live CD" (and Knoppix-STD) users, please see Appendix B
• 0.2.0pre7
• older versions:
• 0.2.0pre6
• 0.2.0pre5
• 0.2.0pre4
• 0.2.0pre3
• 0.2.0pre2

Appendix A: finding and moving the leaked binary driver

1. change to the top-level modules directory, type: cd /lib/modules/`uname -r` (those are backticks)
2. find and verify the signature of the leaked binary, type: grep 'v0.9.0.3a' $(find -name *acx*100*.*) if anything is returned, you have the leaked binary installed and now must uninstall it. if nothing is returned and you're sure there's been no typos, continue where you left off in the installing section, but first return to the directory you were in: type cd /mnt/windows/windows/temp or cd /usr/local depending on which one you were in
3. move the leaked binary to /root, type: mv $(grep 'v0.9.0.3a' $(find -name *acx*100*.* | grep -v 'acx100_pci.o') | cut -d ' ' -f 3) /root, do not type this more than once
4. it should now be in your /root directory
5. if, for some reason the above does not move it out of the modules directory tree, then you'll have to do it manually using konqueror, or your favorite file manager. The file's name you're looking to move should have been returned in item #2 above
6. return to the directory you were in: type cd /mnt/windows/windows/temp or cd /usr/local depending on which one you were using
7. return to the installing section and continue starting with item #5

Appendix B: Using the Open Source Acx100 Driver with the Knoppix 3.3 Live CD

1. Download and save the file above using your browser, remembering where you put it. Windows users should save it to c:\windows\temp, linux users should save it to /tmp, make sure you preserve it's filename.
2. If Knoppix is not currently running, stick the CD in and reboot, when it's finished booting, you can close the "welcome" window and open a shell (the button on the taskbar that is a computer screen with a shell on it). Do not su to become the root user, all this can and should be done by the user named "knoppix".
3. Unpack the archive, windows downloaders type: tar Pzxf /mnt/hda1/windows/temp/acx100-knoppix-3.3.tar.gz, you may have to type: mount /mnt/hda1 first. Linux downloaders type: tar Pzxf /tmp/acx100-knoppix-3.3.tar.gz
4. Open and edit the settings, type: kedit /home/knoppix/Desktop/acx100/scripts/my_settings, using the comments there as your guide, make any necessary changes, save the file, and select file/quit to exit kedit and return to the shell.
5. Start the interface, type /home/knoppix/Desktop/start_net it should finish with Interface has been set up successfully, hit enter to regain the prompt.
6. Run a quick test, type: ping -c 4 cnet.com, you should see 0% packet loss.
7. Optionally, You can now delete the acx100-knoppix-3.3.tar.gz file you downloaded, you can check back here from time to time for new versions if you like.
8. In order for any of what you've just done to be there the next time you boot up the Knoppix Live CD you'll need to click the knoppix button on the taskbar and select configure/save KNOPPIX configuration, making sure to check the save all the files on the desktop option and making sure to un-check the network settings option screenshot. Upon subsequent boots of knoppix you'll need to have at least this much on the command line: knoppix myconfig=scan, along with any other options you normally use such as lang= or dma, etc...
9. Make sure when you boot Knoppix that the media that you saved your settings on is available prior to booting, this can be a hard drive, memory stick, floppy, usb pen drive, etc...
10. Now all you have to do whenever you boot the Live CD is click the icon on the Desktop labelled start_net, if for some reason you need to stop the interface, use the other file on the Desktop named (you guessed it) stop_net
11. That's it, time to check your email from Knoppix!