FATAL: Module not found

[barue]

After installing latest nvidia with yum and then reboot, when I try:

modprobe ndiswrapper

I get:

FATAL: Module ndiswrapper not found

After some investigation on google, I found this isn't the only module failing.

modprobe usbcore
FATAL: Module usbcore not found

ndiswrapper was working OK before installing nvidia packages.

Any ideas how I can resolve this that doesn't involve recompiling kernel?

[stoat]

Hello barue,

This idea may go nowhere, but if that nvidia thing involved kmods, there is a possibility that a new i586 kernel was installed with them. Anyway, it won't hurt to take a moment to review what is installed regarding those...

rpm -qa | grep -e kernel -e nvidia | sort

If I'm wrong, so be it. No harm done looking.

[barue]

Hi stoat, thank-you for your reply. Here's the output from the rpm query.

rpm -qa | grep -e kernel -e nvidia | sort

kernel-2.6.29.4-167.fc11.x86_64
kernel-2.6.30.5-43.fc11.x86_64
kernel-devel-2.6.29.4-167.fc11.x86_64
kernel-firmware-2.6.30.5-43.fc11.noarch
kernel-headers-2.6.29.4-167.fc11.x86_64
kerneloops-0.12-5.fc11.x86_64 (good with milk)
kmod-nvidia-185.18.36-1.fc11.1.x86_64
kmod-nvidia-2.6.30.5-43.fc11.x86_64-185.18.36-1.fc11.1.x86_64
xorg-x11-drv-nvidia-185.18.36-1.fc11.x86_64
xorg-x11.drv-nvidia-libs-185.18.36-1.fc11.x86_64

[stoat]

Okay. It's not what I said. You have the 64-bit packages, and the bizarre recent effect that I had in mind involves the 32-bit kernels and kmods. No harm done by looking. At least your thread was bumped.

P.S.: If you're using RPM Fusion's ndiswrapper, you can check that those kmods match the kernel you are booted into when this happens. Maybe the kernel updated and the kmods didn't. It's not unheard of.

rpm -qa | grep -e kernel -e ndiswrapper | sort

If you compiled ndiswrapper from source, remember it has to be recompiled for each new kernel. The usbcore thing is a different matter, and I've got nothing for that.

[barue]

Thank-you stoat. Updated kernel-devel and headers and recompiled ndiswrapper and no longer get the error for this module although usbcore issue still persists which ultimately is still preventing ndiswrapper from functioning even though modprobe ndiswrapper now works.

When I locate usbcore.ko it finds it successfully:

modprobe usbcore
FATAL: Module usbcore not found.

locate usbcore.ko

/lib/modules/2.6.29.4-167.fc11.x86_64/kernel/drivers/usb/wusbcore/wusbcore.ko
/lib/modules/2.6.30.5-43.fc11.x86_64/kernel/drivers/usb/wusbcore/wusbcore.ko

Any ideas? Google results on this issue are gray.

[ghis_frederic]

Originally Posted by stoat

Okay. It's not what I said. You have the 64-bit packages, and the bizarre recent effect that I had in mind involves the 32-bit kernels and kmods. No harm done by looking. At least your thread was bumped.

P.S.: If you're using RPM Fusion's ndiswrapper, you can check that those kmods match the kernel you are booted into when this happens. Maybe the kernel updated and the kmods didn't. It's not unheard of.

rpm -qa | grep -e kernel -e ndiswrapper | sort

If you compiled ndiswrapper from source, remember it has to be recompiled for each new kernel. The usbcore thing is a different matter, and I've got nothing for that.

I HAVE the same struggle: (FATAL: module ndiswrapper not found):

# rpm -qa | grep -e kernel -e ndiswrapper | sort
arm-gp2x-linux-kernel-headers-2.6.12.0-3.fc11.noarch
kernel-2.6.30.5-43.fc11.i586
kernel-firmware-2.6.30.5-43.fc11.noarch
kernel-headers-2.6.30.5-43.fc11.i586
kerneloops-0.12-5.fc11.i586
kernel-PAE-2.6.30.5-43.fc11.i686
kernel-PAE-devel-2.6.30.5-43.fc11.i686
kmod-ndiswrapper-1.54-4.fc11.17.i586
kmod-ndiswrapper-2.6.30.5-43.fc11.i586-1.54-4.fc11.17.i586
ndiswrapper-1.54-2.fc11.i586

# locate usbcore.ko
/lib/modules/2.6.30.5-43.fc11.i686.PAE/kernel/drivers/usb/wusbcore/wusbcore.ko

# ndiswrapper -l
mrv8335 : driver installed
device (11AB:1FAA) present

BUT failure for both ndiswrapper, usbcore as below.
# modprobe ndiswrapper
FATAL: Module ndiswrapper not found.


Can you help us, please

[stoat]

Hello ghis_frederic,

I think I may see something to do in your case. You have both the i586 and i686 versions of the latest kernel installed. And your kmods are i586 also. I don't know why it happens, but you are not the first one. It also happened recently with kmod-nvidia and kmod-wl. Your's is an interesting addition to the collection.

I recommend that you reboot into the PAE kernel, remove the i586 kernel (yum remove kernel-2.6.30.5-43.fc11.i586), and remove the ndiswrapper packages (yum remove kmod-ndiswrapper). Don't worry about ndiswrapper if it remains (but it probably won't) because it only comes in the i586 version. The same is true for kernel-headers and kerneloops. After all that kernel business looks right and the kmods are gone, then re-install ndiswrapper like this...

su
yum install kmod-ndiswrapper-PAE

That should install the correct group of ndiswrapper packages for the PAE kernel and not install the i586 kernel. I believe it may also fix your usbcore situation, too, because you found that module only in the PAE kernel's modules.

P.S.: Just in case someone reading this doesn't know it, the PAE kernel is now the only i686 kernel.

[ghis_frederic]

Originally Posted by stoat

Hello ghis_frederic,

I think I may see something to do in your case. You have both the i586 and i686 versions of the latest kernel installed. And your kmods are i586 also. I don't know why it happens, but you are not the first one. It also happened recently with kmod-nvidia and kmod-wl. Your's is an interesting addition to the collection.

I recommend that you reboot into the PAE kernel, remove the i586 kernel (yum remove kernel-2.6.30.5-43.fc11.i586), and remove the ndiswrapper packages (yum remove kmod-ndiswrapper). Don't worry about ndiswrapper if it remains (but it probably won't) because it only comes in the i586 version. The same is true for kernel-headers and kerneloops. After all that kernel business looks right and the kmods are gone, then re-install ndiswrapper like this...

su
yum install kmod-ndiswrapper-PAE

That should install the correct group of ndiswrapper packages for the PAE kernel and not install the i586 kernel. I believe it may also fix your usbcore situation, too, because you found that module only in the PAE kernel's modules.

P.S.: Just in case someone reading this doesn't know it, the PAE kernel is now the only i686 kernel.

Thank for your help! (I am verbose below to help the others, because it is not easy for beginners)
=> After some "remove tasks" and reboot as you asked,
I have the following:
# rpm -qa | grep -e kernel -e ndiswrapper | sort
arm-gp2x-linux-kernel-headers-2.6.12.0-3.fc11.noarch
kernel-firmware-2.6.30.5-43.fc11.noarch
kernel-PAE-2.6.30.5-43.fc11.i686
kernel-PAE-devel-2.6.30.5-43.fc11.i686

# yum install kmod-ndiswrapper-PAE
(some bla bla there, and later
Installation:
kmod-ndiswrapper-PAE i686 1.54-4.fc11.17 rpmfusion-free-updates 14 k
Installation pour dépendance:
kmod-ndiswrapper-2.6.30.5-43.fc11.i686.PAE i686 1.54-4.fc11.17 rpmfusion-free-updates 99 k
ndiswrapper i586 1.54-2.fc11 rpmfusion-free 35 k
================================================== =====================================
Installation 3 paquet(s)
Suppression 0 paquet(s)

=> AS YOU CAN remark, I still got ndiswrapper i586, not i686.PAE: Is it normal???

BUT It worked; I got the following at the end of my ndiswrapper + XP driver installation process:
In the directory where windows mrv8335(*.inf, *.sys, *.cat files) drivers are present:
#ndiswrapper -i mrv8335.inf
installing mrv8335 ...

# ndiswrapper -l
mrv8335 : driver installed
device (11AB:1FAA) present

# modprobe ndiswrapper

# lsmod | grep ndiswrapper
ndiswrapper 157436 0

#iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
pan0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:1 Mb/s Sensitivity=-200 dBm
RTS thr=2346 B Fragment thr=2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

=> NOW, I am trying to configure the wlan0(WIFI with WAP key); Some tips from you are welcome ;-)
Thank you.

[stoat]

Originally Posted by ghis_frederic

=> AS YOU CAN remark, I still got ndiswrapper i586, not i686.PAE: Is it normal???

That is normal. The ndiswrapper package exists only in the i586 version.

Originally Posted by ghis_frederic

=> NOW, I am trying to configure the wlan0(WIFI with WAP key); Some tips from you are welcome ;-)

I recommend letting NetworkManager handle that. At least try it. I've been using it for a long time now. All I have to do is get my driver installed, and NetworkManager takes off with it. When I first tried NetworkManager I had trouble with it like some people still do today, but I eventually found out that it was because I was still doing the old manual stuff, too. Don't do that. Stay out of the Network Configuration utility (system-config-network). Don't edit its config files. If your driver is working as ndiswrapper -l and lsmod suggest, then look in the NetworkManager panel applet for a list of available networks.

[ghis_frederic]

Originally Posted by stoat

That is normal. The ndiswrapper package exists only in the i586 version.

I recommend letting NetworkManager handle that. At least try it. I've been using it for a long time now. All I have to do is get my driver installed, and NetworkManager takes off with it. When I first tried NetworkManager I had trouble with it like some people still do today, but I eventually found out that it was because I was still doing the old manual stuff, too. Don't do that. Stay out of the Network Configuration utility (system-config-network). Don't edit its config files. If your driver is working as ndiswrapper -l and lsmod suggest, then look in the NetworkManager panel applet for a list of available networks.

Thankx, It was easy as hell ;-)
NetworkManager just needed me to select my wifi network name between others it has detected in my area, and it recognizes my key type (WAP for me). I typed mine and things gone well.
BUT I dont know why I must unplug and plug again my wifi card, to be detected after reboot (good news is:no password ask again if card is detected) ???

[ghis_frederic]

Hello.

My problem is: ndiswrapper is not loaded at reboot, so my card is not detected.

=> I have done the following:
# ndiswrapper -m
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
module configuration already contains alias directive

=> I get an empty file /etc/modprobe.conf ; AND
another file /etc/modprobe.d/ndiswrapper ( without extension but which contains the line:
alias wlan0 ndiswrapper ) with others *.conf files as anaconda.conf for example.

Through the warnings, I think something is not going well, so it can justify why ndiswrapper is not loaded automatically at boot/reboot.

What do you think about?

[stoat]

Right. In Fedora 11, there is no /etc/modprobe.conf file now, and the files that used to be in it are now in other files in the /etc/modprobe.d folder. And they all have .conf endings. It is my belief that if you rename your /etc/modprobe.d/ndiswrapper file to have a .conf ending, then it will be processed and the module may load. I recommend trying that right now. For me, simply creating that same alias as you posted made the module load. I used to do it in /etc/modprobe.conf. Now you likely can do it in /etc/modprobe.d/ndiswrapper.conf.

There are two other related ndiswrapper options that sometimes work better than -m to get the module to load (e.g., -mi, -ma). You can read more about them in ndiswrapper --help and here (see "Experiments to try")...

http://forums.fedoraforum.org/showth...71#post1129271

But they may create files that need to be renamed, too. I doubt that anybody is really maintaining ndiswrapper that closely for such a new thing. But maybe so.

Lastly, there is always /etc/rc.local where you can put your manual modprobe ndiswrapper command. That usually works.

[ghis_frederic]

Originally Posted by stoat

Right. In Fedora 11, there is no /etc/modprobe.conf file now, and the files that used to be in it are now in other files in the /etc/modprobe.d folder. And they all have .conf endings. It is my belief that if you rename your /etc/modprobe.d/ndiswrapper file to have a .conf ending, then it will be processed and the module may load. I recommend trying that right now. For me, simply creating that same alias as you posted made the module load. I used to do it in /etc/modprobe.conf. Now you likely can do it in /etc/modprobe.d/ndiswrapper.conf.

There are two other related ndiswrapper options that sometimes work better than -m to get the module to load (e.g., -mi, -ma). You can read more about them in ndiswrapper --help and here (see "Experiments to try")...

http://forums.fedoraforum.org/showth...71#post1129271

But they may create files that need to be renamed, too. I doubt that anybody is really maintaining ndiswrapper that closely for such a new thing. But maybe so.

Lastly, there is always /etc/rc.local where you can put your manual modprobe ndiswrapper command. That usually works.

Hello.
I have tried the following cases(with alias line inside files):
a) only etc/modprobe.d/ndiswrapper.conf -> KO
d) only etc/modprobe.d/modprobe.conf -> KO
c) only etc/modprobe.conf -> KO
d) all above files -> KO

Then later, it's worked after I typed the command below:
# ndiswrapper -mi
module configuration information is stored in /etc/modprobe.d/ndiswrapper
# more ndiswrapper
install pci:v000011ABd00001FAAsv*sd*bc*sc*i* /sbin/modprobe ndiswrapper
install pci:v000011ABd00001FABsv*sd*bc*sc*i* /sbin/modprobe ndiswrapper

Later, I removed all related *.conf files and it still worked.
So, I decided just to keep the successful ndiswrapper file and an empty etc/modprobe.d/modprobe.conf (without alias line).

Curious about it works without an "alias wlan0 ndiswrapper" *.conf file !!!

Thank you so much.

[stoat]

Originally Posted by ghis_frederic

Then later, it's worked after I typed the command below:
# ndiswrapper -mi

I always had success with that one, too. Never knew why really. You will occasionally read posts recommending to do all three (-m, -ma, -mi). I promise that will not do any good. Those second two will completely overwrite the existing file. And if the first one is done after either of the other two, it complains a lot. I've tried all of this before. But it is acceptable to try them one at a time, checking after each one, and in the order that I showed above. Stop when something works.

Originally Posted by ghis_frederic

Curious about it works without an "alias wlan0 ndiswrapper" *.conf file !!!

Maybe the deprecated filename is still working for the time being. If ndiswrapper stops loading in the near future, remember this issue as a possible cause and try renaming the ndiswrapper file.

[barue]

I reverted back to Fedora 10 and did my kernel and kmod updates and installs from there and all is well. Aside from my issue with usbcore/ndiswrapper in this post there were some other issues I was experiencing on 11 as well esp. relating to graphics card.

Thanks for all your help stoat and glad another could benefit from these posts also.

SOLVED