At some point during boot, the systctl variable kernel.modules_disabled gets set to 1, effectively disabling all future loading of kernel modules.
I have grep'ed all of my /etc for "modules_disabled" and looked in /etc/default/grub but I can't figure out how my Sid box (4.13.0-1-amd64 kernel) is setting this.
Any module I add to /etc/modules will get properly loaded before kernel.modules_disabled gets set, but as soon as I login and get a shell, "cat /proc/sys/kernel/modules_disabled" returns 1 and any modprobe call fails.
Is there something I overlooked?
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[SOLVED] "kernel.modules_disabled = 1" shortly after boot
[SOLVED] "kernel.modules_disabled = 1" shortly after boot
Last edited by fmarier on 2017-11-21 10:37, edited 1 time in total.
Re: "kernel.modules_disabled = 1" shortly after boot
Here's the reason: https://packages.debian.org/sid/lockdown
I totally forgot I had installed that package.
I totally forgot I had installed that package.