He is running Ubuntu 9.04. I know that it’s not officially supported by nvidia but all the forums say that the Hardy version works just fine in Jaunty.
no I told him not to worry about rebuilding it. We added under device: driver “nvidia” and that caused the panic, he then nano edited the xorg and removed the driver line and now he’s able to get in with no problem but of course it’s using the Vesa default driver so the resolution is horrible (800x600). I think he’s going to use the nv driver for the time being until this issue is solved.
I have attached the bug report.
Here is the order of how we did things:
Installed 185.XX driver (newest one) via binary, no errors at all
rebooted – received x server error but were able to get into gnome (I’m not even sure if that’s possible but when we ran nvidia-settings it said that x wasn’t running)
Installed the toolkit with no problem
Installed the SDK, no errors after a few installs with minor programs
Friend tried simpleTexture file that is included in the examples, said “TEST PASSED”
Friend tried the BlackScholes file that was included in SDK and it said, “TEST PASSED”
Tried fluidsGL example
spit out “Xlib: extension “GLX” missing on display “:0.0”.”
then spit out
Error: couldn’t find RGB GLX visual or fbconfig
decided to uninstall 185 and go back to 180 using the Ubuntu Hardware Manager method instead of binaries, installed no problem, x started up, 1920 resolution like he wants
then tried CUDA and of course you know that that didn’t work because it requires 185
So that’s what we’ve done and the errors we’ve seen, bug report is attached.
Thanks for the help, he is a native Windows user but his g/f uses Ubuntu and he has read all over the place that CUDA runs 20-100% faster in Linux so he wants it up and running but is running out of patience.
nvidia_bug_report.log.gz (40 KB)