Starting ndiswrapper at boot

English Network/Internet
1

Hi
I have to insert “modprobe ndiswrapper” as a line in the file /etc/init.d/boot.local, to get my ndiswrapper kick started at boot time.

I know that theoretically I should use the neater method of listing ndiswrapper as a kernel module to start at boot. How do I do that?

Thanks
Swerdna

2

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Perhaps try running (as root):

ndiswrapper -m

Good luck.

swerdna wrote:
| Hi
| I have to insert “modprobe ndiswrapper” as a line in the file
| /etc/init.d/boot.local, to get my ndiswrapper kick started at boot
| time.
|
| I know that theoretically I should use the neater method of listing
| ndiswrapper as a kernel module to start at boot. How do I do that?
|
| Thanks
| Swerdna
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIoMZh3s42bA80+9kRArCwAJ0V4ChpZApDjVQq2i7aDHcZssC21QCfY3Ds
IQsyTbroJY9BnWF/0ELN83w=
=zLyk
-----END PGP SIGNATURE-----

3

swerdna wrote:
> Hi
> I have to insert “modprobe ndiswrapper” as a line in the file
> /etc/init.d/boot.local, to get my ndiswrapper kick started at boot
> time.
>
> I know that theoretically I should use the neater method of listing
> ndiswrapper as a kernel module to start at boot. How do I do that?

Wow, I get to help Swerdna!

Using YaST => System =>/etc/sysconfig Editor, open System, then Kernel
and edit MODULES_LOADED_ON_BOOT.

Larry

4

Thanks for that. It added the file “ndiswrapper” containing the line “alias wlan0 ndiswrapper” into the directory /etc/modprobe.d – what you intended. But then when I boot, the computer locks. When I delete the file /etc/modprobe.d/ndiswrapper, the lockup on boot stops. So I suppose my computer must be quirky, unless wlan0 is a wrong guess.

So of the two choices, yours and a line in /etc/init.d/boot.local, strangely the latter is the one for me.

Thanks anyway
Swerdna

5

And so you did help me. I imagine you saw how ab’s good advice didn’t work on my particular computer. So I edited ndiswrapper in with the /etc sysconfig Editor as you suggested. I see the module being loaded in the boot up messages. And that seems to work as well as “modprobe ndiswrapper” (probably becasue it’s the same thing??).

Thanks
Swerdna

6

Hmmm…if it locks, first thing is to make sure that you’ve blacklisted
the native competition. When you do
ndiswrapper -l
you should see a line like:
device (xxxx:xxxx) present (alternate driver: <native-driver-name>)
[if you’ve got the newer ndiswrapper package]

They added the ‘alternate driver’ info to help remind you to blacklist.
That said, in a few circumstances, it might be necessary to blacklist
MORE than just that single driver, so post that output from ndiswrapper -l.

7

Thanks. I checked the ndiswrapper -l. It’s not a driver conflict (no alternates present) and it’s intermittent. I’m not going to pursue it since I’ve now got two alternate methods that do the job.