still no log viewing with modular_4.0

Questions specific to Megatunix - alternate tuning software that runs on unix and windows.
Note that Megatunix is obsolete.

Moderator: djandruczyk

Post Reply
StevenD57
Helpful MS/Extra'er
Posts: 103
Joined: Fri Oct 14, 2005 1:14 pm
Location: Phoenix, AZ
Contact:

still no log viewing with modular_4.0

Post by StevenD57 »

OK, I tried just now the modular_4.0 tree and I moved my /usr/share/Megatunix directory out of the way prior to doing the make install. I went out to the car just now and tried the logviewer again both in playback mode from a file and in RT mode but I still get a blank all black screen even when I move the scroll bar side to side at the bottom of the screen.

Any thoughts or suggestions?
Jaguar E-Types, modified Merkur XR4Ti, Jensen-Healey
Linux = no virii or spyware, EVER
djandruczyk
MS/Extra Guru
Posts: 1210
Joined: Fri May 07, 2004 6:55 pm
Location: Rochester, NY, U.S.A.
Contact:

Re: still no log viewing with modular_4.0

Post by djandruczyk »

StevenD57 wrote:OK, I tried just now the modular_4.0 tree and I moved my /usr/share/Megatunix directory out of the way prior to doing the make install. I went out to the car just now and tried the logviewer again both in playback mode from a file and in RT mode but I still get a blank all black screen even when I move the scroll bar side to side at the bottom of the screen.

Any thoughts or suggestions?

Have you selected any variables?, which ones? can you send me the log? (djandruczyk at yahoo dot com)
David J. Andruczyk
MegaTunix author. The only non-java cross platform tuning software for MS-I/II hardware.
Where to get and how to install:
http://msextra.com/viewtopic.php?t=23080
http://sourceforge.net/projects/megatunix
StevenD57
Helpful MS/Extra'er
Posts: 103
Joined: Fri Oct 14, 2005 1:14 pm
Location: Phoenix, AZ
Contact:

Re: still no log viewing with modular_4.0

Post by StevenD57 »

djandruczyk wrote:Have you selected any variables?, which ones? can you send me the log? (djandruczyk at yahoo dot com)
I will E-mail the log file to you when I get back home this evening. I did select quite a few variables.
Jaguar E-Types, modified Merkur XR4Ti, Jensen-Healey
Linux = no virii or spyware, EVER
StevenD57
Helpful MS/Extra'er
Posts: 103
Joined: Fri Oct 14, 2005 1:14 pm
Location: Phoenix, AZ
Contact:

Re: still no log viewing with modular_4.0

Post by StevenD57 »

Dave:
Did you get the two log files I sent?

I tried the same log files with modular_4.0 this evening running in offline mode (not connected to the ECU)
and selecting playback mode. After selecting a particular log file it brought up an additional little popup window with various controls in it but no matter what I did to play around with the controls I still did not see anything at all in the playback window. It was completely black. This was on a completely different computer running a different version of Linux OS. As I suggested in the E-mail I sent with the data log files, if this playback window is using OpenGL, is it possible the visual being chosen is not appropriate for the visuals my X-servers have available?
Jaguar E-Types, modified Merkur XR4Ti, Jensen-Healey
Linux = no virii or spyware, EVER
StevenD57
Helpful MS/Extra'er
Posts: 103
Joined: Fri Oct 14, 2005 1:14 pm
Location: Phoenix, AZ
Contact:

Re: still no log viewing with modular_4.0

Post by StevenD57 »

I built the latest release of MegaTunix on a new laptop now that I have a working USB to serial adaptor and the new release from git does indeed seem to be an improvement but I still get a completely blank screen when I try to use the logviewer. Is it possible that there is some library that is not getting linked in when I build MegaTunix on these OpenSuSE laptops?

Here is the ldd output on /usr/bin/megatunix

linux-vdso.so.1 => (0x00007fff253ff000)
libgtkglext-x11-1.0.so.0 => /usr/lib64/libgtkglext-x11-1.0.so.0 (0x00007f3326067000)
libgdkglext-x11-1.0.so.0 => /usr/lib64/libgdkglext-x11-1.0.so.0 (0x00007f3325e03000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f3325bd9000)
libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x00007f332596a000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f33256f4000)
libXmu.so.6 => /usr/lib64/libXmu.so.6 (0x00007f33254da000)
libXt.so.6 => /usr/lib64/libXt.so.6 (0x00007f3325273000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x00007f332506a000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x00007f3324e4d000)
libpangox-1.0.so.0 => /usr/lib64/libpangox-1.0.so.0 (0x00007f3324c40000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f3324900000)
libglade-2.0.so.0 => /usr/lib64/libglade-2.0.so.0 (0x00007f33246e5000)
libmtxcommon.so.0 => /usr/lib64/libmtxcommon.so.0 (0x00007f33244dd000)
libmtxprogress.so.0 => /usr/lib64/libmtxprogress.so.0 (0x00007f33242d8000)
libmtxpie.so.0 => /usr/lib64/libmtxpie.so.0 (0x00007f33240d3000)
libmtxstripchart.so.0 => /usr/lib64/libmtxstripchart.so.0 (0x00007f3323ecc000)
libmtxgauge.so.0 => /usr/lib64/libmtxgauge.so.0 (0x00007f3323caf000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f3323959000)
libmtxcombo_mask.so.0 => /usr/lib64/libmtxcombo_mask.so.0 (0x00007f3323755000)
libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x00007f332311c000)
libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x00007f3322e6a000)
libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007f3322c48000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007f3322a16000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f33227f8000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f3322541000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f332233d000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007f3322130000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007f3321eaf000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007f3321c63000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f33219da000)
libz.so.1 => /lib64/libz.so.1 (0x00007f33217c4000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f332158d000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f3321343000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f332113e000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f3320f3a000)
librt.so.1 => /lib64/librt.so.1 (0x00007f3320d31000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f3320a4d000)
libm.so.6 => /lib64/libm.so.6 (0x00007f33207f6000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f33205d9000)
libc.so.6 => /lib64/libc.so.6 (0x00007f3320279000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f331ff6f000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f331fd59000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f331fb46000)
libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007f331f940000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f331f73d000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f331f537000)
libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f331f32b000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f331f126000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f331ef09000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f331ecfe000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f331eafb000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f331e8eb000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f331e6e2000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f331e4d7000)
libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007f331e2d4000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f331e0bd000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f331de9e000)
/lib64/ld-linux-x86-64.so.2 (0x00007f332626b000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f331dc3c000)
libpng14.so.14 => /usr/lib64/libpng14.so.14 (0x00007f331da12000)
libxcb-render-util.so.0 => /usr/lib64/libxcb-render-util.so.0 (0x00007f331d80e000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007f331d605000)
libpcre.so.0 => /lib64/libpcre.so.0 (0x00007f331d3d7000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f331d1d3000)

I looked through the output from running configure but I did not see anything that would indicate a missing library though. Is it possible it is something to do with the OpenSuSE I am installing being a x86_64 distro?

I.E.

~/MTX_VexFiles/git/MegaTunix> file /usr/bin/megatunix
/usr/bin/megatunix: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.4, not stripped
Jaguar E-Types, modified Merkur XR4Ti, Jensen-Healey
Linux = no virii or spyware, EVER
Post Reply