Hi, I hit this problem too.
Also, a whole load of other modules were repporting the problem (mostly file systems: ntfs, fat, fuse qnx, ...) While investigating, I noticed that 'uname -a' reported the latest kernel that I installed during the update (4.9.0-2-amd64), although I hadn't rebooted yet. Could this be part of the problem? It looks like modprobe is trying to load the module for the newly updated kernel version, although it isn't running yet. modprobe should load kernel modules for the kernel that's currently running, shouldn't it? The problem goes away after a reboot, of course. Cheers, Dave -- David Haworth Baiersdorf, Germany d...@fen-net.de
