[svlug] linux PCI wireless

Karen Shaeffer shaeffer at neuralscape.com
Mon Oct 2 12:52:30 PDT 2006

On Sun, Oct 01, 2006 at 03:55:06PM -0700, Mark Jaffe wrote:
> >
> >PCI: Enabling device 0000:00:0f.0 (0000 -> 0003)
> >ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 18 (level, low) -> IRQ 17
> >PLX9052 PCI/PCMCIA adapter: mem=0xed800000, plx_io=0x9800, irq=17, 

Hi Mark,

The PLX9052 is your PCMCIA to PCI bridge. and It is configured.

Try lspci -vv

This is old technology. You can also see that below, where
it detects the Prism2/2.5 chipset. But those prism chipsets
are very good wireless cards for 802.11b protocols. That
prism chipset implements the full features to enable it
to be configured and run as a fully functional Host Access
Point -- a wireless LAN bridge. It can also be run as a
basic wireless NIC in your laptop too.

> >pccard_io=0x9
> >400
> >hostap_plx: CIS: 01 03 00 00 ff 17 ...
> >hostap_plx: manfid=0x0156, 0x0002
> >hostap_plx: cor_index=0x1 cor_offset=0x3e0
> >Prism2/2.5 PC Card detected in PLX9052 adapter
> >PLX_INTCSR=0x1063
> >PLX_CNTRL=0x187866d2 (Serial EEPROM present=1)
> >hostap_plx: Registered netdevice wifi0
> >prism2_hw_init: initialized in 376 ms
> >wifi0: NIC: id=0x8008 v1.0.1
> >wifi0: PRI: id=0x15 v0.3.0
> >wifi0: STA: id=0x1f v0.8.3
> >ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI)

So, your hostap_plx driver is up and running. It has
registered netdevice wifi0.

I am not sure about the ohci_hcd driver

try lsmod

does it show up as part of your wireless module stack?

> >Driver (PCI)
> >wifi0: defaulting to host-based encryption as a workaround for  
> >firmware bug in H
> >ost AP mode WEP
> >wifi0: defaulting to bogus WDS frame as a workaround for firmware  
> >bug in Host AP
> > mode WDS
> >wifi0: registered netdevice wlan0
> >

try ifconfig -a    and look for wlan0

You should see it is there. But it likely isn't up and running,
without proper configuration. 

> Next challenge is to locate an appropriate driver. Is there any  
> commands I can send the HBA to probe the device?

Your only problem appears to be to configure the system to run it.
And you might also look for some firmware updates, cause that would
be a good thing to do next.

Hope that helps. I am really busy and have no time to fool with
this at the moment.

 Karen Shaeffer
 Neuralscape, Palo Alto, Ca. 94306
 shaeffer at neuralscape.com  http://www.neuralscape.com

More information about the svlug mailing list