Re: Need Help With Linksys WMP54G PCI Card

You have the answer by LSPCI,
your card is based on Broadcom chipset, not Intersil/Globespan/Conexant.
The solution (not driver) is at :

http://www.linuxant.com/company/press_dldr.php
or
http://sourceforge.net/projects/ndiswrapper/

Seb.



Werner Kuballa wrote:
> I have successfully installed prism54 on my laptop using a Netgear
> WG511.  I used the linux-2.4.25-prism54-1.0.2.2 patch, compiled a new
> kernel and everything works just fine, including ap-mode and using
> kismet.
> 
> Now I got a Linksys WMP54G PCI card for my desktop and would like to
> use the prism54 driver.  Somebody reported in the prism54 user group
> ("david" on 10-Nov-03) that he has got this card up and running, but I
> don't know how.  
> 
> I was trying to use again the patched 2.4.25-prism54 kernel.  The
> desktop has no PCMCIA and if I don't select "CONFIG_PCMCIA=y", I don't
> even get a chance to select "CONFIG_PRISM54=m".  I have tried setting
> "CONFIG_PCMCIA=y", "CONFIG_CARDBUS=y", "CONFIG_PRISM54=M" but this does
> not help.  Below you can see the error messages when trying to load
> prism54.  
> 
> Maybe it's a stupid question, but I ask it anyway:  Are plain PCI cards
> like the WMP54G supported at all?  And how do you configure the system
> if it has no PCMCIA support?
> 
> Any advice is appreciated.
> 
> Regards,
> Werner
> 
> 
> # lspci -v -v -v -s 2:2.0
> 02:02.0 Network controller: Broadcom Corporation: Unknown device 4320
> (rev 03)
>         Subsystem: Linksys: Unknown device 0014
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
>         Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32
>         Interrupt: pin A routed to IRQ 17
>         Region 0: Memory at ff8fc000 (32-bit, non-prefetchable)
> [size=8K]
> 
> # modprobe prism54
> /lib/modules/2.4.25-WK-0405A/kernel/drivers/net/wireless/prism54/prism54.o:
> init_module: No such device
> /lib/modules/2.4.25-WK-0405A/kernel/drivers/net/wireless/prism54/prism54.o:
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.25-WK-0405A/kernel/drivers/net/wireless/prism54/prism54.o:
> insmod
> /lib/modules/2.4.25-WK-0405A/kernel/drivers/net/wireless/prism54/prism54.o
> failed
> /lib/modules/2.4.25-WK-0405A/kernel/drivers/net/wireless/prism54/prism54.o:
> insmod prism54 failed
> [email protected].
> 
> 
> 
> _______________________________________________
> Prism54-users mailing list
> [email protected]
> http://prism54.org/mailman/listinfo/prism54-users
> 
>