My WLAN-Card is a D-Link DWL-G650+ B1 (You can check your revision by looking at the backside
of your D-Link card. Mine is H/W:B1) with the Texas Instruments ACX 111 Chip.
My Laptop is a Toshiba Satellite and my access point is a
Trendnet TEW-431BRP.

After your kernel was compiled you should now have a compiled module
acx_pci.ko in /usr/src/linux/drivers/net/wireless/acx.

If you only have to compile the module you just have to do a

/usr/src/linux/make modules

Edit your /boot/grub/grub.conf if needed:

vi /boot/grub/grub.conf

4. Reboot

reboot

5. Install the firmware for the DWL-G650+

To prevent using the wrong firmware, I recommend using the drivers from the driver cd shipped with your card.
I really got annoyed about the driver confusion on the D-Link Webpage and the naming of the cards..
and i got to know that especially the DWL-G650+ card is not sold outside Europe, so you won't get
the correct driver from ftp.d-link.com...
I would also like to place the compiled module and the firmware
somewhere else than in the kernel tree:
mkdir /lib/modules/2.6.7/net
cp -r /usr/src/linux/drivers/net/wireless/acx /lib/modules/2.6.7/net
mkdir /lib/modules/2.6.7/net/acx/firmware
mount /dev/cdrom /mnt/cdrom
cd /lib/modules/2.6.7/net/acx/firmware
cp /mnt/cdrom/Driver/Drivers/Win2000/GPLUS.bin .

IMPORTANT: Case sensitive..

mv GPLUS.bin TIACX111.BIN

You'll have to do this, because the start_net script searches for TIACX111.BIN.

In case you have two .bin files in the "Driver/Drivers/Win2000/" directory, you
have to copy both (eg. FwRad16.bin & FwRad17.bin) into your firmware dir and
rename the FwRad17.bin file to WLANGEN.BIN. Keep FwRad16.bin as is!
cp /mnt/cdrom/Driver/Drivers/Win2000/FwRad* .
mv FwRad17.bin WLANGEN.BIN

6. Install the scripts for configuring and starting up your new wlan0 device

The Changelog for acx100-0.2.0pre8_plus_fixes_14 says, that WEP
support has been removed for the acx111 based wlan cards...
I will try using version acx100-0.2.0pre8_plus_fixes_13 and post my
expreriences to this thread later...

--------------------

I hope this works for you.

Greetings

reznor666

Last edited by reznor666 on Sun Jul 11, 2004 2:40 pm; edited 1 time in total

I recompiled my kernel for some reason and went to start the wireless card and poof all my scripts and firmware was missing. I'm currently working on a permanent fix for this that should even get one through a kernel upgrade. I have the start_net script finished, but I'm kind of struggling with where all the files should be located to be "correct". I know they should go somewhere in /usr/local since this is something that I'm doing myself. So that limits the options.

Unfortunately I won't be around for a few days but when I get back hopefully I can get the locations up and running. I'm thinking right now that eventually I/we could even turn this into an ebuild. When I do get back I want to see if this module will work as a standard wireless nic, ie. not having to use the start_net script to get it working. Anyone tried this?

I recompiled my kernel for some reason and went to start the wireless card and poof all my scripts and firmware was missing. I'm currently working on a permanent fix for this that should even get one through a kernel upgrade. I have the start_net script finished, but I'm kind of struggling with where all the files should be located to be "correct". I know they should go somewhere in /usr/local since this is something that I'm doing myself. So that limits the options.

Unfortunately I won't be around for a few days but when I get back hopefully I can get the locations up and running. I'm thinking right now that eventually I/we could even turn this into an ebuild. When I do get back I want to see if this module will work as a standard wireless nic, ie. not having to use the start_net script to get it working. Anyone tried this?

chris

What? Sure it works as a standard wireless nic, I use the Gentoo Wireless startup script from another thread on this forum. Works like a charm.

Also, default place the module looks for firmware is "/usr/share/acx/", so put it there. Or, you could place it in your "/etc/modules.autoload.d/kernel-2.6" like this:

Code:

acx_pci FIRMWARE_DIR="/some/directory/here/"

Which would work as well.

Also, the latest version of this driver can always be found in the latest love-sources, so I recommend checking that out as well...

VERY IMPORTANT AS WELL, READ THIS!

The acx driver is NOT, repeat NOT, SMP safe. That is the reason you had to edit Makefile is because the driver knows this, and doesn't put itself in the menu if SMP is enabled.

Also, the way the author edited the file was not so good, since it meant that the acx driver will be compiled without taking heed of the .config file. A better way is to edit the Kconfig file and removing the "!SMP" bit in the ACX driver's line, which would ensure the driver shows up when you do `make menuconfig`.

(Its in the networking section next to all the other Wireless drivers)

It's really not very important where the acx_pci.ko (kernel-module) or the start_net/stop_net scripts are located.
Important is to set the right paths in the start_net script, since relative
paths are used.
Take a look at the script start_net:
There are two variables that define the location of the firmware
and the kernel module:

SCRIPT_AT --> where the start_net script is located
MODULE_AT --> for the kernel module
FIRMWARE_AT --> for the firmware

and all paths to the module and firmware are set relative to the path of the start_net script:

So, the script "searches" for the module in "../acx_pci.ko" which is one level lower in the directory hierarchy relative to where the script is located.
The same for the firmware. But in this case the variable points to a directory "../firmware" one level lower relative to the script.

reznor666_________________My opinions may have changed,
but not the fact that I am right.
_________________

I think you guys should look here:
http://www.linuxquestions.org/hcl/showproduct.php?product=1125
to see a little guide that works with WEP and don't really care if you update your kernel.
I've also written a little script that deides if the card is inserted or not and if it is inserted it configurates it automatically, this sequence is run every time I boot my laptop.

I think you guys should look here:
http://www.linuxquestions.org/hcl/showproduct.php?product=1125
to see a little guide that works with WEP and don't really care if you update your kernel.
I've also written a little script that deides if the card is inserted or not and if it is inserted it configurates it automatically, this sequence is run every time I boot my laptop.

... SNIP! ...

NO, NO, NO!

Your script uses NDISWRAPPER! NDISWRAPPER is evil! It should only be used in cases where there is no alternative native linux driver available, which is most definatly not the case here!

I used this method instead of loading with modules.autoload because I'm using a laptop, so hotplug takes care of loading the module for me when I insert the card. I put the usb part in just in case I may need it someday.

now working good!! I have acx100 working with wireless-config and ifplugd. Sweet!!!!!

however, same as when I had it working, I am unable to retrieve an ip address via dhcp.

what on earth is going on?!/where else could I be looking for messages?

[edit]weird, seems to have resolved itself by continually stopping/starting and fiddling about. wonder if it was perhaps my double checking of the settings on the router that caused the router to reboot[/edit]

The reason why I use Ndiswrapper is that the ACX111 is very beta and doesn't perform well. My laptop operates very hot and due to that my card gets hot and then stops transmitting and not performing well at all. If i use Ndis it doesn't care about the temperature. I know this isn't ideal. But is there someway to make my laptop work cooler(fan working harder)_________________//Festiz