ACX111 Help.

[sturung]

Can anyone tell me if it is possible to get the ACX100 driver running on an HP ZV6000 with FC5.x86_64 as a module out of the kernel tree? The card is a USR5410 and was bought around 2/2.5 years from 08/29/2006. So far I have followed the guides on the ACX100 driver site, as well as the guide for FC4 from the search; every time I attempt to activate the card the system either gives some error, or locks up completely mostely the latter though. Another thing on the site for the FC4 tutorial why is it that on the select wireless device step his/hers says Texas Instruments... where as when I do mine all it says is acx? Any help is appreciated.

[JaRaEeZ]

Hi there,

Firstly run lspci as root (su -) & you may see (actually should see) the following

02:09.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface

the Texas part is the chipset (T1). I have this card running perfectly using ndiswrapper along with the windoze drivers. You will not get them working with the ACX 100 drivers but maybe with the ACX 111 (I couldn't when I first tried a couple of years back) Once I manged to get the card working correctly I have never had any problems with ndiswrapper (using 256 WEP) connecting to a USR AP. Heres a copy of the output using iwconfig as root

wlan0     IEEE 802.11g  ESSID:"XXXXX"  Nickname:"emachine.local"
          Mode:Managed  Frequency:2.462 GHz  Access Point: xx:xx:xx:xx:xx:xx
          Bit Rate=125 Mb/s   Tx-Power:10 dBm   Sensitivity=0/3
          RTS thr=4096 B   Fragment thr=4096 B
          Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx   Security mode:restricted
          Power Management:off
          Link Quality:100/100  Signal level:-50 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Is there any particular reason for wanting to use the ACX driver?

[sturung]

Originally Posted by JaRaEeZ

Hi there,

Firstly run lspci as root (su -) & you may see (actually should see) the following

02:09.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface

the Texas part is the chipset (T1). I have this card running perfectly using ndiswrapper along with the windoze drivers. You will not get them working with the ACX 100 drivers but maybe with the ACX 111 (I couldn't when I first tried a couple of years back) Once I manged to get the card working correctly I have never had any problems with ndiswrapper (using 256 WEP) connecting to a USR AP. Heres a copy of the output using iwconfig as root

wlan0     IEEE 802.11g  ESSID:"XXXXX"  Nickname:"emachine.local"
          Mode:Managed  Frequency:2.462 GHz  Access Point: xx:xx:xx:xx:xx:xx
          Bit Rate=125 Mb/s   Tx-Power:10 dBm   Sensitivity=0/3
          RTS thr=4096 B   Fragment thr=4096 B
          Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx   Security mode:restricted
          Power Management:off
          Link Quality:100/100  Signal level:-50 dBm  Noise level:-256 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Is there any particular reason for wanting to use the ACX driver?

So that 1) I am using a native driver, and 2) so I can run apps like Kismet, etc.

[JaRaEeZ]

ok-- good luck then..

[sturung]

thanks, I decided to try installing it a little more and after that just use Ndiswrapper until I can find a Orinoco Classic