piCore14.0 Beta

[aus9]

Hi Rich

Just tested totem.

It needs at least alsa.tcz as dependency.
Info mentions Xorg-3d.tcz
but the dep file only mentions Xorg.tcz

I made Xorg-3d.tcz one of my higher TCEs in onboot.lst above jwm -> fails for waitforX but then startx works

I am aware that Paul_123 is compiling more Apps to depend on openssl but for the moment
launching totem gives

Code: [Select]

totem
libssl.so.1.1: cannot open shared object file: No such file or directory
Failed to load module: /usr/local/lib/gio/modules/libgioopenssl.so
thanks for reading

slightly offtopic
Both totem and parole will give numerous gstreamer warnings if launched from a terminal

things like
(gst-plugin-scanner:8894): GStreamer-WARNING **: 11:50:36.412: Failed to load plugin '/usr/local/lib/gstreamer-1.0/libgstwavpack.so': libwavpack.so.1: cannot open shared object file: No such file or directory

[Rich]

Hi aus9
If you look at the dependency tree:
http://tinycorelinux.net/14.x/armv6/tcz/totem.tcz.tree
http://tinycorelinux.net/14.x/aarch64/tcz/totem.tcz.tree
you will find  Xorg-3d.tcz  and  alsa-modules-KERNEL.tcz  get pulled
in by dependencies further down the chain.

... Info mentions Xorg-3d.tcz ...

If you are not currently running  Xorg-3d , and you  tce-load -i totem , it probably
won't work because you can't start  Xorg-3d  while  Xorg  is running. So  totem
in that case should be:
Download only
Exit to prompt
tce-load -i totem
startx
Then add  totem  to  onboot.lst.

Note: Xorg-3d  will load  graphics-KERNEL.tcz. It hasn't come up in a few years, but loading
      graphics-KERNEL.tcz  while a GUI is running can/will cause the screen to go black.

... fails for waitforX but then startx works ...

I have a laptop that sometimes liked to do that. I added this to  ~/.xsession:

Code: [Select]

sleep 3
/usr/local/bin/Xorg -nolisten tcp &A short delay prior to running  Xorg  appears to fix (hide?) the issue.

[Paul_123]

Perhaps the cause may be the softdep between the vc4 and snd-soc-hdmi-codec modules, as indicated in http://forum.tinycorelinux.net/index.php/topic,26080.msg167351.html

Yes, putting the cma shared memory driver in the initrd seems to help change the path of the race track.   However the best thing to do is, Load alsa modules (and anything non-graphics related) in onboot, then load all of the graphics and Xorg in bootlocal.sh.

[mortegai]

Yes, putting the cma shared memory driver in the initrd seems to help change the path of the race track. 

Just curious, what is the cma shared memory driver?

However the best thing to do is, Load alsa modules (and anything non-graphics related) in onboot, then load all of the graphics and Xorg in bootlocal.sh.

Seems like a tricky solution, instead of fixing the root problem.

[Paul_123]

Just curious, what is the cma shared memory driver?

It is just the memory driver needed for the GPU.   Headless doesn't need it, so that is why its not in the initrd.  The kernel will automatically load it if present.....consuming memory.

However the best thing to do is, Load alsa modules (and anything non-graphics related) in onboot, then load all of the graphics and Xorg in bootlocal.sh.

Seems like a tricky solution, instead of fixing the root problem.

The only way to solve soft dependencies would be to switch from busybox to kmod module utilities.  Which is alot of extra bloat.   Managing the load order, buy how the extensions are loaded should work fine.

[mortegai]

It is just the memory driver needed for the GPU.   Headless doesn't need it, so that is why its not in the initrd.  The kernel will automatically load it if present.....consuming memory.

Just to learn something and curiosity,
What is the name of that driver?

[Paul_123]

vc-sm-cma.ko

https://github.com/raspberrypi/linux/tree/rpi-6.1.y/drivers/staging/vc04_services/vc-sm-cma

[Paul_123]

aus9,

As a test.  Download the module in a initrd format    http://www.tinycorelinux.net/14.x/aarch64/test_releases/RPi/vc-sm-cma.gz
place this file on your boot partition   mmcblk0p1 by default

edit your config.txt file.  In the [Pi4] section of the config.  add the filename to the initramfs line, like this

Code: [Select]

[PI4]
initramfs rootfs-piCore64-14.0.gz,modules-6.1.25-piCore-v8.gz,vc-sm-cma.gz followkernel
kernel kernel6125v8.img

See if this solves the black screen.

[aus9]

Hi Rich

It hasn't come up in a few years, but loading
      graphics-KERNEL.tcz  while a GUI is running can/will cause the screen to go black.

that explains my crash for post 38. Where I was not loading graphics-KERNEL.tcz but trying to load libv4l in jwm desktop,
and discovered it had graphics-KERNEL.tcz has a recursive dep.

OOPS I forgot to check Apps for libvl2 in piCore64-14.x it has

+ alsa-modules-5.10.39-piCore-v8.tcz          1097728,   1.05 MB
  bzip2-lib.tcz                                 32768,   0.03 MB
  gamin.tcz                                     16384,   0.01 MB
  gcc_libs.tcz                                1527808,   1.46 MB
  glib2.tcz                                   1495040,   1.43 MB
+ graphics-5.10.39-piCore-v8.tcz               774144,   0.74 MB
  libelf.tcz                                    36864,   0.04 MB
  libjpeg-turbo.tcz                            262144,   0.25 MB
  libudev.tcz                                   36864,   0.04 MB
  libv4l2.tcz                                  221184,   0.21 MB
  pcre.tcz                                     397312,   0.38 MB
+ v4l-dvb-5.10.39-piCore-v8.tcz               3346432,   3.19 MB

  Total size (bytes)                          9244672,   8.82 MB
+ Indicates need to download                  5218304,   4.98 MB

http://tinycorelinux.net/14.x/aarch64/tcz/libv4l2.tcz.dep says its v4l-dvb-KERNEL.tcz

Code: [Select]

uname -r
6.1.25-piCore-v8
I am sure this will settle when we are closer to final release

[aus9]

Hi Paul_123 before I reboot, I am just posting my kindof normal boot list and reboot with that first before adding in Xorg-3d.tcz

openssh.tcz
libXcursor.tcz
mc.tcz
nano.tcz
jwm.tcz
lxterminal.tcz
leafpad.tcz
firefox-perf.tcz
numlockx.tcz
pcmanfm.tcz
dosfstools.tcz
wbar.tcz

I had removed openssh but leaving it in for now.

[aus9]

Hi Paul_123

added Xorg-3d.tcz just above jwm and reboot -> failed in waitforX

I have deleted direct sync link to dmesg-ssh.txt prev posted but dir link still good .
Today dmesg-cma.txt link will be good for a while.

https://ln5.sync.com/dl/35e9843e0/qwwmxdxb-fj6be3ti-hi479r6g-ijpb4u5q

my config.txt reads

[PI4]
initramfs rootfs-piCore64-14.0.gz,modules-6.1.25-piCore-v8.gz,vc-sm-cma.gz followkernel
kernel kernel6125v8.img
arm_64bit=1

in post 42 I posted a snippet that has vc-sm but I can't see anything special?


this dmesg is created at console prompt then I ran startx and startx works

[aus9]

I also tried swapping the order to vc-sm-cma.gz,modules-6.1.25-piCore-v8.gz still fail waitforX

[mortegai]

For piCore32 the libffi6 extension is needed for backward compatibility with: glib2, wayland, ...

[Paul_123]

For piCore32 the libffi6 extension is needed for backward compatibility with: glib2, wayland, ...

lots of old extensions in 32 bit.

[Paul_123]

Hi Paul_123
added Xorg-3d.tcz just above jwm and reboot -> failed in waitforX
this dmesg is created at console prompt then I ran startx and startx works

You need to start from scratch, Start with only openssh in your onboot.lst and make sure openssh is started in bootlocal.sh. Then add one extension to onboot at a time, and reboot, until you cause it to break.  If you get a black screen, you will need to ssh in and check things out.  Besides dmesg, you also need to look a the xorg log file.

It also might be worth testing between jwm and flwm.