FS#3583 - advanced hwdetect blacklist

Attached to Project: Arch Linux
Opened by Aaron Griffin (phrakture) - Monday, 05 December 2005, 16:09 GMT
Last edited by dorphell (dorphell) - Monday, 05 December 2005, 18:18 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Seeing that hwdetect now seems to load a huge amount of modules compare to other avenues, many people like to blacklist the excess modules they never use.

In my personal case, I used to use a static modules array, of 6-7 modules. Now, with hwdetect, I blacklist almost 20 modules (all firewire, all pcmcia, lp stuff, pcspkr, 8139cp, intel-agp, etc).

It'd be nice to have a way to blacklist an entire subsystem in one go... for instance:

MOD_BLACKLIST=(pcspkr 'subsystem:firewire' 'subsystem:pcmcia')

On a side note, using the existing MODULES array and checking the "!" modules, seems like an interesting idea as well, but that's all syntax.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 27 March 2006, 15:18 GMT
Reason for closing:  Fixed
Comment by dorphell (dorphell) - Monday, 05 December 2005, 18:16 GMT
I've not had time to play around with this but.. if you block the "firmware_class" module, the other firmware modules should not load because they all depend on that main firmware driver.

tpowa: see.. this is why i thought that "show-what-will-load" option would be useful... it would help people resolve blacklist dependencies and such.
Comment by Tobias Powalowski (tpowa) - Monday, 27 March 2006, 15:18 GMT
replaced now by udev hwdetect is not invoke d on boot anymore

Loading...