On 10/15/2010 06:21 PM, Konstantin Svist wrote: > On 10/15/2010 02:33 AM, Michael D. Setzer II wrote: >> I have a project in which I build most nic and disk modules into the kernel file >> so it will support hardware with any of the devices. In most cases this works >> just fine with the kernel only loading the correct ones. But rarely, it stops on a >> module that is not in the hardware. The latest one is the myri10ge module for >> one users. I have built a kernel for this user with this module disable, but >> would like to know if there is a kernel command line option to disable module. >> blacklist doesn't seem to work with built-in modules. >> >> Thanks. >> > > inside /etc/modprobe.d/blacklist.conf: > install <MODULE> /bin/true The OP is talking about components that have been configured to be linked into the main kernel image (i.e. they are not modules at all). Any modprobe.conf/modprobe.d hacks will only affect things built as separate object files (.ko files, or .o for 2.4 and earlier). To answer the original question: generally speaking, you can't unless the component itself provides some mechanism for it to be disabled via a kernel command line option. The ability to completely disable certain modules is one of the benefits of having a modular kernel build in the first place. Regards, Bryn. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
