I’m trying to use ndiswrapper to drive a Buffalo WLI-PCM-L11G pcmcia card without success.
I understand how it’s supposed to work and I understand why it isn’t!!! :sarcastic:
The card does not seem to identify itself at all. If I do lspci I get a list of all the devices present EXCEPT the pcmcia devices - not a one shows up!!
Is there something extra I have to do to list the pcmcia device ids? I have searched hi and lo and everything I have read implies that lspci will show the pcmcia devices and their devids, but not for me.
I know the pcmcia slots are working as standard wired ethernet cards work fine (but they are not shown by lspci either >:( )
Also, the wireless card works fine in WinDoze…pah!!
Can anyone point me in the right direction? I’m sure that once I can see the device ids I can figure out what is going wrong.
Ah - OK. I think I misunderstood the function of lspci. pccardctl does indeed show the cards installed, but for ndiswrapper don’t I need the device id??
How do I find that? I thought that’s what lspci would provide. pccardctl does give me a manufacturer id and device type and function but are these the same as the device id?
This is what comes of coming from Unix to Linux and then not touching either for 4 years!!
Tasemaro wrote:
> Ah - OK. I think I misunderstood the function of lspci. pccardctl does
> indeed show the cards installed, but for ndiswrapper don’t I need the
> device id??
>
> How do I find that? I thought that’s what lspci would provide.
> pccardctl does give me a manufacturer id and device type and function
> but are these the same as the device id?
All that ndiswrapper needs is the Windows driver and the corresponding .inf
file. As long as that driver recognizes the device, it will load. That is where
the device ID comes in.
Hi Larry,thanks for that - therein lies the problem. ndiswrapper reports that the driver is installed but the device isn’t present (Which it plainly is). This is why I was hunting down the devid path thinking that the card may not be reporting the same devid as ndiswrapper is expecting.
I know that the drivers are correct as they are the ones currently used in XP (I dual, in fact triple boot this laptop Suse, XP and 98).
If I re-instate the Linux drivers for the card (for Kismet) the card works OK with Kismet, but it refuses to connect to any wireless lans (even though Kismet can see them). This is why I was trying the ndiswrapper route.
I know the lan works with XP (that’s how I’m doing this now) but not with Linux…
