/etc/modules.d is long deprecated. please provide an equivalent /etc/modprobe.d file.
I have this ready for a while.. I've just decided to include this with the driver releases for the 2.6.25 kernel.
Chainsaw is taking over this package.
All new ebuilds install /etc/modprobe.d/nvidia; this includes 173.08 (masked), 173.14.05, 173.14.09 & 177.13 (masked).
71.x and 96.x still need to do this.
*** Bug 230289 has been marked as a duplicate of this bug. ***
71.86.06 & 96.43.07 install the file in the right place and are compatible with 2.6.26; will be closing this bug shortly.
In CVS. Thanks guys.
Thank you, Tony.
after performing a kernel upgrade (from 2.6.26-gentoo-r4 to 2.6.29-gentoo-r5) I was noticing "* please file a bug about /etc/modules.d/nvidia: it needs an /etc/modprobe.d/nvidia" I have not seen this before, but I cannmot guarantee that i have just not noticed it yet. I checked, and both /etc/modules.d/nvidia and /etc/modprobe.d/nvidia.conf exist on my system: # diff /etc/modules.d/nvidia /etc/modprobe.d/nvidia.conf 7c7 < # options see /usr/share/doc/nvidia-drivers-169.12/README --- > # options see /usr/share/doc/nvidia-drivers-185.18.14/README 9,35d8 < # To enable Side Band Adressing: NVreg_EnableAGPSBA=1 < # < # To enable Fast Writes: NVreg_EnableAGPFW=1 < # < # To enable both for instance, uncomment following line: < # < options nvidia NVreg_EnableAGPSBA=1 NVreg_EnableAGPFW=1 < < # If you have a mobile chip, you may need to enable this option < # if you have hard lockups when starting X. < # < # See: Appendix I. Configuring your laptop < # In /usr/share/doc/nvidia-drivers-100.14.19/README for full details < # < # Choose the appropriate value for NVreg_Mobile from the table: < # Value Meaning < # ---------- -------------------------------------------------- < # 0xFFFFFFFF let the kernel module autodetect the correct value < # 1 Dell laptops < # 2 non-Compal Toshiba laptops < # 3 all other laptops < # 4 Compal Toshiba laptops < # 5 Gateway laptops < # < #options nvidia NVreg_SoftEDIDs=0 NVreg_Mobile=3 < < I guess somewhere between 169.12 and 185.18.14 the ebuild reverted to the old behaviour... can I safely # mv /etc/modules.d/nvidia /etc/modprobe.d/nvidia.conf and forget about it ?