I just installed Fedora Core 2 and ndiswrapper. I was FLOORED how easy it was. It worked fine... until I ran "yum update", which grabbed the latest kernel, 2.6.6-1.435. Upon reboot, ndiswrapper didn't work (of course). So I recompiled it. Even then, it didn't work. I kept getting:
ndiswrapper: Windows driver couldn't initialize the device
mrv8k51.sys: probe of 0000:01:0a.0 failed with error -22
Lucky for me, Fedora keeps the old kernels around when it updates. I booted back to the old kernel (2.6.5-1.358) and everything worked fine. *shrug*
So then, I grabbed ndiswrapper from CVS. It still didn't work (same errors). On a whim, I grabbed the vanilla kernel source for 2.6.7 and built my own kernel. Same problem.
I finally decided to mail the list about this. I recompiled ndiswrapper with DEBUG defined. The output is enormous (~3000 lines), so I won't put it in this email. Instead, it's on my web page. Here's a direct link:
About my system:
Home-built Athlon XP 3000 with 400 MHz FSB
512 MB RAM
D-Link DWL-G510 (Marvell (Libertas) chipset)
Brand new Fedora Core 2 installation
For now, I'll stick with the 2.5.5-1.358 kernel. But I think this problem is bigger than just a weird Fedora kernel. Strangely enough, ndiswrapper worked with the kernel that shipped with Fedora Core 2, despite the fact that it was compiled with 4k stacks. Go figure.
Any help you could offer would be greatly appreciated. And please feel free to contact me with any questions. Thanks in advance.