[ATrpms-users] NVidia issues

[Paulo Cavalcanti]

On Mon, Mar 10, 2008 at 5:56 PM, Axel Thimm <Axel.Thimm at atrpms.net> wrote:

> On Mon, Mar 10, 2008 at 01:20:56PM +0000, Neil Bird wrote:
> > Around about 09/03/08 09:43, Axel Thimm typed ...
> > > The fix would be to blacklist all but the current nvidia module. The
> > > problem is that the different nvidia module register into the
> > > modules.{alias,pcimap,symbols} files, and then the PCI Id's trigger
> > > whatever came first in the list.
> > > If someone experiments with blacklisting and manages to get modules.*
> > > behaving properly I'll be glad to stuff it into
> nvidia-graphics-switch.
> >
> >    Whereabouts would that be?  I've fiddle with the blacklisting stuff
> > before (DVB cards) but not with much knowledge!
>
> It would be in modprobe.conf on nvidia-*. The issue is that depmod
> should only look at nvidia.ko and not all the other nvidia-*.ko
> modules.
>
> >    I couldn't figure out (for nVidia) which other file/config was
> affecting
> > things.  I.e., what's making the kernel (from PCI ID?) load whatever
> module?
> >   modprobe.conf is OK, and the udev stuff is version agnostic.
>
> It's modules.pcimap. Which is constructed out of the *.ko present. If
> they are blacklisted modules.pcimap won't point to them.
>


Yes, you are right as always, Axel.

I just needed to create

/etc/modprobe.d/blacklist-nvidia

with a single line in my case:

blacklist nvidia-169_09

Nore that I have only nvidia 169_09 and 169_12 installed.

Therefore, the nvidia switch must only scan all kmdls installed
and blacklist all, but the selected one.

Maybe someone else should also test this workaround before coding it.

Thanks.

-- 
Paulo Roma Cavalcanti
LCG - UFRJ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-users/attachments/20080314/8781e550/attachment.html