[Solved] My Geany is slow on TC 11.1 + Xorg!

[jazzbiker]

Hi, Rich!

Thanks for advice, but adding this "agp=off" don't prevent loading agpgart. I've lsmod-ed immediately after boot before starting X. Lubuntu 14.04 uses 3.xx series kernel, maybe this module appeared later. 

[Rich]

Hi jazzbiker

... Lubuntu 14.04 uses 3.xx series kernel, maybe this module appeared later.

I don't think so. This is from a TC4 machine:

Code: [Select]

tc@box:~$ lsmod | grep agp
intel_agp              12288  1
intel_gtt              16384  1 intel_agp
agpgart                24576  3 nvidia,intel_agp,intel_gtt
tc@box:~$ uname -r
3.0.3-tinycore
tc@box:~$

[jazzbiker]

Hi, elf!

Please don't be "terrible sorry"! It's fun, it can be useful, and it is communication with interesting people I am absolute noob in graphics subsystem,  and I want to learn it, but I can not learn something without the real appliance. So let's try to make this cheating Poulsbo dance along our music.

What I've seen in Puppy's Xorg0.log

1. X server version is rather old - 1.12
2. I see the next objects, having relations with videosystem

Code: [Select]

Loading /usr/lib/xorg/modules/extensions/libglx.so
Loading /usr/lib/xorg/modules/extensions/librecord.so
Loading /usr/lib/xorg/modules/extensions/libdri.so
Loading /usr/lib/xorg/modules/extensions/libdri2.so
Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
no fbdev_drv.so, no vesa_drv.so, no libfbdevhw.so

From the other side i don't see libdri.so adn libdri2.so in my Xorg logs  both in TC  and Lubuntu.

There exists adriconf.tcz extension in TC10 repo. Maybe we need to use it for some configuring? But from the other side, dri libraries are part of Xorg-7.7-3d, which is unusable for our chipsets... So now I have no proposals what to do.

[jazzbiker]

Rich, aren't You finding the too big gma500_gfx in Lubuntu suspicious? Why is it so big?

[Rich]

Hi jazzbiker
All of the drivers listed are larger. I would suggest comparing some sections of the Lubuntu kernel config to this:
http://tinycorelinux.net/11.x/x86/release/src/kernel/config-5.4.3-tinycore

Sections you might want to check for differences include:

Code: [Select]

#
# Graphics support
#
#
# Frame buffer Devices
#
#
# Frame buffer hardware drivers
#and sections with options including  DRM  in their name.

[jazzbiker]

All of the drivers listed are larger. I would suggest comparing some sections of the Lubuntu kernel config to this:
http://tinycorelinux.net/11.x/x86/release/src/kernel/config-5.4.3-tinycore

Hi, Rich!
You are right, as usual. Probably we were to start with this comparing.

[jazzbiker]

Before examining kernel config I've took one more attempt to understand what's the difference between working well and not absolutely well cases. I was testing Lubuntu 14.04, Puppy 8 (Bionic) and TinyCore 10. All are 32-bit. Testing tool was upscrolling in geany. Lubuntu and Puppy showed fast scrolling while in TinyCore upscrolling is harmful. All use modesetting driver, according to their Xorg.0.log's.

In both Lubuntu and Puppy Xorg.0.log

Code: [Select]

[    99.670] (II) AIGLX: Screen 0 is not DRI2 capable
[    99.670] (EE) AIGLX: reverting to software rendering
[    99.688] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[    99.692] (II) IGLX: Loaded and initialized swrast
[    99.692] (II) GLX: Initialized DRISWRAST GL provider for screen 0

while in TinyCore

Code: [Select]

[   149.452] (II) AIGLX: Screen 0 is not DRI2 capable
[   149.473] (II) IGLX: Loaded and initialized swrast
[   149.474] (II) GLX: Initialized DRISWRAST GL provider for screen 0

I've checked in TinyCore with the glxinfo that  GLX_MESA_copy_sub_buffer is present. Xorg-7.7-3d loaded.
Does anybody  knows, is it possible to enable it with the help of some config file or something that kind?

In TinyCore 9.0 and 8.2.1

Code: [Select]

tce-load -i graphics-KERNEL
tce-load -i Xorg-7.7-3d flwm aterm
startx

ends in the same manner without runnung X with the Xorg.0.log tail identical to those described in http://forum.tinycorelinux.net/index.php/topic,21889.0.html and http://forum.tinycorelinux.net/index.php/topic,21737.0.html topics with "Illegal instruction" message.

[jazzbiker]

Here are the kernel config diff's between 4.14 (TC9, no 3d X, Illegal instruction) and 4.19 (TC10, working Xorg-3d, slow upscrolling)

Code: [Select]

tc@box:~/sh/poulsbo$ diff graphics-4.14 graphics-4.19
--- graphics-4.14
+++ graphics-4.19
@@ -19,10 +19,12 @@
 CONFIG_DRM=m
 CONFIG_DRM_MIPI_DSI=y
 CONFIG_DRM_DP_AUX_CHARDEV=y
-# CONFIG_DRM_DEBUG_MM_SELFTEST is not set
+# CONFIG_DRM_DEBUG_SELFTEST is not set
 CONFIG_DRM_KMS_HELPER=m
 CONFIG_DRM_KMS_FB_HELPER=y
 CONFIG_DRM_FBDEV_EMULATION=y
 CONFIG_DRM_FBDEV_OVERALLOC=100
 # CONFIG_DRM_LOAD_EDID_FIRMWARE is not set
+CONFIG_DRM_DP_CEC=y
 CONFIG_DRM_TTM=m
+CONFIG_DRM_SCHED=m
tc@box:~/sh/poulsbo$


Code: [Select]

tc@box:~/sh/poulsbo$ diff drm-4.14 drm-4.19
--- drm-4.14
+++ drm-4.19
@@ -5,10 +5,12 @@
 # CONFIG_DRM_I915_DEBUG is not set
 # CONFIG_DRM_I915_SW_FENCE_DEBUG_OBJECTS is not set
 # CONFIG_DRM_I915_SW_FENCE_CHECK_DAG is not set
+# CONFIG_DRM_I915_DEBUG_GUC is not set
 # CONFIG_DRM_I915_SELFTEST is not set
 # CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS is not set
 # CONFIG_DRM_I915_DEBUG_VBLANK_EVADE is not set
 CONFIG_DRM_VGEM=m
+# CONFIG_DRM_VKMS is not set
 CONFIG_DRM_VMWGFX=m
 CONFIG_DRM_VMWGFX_FBCON=y
 CONFIG_DRM_GMA500=m
tc@box:~/sh/poulsbo$


Code: [Select]

tc@box:~/sh/poulsbo$ diff fb-4.14 fb-4.19
--- fb-4.14
+++ fb-4.19
@@ -5,21 +5,15 @@
 CONFIG_FIRMWARE_EDID=y
 CONFIG_FB_CMDLINE=y
 CONFIG_FB_NOTIFY=y
-# CONFIG_FB_DDC is not set
 CONFIG_FB_BOOT_VESA_SUPPORT=y
 CONFIG_FB_CFB_FILLRECT=y
 CONFIG_FB_CFB_COPYAREA=y
 CONFIG_FB_CFB_IMAGEBLIT=y
-# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
 CONFIG_FB_SYS_FILLRECT=m
 CONFIG_FB_SYS_COPYAREA=m
 CONFIG_FB_SYS_IMAGEBLIT=m
-# CONFIG_FB_PROVIDE_GET_FB_UNMAPPED_AREA is not set
 # CONFIG_FB_FOREIGN_ENDIAN is not set
 CONFIG_FB_SYS_FOPS=m
 CONFIG_FB_DEFERRED_IO=y
-# CONFIG_FB_SVGALIB is not set
-# CONFIG_FB_MACMODES is not set
-# CONFIG_FB_BACKLIGHT is not set
 CONFIG_FB_MODE_HELPERS=y
 CONFIG_FB_TILEBLITTING=y
tc@box:~/sh/poulsbo$


[elf]

Hi, jazzbiker!

So let's try to make this cheating Poulsbo dance along our music.

Thanks for your saying that! Your jazzy humour relieved me! lol

And sorry for my being silence.
I want provide some useful information or idea here, instead meaningless excuse(like this) or irrerlevant chat.
But things are getting beyond me now! I'm full of(there isn't available capacity in me any more) reading your posts and searching unknown terms in them.

I wish you will get good results for you, for me and for the TinyCore community. Of course I don't take any assumption abou it, that is you don't have any duty of it. But I'm following your attempt! and trying to find helpful information or other approach.
Thank you!

[jazzbiker]

Hi, elf!

If it is still interesting for You, I've got geany working flawless. It is not kernel or driver issue, it is gtk2 toolkit issue. Geany.tcz depends on gtk2.tcz toolkit. I've compiled it against gtk3 and it works nice. I think this is good reason for You to learn, how TinyCore extensions are being compiled and packed

By the way it means that for our beloved Poulsbo's all extensions compiled against gtk2 may exhibit misbehaviour in some cases.

[elf]

Hi, jazzbiker!

Of course I'm interested in your story! I downloaded geany-dev.tcz but it didn't include so much(I simply wondered what this tcz is.).
Where did you get that source code, and which version? From geany's site? and the latest one? Could you elaborate what you did?
I'm not familiar with C and "make" culture, but maybe I'll give it a try!
Thank you!

By the way, I might misread your saying again...

By the way it means that for our beloved Poulsbo's all extensions compiled against gtk2 may exhibit misbehaviour in some cases.

You mean your compilation might affect other application than geany?

[jazzbiker]

Hi, elf!

You mean your compilation might affect other application than geany?

Certainly - no. Geany can be told during compile time to use one of the toolkits - gtk2 or gtk3. Once compiled it will try to use only this toolkit and in the case of its absence in the system geany will exit with error.
Of course if You want to  make Your own extension, I will gladly help You. If You haven't read yet the brilliant "Into the Core" book, I think this time has come.

I've loaded sources from geany.org. Versions 1.27-1.37 available. Our current in TC is 1.23. Which version to choose is up to You I was experimenting with the latest one.

[elf]

Hi, jazzbiker!

Now I tried to compile geany(1.37.1). And I got an error...

Code: [Select]

make[3]: Leaving directory '/tmp/geany-1.37.1/src/tagmanager'
make[3]: Entering directory '/tmp/geany-1.37.1/src'
  CXXLD    libgeany.la
libtool:   error: cannot find the library '/usr/local/lib/libgio-2.0.la' or unhandled argument '/usr/local/lib/libgio-2.0.la'
make[3]: *** [Makefile:801: libgeany.la] Error 1
make[3]: Leaving directory '/tmp/geany-1.37.1/src'
make[2]: *** [Makefile:1268: all-recursive] Error 1
make[2]: Leaving directory '/tmp/geany-1.37.1/src'
make[1]: *** [Makefile:598: all-recursive] Error 1
make[1]: Leaving directory '/tmp/geany-1.37.1'
make: *** [Makefile:482: all] Error 2

Can you see what I'm missing? or could you show me your loaded-tczs' list?
Thanks!

[jazzbiker]

Hi, elf!

You will need several .la files for geany build:

Code: [Select]

tc@box:/mnt/sda6/ken/Downloads$ ls *.la
libEGL.la          libgbm.la          libglib-2.0.la     libgthread-2.0.la
libGLESv2.la       libgio-2.0.la      libgmodule-2.0.la
libdrm.la          libglapi.la        libgobject-2.0.la
You can download this files from http://tinycorelinux.net/11.x/x86/tcz/src/la/. Don't ask me, why they are not in the -dev extensions. Seems this is one of the progress side effects. Don't You like progress ?
After downloading You will need to copy these files to /usr/local/lib/ directory. Don't forget to use sudo, this directory is owned by root.
By the way, what version of geany You will build?

[Juanito]

Don't ask me, why they are not in the -dev extensions.

*.la files are produced by an autotools build (configure, make) - many apps have changed to a meson/ninja build that no longer produces *.la files.