On 06/14/2016 01:17 PM, Christoph Hellwig wrote: > On Mon, Jun 13, 2016 at 08:32:41AM -0400, Prarit Bhargava wrote: >> Blacklisting a module in linux has long been a problem. The process of >> blacklisting a module has changed over time, and it seems that every OS >> does it slightly differently and depends on the age of the init system >> used on that OS. > > And why would we care about blacklisting a module? <rant> I have a new system that I want to install that a customer could not install any Linux OS on. It's sitting on my desk right now because I finally had to get them to send me the system. And I *cannot* get the bloody thing to install anything recent because the damned nouveau driver keeps blowing up in the latest Fedora rawhide (which is pretty close to upstream), or install anyting older because the storage isn't detected on older releases. I have *no* way of stopping the driver from loading so that I can at least start debugging, or provide valuable debug information in a kernel.org bugzilla (or appropriate mailing list). So what I'm stuck with now is a very expensive (albeit pretty) paperweight. </rant> Sorry about the rant ... but I had to let it all out Christoph ... :) Now, I am smart enough to install to a USB stick, remove the nouveau driver from both the install image and the initramfs, play around with the myriad and random BIOS settings on this laptop (I will note that these are different for EVERY piece of hardware) to figure out how to get the BIOS or EFI and Secure Boot settings to detect the USB stick, cross my fingers and stand on one leg while I pray to $deity that the system boots. I do NOT expect random user to follow those steps in order to install Fedora or another other upstream-following Linux OS. They won't, and users turn to other OSes that "just work". That does nothing for the community. It does nothing to improve bug reporting. It does nothing to improve the kernel. I'd much rather tell those users to add "module_blacklist=nouveau" and send me some debug information so I can find out what the issue might be, and find hardware similar to theirs to help them out. I still might have to tell that user to send me their hardware but that's always a last resort. P. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
