Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
Opened by Aaron Griffin (phrakture) - Monday, 05 December 2005, 16:09 GMT
Last edited by dorphell (dorphell) - Monday, 05 December 2005, 18:18 GMT
|
DetailsSeeing 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
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.