Sure... whether you downloaded the "linux-tested" driver from the ndiswrapper page or you use the driver that came with the card, you should have a .sys file and a .inf file. Put them both in the same directory and cd into that directory.
As root you would do the following:
Code:
ndiswrapper -i *.inf
where *.inf is the name of the .inf file for ndiswrapper to load up the file.
If you don't get any errors, and the card is plugged in or operational, you'll want to make sure that the drivers are working. I'll use an example from my setup:
Code:
ndiswrapper -l
Installed drivers:
lsbcmnds driver installed, hardware present
If you get the "driver installed, hardware present" output, then the driver recognizes the card and ndiswrapper recognizes the driver. You can go ahead and create an alias so that you can actually use the card properly:
I'm not sure how Suse is set up but this should all work properly. It's possible that there might be a different process for that distro so if anything looks a little funny then search around the fora for that "one extra step" but I'm pretty sure that you won't have any problems along those lines.
That should work properly, though, so I don't think you'll have any other problems. Always keep an eye on the native linux drivers though. If for some reason the native drivers become fully functional I would recommend using those. Until then, you shouldn't have any problems with this driver unless it's documented. I have not had any problems with mine. If you want to look into WPA or WEP encryption I'm sure that Suse has something in Yast that I don't know about so I wouldn't be a very good reference for that.
Good luck.
