Tiny Core Extensions > TCE Talk

An issue with booting SeaTools

<< < (3/4) > >>

Smasher:
What I've found out after a long trial and error makes absolutely no sense to me :o but here it is, the following diff made it work:


--- Code: ---diff --git a/tce/onboot_STB_Xorg.lst b/tce/onboot_STB_Xorg.lst
index 9c2c74e..ec87eeb 100644
--- a/tce/onboot_STB_Xorg.lst
+++ b/tce/onboot_STB_Xorg.lst
@@ -1,6 +1,5 @@
 Xfbdev.tcz
 Xorg-7.7.tcz
-xf86-video-modesetting.tcz
 xf86-input-synaptics.tcz
 kmaps.tcz
 libEGL.tcz
@@ -29,5 +28,4 @@ openssl.tcz
 pixman.tcz
 mylocale.tcz
 curl.tcz
-SeaChest_noAuto.tcz
 SeaTools212_noAuto.tcz
--- End code ---

As soon as I add one of the extensions, either xf86-video-modesetting.tcz or SeaChest_noAuto.tcz, the boot process breaks. The first one contains usr\local\lib\xorg\modules\drivers\modesetting_drv.so and the second one 10 binaries with the path scheme usr\bin\SeaChest_* Then I tried something, what confused me even more. If I add SeaChest.tcz instead of SeaChest_noAuto.tcz to the boot list, it works! That extension, in addition to the binaries named above, has a file usr\local\tce.installed\SeaChest and some PNG images in usr\local\include\seachest\. In search of commonalities, I examined the dependencies of these extensions. Both of xf86-video-modesetting.tcz.dep and SeaChest_noAuto.tcz.dep include graphics-KERNEL.tcz and I think this is the key. I just still don't understand yet the reason behind it.

I made the extensions available for download here: https://filetransfer.io/data-package/sapqcvCm

Juanito:
Once in the GUI, does /var/log/Xorg.0.log exist (this will show whether Xfbdev or Xorg-7.7 is being used)?

Rich:
Hi Smasher
Try adding  graphics-KERNEL.tcz  as the first entry in your onboot.lst file in the non-working version and see if that fixes it.

Smasher:
Hey Rich,

I tried adding graphics-KERNEL.tcz to tce/onboot.lst and to the top of tce/onboot_STB_Xorg.lst and it didn't help. I can tell even more: if I omit the problematic extensions (SeaChest_noAuto and xf86-video-modesetting) but add graphics-KERNEL.tcz to a list, it breaks as well.

I learned that if I wait a while after screen turning black I get access to a console. And from the log, I learned that X cannot start because of the lack of hardware rendering support and a missing library for software rendering. Here is the relevant part of Xorg.0.log


--- Code: ---[    30.233] (II) AIGLX: Screen 0 is not DRI2 capable
[    30.233] (EE) AIGLX: reverting to software rendering
[    30.233] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[    30.233] (EE) GLX: could not load software renderer
[    30.233] (II) GLX: no usable GL providers found for screen 0
[    30.233] (II) modeset(G0): Damage tracking initialized
[    30.233] (EE)
[    30.233] (EE) Backtrace:
[    30.233] (EE) 0: /usr/local/lib/xorg/Xorg (xorg_backtrace+0x49) [0x80dd9e5]
[    30.233] (EE) 1: /usr/local/lib/xorg/Xorg (0x8048000+0x139d5e) [0x8181d5e]
[    30.233] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xf77d1b80]
[    30.233] (EE) 3: /usr/local/lib/xorg/Xorg (RRScreenSetSizeRange+0x85) [0x810ff0b]
[    30.233] (EE) 4: /usr/local/lib/xorg/Xorg (xf86RandR12CreateScreenResources+0x2ac) [0x8175c78]
[    30.233] (EE) 5: /usr/local/lib/xorg/Xorg (0x8048000+0xfe1a2) [0x81461a2]
[    30.233] (EE) 6: /usr/local/lib/xorg/Xorg (0x8048000+0x1ff77) [0x8067f77]
[    30.233] (EE) 7: /lib/libc.so.6 (__libc_start_main+0x157) [0xf73a723f]
[    30.233] (EE) 8: /usr/local/lib/xorg/Xorg (0x8048000+0x2076c) [0x806876c]
[    30.233] (EE)
[    30.233] (EE) Segmentation fault at address 0x58
--- End code ---

The whole log: https://pastebin.com/raw/fqHVYQdv

@Juanito: on a working version Xorg.0.log exists as well

Juanito:
What graphics hardware do you have?

Near the beginning of the xorg log it will show which drivers it is trying to load - it sounds like yours is missing?

Navigation

[0] Message Index

[#] Next page

[*] Previous page