View Single Post
Old 01-12-03, 03:13 PM   #8
junkieclown
Helium Abuser
 
junkieclown's Avatar
 
Join Date: Nov 2002
Location: Summers in Rangoon, but mostly in my evil underground lair and Volcano laboratory. though
Posts: 45
Default

and presumably you followed the same procedures as before to install the Nvidia drivers and configure your XF86Config.....

I am impressed. I had a problem that merely seemed the same no matter what options I tried. You have a similar problem that has appeared where once there was working hardware & setup...

I am so stumped now, I don't know whether to **** or go blind.

You were using RH8.0 before as well, right, when it was working for UT2003?

Did you ever have a boot option like mem=nopentium for grub or lilo before your reinstall?
I don't think that's supposed to be necessary with recent kernels but...


Here's another thing: there's no NvAGP option set in your XF86Config.
You could try it different ways to see if one avoids the crashing.
"NvAGP" "0" #equals no agp of any kind
.............."1" #equals , try nvagp if possible
.............."2" # equals, try Linux agpgart if possible
.............."3" #equals, try agpgart and fallback to nvagp if unsuccessful.

default is "3" if nothing is specified.
Since you aren't specifying anything, then it should try agpgart. But I don't know if there is agpgart support for Kt333 chipsets in the kernels RH ships. I can't really say if there is any in the Nvidia driver either. What I've seen in Nvidia's documentation says Kt266. However, my 2.4.20-ac2 kernel identifies the 333 chipset as Kt266Pro at least for purposes of AGP.
cat /proc/driver/nvidia/agp/host-bridge
Host Bridge: Via Apollo Pro KT266
Fast Writes: Supported
SBA: Supported
AGP Rates: 4x 2x 1x
Registers: 0x1f000217:0x00000104


It seems to work with Nvidia's agp module :::

cat /proc/driver/nvidia/agp/status
Status: Enabled
Driver: NVIDIA
AGP Rate: 4x
Fast Writes: Disabled
SBA: Disabled

(snipped from /var/log/XFree86.0.log)
(II) NVIDIA(0): Setting mode "1600x1200"
SwitchToMode - Succeeded
(II) Open APM successful
(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1600x1200"
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-GLX
(II) [GLX]: Initializing GLX extension
(II) Open APM successful
(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1600x1200"
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-GLX
(II) [GLX]: Initializing GLX extension
(II) Open APM successful
(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1600x1200"
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-GLX
(II) [GLX]: Initializing GLX extension
(II) Open APM successful
(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1600x1200"
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-GLX
(II) [GLX]: Initializing GLX extension

It's very perplexing and i'm getting the distinct feeling that neither Linux kernel people nor Nvidia give much of a damn about AMD cpus and VIA boards, as they're always having trouble with them, and are typically very late getting things working right.
Maybe it won't crash on NvAGP "0" (won't that be fun?)

Last edited by junkieclown; 01-12-03 at 04:23 PM.
junkieclown is offline   Reply With Quote