You are not logged in.
I an unable to run blender on my system:
Dell T3600 (Xeon-based workststion)
card: nVidia Quadro 2000
drivers: latest nvidia package (346.35-5)
dual screen configuration
I use the Razor-qt desktop environment.
Launching blender completely freezes the system and a hard reset is needed. Any suggestion on how to find out what is wrong?
I tried searching the forums and other online sources but came up empty, probably because I do not really know what to search for.
(In fact I am not even sure this is the right arch forum for this question...)
I never used blender before, and in fact I only need it because a robotic simulation environment I'd like to use (morse) is built on top of it.
Help greatly appreciated.
Stefano
Last edited by stefano (2015-02-09 17:22:21)
Offline
Do any error messages get displayed before a lockup if you run blender from a terminal?
Matt
"It is very difficult to educate the educated."
Offline
Do any error messages get displayed before a lockup if you run blender from a terminal?
More details:
1. No error messages appear on the console after Blender is started. In fact, no messages at all
2. The problem is with Xorg: after Blender is launched, it goes to 100% CPU for a while (a minute or two), then it goes back to normal.
However, any window-related event (e.g. clicking) brings it back to 100%. Interestingly, after every lock up it takes longer to come back
to normal. After three or four times, it locks up solid (checked with top running in a terminal from a ssh-connected machine)
3. Blender itself seem to consume very few resources, at least according to top
Offline
After further experiments, I can obtain the same behavior (total system lockup) with different applications,
so the problem is not related to Blender. The applications are all robotic simulators (Gazebo, V-Rep, player-stage, Webots, Morse).
In some cases (V-Rep, player-stage), the lock up only happens when moving the app's window between the tow physical monitors,
or between virtual desktops. In other cases (Gazebo, Blender-based Morse), the lockup happens when the application starts
The only conclusion I can draw is that the problem has nothing to do with Blender---may be it is an openGL issue related to the nVidia driver.
In any case, I am marking the issue as Closed
Offline
Please do not used [Closed], it denotes a locked thread, use [Solved] or [Resolved] instead...
Offline
Please do not used [Closed], it denotes a locked thread, use [Solved] or [Resolved] instead...
All right---didn't know that.
Offline