On Thu, 2006-05-11 at 18:01 -0600, JD. Brown wrote:

On 5/11/06, Ken Schneider wrote:

...

Anyone else having problems with ndiswrapper on 10.1 GM? I keep getting the error "module not found" when doing "modprobe ndiswrapper". This is after ndiswrapper -i driver.inf and before or after ndiswrapper -m.

-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

Ken,

I have personally always received that message with SUSE's RPM NDiswrapper version. I've looked into this and it never seems to recognize that NDiswrapper is installed; when in fact it is. I've been resorting to building NDiwrapper from source. Which always has been fail proof, unless of course you do a kernel patch and/or upgrade.

If anyone else out there can get SUSE's RPM version working. I would like to know how you did it???

I have had no problems up through 10.1RC3. Once I upgraded to GM it stopped working. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

On Thu, 2006-05-11 at 18:54 -0600, JD. Brown wrote:

...

I have had no problems up through 10.1RC3. Once I upgraded to GM it stopped working.

Interesting, I wonder if it's somehow hardware related; Certain cards not triggering the module? I've been dealing with some BCM chip sets and I just cannot get them to work with the RPM. It's definitely nice to know that it has worked.

In my case it is not hardware related. After using "ndiswrapper -i" to install the driver and then using "ndiswrapper -l" is shows the driver installed and the hardware present. I just get a "module not found" error when trying to "modprobe ndiswrapper". -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

On Fri, 2006-05-12 at 06:53 +0100, James Ogley wrote:

...

Anyone else having problems with ndiswrapper on 10.1 GM? I keep getting the error "module not found" when doing "modprobe ndiswrapper". This is after ndiswrapper -i driver.inf and before or after ndiswrapper -m.

The kernel module itself is now in the package ndiswrapper-kmp-FLAVOUR where FLAVOUR is your kernel type (eg. default; smp).

I have found the problem. I have installed ndiswrapper-kmp-default but when I upgraded the system it installed the bigsmp kernel as well as the default kernel -and- made the bigsmp kernel the default at boot time. This is on a P3 1Ghz with 256M of ram. I guess I need to open a bug report about the -wrong- kernel being installed at install time. Perhaps the program that probes for the correct kernel to install is not working correctly. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998