(no subject)

[Dominik Brodowski]

Hi Jose,

On Fri, Sep 16, 2005 at 02:12:44PM +0000, jose' ventura wrote:
> If your card really is a Linksys WPC54G, then your cardbus bridge is not 
> functioning correctly as you can see by comparing my lspci output with yours
lspci output changes are quite common.

> acx100_pci: module not supported by Novell, setting U taint flag.
							^^^^^^^^^^
If you use such a driver, you cannot expect support.

> acx100: that uses the mysterious ACX100 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_init_module: TI acx100_pci.o: Ver 0.2.0pre6 Loaded
> acx100_init_module: dev_info is: TI acx100_pci
> PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
> PCI: Setting latency timer of device 0000:02:00.0 to 64
> acx100_probe_pci: WARNING: ACX111 support is highly experimental!
> Found ACX100-based wireless network card, phymem1:0x1e820000, 
> phymem2:0x1e800000, irq:11, mem1:0xe0960000, mem1_size:8192, 
> mem2:0xe0963000, mem2_size:131072 compiled with wireless extensions v16
> acx100_probe_pci: using acx111 io resource adresses (size: 96)

This all sounds like the device is set up correctly. So it really doesn't
look to be a PCMCIA or CardBus problem. However,

> ERROR: no directory for firmware file specified, ABORTING. Make sure to set 
> module parameter 'firmware_dir'! (specified as absolute path!)

it needs some firmware which you need to set up correctly. Most probably the
documentation you can find at acx100.sf.net tells you how to do that.