On Mon, Dec 07, 2009 at 05:58:20PM +0100, Takashi Iwai wrote:
At Mon, 07 Dec 2009 11:51:58 -0500, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/07/2009 11:46 AM, Takashi Iwai wrote:
At Sun, 06 Dec 2009 18:34:52 -0500, Jeff Mahoney wrote:
The problem in general is that we can't tell the kernel about rules for a module without first loading the module.
But we can know the PCI id before loading the corresponding module, at least. So, it'd be possible to load the module only when no blacklisted pci id is found in the modprobe install script.
Yeah, but then we're in essentially the same position as we would be if we just blacklisted the module entirely, right?
No, what I suggest is to write a script to check lspci, then load the module selectively only when any of lspci devices aren't on the blacklist.
For example, something like below: % cat /sbin/i915_loader.sh #!/bin/sh modeset="" /sbin/lspci -n | grep -q 1234:5678 || modeset="modeset=1" exec /sbin/modprobe i915 $modeset
Then add a line below to modprobe.d/somewhere.conf install i915 /sbin/i915_loader.sh
Should be: install --ignoreinstall i915 /sbin/i915_loader.sh to avoid a loop. Thanks for the idea, Takashi! This will do the trick :) Cheers, Egbert. -- Egbert Eich (Res. & Dev.) SUSE LINUX Products GmbH X Window System Development Tel: +49 911-740 53 0 http://www.suse.de ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org