Can't have an AGP 4x on via

[Jah]

Hi !
I have flash the motherboard with the last bios.
I have activated AGP 4x on bios (gigabytes GA-6VTXD).
I am running kernel 2.4.19.
i have in my /etx/X11/XF86Config:

[...]
Load "glx"
[...]
Section "Device"
Identifier "Asus v7700 GTS"
Driver "nvidia"
VideoRam 32768
Option "NvAgp" "2"
[...]

I have the 3123 version of nvidia driver.
i load NVdriver by typing:

modprobe NVdriver NVreg_EnableVia4x=1

/var/log/kern.log:

nvidia: loading NVIDIA Linux x86 NVdriver Kernel Module 1.0-3123
NVRM: AGPGART: VIA Apollo Pro chipset
NVRM: AGPGART: aperture: 256M @ 0xe0000000
NVRM: AGPGART: aperture mapped from 0xe0000000 to 0xf99ee000
NVRM: AGPGART: mode 4x

after a startx:
root@gnutopya / # cat /proc/driver/nvidia/agp/card
Fast Writes: Supported
SBA: Supported
AGP Rates: 2x 1x
Registers: 0x1f000213:0x1f000102
root@gnutopya / # cat /proc/driver/nvidia/agp/host-bridge
Host Bridge: Via Apollo Pro
Fast Writes: Not Supported
SBA: Supported
AGP Rates: 2x 1x
Registers: 0x1f000203:0x00000102
root@gnutopya / # cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: AGPGART
AGP Rate: 2x
Fast Writes: Disabled
SBA: Disabled

My nvidia card is an asus v7700 geforce 2 GTS with agp 4x supported.

Have you any idea to have agp 4x running ?
Thanks ...

[crimsun]

I vaguely remember there being discussion on this forum regarding a typo in 1.0-3123 wrt this parameter:

NVreg_EnableVia4x

Try using

modprobe NVdriver NVreg_enableVia4x=1

[Jah]

Originally posted by crimsun
I vaguely remember there being discussion on this forum regarding a typo in 1.0-3123 wrt this parameter:

NVreg_EnableVia4x

Try using

modprobe NVdriver NVreg_enableVia4x=1
thanks but i have already tryied this has you can see up.

[Andy Mecham]

Please see http://www.nvnews.net/vbulletin/showthread.php?s=&threadid=3737

Note the lowercase 'e' in NVreg_enableVia4X.

--andy

[Jah]

ok thanks, i will try with "e".
I use this doc , and perhaps there's an error (It's "E" inside)
http://www.gentoo.org/doc/en/nvidia_tsg.xml
thanks

[Andy Mecham]

As mentioned in the thread I pointed you to, there was a typo in the driver.

--andy