Could you outline the exact steps you used?
If you run "/sbin/lsmod", does ndiswrapper show up.
That model isn't listed in the ndiswrapper wiki:
http://ndiswrapper.sourceforge.net/j...3/id,list_c-f/
However other d-link cards are. You should run "sudo /sbin/lspci -v" followed by "sudo /sbin/lspci -n" and make a note of the manufacturer's code. For example, on my laptop:
Code:
sudo /sbin/lspci -v | sed -n '/Broadcom/,/^$/p'
02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
Subsystem: Hewlett-Packard Company NX9500 Built-in Wireless
Flags: bus master, fast devsel, latency 64, IRQ 11
Memory at e0104000 (32-bit, non-prefetchable) [size=8K]
/sbin/lspci -n | sed -n '/02:02.0/p'
02:02.0 Class 0280: 14e4:4320 (rev 03)
If I couldn't find "BCM4306" listed in the wiki or the ndiswrapper's package README, I would search for 14e4:4320. This is the unique code for the controller chip, which is what is important for identifying the driver needed. There was a Linksys wireless card that had 3 different controller chips used in it's lifetime, even though the model number was the same.
Did you run through the setup in YaST? Which SuSE are you running. For SuSE 10.2, you want to click on the "advanced .." button on the bottom of the "network devices" screen, after selecting your device. Make sure that "ndiswrapper" is listed on the bottom. The config for SuSE 10.3 is different and this part isn't "hidden".