Blacklisting modules in modprobe.d and kernel params is not working
2
Ok, I have read and followed the instructions on the following posts, however, my kernel modules are still being loaded...
Kernel module blacklist not working
How do I disable a kernel module persistently?
Excluding kernel modules through /etc/modprobe.d/blacklist.conf does not work
I am running
Debian GNU/Linux 9
Originally I created a file /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist nvidiafb
I have tried creating files for the individual modules
/etc/modprobe.d/nvidiafb.conf = blacklist nvidiafb
/etc/modprobe.d/nouveau.conf = blacklist nouveau
I have tried adding to the kernel boot params
modprobe.blacklist=nouveau modprobe.blacklist=nvidiafb
I have tried faking the install in /etc/modprobe.d/blacklist.conf
install nouveau /bin/false
install nvidiafb /bin/false
And after each try, I have ran
depmod -ae && update-initramfs -u
yet, the modules still seem to be loaded
02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
Flags: fast devsel, IRQ 10
Memory at dc000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Memory at a0000000 (64-bit, prefetchable) [disabled] [size=256M]
Memory at b0000000 (64-bit, prefetchable) [disabled] [size=32M]
I/O ports at d000 [disabled] [size=128]
Expansion ROM at dd000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [128] Power Budgeting <?>
Capabilities: [420] Advanced Error Reporting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Capabilities: [900] #19
Kernel driver in use: vfio-pci
Kernel modules: nvidiafb, nouveau
It seems that I have ran out of solutions to try
modprobe
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
add a comment |
2
Ok, I have read and followed the instructions on the following posts, however, my kernel modules are still being loaded...
Kernel module blacklist not working
How do I disable a kernel module persistently?
Excluding kernel modules through /etc/modprobe.d/blacklist.conf does not work
I am running
Debian GNU/Linux 9
Originally I created a file /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist nvidiafb
I have tried creating files for the individual modules
/etc/modprobe.d/nvidiafb.conf = blacklist nvidiafb
/etc/modprobe.d/nouveau.conf = blacklist nouveau
I have tried adding to the kernel boot params
modprobe.blacklist=nouveau modprobe.blacklist=nvidiafb
I have tried faking the install in /etc/modprobe.d/blacklist.conf
install nouveau /bin/false
install nvidiafb /bin/false
And after each try, I have ran
depmod -ae && update-initramfs -u
yet, the modules still seem to be loaded
02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
Flags: fast devsel, IRQ 10
Memory at dc000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Memory at a0000000 (64-bit, prefetchable) [disabled] [size=256M]
Memory at b0000000 (64-bit, prefetchable) [disabled] [size=32M]
I/O ports at d000 [disabled] [size=128]
Expansion ROM at dd000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [128] Power Budgeting <?>
Capabilities: [420] Advanced Error Reporting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Capabilities: [900] #19
Kernel driver in use: vfio-pci
Kernel modules: nvidiafb, nouveau
It seems that I have ran out of solutions to try
modprobe
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
I don't know the answer, but imo the situation is ridiculous. If a module is blacklisted on the command line or in blacklist.conf, then the kernel should simply refuse requests to load it, from any source. Why else would a user blacklist a module, unless they don't want it to load?
– Time4Tea
13 hours ago
I think it's only/etc/modprobe.d/blacklistno.conf. I also think itsmodule_blacklistand notmodprobe.blacklistfor the kernel command line. I am a little uncertain b/c I have a feeling this interface keeps changing over time.
– Bananguin
3 hours ago
add a comment |
2
2
2
Ok, I have read and followed the instructions on the following posts, however, my kernel modules are still being loaded...
Kernel module blacklist not working
How do I disable a kernel module persistently?
Excluding kernel modules through /etc/modprobe.d/blacklist.conf does not work
I am running
Debian GNU/Linux 9
Originally I created a file /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist nvidiafb
I have tried creating files for the individual modules
/etc/modprobe.d/nvidiafb.conf = blacklist nvidiafb
/etc/modprobe.d/nouveau.conf = blacklist nouveau
I have tried adding to the kernel boot params
modprobe.blacklist=nouveau modprobe.blacklist=nvidiafb
I have tried faking the install in /etc/modprobe.d/blacklist.conf
install nouveau /bin/false
install nvidiafb /bin/false
And after each try, I have ran
depmod -ae && update-initramfs -u
yet, the modules still seem to be loaded
02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
Flags: fast devsel, IRQ 10
Memory at dc000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Memory at a0000000 (64-bit, prefetchable) [disabled] [size=256M]
Memory at b0000000 (64-bit, prefetchable) [disabled] [size=32M]
I/O ports at d000 [disabled] [size=128]
Expansion ROM at dd000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [128] Power Budgeting <?>
Capabilities: [420] Advanced Error Reporting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Capabilities: [900] #19
Kernel driver in use: vfio-pci
Kernel modules: nvidiafb, nouveau
It seems that I have ran out of solutions to try
modprobe
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
Ok, I have read and followed the instructions on the following posts, however, my kernel modules are still being loaded...
Kernel module blacklist not working
How do I disable a kernel module persistently?
Excluding kernel modules through /etc/modprobe.d/blacklist.conf does not work
I am running
Debian GNU/Linux 9
Originally I created a file /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist nvidiafb
I have tried creating files for the individual modules
/etc/modprobe.d/nvidiafb.conf = blacklist nvidiafb
/etc/modprobe.d/nouveau.conf = blacklist nouveau
I have tried adding to the kernel boot params
modprobe.blacklist=nouveau modprobe.blacklist=nvidiafb
I have tried faking the install in /etc/modprobe.d/blacklist.conf
install nouveau /bin/false
install nvidiafb /bin/false
And after each try, I have ran
depmod -ae && update-initramfs -u
yet, the modules still seem to be loaded
02:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070]
Flags: fast devsel, IRQ 10
Memory at dc000000 (32-bit, non-prefetchable) [disabled] [size=16M]
Memory at a0000000 (64-bit, prefetchable) [disabled] [size=256M]
Memory at b0000000 (64-bit, prefetchable) [disabled] [size=32M]
I/O ports at d000 [disabled] [size=128]
Expansion ROM at dd000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [250] Latency Tolerance Reporting
Capabilities: [128] Power Budgeting <?>
Capabilities: [420] Advanced Error Reporting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
Capabilities: [900] #19
Kernel driver in use: vfio-pci
Kernel modules: nvidiafb, nouveau
It seems that I have ran out of solutions to try
modprobe
modprobe
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
edited 11 hours ago
Rui F Ribeiro
39.5k1479133
39.5k1479133
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
asked 13 hours ago
Jeffrey L. RobertsJeffrey L. Roberts
99113
99113
I don't know the answer, but imo the situation is ridiculous. If a module is blacklisted on the command line or in blacklist.conf, then the kernel should simply refuse requests to load it, from any source. Why else would a user blacklist a module, unless they don't want it to load?
– Time4Tea
13 hours ago
I think it's only/etc/modprobe.d/blacklistno.conf. I also think itsmodule_blacklistand notmodprobe.blacklistfor the kernel command line. I am a little uncertain b/c I have a feeling this interface keeps changing over time.
– Bananguin
3 hours ago
add a comment |
I don't know the answer, but imo the situation is ridiculous. If a module is blacklisted on the command line or in blacklist.conf, then the kernel should simply refuse requests to load it, from any source. Why else would a user blacklist a module, unless they don't want it to load?
– Time4Tea
13 hours ago
I think it's only/etc/modprobe.d/blacklistno.conf. I also think itsmodule_blacklistand notmodprobe.blacklistfor the kernel command line. I am a little uncertain b/c I have a feeling this interface keeps changing over time.
– Bananguin
3 hours ago
I don't know the answer, but imo the situation is ridiculous. If a module is blacklisted on the command line or in blacklist.conf, then the kernel should simply refuse requests to load it, from any source. Why else would a user blacklist a module, unless they don't want it to load?
– Time4Tea
13 hours ago
I don't know the answer, but imo the situation is ridiculous. If a module is blacklisted on the command line or in blacklist.conf, then the kernel should simply refuse requests to load it, from any source. Why else would a user blacklist a module, unless they don't want it to load?
– Time4Tea
13 hours ago
I think it's only
/etc/modprobe.d/blacklist no .conf. I also think its module_blacklist and not modprobe.blacklist for the kernel command line. I am a little uncertain b/c I have a feeling this interface keeps changing over time.– Bananguin
3 hours ago
I think it's only
/etc/modprobe.d/blacklist no .conf. I also think its module_blacklist and not modprobe.blacklist for the kernel command line. I am a little uncertain b/c I have a feeling this interface keeps changing over time.– Bananguin
3 hours ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495204%2fblacklisting-modules-in-modprobe-d-and-kernel-params-is-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495204%2fblacklisting-modules-in-modprobe-d-and-kernel-params-is-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I don't know the answer, but imo the situation is ridiculous. If a module is blacklisted on the command line or in blacklist.conf, then the kernel should simply refuse requests to load it, from any source. Why else would a user blacklist a module, unless they don't want it to load?
– Time4Tea
13 hours ago
I think it's only
/etc/modprobe.d/blacklistno.conf. I also think itsmodule_blacklistand notmodprobe.blacklistfor the kernel command line. I am a little uncertain b/c I have a feeling this interface keeps changing over time.– Bananguin
3 hours ago