In order to use the acx100 driver with Linux 2.6 you'll need a complete 2.6
source tree and have to build the module "in-tree". You'll have to:

1. Create a directory drivers/net/wireless/acx100 in your 2.6 source tree.
2. Copy the files
- src/Makefile
- src/*.c
- include/*.h
from the acx100 sources into drivers/net/wireless/acx100 in your 2.6 tree.
3. Add a line reading "obj-m += acx100/" to the bottom of
drivers/net/wireless/Makefile .
4. Then build your kernel as usual, the acx100 driver will be built as module
(acx100_pci.ko). Make sure you have the required 2.6 module userspace
package (module-init-tools) and enjoy

If you cannot Wget the files as above, copy them from the CD if you have the Windows install disc. Or if you have a windows boto partition, download in windows and then mount the windows partition in Gentoo and copy the required files over.

mkdir /usr/src/linux-2.6.0-test6-mm1/drivers/net/wireless/acx100/firmware and copy the files (that have been downloaded above) WLANGEN.BIN RADIO0d.BIN and RADIO11.BIN into this directory

That's all I needed to do. If anyone has problems with this, I will try and help as much as possible. But if you follow this post you should really be ok.

Regards
Gary

P.S. If anyone knows how to run the start_net script at boot up (EG, as a /etc/init.d script) I would be grateful._________________No one means all he says, and yet very few say all they mean, for words are slippery and thought is viscous.

Last edited by GaryMercer on Thu Jan 22, 2004 10:36 pm; edited 1 time in total

I do hope this is useful as it took me ages to find this info out and work out what to do with it. _________________No one means all he says, and yet very few say all they mean, for words are slippery and thought is viscous.

1. Create a directory drivers/net/wireless/acx100 in your 2.6 source tree.
2. Copy the files
- src/Makefile
- src/*.c
- include/*.h
from the acx100 sources into drivers/net/wireless/acx100 in your 2.6 tree.
3. Add a line reading "obj-m += acx100/" to the bottom of
drivers/net/wireless/Makefile .
4. Then build your kernel as usual, the acx100 driver will be built as module

Hi,
There are 2 thing are not clear for me, that maybe you can explain:
1) at point 2 should I copy all the file in acx100 dir or I have to create also the subdirs src and include ???
2) when I use make menuconfig I don't see the acx100 option. Is it right?

Then edit the file /usr/src/linux/drivers/net/wireless/Makefile and add

obj-m += acx100/

Then do your make menuconfig. You will not see an acx100 option in here, however when you do make to make your bzImage file you will see acx100 being compiled into the kernel._________________No one means all he says, and yet very few say all they mean, for words are slippery and thought is viscous.

Holy crap finally! I had given up on that one. The only winblows box I have is because of the AG-520 card I have. Thanks for the info. I'll have to sneaker net the files over of course, but I'll try this out right away._________________The Fueley
0x54 0x68 0x65 0x20 0x46 0x75 0x65 0x6C 0x65 0x79

Oh wait a minute. I see something about acx100. Is that the chipset? Cause I know that my DWL-AG520 has the Atheros Chipset. Does this tut still apply or am I still stuck?_________________The Fueley
0x54 0x68 0x65 0x20 0x46 0x75 0x65 0x6C 0x65 0x79

Yeah, I never had much luck with mad-wifi. I can get it installed no prob. Just getting the setttings to stick is the problem. I enter the settings and get no error. Then I display the settings and they are still blank. I can never get the essid especially to stick. It can never find my AP either. Even if it was sitting next to the AP. The modules are or were loaded too. I gave up on it._________________The Fueley
0x54 0x68 0x65 0x20 0x46 0x75 0x65 0x6C 0x65 0x79

i installed the drivers for my d-link 520+ card, i used acx100-0.2.0pre6_plus_fixes_15 that version and the start_net script worksm iwconfig shows my card, i can ping to the ip of the card but when i try to ping to another ip it say's destination host unreachable!

if test -z "$SYNC"; then echo "sync not found. Go get a sane Linux system. Bailing..."; exit 1; fi
if test -z "$INSMOD"; then echo "insmod not found. Go get a sane Linux system. Bailing..."; exit 1; fi
if test -z "$IFCONF"; then echo "ifconfig not found. I can insert the module for you, but you won't be able to configure your interface."; CONTINUE=ASK; fi
if test -z "$IWCONF"; then echo "iwconfig not found. Make sure it is installed. The interface might work without, though."; CONTINUE=ASK; fi

if test ! -r "$MODULE_AT"; then echo "Module not found or not readable. Have you built it? This script expects it to be at ../src/acx100_pci.o, relative to the script's location. Bailing..."; exit 1; fi

# FIRMWARE_AT has to be given as an absolute path!!
FIRMWARE_AT="${SCRIPT_AT}/../firmware/"

# check whether either of the two required main firmware files is
# available
if test ! -r "$FIRMWARE_AT/WLANGEN.BIN" -a ! -r "$FIRMWARE_AT/TIACX111.BIN"; then echo "Firmware not found or not readable. Have you placed it in the firmware directory or run make extract_firmware once? This script expects it to be at ../firmware/WLANGEN.BIN (or ../firmware/TIACX111.BIN for the ACX111 chip), relative to the script's location. Bailing..."; exit 1; fi

So I presume that the cardbus is working fine, and it recognizes my network card. Has anyone encountered this problem? How did you get around the insmod error. I have tried different version of acx100 driver, but still get the same error.

My start_net script just sits and thinks for ages and other scripts i've tried (/etc/init.d/net.ath0) just return errors. I'm going to try a straight ethernet cable connection to my router as soon as i can get a long enough cord, but i really want wireless running.

Any suggestions are appreciated._________________Zak: Luke's making a 3D interface for Linux"
Jon G: "Yeah, Luke's making a 3D user interface with Logowriter"
Jon H: "He's only got 99 shapes to work with"
Jon G: "And they're all turtles."

I think i should be using different drivers as my card is a WG311 v2, not v1. I may end up changing the card itself if I cant get it working. Can you recommend a good card that the madwifi drivers work really well for?_________________Zak: Luke's making a 3D interface for Linux"
Jon G: "Yeah, Luke's making a 3D user interface with Logowriter"
Jon H: "He's only got 99 shapes to work with"
Jon G: "And they're all turtles."

I think i should be using different drivers as my card is a WG311 v2, not v1. I may end up changing the card itself if I cant get it working. Can you recommend a good card that the madwifi drivers work really well for?

would these instructions also work for the DWL-120+? from what i can find out the 120+, 520+ and 650+ are essentially the same chip but just different interface types (usb, pci, cardbus). can anyone verify that the 120+ works?