You are not logged in.
I would rather have these options in /etc/modprobe.d/* than in /boot/grub/menu.lst, but setting them in modprobe.d seems to have no effect. What's wrong?
[root@x220 ~]# cat /etc/modprobe.d/i915.conf
options i915 i915_enable_rc6=1
options i915 i915_enable_fbc=1
options i915 lvds_downclock=1
[root@x220 ~]# head /sys/module/i915/parameters/* | egrep -A1 "(i915_|downclock)"
==> /sys/module/i915/parameters/i915_enable_fbc <==
-1
--
==> /sys/module/i915/parameters/i915_enable_rc6 <==
-1
--
==> /sys/module/i915/parameters/lvds_downclock <==
0
Setting them from menu.lst works just perfectly.
Offline
Do you have the i915 module inside the initramfs? If yes, is the i915.conf file also there?
Offline
Do you have the i915 module inside the initramfs? If yes, is the i915.conf file also there?
RIght! I forgot to add it to mkinitcpio.conf. Thanks!
But that leads to another question. I also have this file:
[root@x220 ~]# cat /etc/modprobe.d/mei.conf
blacklist mei
But this works without adding it to mkinitcpio.conf. Why is that? What's the difficerence between module options and blacklisting of modules in that respect?
Offline
Is mei in in the initramfs? Probably not. That's the difference - a module loaded from the initramfs also needs it's configurations there.
Offline
That makes sense. Thank you.
Offline
And you could also write all options in the first line after "options [module]" in conf file instead of three lines.
The greatest threat to knowledge is not ignorance - it is the illusion of knowledge!
Offline
I see you just dumped the /sys path of i915, it might be easier to use systool.
# systool -m i915 -av
Of course, then you need root access (otherwise the parameters don't show up).
Offline