GNOME Bugzilla – Bug 555269
should respect blacklisted modules on reload
Last modified: 2008-11-25 17:36:32 UTC
Please describe the problem: currently the modreload() function in pm-utils ignores blacklisted modules, that exposes problems with hardware where two valid modules exist for the same device and only one is blacklisted. Steps to reproduce: 1. have hardware that can be drive by two different modules, i.e. a madwifi driven wlan card that can use ath5k (new free driver) or ath_pci, assume ath_pci (madwifi) provides features needed that ath5k doesnt provide yet. 2. blacklist ath5k to not be used for the device in an /etc/modprobe.d/blacklist-ath file 3. note that everything works fine on boot with this setup, suspend and resume, notice that ath5k suddenly got loaded on resume, superseding ath_pci Actual results: the wrong module gets used on resume Expected results: expected would be the blacklist being respected and thus the module that's blacklisted not being used Does this happen every time? it happens every suspend/resume cycle Other information: adding -b to the modprobe command in modreload() fixes this problem (see man modprobe)
Please report this in bugzilla.freedesktop.org against pm-utils, together with the patch. Thanks!