NVdriver 1.0-3123 ignores NVreg_ReqAGPRate

[randolf]

Hi,

after successful installation of the NVdriver
(1.0-3123) on my system (440BX-chipset/Diamond
Viper 770 (TNT2)/Debian Woody (3.0)) I experienced
two complete lockups of the machine related
to the start of an OpenGL using application
(nothing to be found in any logfile). Pretty
scary experience: I could not even telnet
remotely into the machine for graceful reboot...
Anyway, /proc/... was telling me nvidia-AGP
was in use, at AGP-rate 2x. I decided to lower
the AGP-rate, however, the driver completely
ignored any "options" given right before or
after the "alias" in my /etc/modules... It even
ignored the option when appended to the insmod
command. I had to hack os-registry.c. Is this
the way this is supposed to work, or "just" a
bug? (Took me 3h to figure out!)

best regards,
Randolf,
--
http://www.ayam3d.org/ Reconstruct the World!

[bwkaz]

Did you see the comments in os-registry.c right next to the ReqAGPRate setting? ;)

/*
* Option: ReqAGPRate
*
* ...
*
* This is completely unsupported!
*
* ...
*
* This option is disabled by default, see below for information on how
* to enable it.
*/ Below, there are more comments:

/*
* You can enable any of the registry options disabled by default by
* editing their respective entries in the table below. Options with
* two leading underscores ("__EnableAGPSBA") are disabled; you can
* enable such options by removing the underscores; in order for the
* changes to take effect, you need to recompile and load the kernel
* module.
*/So it appears you can make the option be recognized by editing os-registry.c and removing the two underscores from the second section (on or about line 330).

[randolf]

While this is all true, the FAQ does not mention
hacking os-registry.c, it just says: "add
options NVdriver NVreg_ReqAGPRate=1
to the appropriate modules configuration file".
This did not work for me! And yes, I did
"rmmod NVdriver" and "update-modules" for each
test.
Even after enabling the NVreg_ReqAGPRate option
in os-registry.c it still ignored the 1x-setting
from the modules configuration file! I also had to
tweak the value of the option in os-registry.c.

Sadly enough: all this tweaking did not help with
my original problem, as I got another lockup
today. Now trying without AGP. Disabling AGP
worked as documented via XF86Config-4. ;)

best regards,
Randolf,
--
http://www.ayam3d.org/ Reconstruct the World!