You are not logged in.

#1 2008-01-17 04:53:57

blu3ness
Member
From: Edmonton, Canada
Registered: 2007-12-28
Posts: 169

blacklisted module still gets loaded, why?

Hello all, I tried to blacklist the fglrx module to disable 3d acceleration and only get 2d (this way I can suspend, god dam it), I tried adding !fglrx into the modules array of rc.conf, that didn't work, I also tried to add an entry into MODULE_BLACKLIST() array, nothing changed either. So yeah... why? sad


Archlinux on Compaq Presario v5000 laptop smile

Offline

#2 2008-01-17 05:17:06

bender02
Member
From: UK
Registered: 2007-02-04
Posts: 1,328

Re: blacklisted module still gets loaded, why?

Sometimes the modules are loaded earlier than rc.conf's MODULES field starts to matter. Have a look at
http://bbs.archlinux.org/viewtopic.php?id=41062

Offline

#3 2008-01-17 05:21:43

fwojciec
Member
Registered: 2007-05-20
Posts: 1,411

Re: blacklisted module still gets loaded, why?

It's possible that it is in the kernel image generated when you were installing the kernel.  Try rmmoding it manually, blacklisting it in /etc/rc.conf and then regenerating the kernel image ("mkinitcpio -p kernlel26" as root) and see if that helps.

Offline

#4 2008-01-17 10:45:14

chimeric
Member
From: Munich, Germany
Registered: 2007-10-07
Posts: 254
Website

Re: blacklisted module still gets loaded, why?

I think the problem is rather that blacklisting a module tells udev to not load a certain module in any case, my strongest guess is that you have fglrx as driver in your xorg.conf and Xorg therefore loads it if it's not loaded already. You could try to switch to another driver, maybe suspend works with the open source version of the ATI drivers?

Offline

Board footer

Powered by FluxBB