modprobe tun - ERROR: could not insert 'tun': Unknown symbol in module

November 2, 2014 31.5k views
LG
By:
LG

Unable to modprobe tun
ERROR: could not insert 'tun': Unknown symbol in module, or unknown parameter (see dmesg)

Nov 2 22:55:22 x1 kernel: [102643.488499] Loading kernel module for a network device with CAPSYSMODULE (deprecated). Use CAPNETADMIN and alias netdev- instead
Nov 2 22:56:48 x1 kernel: [102730.054589] tun: Unknown symbol ipv6proxyselect_ident (err 0)

ls /lib/modules/uname -r/kernel/drivers/net/tun.*

/lib/modules/3.2.0-4-amd64/kernel/drivers/net/tun.ko

lsb_release -a

No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.7 (wheezy)
Release: 7.7
Codename: wheezy

uname -a

Linux x1 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux

1 comment
  • ataliba January 12, 2016

    Anyone have the solution for this error ?

    I have this too, and try many things and nothing works.

Log In to Comment
10 Answers
seanp2k October 11, 2016

I was running into this as well, and I chose "DigitalOcean GrubLoader v0.2 (20160714) Debian" as my kernel (already had sudo apt-get install linux-image-$(uname -r) installed), ran poweroff , and turned instance back on via DO control panel. Now it's working again!

Reply
gaetancollaud December 30, 2014

Worked for me with the last kernel at the moment : Debian 7.0 x64 vmlinuz-3.2.0-4-amd64 (3.2.63-2+deb7u2)

Reply
kamaln7 MOD November 3, 2014

Run the following commands and then boot your droplet from the control panel:

sudo apt-get install linux-image-$(uname -r)
sudo poweroff
Reply
  • LG November 3, 2014

    apt-get install linux-image-$(uname -r)

    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    linux-image-3.2.0-4-amd64 is already the newest version.
    linux-image-3.2.0-4-amd64 set to manually installed.
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  • kamaln7 MOD November 3, 2014

    Ok, so the kernel is already installed. Try powering off your droplet from the command line and booting it up from the control panel:

    sudo poweroff
  • LG November 3, 2014

    I did try that but no luck.

  • thuejk November 3, 2014

    I have the same problem. The running kernel is 3.2.54-2, and I have no idea where it is coming from, since only 3.2.63-2+deb7u1 is installed.

    /boot/grub/menu.lst says that /boot/vmlinuz-3.2.0-4-amd64 is loaded, and dpkg says that /boot/vmlinuz-3.2.0-4-amd64 belongs to the linux-image-3.2.0-4-amd64, which is version 3.2.63-2+deb7u1.

  • LG November 3, 2014
    [deleted]
thuejk November 3, 2014

It seems that you actually have to choose which kernel is booted from the digital ocean control panel, and that the grub entry is ignored. From k.whitaker's comment ( https://www.digitalocean.com/community/questions/can-t-seem-to-load-fuse-module?comment=17236 ):

1) log into the digital ocean control panel
2) go to the droplet that has this issue.
3) go to settings, then kernel
4) change it to the latest kernel. i.e. for me its: * Debian 7.0 x64 vmlinuz-3.2.0-4-amd64 (3.2.60-1+deb7u3)
5) power down your droplet
6) power up.

Reply
  • LG November 3, 2014

    uname -a

    Linux x1 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2 x86_64 GNU/Linux

    modprobe tun

    ERROR: could not insert 'tun': Unknown symbol in module, or unknown parameter (see dmesg)

    [ 96.238722] tun: Unknown symbol ipv6proxyselectident (err 0)
    [ 96.241852] Loading kernel module for a network device with CAP    SYSMODULE (deprecated). Use CAPNETADMIN and alias netdev- instead
    [ 96.243990] Loading kernel module for a network device with CAP    SYS_MODULE

    Also tried with kernel that you have suggested, same results:

    root@m0:~# uname -a
    Linux x1 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u1 x86_64 GNU/Linux

    root@m0:~# modprobe tun
    ERROR: could not insert 'tun': Unknown symbol in module, or unknown parameter (see dmesg)

  • thuejk November 3, 2014

    You installed the 3.2.63-2 kernel from Digital Ocean. The kernel modules from debian are 3.2.63-2+deb7u1. So the Debian modules are another version (newer), hence the mismatch.

    Digital Ocean doesn't seem to have a 3.2.63-2+deb7u1 kernel available.

    Also tried with kernel that you have suggested, same results:

    I didn't recommend that kernel, I was just cut'N'pasting.

  • LG November 3, 2014

    Finally started to work with:

    uname -a

    Linux x1 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux

    modprobe tun

    It didn't work with any other kernel versions unfortunately.

    openvpn now working properly :)

raspiantorogame November 20, 2014

hi, i have this error on my vps
modprobe tun
libkmod: ERROR ../libkmod/libkmod.c:554 kmodsearchmoddep: could not open moddep file '/lib/modules/3.2.0-4-amd64/modules.dep.bin'

uname -a
Linux raspiantoro 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u1 x86_64 GNU/Linux

how to fix it?

Reply
antarctician November 27, 2014

Hi, I had the same problem after upgrading my Debian from version 6 to 7. I had switched to the latest kernel from the control panel and rebooted but was still getting errors.

So if I don't miss anything, I removed /dev/net/tun and then ran modprobe tun again and it somehow worked.

Hope this helps

Reply
stv0g December 18, 2014

Same problem occurs again:

Latest Debian Kernel revision: 3.2.63-2+deb7u2

Latest DO Kernel revision: 3.2.63-2+deb7u1

Sorry guys, but we can't we boot official stock kernels?

Best Regards,

Steffen

Reply
LG December 21, 2014

Keep in mind also that there is some kind of throttle on link from DO dropplets, let me know if you get more that 400-450KB/sec speed with openvpn. Without VPN you will have 1.0MB/s - 1.1MB/s still investigating the possible cause.

Reply
enomoto January 18, 2015

To correct this, you need:

1) Verify your kernel version:

uname -a

2) Go to the Digital Ocean Panel, in Droplets -> Settings -> Kernel, choose the same kernel e clik in Change

3) Go to the Power menu and do a POWER CYCLE, a single reboot from your VM doesn't apply the changes.

Reply
mots February 2, 2015

hi,

i tried quite a few different kernels. i am a bit lost about this.

uname -a gives me :
3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux

grub (even though it is ignored) seems to point (looking at the menu.lst and the date if the vmlinuz file) this kernel dates from mid january.
Debian 7.0 x64 vmlinuz-3.2.0-4-amd64 (3.2.65-1+deb7u1)

i tried to select 3.2.54-2 kernel in droplet options, which by the way is only available in 32bit flavour.
or 3.2.65-1+deb7u1.
i also tried last debian update Debian 7.0 x64 vmlinuz-3.2.0-4-amd64 (3.2.60-1+deb7u3)

no luck with any of them.

did anyone got this sorted recently ?

Reply
Have another answer? Share your knowledge.