I followed the instructions in your nVidia guide. I had to add the following to my kernel configuration to get it to work. CONFIG_AGP=y CONFIG_AGP_NVIDIA=y You may want to add this to your guide.
(In reply to comment #0) > I followed the instructions in your nVidia guide. I had to add the following to > my kernel configuration to get it to work. It isn't necessarily required. I use the binary nvidia drivers, but my kernel config looks like this: CONFIG_AGP=y CONFIG_AGP_NVIDIA is not set CONFIG_FB_NVIDIA is not set So while I do have an AGP chipset, 9 times out of 10, setting fb_nvidia and/or agp_nvidia will conflict with the generic chipset support and the nvidia binary driver. Besides, not everyone's chipset uses AGP. There are lots of PCI-express motherboards floating around, and they shouldn't have AGP set in their kernel config. I'm reluctant to include this based on my experience and on the many, many other reports I've heard that went into the making of this guide. What's your motherboard/chipset/kernel version?
Mine is the same config as Josh, kernel-wise and I have no issues with the nvidia and binary drivers.
(In reply to comment #2) Oh, I forgot: the "agp_foo" modules created by your kernel are for your *chipset's* AGP. Even if you have an nvidia card, if you have an Intel motherboard and you wanted (for some reason) to use that agp, you'd want to use agp_intel, *not* agp_nvidia. But much of the time the generic agpgart driver is the only one that works properly with the nvidia drivers. Recommend this bug be closed?
Hold on, the guide should still say to set, CONFIG_AGP=y Without that, my setup wouldn't work.
(In reply to comment #4) > Hold on, the guide should still say to set, > CONFIG_AGP=y > Without that, my setup wouldn't work. > Hmm. Not everyone uses AGP, though; an increasing amount of users have PCI-express graphics cards. ...this might need to be addressed.
Weird; it unassigned it when I reopened it. I'll take this again. The patch will go in soon unless there are any objections.
Whoops, grabbed the wrong bug. Reassigning back to the GDP. Besides, I think fox2mike wanted this one anyway. :)
Fixed in CVS; thanks for reporting. (Left out specific chipsets, though, since it would take dozens of examples to show all the chipsets that you can plug an nVidia card into. besides, if users use specific chipset support rather than the excellent generic chipset drivers provided by the kernel, they're expected to know which it is & what the driver name is.)
