Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: elf on January 25, 2021, 11:17:25 PM
-
Hi!
At first, I feel sorry that I'm a newbie to Linux and English is a foreign language to me.
Anyway I have a problem on using geany with Xorg-7.7 (on TinyCore 11.1). It's slow especially when I scroll up a text on it.
With Xvesa it's really smooth.
And I used to use Puppy Linux 5.7.0 (on the same PC) where geany (1.23.1) works really fine.
I tried Leafpad and beaver. They had the same problem. And GVim wasn't worse but still bad. L3afpad wasn't bad but not ideal again. The pre-installed 'editor' works perfect, but I need more powerfull undo-redo function at least...
Using jwm instead flwm made no change.
My laptop is DELL Inspiron 1210(Intel Atom Z530).
And here's my onboot.lst.
kmaps.tcz
xf86-video-intel.tcz
xf86-video-intel-i810.tcz
graphics-5.4.3-tinycore.tcz
Xorg-7.7.tcz
Xorg-7.7-3d.tcz
aterm.tcz
flwm.tcz
ttf-bitstream-vera.tcz
geany.tcz
I'm almost giving up finding a solution for the problem now. Because I feel Xvesa is acceptable to me for now.
But if someone happens to know about the problem(and the solution for it. Maybe I'm just missing some basic things? or some relevant information in this forum?), please give me a hint. Thanks!
-
Hi, elf!
I use TinyCore on the laptops with Atom Z-series too (mine are ASUS 1201HA with Z520) so I will be able to test some solutions if needed. Z-series is equipped with GMA500 video subsystem, which is not Intel video (!). It has absolutely no 3d features - at all.
1. Have You tried not loading Xorg-7.7-3d in onboot.lst? I expect it is absolutely unnecessary.
2. xf86-video-intel and xf86-video-intel-i810 includes different versions of the same librariess, so I think You need to choose one of these extensions, probably xf86-video-intel.
3. Try to move graphics-5.4.3-tinycore to the top of Your onboot.lst
One more qestion: have You tried TC10? There are some differences in how kernel treats GMA500 between TC10 and TC11 not in favor of the last.
Have a nice Core!
-
This one?
https://en.wikipedia.org/wiki/Dell_Inspiron_Mini_Series
That says the laptop uses Poulsbo graphics (PowerVR, which Intel just rebadged for those models). There is no good driver for that, -i810 and -intel only work for real Intel chips. You're going to use vesa or modesetting with Xorg, or Xvesa. Your list doesn't include xf86-video-vesa, so you're probably using modesetting right now.
-
xf86-video-vesa is among the dependencies of Xorg-7.7.
I've compared geany under Xorg and Xfbdev. Under Xorg scrolling up is very slow, while scrolling down is fast enough, even can say fast. Under Xfbdev both directions have the same speed of scrolling, something between scrolling speeds under Xorg. Probably geany is trying use for scrolling up some functions, which are absent. In both cases were loaded graphics-5.4.3-tinycore as the very first extension, Xorg or Xfbdev, then other desktop stuff.
I've tried firefox and seamonkey-noSSE2, they shows smooth scrolling. I felt no differences, depending on the X server.
-
Hello, jazzbiker & curaga! Thank you for your replies!
First of all, I didn't notice about GMA500's disadvantages. Interesting! Fortunately I don't need 3D graphics and expect so much 2D graphics power on this machine.
to jazzbiker:
Yeah, I had tried all of your suggestions about "onboot.lst" pattern, but things were same...
And now I tried TC10(and TC6 which seems have rather near release date with PuppyLinux 5.7.0.), but same old same old...
Xfbdev's response to mouse wheel scroll is nice! But to keybord is terrible, isn't it?
I'm guessing that this phenomenon has something to do with GTK's editable text area(or something like that).
And I'm wondering what's the difference between TinyCore and the (old) Puppy...
Anyway thanks for your suggestions and tries! They were really informative to me!
(And sorry, maybe I'm misunderstanding your last post because of my English skill... I couldn't catch "among the dependencies" and "In both cases were loaded..." well.)
to curaga:
(https://en.wikipedia.org/wiki/Dell_Inspiron_Mini_Series)
Yes, that's what I have!
Poulsbo! Ahh, so my Xorg.0.log says like...
[ 43.578] (II) LoadModule: "psb"
[ 43.579] (WW) Warning, couldn't open module psb
[ 43.579] (EE) Failed to load module "psb" (module does not exist, 0)
[ 43.579] (II) LoadModule: "psbdrv"
[ 43.579] (WW) Warning, couldn't open module psbdrv
[ 43.579] (EE) Failed to load module "psbdrv" (module does not exist, 0)
I had wondered "what's psb?" Eureka!
About modesetting, probably you are right. I'm not sure about how to read the log, though...
[ 43.580] (II) LoadModule: "modesetting"
[ 43.580] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 43.580] (II) Module modesetting: vendor="X.Org Foundation"
[ 43.580] compiled for 1.20.6, module version = 1.20.6
[ 43.580] Module class: X.Org Video Driver
[ 43.580] ABI class: X.Org Video Driver, version 24.0
[ 43.581] (II) LoadModule: "fbdev"
[ 43.581] (WW) Warning, couldn't open module fbdev
[ 43.581] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 43.581] (II) LoadModule: "vesa"
[ 43.582] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[ 43.582] (II) Module vesa: vendor="X.Org Foundation"
[ 43.582] compiled for 1.20.0, module version = 2.4.0
[ 43.582] Module class: X.Org Video Driver
[ 43.582] ABI class: X.Org Video Driver, version 24.0
[ 43.582] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 43.582] (II) VESA: driver for VESA chipsets: vesa
Anyway thanks for your inspection! I've gotten many good things to know!
-
Hi, elf!
~/.config/geany/geany.conf has no parameter responsible for turning scrolling off. Maybe it can be done while compiling. You can try to build Your own geany without scrolling, if it is possible.
English is not my native language, too, that's why my posts may not be understandable well, sorry.
-
Unfortunately https://www.x.org/archive/individual/driver/ directory have no signs of Poulsbo driver :( Is it possible that it is hiding in some xf86-video-intel*.tar.gz?
My current Xorg.log fragment
[ 399.524] (==) Matched psb as autoconfigured driver 0
[ 399.524] (==) Matched psb_drv as autoconfigured driver 1
[ 399.524] (==) Matched modesetting as autoconfigured driver 2
[ 399.524] (==) Matched fbdev as autoconfigured driver 3
[ 399.524] (==) Matched vesa as autoconfigured driver 4
[ 399.524] (==) Assigned the driver to the xf86ConfigLayout
[ 399.524] (II) LoadModule: "psb"
[ 399.525] (WW) Warning, couldn't open module psb
[ 399.525] (EE) Failed to load module "psb" (module does not exist, 0)
[ 399.525] (II) LoadModule: "psbdrv"
[ 399.526] (WW) Warning, couldn't open module psbdrv
[ 399.526] (EE) Failed to load module "psbdrv" (module does not exist, 0)
[ 399.526] (II) LoadModule: "modesetting"
[ 399.526] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 399.527] (II) Module modesetting: vendor="X.Org Foundation"
[ 399.527] compiled for 1.20.4, module version = 1.20.4
[ 399.527] Module class: X.Org Video Driver
[ 399.527] ABI class: X.Org Video Driver, version 24.0
[ 399.527] (II) LoadModule: "fbdev"
[ 399.527] (WW) Warning, couldn't open module fbdev
[ 399.528] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 399.528] (II) LoadModule: "vesa"
[ 399.528] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[ 399.528] (II) Module vesa: vendor="X.Org Foundation"
[ 399.529] compiled for 1.20.0, module version = 2.4.0
[ 399.529] Module class: X.Org Video Driver
[ 399.529] ABI class: X.Org Video Driver, version 24.0
[ 399.529] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 399.529] (II) VESA: driver for VESA chipsets: vesa
[ 399.529] (--) using VT number 2
Should I use xf86-video-fbdev?
-
Here is the fragment of Xorg.0.log from Lubuntu 14.04 on the same laptop with acceptable Xorg performance:
[ 39.013] (==) Matched psb as autoconfigured driver 0
[ 39.013] (==) Matched psb_drv as autoconfigured driver 1
[ 39.013] (==) Matched psb as autoconfigured driver 2
[ 39.013] (==) Matched psb_drv as autoconfigured driver 3
[ 39.013] (==) Matched modesetting as autoconfigured driver 4
[ 39.013] (==) Matched fbdev as autoconfigured driver 5
[ 39.013] (==) Matched vesa as autoconfigured driver 6
[ 39.013] (==) Assigned the driver to the xf86ConfigLayout
[ 39.014] (II) LoadModule: "psb"
[ 39.111] (WW) Warning, couldn't open module psb
[ 39.111] (II) UnloadModule: "psb"
[ 39.111] (II) Unloading psb
[ 39.111] (EE) Failed to load module "psb" (module does not exist, 0)
[ 39.111] (II) LoadModule: "psbdrv"
[ 39.113] (WW) Warning, couldn't open module psbdrv
[ 39.113] (II) UnloadModule: "psbdrv"
[ 39.113] (II) Unloading psbdrv
[ 39.114] (EE) Failed to load module "psbdrv" (module does not exist, 0)
[ 39.114] (II) LoadModule: "modesetting"
[ 39.115] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 39.117] (II) Module modesetting: vendor="X.Org Foundation"
[ 39.117] compiled for 1.18.3, module version = 1.18.3
[ 39.117] Module class: X.Org Video Driver
[ 39.117] ABI class: X.Org Video Driver, version 20.0
[ 39.118] (II) LoadModule: "fbdev"
[ 39.118] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 39.132] (II) Module fbdev: vendor="X.Org Foundation"
[ 39.132] compiled for 1.18.3, module version = 0.4.4
[ 39.132] Module class: X.Org Video Driver
[ 39.132] ABI class: X.Org Video Driver, version 20.0
[ 39.132] (II) LoadModule: "vesa"
[ 39.134] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 39.135] (II) Module vesa: vendor="X.Org Foundation"
[ 39.135] compiled for 1.18.3, module version = 2.3.4
[ 39.136] Module class: X.Org Video Driver
[ 39.136] ABI class: X.Org Video Driver, version 20.0
[ 39.136] (==) Matched psb as autoconfigured driver 0
[ 39.136] (==) Matched psb_drv as autoconfigured driver 1
[ 39.136] (==) Matched psb as autoconfigured driver 2
[ 39.136] (==) Matched psb_drv as autoconfigured driver 3
[ 39.136] (==) Matched modesetting as autoconfigured driver 4
[ 39.136] (==) Matched fbdev as autoconfigured driver 5
[ 39.136] (==) Matched vesa as autoconfigured driver 6
[ 39.136] (==) Assigned the driver to the xf86ConfigLayout
[ 39.136] (II) LoadModule: "psb"
[ 39.138] (WW) Warning, couldn't open module psb
[ 39.138] (II) UnloadModule: "psb"
[ 39.139] (II) Unloading psb
[ 39.139] (EE) Failed to load module "psb" (module does not exist, 0)
[ 39.139] (II) LoadModule: "psbdrv"
[ 39.149] (WW) Warning, couldn't open module psbdrv
[ 39.149] (II) UnloadModule: "psbdrv"
[ 39.149] (II) Unloading psbdrv
[ 39.149] (EE) Failed to load module "psbdrv" (module does not exist, 0)
[ 39.149] (II) LoadModule: "modesetting"
[ 39.150] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 39.151] (II) Module modesetting: vendor="X.Org Foundation"
[ 39.151] compiled for 1.18.3, module version = 1.18.3
[ 39.151] Module class: X.Org Video Driver
[ 39.151] ABI class: X.Org Video Driver, version 20.0
[ 39.151] (II) UnloadModule: "modesetting"
[ 39.151] (II) Unloading modesetting
[ 39.151] (II) Failed to load module "modesetting" (already loaded, 0)
[ 39.151] (II) LoadModule: "fbdev"
[ 39.157] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 39.157] (II) Module fbdev: vendor="X.Org Foundation"
[ 39.157] compiled for 1.18.3, module version = 0.4.4
[ 39.157] Module class: X.Org Video Driver
[ 39.157] ABI class: X.Org Video Driver, version 20.0
[ 39.157] (II) UnloadModule: "fbdev"
[ 39.157] (II) Unloading fbdev
[ 39.157] (II) Failed to load module "fbdev" (already loaded, 0)
[ 39.158] (II) LoadModule: "vesa"
[ 39.159] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 39.159] (II) Module vesa: vendor="X.Org Foundation"
[ 39.159] compiled for 1.18.3, module version = 2.3.4
[ 39.159] Module class: X.Org Video Driver
[ 39.159] ABI class: X.Org Video Driver, version 20.0
[ 39.159] (II) UnloadModule: "vesa"
[ 39.159] (II) Unloading vesa
[ 39.159] (II) Failed to load module "vesa" (already loaded, 0)
[ 39.159] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 39.168] (II) FBDEV: driver for framebuffer: fbdev
[ 39.168] (II) VESA: driver for VESA chipsets: vesa
[ 39.169] (II) modeset(0): using drv /dev/dri/card0
[ 39.169] (WW) Falling back to old probe method for modesetting
[ 39.169] (WW) Falling back to old probe method for fbdev
[ 39.169] (II) Loading sub module "fbdevhw"
[ 39.169] (II) LoadModule: "fbdevhw"
[ 39.170] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 39.186] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 39.187] compiled for 1.18.3, module version = 0.0.2
[ 39.187] ABI class: X.Org Video Driver, version 20.0
Seems, that we need not fbdev, but some fbdevhw driver. Right?
-
I'm trying to compile xf86-video-fbdev, loaded from https://www.x.org/archive/individual/driver/ but configure exits upon error:
configure: error: Package requirements (xorg-server >= 1.0.99.901 xproto fontsproto randrproto renderproto videoproto) were not met:
Package 'dri', required by 'xorg-server', not found
I've loaded xorg-server-dev, Xorg-7.7-dev. Is it possible to satisfy this dri dependency?
Thanks in advance!
-
Xorg-7.7-3d-dev was needed.
-
I've built xf86-video-fbdev.tcz, then rebooted and started Xorg with it. Here is Xorg.0.log fragment:
[ 154.651] (==) Matched psb as autoconfigured driver 0
[ 154.651] (==) Matched psb_drv as autoconfigured driver 1
[ 154.651] (==) Matched modesetting as autoconfigured driver 2
[ 154.651] (==) Matched fbdev as autoconfigured driver 3
[ 154.651] (==) Matched vesa as autoconfigured driver 4
[ 154.651] (==) Assigned the driver to the xf86ConfigLayout
[ 154.651] (II) LoadModule: "psb"
[ 154.652] (WW) Warning, couldn't open module psb
[ 154.652] (EE) Failed to load module "psb" (module does not exist, 0)
[ 154.652] (II) LoadModule: "psbdrv"
[ 154.653] (WW) Warning, couldn't open module psbdrv
[ 154.653] (EE) Failed to load module "psbdrv" (module does not exist, 0)
[ 154.653] (II) LoadModule: "modesetting"
[ 154.653] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 154.660] (II) Module modesetting: vendor="X.Org Foundation"
[ 154.660] compiled for 1.20.4, module version = 1.20.4
[ 154.660] Module class: X.Org Video Driver
[ 154.660] ABI class: X.Org Video Driver, version 24.0
[ 154.660] (II) LoadModule: "fbdev"
[ 154.661] (II) Loading /usr/local/lib/xorg/modules/drivers/fbdev_drv.so
[ 154.669] (II) Module fbdev: vendor="X.Org Foundation"
[ 154.669] compiled for 1.20.4, module version = 0.5.0
[ 154.669] Module class: X.Org Video Driver
[ 154.669] ABI class: X.Org Video Driver, version 24.0
[ 154.669] (II) LoadModule: "vesa"
[ 154.670] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[ 154.672] (II) Module vesa: vendor="X.Org Foundation"
[ 154.672] compiled for 1.20.0, module version = 2.4.0
[ 154.672] Module class: X.Org Video Driver
[ 154.672] ABI class: X.Org Video Driver, version 24.0
[ 154.672] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 154.672] (II) FBDEV: driver for framebuffer: fbdev
[ 154.672] (II) VESA: driver for VESA chipsets: vesa
[ 154.672] (--) using VT number 2
[ 154.748] (II) modeset(0): using drv /dev/dri/card0
[ 154.748] (WW) Falling back to old probe method for fbdev
[ 154.748] (II) Loading sub module "fbdevhw"
[ 154.748] (II) LoadModule: "fbdevhw"
[ 154.749] (II) Loading /usr/local/lib/xorg/modules/libfbdevhw.so
[ 154.751] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 154.751] compiled for 1.20.4, module version = 0.0.2
[ 154.751] ABI class: X.Org Video Driver, version 24.0
[ 154.752] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 154.752] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[ 154.752] (==) modeset(0): RGB weight 888
[ 154.752] (==) modeset(0): Default visual is TrueColor
seems ok, and fbdevhw present. But geany up-scrolling is still dumb. Maybe other drivers must be blacklisted or some Xorg.conf editing is necessary?
Here is lsmod:
Module Size Used by Not tainted
ccm 16384 3
snd_hda_codec_realtek 61440 1
snd_hda_codec_generic 40960 1 snd_hda_codec_realtek
snd_hda_intel 24576 0
snd_hda_codec 57344 3 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel
snd_hda_core 36864 4 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec
snd_hwdep 12288 1 snd_hda_codec
snd_pcm 49152 3 snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer 20480 1 snd_pcm
snd 36864 7 snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 12288 1 snd
cpufreq_powersave 12288 0
cpufreq_userspace 12288 0
cpufreq_conservative 12288 0
ath9k 61440 0
mac80211 237568 1 ath9k
gma500_gfx 69632 2
ath9k_common 12288 1 ath9k
ath9k_hw 368640 2 ath9k,ath9k_common
drm_kms_helper 86016 1 gma500_gfx
i2c_isch 12288 0
drm 212992 4 gma500_gfx,drm_kms_helper
ath 24576 3 ath9k,ath9k_common,ath9k_hw
cfg80211 167936 4 ath9k,mac80211,ath9k_common,ath
agpgart 24576 1 drm
fb_sys_fops 12288 1 drm_kms_helper
syscopyarea 12288 1 drm_kms_helper
sysfillrect 12288 1 drm_kms_helper
sysimgblt 12288 1 drm_kms_helper
i2c_algo_bit 12288 1 gma500_gfx
squashfs 28672 128
zstd_decompress 53248 1 squashfs
xxhash 16384 1 zstd_decompress
loop 20480 256
wmi_bmof 12288 0
asus_wmi 20480 0
sparse_keymap 12288 1 asus_wmi
pcspkr 12288 0
serio_raw 12288 0
video 28672 2 gma500_gfx,asus_wmi
backlight 12288 2 asus_wmi,video
battery 16384 0
ac 12288 0
lpc_sch 12288 0
wmi 16384 2 wmi_bmof,asus_wmi
acpi_cpufreq 12288 1
-
Hi, jazzbiker!
I can't appriciate you more! and I'm feeling terribly sorry...
About xf86-video-fbdev.tcz, TinyCore 6 repo has it, but the module version wasn't compatible with TinyCore 11.
So I checked Xorg.0.log of TC6.
[ 41.658] (II) LoadModule: "modesetting"
[ 41.659] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 41.662] (II) Module modesetting: vendor="X.Org Foundation"
[ 41.662] compiled for 1.17.1, module version = 1.17.1
[ 41.662] Module class: X.Org Video Driver
[ 41.662] ABI class: X.Org Video Driver, version 19.0
[ 41.662] (II) LoadModule: "fbdev"
[ 41.663] (II) Loading /usr/local/lib/xorg/modules/drivers/fbdev_drv.so
[ 41.669] (II) Module fbdev: vendor="X.Org Foundation"
[ 41.669] compiled for 1.17.1, module version = 0.4.4
[ 41.669] Module class: X.Org Video Driver
[ 41.669] ABI class: X.Org Video Driver, version 19.0
[ 41.669] (II) LoadModule: "vesa"
[ 41.670] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[ 41.673] (II) Module vesa: vendor="X.Org Foundation"
[ 41.673] compiled for 1.17.1, module version = 2.3.3
[ 41.673] Module class: X.Org Video Driver
[ 41.673] ABI class: X.Org Video Driver, version 19.0
[ 41.673] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 41.673] (II) FBDEV: driver for framebuffer: fbdev
[ 41.673] (II) VESA: driver for VESA chipsets: vesa
[ 41.673] (--) using VT number 2
[ 41.703] (II) modeset(0): using drv /dev/dri/card0
[ 41.703] (WW) Falling back to old probe method for fbdev
[ 41.703] (II) Loading sub module "fbdevhw"
[ 41.703] (II) LoadModule: "fbdevhw"
[ 41.704] (II) Loading /usr/local/lib/xorg/modules/libfbdevhw.so
[ 41.705] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 41.705] compiled for 1.17.1, module version = 0.0.2
[ 41.705] ABI class: X.Org Video Driver, version 19.0
[ 41.706] (WW) Falling back to old probe method for vesa
In my case, loading fbdevhw failed after all. Hmm...
And here's Puppy's Xorg.0.log. This might be irrelevant information. It seems be using rather different libs from TC(and your Lubuntu).
[ 35.465] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
[ 35.465] (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
[ 35.465] (II) "glx" will be loaded by default.
[ 35.465] (II) "record" will be loaded by default.
[ 35.465] (II) "dri" will be loaded by default.
[ 35.465] (II) "dri2" will be loaded by default.
[ 35.465] (II) LoadModule: "synaptics"
[ 35.471] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 35.492] (II) Module synaptics: vendor="X.Org Foundation"
[ 35.492] compiled for 1.12.2, module version = 1.6.2
[ 35.492] Module class: X.Org XInput Driver
[ 35.492] ABI class: X.Org XInput driver, version 16.0
[ 35.492] (II) LoadModule: "dbe"
[ 35.493] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 35.507] (II) Module dbe: vendor="X.Org Foundation"
[ 35.507] compiled for 1.12.4, module version = 1.0.0
[ 35.507] Module class: X.Org Server Extension
[ 35.507] ABI class: X.Org Server Extension, version 6.0
[ 35.507] (II) Loading extension DOUBLE-BUFFER
[ 35.507] (II) LoadModule: "extmod"
[ 35.508] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 35.523] (II) Module extmod: vendor="X.Org Foundation"
[ 35.523] compiled for 1.12.4, module version = 1.0.0
[ 35.523] Module class: X.Org Server Extension
[ 35.523] ABI class: X.Org Server Extension, version 6.0
[ 35.523] (II) Loading extension MIT-SCREEN-SAVER
[ 35.523] (II) Loading extension XFree86-VidModeExtension
[ 35.523] (II) Loading extension DPMS
[ 35.523] (II) Loading extension XVideo
[ 35.523] (II) Loading extension XVideo-MotionCompensation
[ 35.523] (II) Loading extension X-Resource
[ 35.523] (II) LoadModule: "glx"
[ 35.524] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 35.550] (II) Module glx: vendor="X.Org Foundation"
[ 35.550] compiled for 1.12.4, module version = 1.0.0
[ 35.550] ABI class: X.Org Server Extension, version 6.0
[ 35.560] (==) AIGLX enabled
[ 35.560] (II) Loading extension GLX
[ 35.560] (II) LoadModule: "record"
[ 35.561] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 35.561] (II) Module record: vendor="X.Org Foundation"
[ 35.561] compiled for 1.12.4, module version = 1.13.0
[ 35.561] Module class: X.Org Server Extension
[ 35.561] ABI class: X.Org Server Extension, version 6.0
[ 35.562] (II) Loading extension RECORD
[ 35.562] (II) LoadModule: "dri"
[ 35.563] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 35.585] (II) Module dri: vendor="X.Org Foundation"
[ 35.585] compiled for 1.12.4, module version = 1.0.0
[ 35.585] ABI class: X.Org Server Extension, version 6.0
[ 35.585] (II) Loading extension XFree86-DRI
[ 35.585] (II) LoadModule: "dri2"
[ 35.586] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 35.587] (II) Module dri2: vendor="X.Org Foundation"
[ 35.587] compiled for 1.12.4, module version = 1.2.0
[ 35.587] ABI class: X.Org Server Extension, version 6.0
[ 35.587] (II) Loading extension DRI2
[ 35.587] (II) LoadModule: "modesetting"
[ 35.587] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 35.597] (II) Module modesetting: vendor="X.Org Foundation"
[ 35.597] compiled for 1.12.2, module version = 0.4.0
[ 35.597] Module class: X.Org Video Driver
[ 35.597] ABI class: X.Org Video Driver, version 12.0
[ 35.597] (II) LoadModule: "kbd"
[ 35.598] (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
[ 35.611] (II) Module kbd: vendor="X.Org Foundation"
[ 35.611] compiled for 1.12.1, module version = 1.6.1
[ 35.611] Module class: X.Org XInput Driver
[ 35.611] ABI class: X.Org XInput driver, version 16.0
[ 35.611] (II) LoadModule: "mouse"
[ 35.613] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[ 35.613] (II) Module mouse: vendor="X.Org Foundation"
[ 35.613] compiled for 1.12.1, module version = 1.7.2
[ 35.613] Module class: X.Org XInput Driver
[ 35.613] ABI class: X.Org XInput driver, version 16.0
[ 35.613] (II) LoadModule: "synaptics"
[ 35.615] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 35.615] (II) Module synaptics: vendor="X.Org Foundation"
[ 35.615] compiled for 1.12.2, module version = 1.6.2
[ 35.615] Module class: X.Org XInput Driver
[ 35.615] ABI class: X.Org XInput driver, version 16.0
[ 35.615] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 35.615] (--) using VT number 4
[ 35.653] (**) modeset(0): claimed PCI slot 0@0:2:0
[ 35.653] (II) modeset(0): using default device
Now that I know you have same experience on your ASUS machine, I have some feeling like
"So be it! Anyway this happens not only to me. I might be able to go with this awkward scroll movement!"
So, unless you are willing to go further about this problem for yourself, please don't use your resources any more!
Of course, I will keep searching and studying about this glitch my own pace. It's fun! I believe you have same feeling!
Thank you!
-
The psb driver was a binary blob that only worked on a specific old version of Ubuntu.
-
I've captured lsmod-s on above mentioned Lubuntu 14.04 and TinyCore 10.1 (graphics-KERNEL loaded) and cleaned them manually from everything not dealing with graphics. Here's what I've got:
tc@box:~/sh/lsmod/edited$ cat lu.sorted
drm 307200 4 drm_kms_helper,gma500_gfx
drm_kms_helper 135168 1 gma500_gfx
fb_sys_fops 16384 1 drm_kms_helper
gma500_gfx 217088 2
i2c_algo_bit 16384 1 gma500_gfx
i2c_isch 16384 0
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
video 40960 2 gma500_gfx,asus_wmi
and
tc@box:~/sh/lsmod/edited$ cat tc.sorted
agpgart 24576 1 drm
drm 212992 4 gma500_gfx,drm_kms_helper
drm_kms_helper 86016 1 gma500_gfx
fb_sys_fops 12288 1 drm_kms_helper
gma500_gfx 69632 2
i2c_algo_bit 12288 1 gma500_gfx
i2c_isch 12288 0
syscopyarea 12288 1 drm_kms_helper
sysfillrect 12288 1 drm_kms_helper
sysimgblt 12288 1 drm_kms_helper
video 28672 2 gma500_gfx,asus_wmi
TC engages agpgart, in Lubuntu gma500_gfx is much bigger. Others seem to be alike. Is the trick inside gma500_gfx?
-
Hi jazzbiker
... TC engages agpgart, in Lubuntu gma500_gfx is much bigger. Others seem to be alike. Is the trick inside gma500_gfx?
Maybe this boot code would help:
agp=offFound here:
https://mjmwired.net/kernel/Documentation/kernel-parameters.txt#439
-
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.
-
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:
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:~$
-
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
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.
-
Rich, aren't You finding the too big gma500_gfx in Lubuntu suspicious? Why is it so big?
-
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:
#
# Graphics support
#
#
# Frame buffer Devices
#
#
# Frame buffer hardware drivers
#and sections with options including DRM in their name.
-
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.
-
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
[ 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
[ 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
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.
-
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)
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$
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$
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$
-
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!
-
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.
-
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?
-
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.
-
Hi, jazzbiker!
Now I tried to compile geany(1.37.1). And I got an error...
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!
-
Hi, elf!
You will need several .la files for geany build:
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?
-
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.
-
Hi, Juanito!
Thank for the explanation. You've did it before but unfortunately I've forgot it. Probably because we have no influence on this phenomenon, but we need to know the solution - src/la directory in the repo.
-
Hi, jazzbiker!
Now I compiled and checked the Geany(version 1.37.1)+GTK3. This's nice! But I don't pack into a tcz yet. I'm reading "Into the Core Ch.15.2" now.
And still now I want to try improving Geany+GTK2 a little bit more somehow...
Don't You like progress?
Partially "yes" and not unconditionally. You know me who's using an over 10-year-old PC now! lol
Now I really appreciate you, jazzbiker. I got an answer what I hadn't expected at all. This's a kind of 'serendipity'! You gave me it! Thank you, again!
May Tiny force be with you!
-
to administrator
Could you mark the [SOLVED] sign for this thread?
Thanks!
-
Hi elf
... Could you mark the [SOLVED] sign for this thread? ...
Of course. :)
-
Hi, elf!
I'm glad to know, that You've got geany, working as expected and as it must do. No thanks to me, keep them for TinyCore team :)
Geany is cute, 1.23 version will celebrate 10th birthday this year, still working nice! Excepts Poulsbo, so sad. By the way, in Lubuntu 14.04 geany is 1.23, but don't forget, that it was using the earlier version of gtk. and it worked fine on Poulsbo too. So I think the issue You faced is something that is named regression in gtk. You can obtain geany-1.23 sources from http://tinycorelinux.net/4.x/x86/tcz/src/geany/
One more note about geany-1.37.1. Size of the package packed for gtk2 was slightly larger, than of packed for gtk3. I think it means, that linking for gtk2 needs additional software layer and it may cause troubles too. In other words for modern geany gtk3 is native while gtk2 is step aside.
In any case if You will make progress in You geany and gtk-s exploration, please share the results.
Have a nice Core!
P.S. 10-year old computers are not equipped with hardware bugs like Intel IME, and one day they can become something, that You can not buy for the money.
-
Hi, jazzbiker!
10-year old computers are not equipped with hardware bugs like Intel IME, and one day they can become something, that You can not buy for the money.
And it made me access this forum and converse with you already! Thanks!