Tilted Forum Project Discussion Community - View Single Post

skaven · 01-09-2005, 03:35 PM

I've been searching all over Google and can't seem to find anybody with the same problem.

My new 6600GT seems to have issues running at the appropriate clock speed in Linux. Occasionally it'll initialize at 100Mhz core/500Mhz memory and get "stuck" (won't change even in 3D mode). However sometimes it'll initialize properly in 2D (300 core/900 memory) but then still be stuck in 3D. And then other times (these are the best) it works just fine and switches up to 500/900 when entering 3D mode.

I've been trying in vain to figure out what causes it to do this, and I'm praying it's not the card, since I've definitely lost any claims to a warranty on the card (waterblock is epoxied on with arctic silver, as is a larger AGP bridge heat sink).

I'm running the latest linux driver set from nVidia, and the only thing I can think of is that there might be some XF86Config options I need to make the driver set the correct clock speeds at all times.

I'm reading the clock speed using nvclock (CVS bleeding-edge version).

01-09-2005, 03:35 PM	#1 (permalink)
skaven Insane Location: Austin, TX	GeForce 6600GT clock speed woes I've been searching all over Google and can't seem to find anybody with the same problem. My new 6600GT seems to have issues running at the appropriate clock speed in Linux. Occasionally it'll initialize at 100Mhz core/500Mhz memory and get "stuck" (won't change even in 3D mode). However sometimes it'll initialize properly in 2D (300 core/900 memory) but then still be stuck in 3D. And then other times (these are the best) it works just fine and switches up to 500/900 when entering 3D mode. I've been trying in vain to figure out what causes it to do this, and I'm praying it's not the card, since I've definitely lost any claims to a warranty on the card (waterblock is epoxied on with arctic silver, as is a larger AGP bridge heat sink). I'm running the latest linux driver set from nVidia, and the only thing I can think of is that there might be some XF86Config options I need to make the driver set the correct clock speeds at all times. I'm reading the clock speed using nvclock (CVS bleeding-edge version).