Nvidia XFX 6600GT video card Linux howto - opengl crash fix
I take no responsibility if you mess up your card, however if you want the
drivers to work, you have no choice :(.
I had difficulty getting my XFX 6600GT video card working under linux.
I am running Debian SID with a compiled kernel 2.6.11.5 from sources.
I used the latest sources from kernel.org and compiled the kernel using the
latest debian 2.6.10 .config file as a model.
I then took the latest nvidia linux binary drivers
NVIDIA-Linux-x86-1.07167-pkg1.run.
I installed them.
I then configured my XF86Config-4 according to the readme.
I then tried to run Opengl screen savers I find under KDE screensavers
such as Skyrocket (GL). This amazing opengl ap causes my system to crash in
approximately 1 minute. Similarly with all other opengl 3d applications.
I then went to the nvnews.net site and discovered from the other users there
that I had to reflash my bios. The settings of my video card as shipped of
the XFX 6600GT are
3D 500 MHz
2D 300 MHz.
According to the gurus, this must be corrected so that the two numbers are
equal. I am a conservative man so I make them both 300MHz. Others can try
setting them both to 400 or 500 MHz.
I advise reading more about the below from a guru as I am no expert, but I
will say what I did.
The resetting of the bios requires the utility nvflash.exe and a dos win95
disk. It also requires the Nbitor nvidia bios editor. These can be found at
the site http://www.mvktech.net.
In short you will need.
win98 boot disk
nvflash.exe (from nvidia.zip)
csdpmi4b.zip
(nvflash wont work without 3 files from this also on the win98 boot disk)
NiBiTorv20.zip
Briefly, create a win98 boot disk. load the files
nvflash.exe and the 3 files CWSDPMI.EXE, CWSDPR0.EXE and CWSPARAM.EXE
(you need the 3 files or you will get an error from dos
"Load error: no DPMI - Get csdpmi*b.zip"
trying to copy your bios see explanation see* here below).
then run
nvflash -b backup.rom from a dos prompt.
then edit the rom using the Nbitor and change the 2d and 3d speed values
Then flash the rom
nvflash new.rom.
And reboot and your system will work fine. I tried with speed 300/300.
Please read the documentation on the
nvnews.net site linux forum.
I take no responsibility for your messing up your system. If you can no longer
use your nvidia card, it is your responsibility. MIne works though :).
Mitchell Laks
* ( the below is copied from a web site at
http://www.short-media.com/forum/showthread.php?t=120
Post by SIMGUY of toronto canada
Here's an explaination of what this "DPMI" is and what looks like a solution.
I'll tell you right now that I have never run into this problem when working
in DOS mode at all. Are the 2 of you who are having trouble using a boot disk
made from bootdisk.com by chance?
I've attached the required CSDPMI4B.ZIP file, but again I haven't tested it
and have no idea how to use it. If you could, try using an official Windows
98 Boot Disk (made from a Windows 95/98/Me installation) before trying this
CSDPMI4B stuff. I don't know how it works and I haven't tested it.
GNU sed is just the DOS application referred to in the documentation. I'm
guessing the same parameters & situations could be said about any C/C++
program made for use in a DOS Protected Mode Interface.
Quote:
5.4. What is CSDPMI*B.ZIP and why do I need it?
If you boot to MS-DOS instead of Windows and try to use GNU sed v1.18 or
3.02, you may encounter the following error message:
no DPMI - Get csdpmi*b.zip
"DPMI" stands for DOS Protected Mode Interface; it's basically a means of
running DOS in Protected Mode (as opposed to Real Mode), which allows
programs to share resources in extended memory without conflicting with one
another. Running HIMEM.SYS and EMM386.EXE is not enough. The "CSDPMI*B.ZIP"
refers to files written by Charles Sandmann to provide DPMI services for
32-bit computers (i.e., 386SX, 386DX, 486SX, etc.). Download this file:
csdpmi4b.zip
and extract CWSDPMI.EXE, CWSDPR0.EXE and CWSPARAM.EXE from the ZIP file. Put
all 3 CWS*.EXE files in the same directory as GSED.EXE and you're all set.
There are DOC files enclosed, but they're nearly incomprehensible for the
average computer user. (Another case of user-vicious documentation.)
)
Reply to: