|
|
#13 | |
|
NVIDIA Corporation
Join Date: Dec 2004
Posts: 8,763
|
What happens if you run the modprobe command manually with those options?
|
|
|
|
|
|
|
#14 | |
|
Registered User
Join Date: Aug 2007
Posts: 22
|
Ahah, adding the options to /etc/modprobe.conf directly, they work!
Should modprobe.conf be set with modules.conf, or are they independent? |
|
|
|
|
|
|
#15 |
|
NVIDIA Corporation
Join Date: Dec 2004
Posts: 8,763
|
modules.conf is normally only used with 2.4.x kernels.
|
|
|
|
|
|
#16 | |
|
Registered User
Join Date: Aug 2007
Posts: 22
|
Well, either way, the nvidia options in /etc/modules.d/nvidia aren't appearing in /etc/modprobe.conf - it's a problem with gentoo's module-init-tools, not your driver package. ( I should never have doubted you, nvidia! )
Thanks for your help. Andy |
|
|
|
|
|
|
#17 | |
|
Registered User
Join Date: Apr 2006
Posts: 277
|
Quote:
|
|
|
|
|
|
|
#18 | |
|
Registered User
Join Date: Aug 2007
Posts: 22
|
Hullo again!
Yes, I ran update-modules, which generates /etc/modules.conf .. the two lines of the form 'options nvidia NVoption_1 NVoption_2 ...' correctly appear there. Now when I run regenerate-modprobe.conf, which is what makes /etc/modprobe.conf (used by 2.6.x kernels) from /etc/modules.conf, I find that it only handles a single 'options ...' line per module name, hence picking out only the second 'options ...' line from /etc/modules.d/nvidia (options nvidia NVreg_DeviceFileMode=432 NVreg_DeviceFileUID=0 ... etc), and thus ignoring my options NVreg_EnableAGPSBA and NVreg_EnableAGPFW. i.e. not nvidia's fault. Andy |
|
|
|
|
![]() |
| Thread Tools | |
|
|