AGPGART/NvAGP don't load

senorsnor · 08-18-2004, 11:37 AM

I just installed Fedora Core 1 and I'm having trouble getting my NVidia-drivers to work. I've compiled them, edited /etc/XF86Config, but when I start X I see the NVidia-splash-screen for a split-second, then X crashes without messages (not even when I `startx -- -verbose 5 -logverbose 5`. However, in /var/log/messages the following entries are made:

Code:

Aug 18 17:52:09 purr kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
Aug 18 17:52:09 purr kernel: agpgart: Maximum main memory to use for agp memory: 439M
Aug 18 17:52:09 purr kernel: agpgart: Detected Via Apollo Pro KT400 chipset
Aug 18 17:52:09 purr kernel: agpgart: unable to determine aperture size.
Aug 18 17:52:09 purr insmod: /lib/modules/2.4.26-1.ll.rhfc1.ccrma/kernel/drivers/char/agp/agpgart.o: init_module: Invalid argument
Aug 18 17:52:09 purr insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
Aug 18 17:52:09 purr insmod: /lib/modules/2.4.26-1.ll.rhfc1.ccrma/kernel/drivers/char/agp/agpgart.o: insmod agpgart failed

I do have a Via KT400 chipset, yet it isn't the Apollo Pro chipset (as far as I know; my motherboard is a AOpen AK778XN). So then I tried to use Nvidia's own agp-driver by adding the option "Option" "NvAGP" "1" to my XF86Config-file but it still crashes, adding the following entry to messages:

Code:

Aug 18 18:05:32 purr modprobe: modprobe: Can't locate module char-major-10-134

So then I tried not to use AGP at all, with "Option" "NvAGP" "0" but that gives the same error-message as "1".

Can anybody help me? I am able to load agpgart on slackware without a hitch so it must be something with Fedora but I can't figure out what it is...

320mb · 08-18-2004, 01:00 PM

try this instead................

Code:

Option "NvAgp"  "1"

type it just like you see it!

and this should go in /etc/modules.conf

Code:

alias char-major-195 nvidia

senorsnor · 08-18-2004, 03:59 PM

Tnx for your reply! As I said in my start post I already tried Option "NvAGP" "1" but it didn't work. (I even tried without capitals but no); the line in modules.conf was already there.

I found that if I uncomment the line Load "glx" from the Modules-section, it does actually work! However, this line should be present. I went over appendix C of the NVidia-Readme (checking installed libraries and symlinks) and they all seem to be ok, yet with Load "glx" enabled it just doesnt work...

senorsnor · 08-19-2004, 06:52 AM

So, for people out there who experience the same, the problem is two-folded:

1. agpgart doesn't load because it detects the wrong chipset, however, the nvidia-agp-driver did actually load. The char-major-10-134-entry in the logs had something to do with apm.

2. However, X didn't start because of something with GLX (the OpenGL-drivers). On the nvnews.com-forum I found the solution: replace /usr/lib/tls/libnvidia-tls.so.1.0.6111 by /usr/lib/libnvidia-tls.so.1.0.6111. This has worked for more people, yet nobody seems to know why ... anyway, it works for me too!