Depmod -> Floating point exception

[raab]

I am trying to run depmod on my computer, but it comes back with "Floating point exception" every time. I turned on verbose and get this at the end:

xftw starting at /lib/modules/2.4 lstat on /lib/modules/2.4 failed
xftw starting at /lib/modules/kernel lstat on /lib/modules/kernel failed
xftw starting at /lib/modules/fs lstat on /lib/modules/fs failed
xftw starting at /lib/modules/net lstat on /lib/modules/net failed
xftw starting at /lib/modules/scsi lstat on /lib/modules/scsi failed
xftw starting at /lib/modules/block lstat on /lib/modules/block failed
xftw starting at /lib/modules/cdrom lstat on /lib/modules/cdrom failed
xftw starting at /lib/modules/ipv4 lstat on /lib/modules/ipv4 failed
xftw starting at /lib/modules/ipv6 lstat on /lib/modules/ipv6 failed
xftw starting at /lib/modules/sound lstat on /lib/modules/sound failed
xftw starting at /lib/modules/fc4 lstat on /lib/modules/fc4 failed
xftw starting at /lib/modules/video lstat on /lib/modules/video failed
xftw starting at /lib/modules/misc lstat on /lib/modules/misc failed
xftw starting at /lib/modules/pcmcia lstat on /lib/modules/pcmcia failed
xftw starting at /lib/modules/atm lstat on /lib/modules/atm failed
xftw starting at /lib/modules/usb lstat on /lib/modules/usb failed
xftw starting at /lib/modules/ide lstat on /lib/modules/ide failed
xftw starting at /lib/modules/ieee1394 lstat on /lib/modules/ieee1394 failed
xftw starting at /lib/modules/mtd lstat on /lib/modules/mtd failed
Floating point exception

That would make sense because those directories don't exist. But why is it even looking there? Is there some config file or option that tells it where to look? I've tried searching other forums and Google and no one has the answer. Please help!

[kevinalm]

That is very strange. I presume you're running depmod manually without a kernel version argument. When you do that depmod checks the version string for the running kernel and then looks in /lib/modules/<version>/ for modules. What does uname -R return for this kernel? Howing exactly did you get to this point? (Like did you compile your own kernel, perhaps?)

[mdwatts]

If as suggested by kevinalm you find that the kernel version you are running (uname -r) does indeed match the modules directory (/lib/modules/<kernel version>), then see if this helps.

Move (to have a backup copy)

/lib/modules/<kernel version>/modules.dep

to a backup directory and then try running

depmod -ae (as root)

to see if it will build a new modules.dep.

If it fails, move the backup copy back to /lib/modules/<kernel version>