Bad Graphics Issue with Scilab 5.1.1 and Slackware64 13
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Graphical issues with Scilab 5.0
Scilab 5.0 is doing an advanced use of JOGL (the Java Binding for the OpenGL). For performance reasons, we are using the Java2D OpenGL Pipeline. From a more technical aspect, it is using the internal buffer of the graphic cards called pbuffer.
The problem of this is caused by a bad support of this feature by the drivers. Some of them are badly (or not at all) supporting this feature.
Free drivers under Linux
As far as we know, there is no free driver handling this feature
Sounds like the 'issue' would be fixed by not using the open source drivers...
While an advocate myself of open source, sometimes (ESPECIALLY with video in Linux) you gotta go proprietary. Open source does a fine job, but when you start messing with 3D acceleration, or other specific chip implementations, the card/chip manufacturer usually does a much better job (Or, sometimes, the ONLY job). While it's not open source, it will allow you to do what you wish to do, for the time being.
Later, if the open source drivers start to function the way the closed source does, you can always go to those, instead.
Sometimes, it can be a trade off between what you want, and what you need.
You haven't actually told what GPU you are using or what the bad graphics issue actually looks like :-)
U r right.... my fault ...
The GPU is an ATI Mobility Radeon 2300
The bad graphics Issue is that:
... in any graphic window opened by Sci-5.1.1 there is NOTHING... The windows open allright... some of them have buttons and commands, if they act as gui's for some scripts, but graphical output, graphics, state-space diagrams, phase trajectories... no way...
Is this reproducible with OSS graphics drivers...? according to the link in the original post, it should be...
So you have already installed the proprietary driver for the 2300?
EDIT: The open source driver only recently gained support for 3D acceleration for your GPU, so it's very doubtful that it would work. And, out of the box, Slackware 13 isn't going to provide any 3D acceleration for your GPU.
Distribution: pclos2016, Slack14.1 Deb Jessie, + 50+ other Linux OS, for test only.
Graphics .. missing JOGL ? .. I don't use ATI, prefer Nvidia's.
Then my build "log" ..
.. Slackware 13 : Nice when configure says yes to all options .. ..
First this command on Debian : # apt-get build-dep scilab
.. to get a pointer for the most dependencies.
And then .. work .. a lot ..
Half the way I gave up building all those files with ant, too many errors.
Plugged out some jar's from the "3 file" Debian Squeeze packages.
Others were converted with # 'alien -t' from Squeeze packages.
I have tried ScicosLab allright... the source from GIT...
so, I tried the "./configure make trackinstall" approach :
1) First probl [solved ] ./configure fails to find the tcl and tk configure files, so, --with-tcl=/usr/lib64 and --with-tk=/usr/lib64;
The package gets built in /tmp, so #installpkg /tmp/<scicoslab.pkg>&&scilab
This time scilab complaints about a missing /usr/lib/pvm3 directory and a missing pvmgetarch... :-(, so back to 1) with --without-pvm;
2) Second probl [Partially Solved ] Despite the --without-pvm, the build still include the pvm3 thing, and still complaints about missing dirs with pvm3 stuff when I launch scilab, so... a bit of hackery this time... :
#nano /usr/bin/scilab , and comment out the whole of the PVM stuff... save and close.
#scilab ( now it complains about the zterm ( some gnome widget collection used by a shell created by scilab process...
I will have to dig a bit more... :-(
PS I Absolutely hate to hack into code which i do not know... only used this as a "last ditch" solution...
From all the dependencies that you stated , I only had to build fftw3, lapack, blas, suitesparse, and apache-ant.
I proceeded to ./configure with --without-ocaml, --without-pvm, and #make
Somehow a funny ( do not have the build log around ) error popped out, when building scicos, it was unable fo find system_gettime... so I reconfigured --without-scicos... this time it built the package... I installed ant tested it...
...This is when I found out that graphic output did not exist... :-(
This night I will rebuild with ocaml and pvm from slackbuilds, just to get to the point where i have the gettime thing...
I'll post the buildlog tomorrow...
About ATI vs NVIDIA...
I also prefer the NVIDIAs, but for now I am testing Slackware, as to see wether my work applications can be built over this OS, and I am testing it in a tiny 2GB Ram Laptop, Asus F3jr, that shipped with an ATI thing...
In case most of the apps can be created, I will install Slackware on my Work laptop, which has an NVIDIA GPU, and currently hosts a Debian lenny ( this is what I am using right now... )
BTW, Slackware/FluxBox in the Lappy with 2GB ram, boots faster, and runs faster than Lenny/Gnome in a 8GB HP Pavillion DV 1170 ... This is why I want to have most of my apps built as Slackware packages, before installing Slackware in my work Laptop...
Dassault Systemes used to release Unix ( HP-Ux I guess ) and AIX versions of Catia a few years ago...
AFAIK There is not a current version of CATIA for *nix ( Solaris, AIX, HP-Ux) /Linux at the moment...
Even One of the most well designed commercial 3d CAD-CAM packages out there, Pro Engineer WildFire, is no longer released for anything but W&&#(?OZE... Last Linux version was ProE wilfire 3, I managed to Install it in Ubuntu, Debian, the RHEL's ( if not in the RHEL's then where else...??!! :-) ) and the Suse's
What the heck is the matter with these ppl...?
Is Linux so unpopular among engineers that ProE, Catia, AutoDesk Inventor or SolidWorks don't even care building a Linux version...?
Os Has Evil Bill paid them to release nothing but for Mic%$33"#$oft...? :-(
BTW, even the ProE Linux version only shipped as 32bits...
I think that the F14 Tomcat, and the Sr71 a Blackbird were designed using either the BRL CAD thing or the CADAM thing...
I made a fresh install of Slackware64 13 in a USB HDD in my Nvidia PC; glxgears were at a lousy 133 FPS... after I have installed the proprietary Nvidia Driver, they rose to some 3000s FPS... not bad heh...?!
About my Ati machine, I will report the Gxlgears and the GlxInfo here tomorrow...
... but I think that even Proprietary Ati Linux Drivers are not much, by what I have seen in Forums...