Voila un tuto plus clair, j´espère que tu n´est pas anglophobe :
Note:
1. Tested with kernel 2.6.12 ok with WEP
2. kernel was built fresh with PCI hotplug options. Perhaps redundant.
3. (Important) In kernel configuration,you should turn on "Module unloading"
and "Forced module unloading" at Loadable module support" section.
Possibly ok without them, depending on how reliable this driver is.
Old versions occasionally lost connection to the access point and a user
manually had to restart the network. I so far have no such a problem yet.
4. firmware needs to be installed in /lib/firmware
5. original start_net, stop_net scripts were modified.
--------------------------------------------------
---------------------------
Installation:
1. Extract acx-20060215.tar.bz2 in any directory of your choice.
eg)/usr/local/src/acx
2. Copy a firmware you got from
http://acx100.erley.org/acx_fw/acx1xx.htm
in /lib/firmware
3. Copy start_net and stop_net to /usr/local/src/acx/script/ and remove
start_net.sh and stop_net.sh. They are outdated.
4. Building out of kernel tree is easier.
"By Per Bjornsson <perbj@stanford.edu>"
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%
If you´re building for the currently running kernel, build the modules with
the command
make -C /lib/modules/`uname -r`/build M=`pwd`
Install the modules (must be root for this step, so use ´su´ if that´s your
preferred method of doing root stuff) with
make -C /lib/modules/`uname -r`/build M=`pwd` modules_install
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%
5. Change directory to /usr/local/src/acx/script/ and open "start_net".
Change details of your network, including ESSID, WEP etc. DHCP and WEP work
well.
6. ./start_net
OR, if you prefer the joy of tedious work, come back to /usr/local/src/acx
and
insmod acx.ko
Check with
lsmod |grep acx
If nothing appears, something is wrong. Possibly firmware is. Change to
/lib/firmware and check against the message from
dmesg | tail -30 (or so)
You will see something similar to this one.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$$$$$$$$$$$$$$$$$$$$$$$$$$$
acx: this driver is still EXPERIMENTAL
acx: reading README file and/or Craig´s HOWTO is recommended, visit
http://acx100.sf.net in case of further questions/discussion
acx: compiled to use 32bit I/O access. I/O timing issues might occur, such as non-working firmware upload. Report them
running on a little-endian CPU
PCI module v0.3.35 initialized, waiting for cards to probe...
PCI: Found IRQ 10 for device 0000:00:0b.0
PCI: Sharing IRQ 10 with 0000:00:09.2
acx: found ACX111-based wireless network card at 0000:00:0b.0, irq:10, phymem1:0xD7020000, phymem2:0xD7000000, mem1:0xd9888000, mem1_size:8192, mem2:0xda9c0000, mem2_size:131072
initial debug setting is 0x000B
using IRQ 10
requesting firmware image ´tiacx111c16´
acx: firmware image ´tiacx111c16´ was not provided. Check your hotplug scripts
requesting firmware image ´tiacx111´
acx_write_fw (main/combined):0
acx_validate_fw (main/combined):0
requesting firmware image ´tiacx111r16´
acx: firmware image ´tiacx111r16´ was not provided. Check your hotplug scripts
acx: can´t load radio module ´tiacx111r16´
.....
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$$$$$$$$$$$$$$$$$$$$$$$$$$$
OK, even if I got it working, dmesg returns some unhappy messages.
At least, in my case, ´tiacx111´ firmware is there. I´m not sure
what the radio module is, but without it, it still works ok.
In fact, I tested with FwRad16.bin from Win XP driver CD and it
totally messed things up!! So, don´t worry even if radio module
is missing.
If no mathing firmware is found at all, you know what firmware is required by now. Try other firmware from
http://acx100.erley.org/acx_fw/acx1xx.htm
Copy it to /lib/firmware and run ./start_net again.
./start_net
wlan0 deconfigured, module unloaded.
using wlan0.
Module successfully inserted.
Setting rate to 22M auto.
Setting channel 1.
Going to try to join or setup ESSID default.
Setting mode to Managed.
Setting key to 123456789A, algorithm open.
Waiting for association...10 9 8 7 OK.
Attempting to use /sbin/dhcpcd for DHCP, this may take a moment...OK.
7. run iwconfig and if everything was well, you will see something like:
wlan0 IEEE 802.11b+/g+ ESSID:"default" Nickname:"acx v0.3.35"
Mode:Managed Channel:6 Access Point: 00:40:05:28:DC:A2
Bit Rate:22Mb/s Tx-Power=15 dBm Sensitivity=1/3
Retry min limit:7 RTS thr:off
Encryption key:1234-5678-9A Security mode:open
Power Management:off
Link Quality:44/100 Signal level:21/100 Noise level:0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Having Access Point: 00:00:00:00:00:00 means something is wrong.
Many factors might be involved. It can be your kernel, driver, firmware
or start_net script configuration.
8. (Optional)
For slackware 10.X (or older/newer) users, following entry to
/etc/rc.d/rc.local will start the network at boot time. Handy, it will be.
- Bring acx100 device up
cd /usr/local/src/acx/script
./start_net