D. Michaud
04-02-03, 09:33 AM
We are seeing a major problem with the released 4349 drivers that is 100% repeatable on multiple systems and multiple cards.
Here's the system information:
Dell P550 workstation w/
Dual 2.0Ghz Xeon CPUs
NVidia Quadro4-700 and Quadro4-950
Redhat 7.2 and Redhat 8.0 Linux kernel 2.4.18-27bigmem
Dell 17" DFP w/ DVI interface
Here's the problem:
Whenever we start X when the DFP is connected to the NVidia's DVI input, the system locks up hard. THe monitor goes into powersaving mode, the keyboard is unresponsible, the OS hangs, and a hard reboot is necessary.
This does not happen if we use the VGA analog interface with the same monitor.
This also does not happen if we use a single-CPU kernel without BIGMEM. Both the sock redhat 7.2 2.4.18-27bigmem kernel and our custom kernels with bigmem enabled cause the hang to happen.
When the hang happens there is no useful output in the XFree86.0.log file.. It looks just like X started normally, with no errors.
This problem does not occur with the older 4131 drivers on the same exact system hardware. Those drivers work just fine, except for the bad initial 2D performance.
This leads us to believe that the problem lies somewhere in the new NVidia drivers.
Here's the system information:
Dell P550 workstation w/
Dual 2.0Ghz Xeon CPUs
NVidia Quadro4-700 and Quadro4-950
Redhat 7.2 and Redhat 8.0 Linux kernel 2.4.18-27bigmem
Dell 17" DFP w/ DVI interface
Here's the problem:
Whenever we start X when the DFP is connected to the NVidia's DVI input, the system locks up hard. THe monitor goes into powersaving mode, the keyboard is unresponsible, the OS hangs, and a hard reboot is necessary.
This does not happen if we use the VGA analog interface with the same monitor.
This also does not happen if we use a single-CPU kernel without BIGMEM. Both the sock redhat 7.2 2.4.18-27bigmem kernel and our custom kernels with bigmem enabled cause the hang to happen.
When the hang happens there is no useful output in the XFree86.0.log file.. It looks just like X started normally, with no errors.
This problem does not occur with the older 4131 drivers on the same exact system hardware. Those drivers work just fine, except for the bad initial 2D performance.
This leads us to believe that the problem lies somewhere in the new NVidia drivers.