Hi Forum

I Have successuflly built a limited ( --without-pvm --without-ocaml --without-scicos ) version of Scilab 5.1.1 over Slackware64 13...

Thing is that I have an ATI ( ...I know :-( !!! ) GPU, and googled and found this...


http://wiki.scilab.org/Graphical_issues_with_Scilab_5.0

According to this,


####################################################################


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.

Issue
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


########################################################################


The problem is here...


Thought anyone experiencing this issue might be interested to Know...

BRGDS

Alex

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 :-)

Adam

Hi adamk75



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...

BRGDS

Alex

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.

Adam

Thks Adamk75,

I will try this as soon as I get back home... ( I am not w/ my Slackware box right now... )

Thnkx

Alex

If you aren't sure if your 3D drivers are installed properly (or at all), just show us the output of 'glxinfo' and we can let you know.

Adam

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.

1._ ocaml SBo
2._ pvm slacky.eu
3._ suitesparse slacky.eu (< slack 12.2 version )
4._ apache-ant SBo
5._ jogl + antlr (+ gluegen) (< debian squeeze source )
6._ fdupes SBo '
7._ flexdock > binary https://flexdock.dev.java.net/
> > https://flexdock.dev.java.net/files/...dock-0.5.1.zip
8._ looks binary > libjgoodies-looks-java_2.3.0-1_all.deb > looks.jar
9_. libskinlf-java_6.7-4_all.deb > jar's
10. libjrosetta-java_1.0.2+gpl-2_all.deb > jar's
11. javahelp2_2.0.05-3_all.deb > jhall.jar
12. libcommons-logging-java_1.1.1-5_all.deb > jar's
13. fftw SBo
14. matio-1.3.3 > --prefix=/usr/ --enable-shared
15. batik libbatik-java_1.7-4_all.deb > batik-java-1.7.tgz
(( svn checkout http://svn.apache.org/repos/asf/xmlg...s/batik/trunk/ ))
... The svn : OK, but some binaries missing, hence the alien deb.
16. libsaxon-java_6.5.5-5_all.deb > saxon-java-6.5.5.tgz
17. libjeuclid-core-java_3.1.8-1_all.deb > jeuclid-core-java-3.1.8.tgz
19. libcommons-io-java_1.4-2_all.deb > commons-io-java-1.4.tgz
20. libxmlgraphics-commons-java_1.3.1.dfsg-2_all.deb >
> > xmlgraphics-commons-java-1.3.1.tgz
21. xml-apis-ext.jar
> > http://www.java2s.com/Code/JarDownlo...is-ext.jar.zip
And lapack + blas were already installed some weeks ago.
.....

Other tools / files, some required to build java programs with ant ...
. Xerces SBo '
. xalan SBo '
. avalon
. log4j
http://mirrors.dotsrc.org/apache/log...-1.2.15.tar.gz
. junit .. debian source.
. fop
http://mirrors.dotsrc.org/apache/xml.../fop/binaries/
http://mirrors.dotsrc.org/apache/xml....95-bin.tar.gz
.....
.....
Odd error with ld, refused to find crtbeginS.o , crtendS.o .
.....
The alien compat--g77 from CentOS5 builds the Fortran stuff.
.....
* About JOGL .. is designed to provide hardware-supported 3D graphics
* to applications written in Java.
.....
'm Sad to say, I had to change to './configure --without-pvm' ....
but else : no errors.
.....

1 members found this post helpful.

Hi Knudfl

Thkz for your reply,

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...



About Scilab 5.1.1 :

I think that lots of dependencies that you have tracked are already shipped into scilab prerequirements... check http://www.scilab.org/download/5.1.1..._64-src.tar.gz

... Both http://www.scilab.org/download/5.1.1...1.1-src.tar.gz and http://www.scilab.org/download/5.1.1..._64-src.tar.gz untar to the same folder...

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...

BRGDS

Alex

Thank you.
I totally forgot, downloaded them a month ago .. ..

.....

About CATIA : Never heard of a a Linux version,
was it you mentioning it ?
.....

Hi Knudfl

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...

not sure about it...


http://www.cadazz.com/cad-software-history-1970s.htm

Hi Knudfl and Forum

Is the _gettime thing during scicos (scilab 5.1.1 ) compilation reproducible in Slackware64 13...?

About the Graphic issue... I have this trick to see if it is GPU dependent... I will install Slackware in my Nvidia Laptop in a USB HDD and clone my system...

...to see how far I get...

...but last time I tried to install Slackware to a USB HDD it would kernel panic at boot killing init...

I will have to google a bit more about that...

BRGDS

Alex

Did you ever check to see if the fglrx drivers are installed on your machine?

Hi Adamk

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...

BRGDS

Alex

The AMD proprietary drivers are quite good these days, in fact. The real test, at least for you, is whether or not they work properly in scilab. Have you tried it yet with the nvidia driver?

It is quite possible that scilab will work just fine with the fglrx drivers from AMD.

Adam

1 members found this post helpful.