CompTIA Linux+ (XK0-006)System ManagementMedium
A technician needs to permanently prevent the 'nouveau' kernel module from loading automatically on system boot because it conflicts with a proprietary NVIDIA driver. Which configuration approach is correct?
- ARun 'rmmod nouveau' before every reboot
- BDelete the module file from /lib/modules/ manually
- CAdd 'blacklist nouveau' to a file in /etc/modprobe.d/ and regenerate the initramfs
- DAdd 'nouveau off' to /etc/fstab
Show answer & explanationAnswer & explanation
Correct answer: C. Add 'blacklist nouveau' to a file in /etc/modprobe.d/ and regenerate the initramfs
Persistent module blacklisting is done by creating a .conf file in /etc/modprobe.d/ containing 'blacklist nouveau', followed by regenerating the initramfs (e.g., with dracut or update-initramfs) so the change takes effect at boot, especially if the module is loaded early.
Why the other options are wrong
- A. rmmod only unloads temporarily and must be repeated after every reboot.
- B. Deleting module files manually is unsupported and can break package management.
- D. /etc/fstab controls filesystem mounts, not kernel module loading.
Kernel Module Blacklisting
A method to prevent a kernel module from auto-loading by adding a 'blacklist <module>' directive in /etc/modprobe.d/.
- Files typically named blacklist.conf or custom .conf
- May require initramfs regeneration if module loads early boot
- Does not remove the module, only prevents auto-load
Memory trick: Blacklist = bouncer at the door, keeps unwanted module out permanently