Re: CFT: Texas Instruments ACX100/111 IEEE 802.11 driver.

From: Alexey Shuvaev <shuvaev_at_physik.uni-wuerzburg.de>
Date: Sat, 27 Dec 2008 20:17:13 +0100
On Sat, Dec 27, 2008 at 02:01:58PM -0500, Robert Noland wrote:
> On Sat, 2008-12-27 at 18:18 +0100, Alexey Shuvaev wrote:
> > Hello list!
> > 
> > As it is device driver, I think this list is more appropriate rather than
> > ports_at_.
> > 
> > I've just updated net/acx100 port:
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=129977
> > but I have no actual hardware :(
> > 
> > Have someone one of:
> > 
> > Card                    Bus             Type
> > Binatone WL-1000        CARDBUS         ACX100
> > D-Link DWL-650+         CARDBUS         ACX100
> > US Robotics USR2210     CARDBUS         ACX100
> > US Robotics USR2216     PCI             ACX100
> > D-Link DWL-G650+        CARDBUS         ACX111
> > D-Link DWL-G520+        PCI             ACX111
> > US Robotics USR5416     PCI             ACX111
> > SAFECOM SWLPT-54125     PCI             ACX111
> > 
> > and could give it a try (with a new port from the PR)?
> > Is it a rare hardware? Any interest in maintaining it?
> > Any ongoing support in the base?
> 
> I have a linksys wpc54g v2 card which is a 111 part.  The updated port
> does not autoload the firmware, but if I manually load the firmware,
> then it attaches.  It doesn't quite work though.
> 
Nice (I mean that it attaches, at least :)!
Developer suggests loading appropriate firmware first.
You also need to use specialized acxtool, it is installed by the port.
See (at the bottom): http://dev.kewl.org/acx100+111/
(and man page if_axc(4) too).
Does this pushes the card to work?

> acx111fw: registering firmware
> cardbus0: Expecting link target, got 0xf2
> cardbus0: Expecting link target, got 0xf2
> acx0: <Texas Instruments (TI) 802.11b+/g 54Mbps Wireless Adapter> mem
> 0xfe620000-0xfe63ffff,0xfe602000-0xfe603fff irq 19 at device 0.0 on
> cardbus0
> acx0: Radio type: 16
> acx0: Firmware revision: 1.2.1.34
> acx0: Regulatory domain: FCC USA (1-11)
> acx0: WARNING: using obsoleted if_watchdog interface
> acx0: Ethernet address: 00:0f:66:c6:d7:f2
> acx0: [GIANT-LOCKED]
> acx0: [ITHREAD]
> 
> acx0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         ether 00:0f:66:c6:d7:f2
>         media: IEEE 802.11 Wireless Ethernet autoselect
>         status: no carrier
> ifconfig: unable to get HT configuration information: Invalid argument
> ifconfig: unknown/undefined channel number 255 flags 0x0
>         ssid
> ""%                                                                
> 
Which command it was? Just ifconfig without arguments?
The author says you should use ifconfig only to configure ip address.
For anything else he suggests to use 'acxtool'.
Can you give it a try?

> robert.
> 
Thanks so far,
Alexey.
Received on Sat Dec 27 2008 - 18:17:15 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:39 UTC