Hi Ya'll.
Hoping you can help me out again!

Had the "fun" task of reinstalling my laptop due to a failed hard drive.
While I was at it, I picked up a new Wifi card, Linksys WPC54G V2. I was intending on using Driverloader from Linuxant or Ndiswrapper, but when I put it in the laptop, Suseplugger came up and asked me if I'd like to configure it.

Apparently Linksys switched to an ACX111 chip for the new card.
I thought this was good that Suseplugger picked it up automatically, and wanted to configure it.
It ID'd it as Linksys ACX 111 54Mbps Wireless Interface

Everything stepped through Yast as it normally would for configuring a wireless card.
I opened up a shell to double check things and got this:

~ # iwconfig wlan0
wlan0 No such device

Hrm, okay, that's odd...
~ # ifconfig wlan0
wlan0: error fetching interface information: Device not found

Hrm, odd.. Okay, check the messages file:


Dec 28 19:19:29 laptop1 kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 00
02)
Dec 28 19:19:29 laptop1 kernel: ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11
(level, low) -> IRQ 11
Dec 28 19:19:29 laptop1 kernel: PCI: Setting latency timer of device 0000:03:
00.0 to 64
Dec 28 19:19:29 laptop1 kernel: acx100_probe_pci: WARNING: ACX111 support is
quite experimental!
Dec 28 19:19:29 laptop1 kernel: Found ACX111-based wireless network card at 0
000:03:00.0, irq:11, phymem1:0x20820000, phymem2:0x20800000, mem1:0xe0d1c000, me
m1_size:8192, mem2:0xe0e40000, mem2_size:131072
Dec 28 19:19:29 laptop1 kernel: initial debug setting is 0x001b
Dec 28 19:19:29 laptop1 kernel: acx_select_io_register_set: using ACX111 io r
esource addresses (size: 56)
Dec 28 19:19:29 laptop1 kernel: hw_unavailable = 1
Dec 28 19:19:29 laptop1 kernel: acx_show_card_eeprom_id: EEPROM card ID strin
g check found uninitialised card ID: this is a SpeedStream SS1021 or Gigafast WF
721-AEX, no??
Dec 28 19:19:29 laptop1 kernel: acx100_probe_pci: TI acx_pci: Using IRQ 11
Dec 28 19:19:29 laptop1 kernel: reset hw_unavailable++
Dec 28 19:19:29 laptop1 kernel: acx100_reset_mac: enable soft reset...
Dec 28 19:19:29 laptop1 kernel: acx100_reset_mac: disable soft reset and go to init mode...
Dec 28 19:19:29 laptop1 kernel: Firmware: '/lib/firmware/TIACX111.BIN' not found. Trying alternative firmware.
Dec 28 19:19:29 laptop1 kernel: Firmware: '/lib/firmware/FwRad16.bin' not found. Trying alternative firmware.
Dec 28 19:19:29 laptop1 kernel: Trying to load firmware: '/lib/firmware/FW1130.BIN'
Dec 28 19:19:29 laptop1 kernel: ERROR 2 trying to open firmware image file '/lib/firmware/FW1130.BIN': file not found - make sure this EXACT filename is in eXaCtLy this directory!
Dec 28 19:19:29 laptop1 kernel: acx_read_fw failed.
Dec 28 19:19:29 laptop1 kernel: acx_reset_dev: Failed to upload firmware to the ACX1xx
Dec 28 19:19:29 laptop1 kernel: acx100_probe_pci: TI acx_pci: MAC initializefailure!
Dec 28 19:19:29 laptop1 kernel: acx100_probe_pci: TI acx_pci.o: Ver 0.2.0pre8 Loading FAILED
Dec 28 19:19:29 laptop1 kernel: acx_pci: probe of 0000:03:00.0 failed with error -5


Check dmesg, and while the message I find humerous, it's no more help than the messages file.

module acx_pci unsupported by SUSE/Novell, tainting kernel.
acx100: It looks like you've been coaxed into buying a wireless network card
acx100: that uses the mysterious ACX100/ACX111 chip from Texas Instruments.
acx100: You should better have bought e.g. a PRISM(R) chipset based card,
acx100: since that would mean REAL vendor Linux support.
acx100: Given this info, it's evident that this driver is quite EXPERIMENTAL,
acx100: thus your mileage may vary. Visit http://acx100.sf.net for support.
acx100: Compiled to use 32bit I/O access (I/O timing issues might occur, such as firmware upload failure!)
acx100_init_module: dev_info is: TI acx_pci
acx100_init_module: TI acx_pci.o: Ver 0.2.0pre8 Driver initialized, waiting forcards to probe...
PCI: Enabling device 0000:07:00.0 (0000 -> 0002)
ACPI: PCI interrupt 0000:07:00.0[A] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:07:00.0 to 64
acx100_probe_pci: WARNING: ACX111 support is quite experimental!
Found ACX111-based wireless network card at 0000:07:00.0, irq:11, phymem1:0x21020000, phymem2:0x21000000, mem1:0xe0a44000, mem1_size:8192, mem2:0xe0b00000, mem2_size:131072
initial debug setting is 0x001b
acx_select_io_register_set: using ACX111 io resource addresses (size: 56)
hw_unavailable = 1
acx_show_card_eeprom_id: EEPROM card ID string check found uninitialised card ID: this is a SpeedStream SS1021 or Gigafast WF721-AEX, no??
acx100_probe_pci: TI acx_pci: Using IRQ 11
reset hw_unavailable++
acx100_reset_mac: enable soft reset...
evdev_connect: evdev dffcca80 handle dffcca9c name event4
acx100_reset_mac: disable soft reset and go to init mode...
Attention: no custom firmware directory specified (via module parameter firmware_dir), thus using our default firmware directory /lib/firmware
Firmware: '/lib/firmware/TIACX111.BIN' not found. Trying alternative firmware.
Firmware: '/lib/firmware/FwRad16.bin' not found. Trying alternative firmware.
Trying to load firmware: '/lib/firmware/FW1130.BIN'
ERROR 2 trying to open firmware image file '/lib/firmware/FW1130.BIN': file notfound - make sure this EXACT filename is in eXaCtLy this directory!
acx_read_fw failed.
acx_reset_dev: Failed to upload firmware to the ACX1xx
acx100_probe_pci: TI acx_pci: MAC initialize failure!
acx100_probe_pci: TI acx_pci.o: Ver 0.2.0pre8 Loading FAILED
acx_pci: probe of 0000:07:00.0 failed with error -5

It looks to me that it can't find firmware, and therefor doesn't actually initialize, but I'm not positive that's the problem.

Anyone else seen something similar?

Well, I found the .bin files from the drivers I downloaded from linksys.
I created the directory /lib/firmware, and put the bin files there.

Now, I can see the interface in ifconfig, and iwconfig.
Also, iwlist wlan0 scanning picks up my access point.

Configured the wireless settings via Yast, and I get this in the messages file:

Dec 29 09:44:31 laptop1 kernel: Got IV ICV Failure IRQ
Dec 29 09:44:31 laptop1 kernel: Got Info IRQ: status 0x1001, type 0x0005: encrypt/decrypt on a packet has failed

Anyone seen this before?

WEP is not yet implemented for acx111 in the open source driver (acx_pci) (works great for acx100 pci/cardbus/usb though)

One other thing, the /lib/firmware location looks non-standard (for the os driver it's normally /usr/share/acx), this indicates to me that you're maybe using a distro-supplied/modified older version of the driver, which, once you turn off encryption, may work just fine, if not, you should visit acx100.sf.net and get the latest version, at this writing it's 0.2.0pre8_plus_fixes_43, go to downloads -> snapshots, and the readme's on that page also. The latest version has the most improvements for the acx111's.

ps:
If you must have WEP support immediately, I should tell you that the latest version of ndiswrapper, v1.0rc1 works nicely with these cards and (of course) WEP/WPA, etc. is supported, I've only tested on kernel 2.6.10, but most recent 2.6 kernels should also be fine..

Hrm, I was on acx100.sf.net and didn't see anything about lack of wep/wpa support.
A search on the forums indicates that it's working for some folks.

I'm currently at acx100-0.2.0pre8_plus_fixes_9-1.i586.rpm which tells me I'm *WAY* away from the rev 43 you mentioned. I downloaded acx100-0.2.0pre8_plus_fixes_43.tar.gz, and a quick cursory glance at it doesn't help me figure out how to upgrade from my ver 9 to the ver 43. Any tips/tricks/pointers?

It (wep) really is non-functional, but it's coming. The error msgs you received tell the tale.

There's a link to my guide in the README that comes with the source, if you're at a console you can unpack the source with tar zxf acx100-0.2.0pre8_plus_fixes_43.tar.gz, or use your file manager, then consult the readme in the newly created acx100-0.2.0pre8_plus_fixes_43 dir.

Once you've successfully compiled the source, then you can move your existing modules out of the way with these commands:

find /lib/modules/`uname -r` -name "*acx*"

to verify that the files being moved are only the acx modules
then:

find /lib/modules/`uname -r` -name "*acx*" -exec mv {} /root \;

to move them to /root or wherever else you'd like

then run depmod -a (and go get some coffee)

Right now the most common problem with SuSE 9.2 is getting the build environment setup, I don't yet have 9.2 installed, but I had a terrible time of it with 9.1, I hope you don't have the issue, or that if you do, you can solve/share the solution.

So, to compile these drivers.
Essentially a
./configure
make && make install && make clean?

I read the readme, and, well, honestly, it was over my head.

It's not quite the normal compile routine that you've described, but you're close. You don't need the ./configure, just start with make, don't do the make install until the make succeeds (of course) but also don't do it until you move your old drivers out of the way, else you'll move the new ones as well, and have to sit through 2 depmod's.

When using fixes_43, you'll need to put the firmware in the directory: /usr/share/acx, which you'll need to create.

Interested to know how you fared with this ACX111 headache - I am a new linux user struggling with a DWL-G520+ D-LINK as the only way to get to my network for updates etc.

very close to giving up on Suse when I found your post with the exact same errors.....

so let me know if you succeeded

mat

I found out that the driver does not support WEP.
If you pull the driver from the source, it actually states this.
For some reason, when you get it from Suse, it does not.

I've had good luck with ndiswrapper (although it's a PITA to configure) and my linksys card.

WEP does work with your card. Trust me, or even better trust Craig:

www.houseofcraig.net/acx100_howto.php