I'm not a FC user, but I also had problems automatically starting
install wlan0 /sbin/modprobe <mydrivername> ; sleep 0.5=20
And deleting the=20
alias wlan0 <mydrivername> =20
in /etc/modprobe.conf did the trick for me....
Good luck, Hans.
[mailto:ndiswrapper-general-admin@...] Namens Filip
Verzonden: maandag 13 maart 2006 11:20
Onderwerp: [Ndiswrapper-general] Re: On-demand loading ndiswrapper does =
happen on FC4
Giridhar Pemmasani wrote:
> ndiswrapper ha(s/d) support for hotplug, but I doubt Fedora Core=20
> supports hotplug anymore. Moreover, you need to modify hotplug scripts =
> [...] Windows drivers. In essence ndiswrapper mimics hotplug as far as =
> Windows drivers are concerned, but ndiswrapper itself must be loaded=20
> either manually or through scripts.
I'm not sure I understand what you are saying here.
I had an earlier FC4 setup in which nothing else but 'ndiswrapper -m' =
needed to get the ndiswrapper to load on demand.
So I was kind of expecting that on a new install the same would be =
That is, that FC4 does support hotplug, and the on-demand was possible.
On the other hand, loading the module at boot time (via =
for instance) is also not good, because it makes the NetworkManager =
die. Now I suppose that this is some issue with NM 0.5.2 (whereas in the
previous install I used 0.4).
NB: I asked the same question on the FC4 newsgroup but got no replies.
This SF.Net email is sponsored by xPML, a groundbreaking scripting =
that extends applications into web and mobile media. Attend the live =
and join the prime developer group breaking into this new coding =
Ndiswrapper-general mailing list =