Running into issues with moddep/depmod

Avatar Linode 2 months, 1 week ago

I found the following errors in my logs after performing an update:

could not open moddep file '/lib/modules/4.15.8-x86_64 linode103/modules.dep.bin

Running depmod also produces the following error:

depmod: WARNING: could not open /lib/modules/4.15.8-x86_64 linode103/modules.order: No such file or directory

Is there a missing module in Linode's Debian repo?

4 Replies

These errors indicate your kernel is not compatible with the modules you're trying to run. If Linode's kernels do not contain the modules you need then you'll need to run your Linode on a distribution supplied kernel.

The following guide covers how to accomplish that: Distribution Supplied Kernels

mkdir /lib/modules/`uname -r`;
depmod -a

should make that warning go away.

i have the same issues, and it seems to be preventing my iptables-restore and ufw from starting properly on reboot….at least, that's what led me to realizing i have this issue. note that i can't mkdir the directory as caker recommends, because it already exists, and i can't "depmod -a" because I get the errors like dsmith posts.

I'm also getting hit by this one. caker's suggestion doesn't work. Is there a solution that doesn't involve using distribution kernels?


Please enter an answer

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct