nV News Forums - View Single Post - quadro nvs 160m crashes remote desktop software (all vers 180.29, 180.11, 177, 173)

sjhook · 02-19-09, 10:30 PM

Hi,

I have a Dell Latitude E6500 with a Quadro NVS 160M graphics card. Every time I attempt to remote desktop to a site (either with rdesktop or tightvnc) the initial log in screen is displayed but when I log in the remote screen starts to draw then my mouse freezes, a few seconds later the fan on my laptop speeds up and is quite loud and then my entire system crashes. I reported this bug with versions 173, 177, 180.11 and now 180.29. I am running Ubuntu 8.10. Note the system does not crash with the default open source driver, however, that runs at v. low resolution compared with the nvidia driver. I even contacted Dell and asked about getting the alternate Intel 4500 graphics chip but Dell wants me to pay ~$500 for a new motherboard to switch.

Please fix the NVIDIA driver. Let me know if you need me to test it.

Thanks, Simon

p.s. This bug is 100% repeatable so should be easy to at least test.

02-19-09, 10:30 PM	#1
sjhook Registered User Join Date: Jan 2009 Posts: 7	quadro nvs 160m crashes remote desktop software (all vers 180.29, 180.11, 177, 173) Hi, I have a Dell Latitude E6500 with a Quadro NVS 160M graphics card. Every time I attempt to remote desktop to a site (either with rdesktop or tightvnc) the initial log in screen is displayed but when I log in the remote screen starts to draw then my mouse freezes, a few seconds later the fan on my laptop speeds up and is quite loud and then my entire system crashes. I reported this bug with versions 173, 177, 180.11 and now 180.29. I am running Ubuntu 8.10. Note the system does not crash with the default open source driver, however, that runs at v. low resolution compared with the nvidia driver. I even contacted Dell and asked about getting the alternate Intel 4500 graphics chip but Dell wants me to pay ~$500 for a new motherboard to switch. Please fix the NVIDIA driver. Let me know if you need me to test it. Thanks, Simon p.s. This bug is 100% repeatable so should be easy to at least test.