Tiny Core Base > piCore Test Releases
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: ---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
--- End code ---
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.
--- Quote from: aus9 on May 30, 2023, 08:19:08 AM --- ... Info mentions Xorg-3d.tcz ...
--- End quote ---
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.
--- Quote --- ... fails for waitforX but then startx works ...
--- End quote ---
I have a laptop that sometimes liked to do that. I added this to ~/.xsession:
--- Code: ---sleep 3
/usr/local/bin/Xorg -nolisten tcp &
--- End code ---
A short delay prior to running Xorg appears to fix (hide?) the issue.
Paul_123:
--- Quote from: mortegai on May 30, 2023, 05:48:26 AM ---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
--- End quote ---
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:
--- Quote from: Paul_123 on May 30, 2023, 11:03:49 AM ---Yes, putting the cma shared memory driver in the initrd seems to help change the path of the race track.
--- End quote ---
Just curious, what is the cma shared memory driver?
--- Quote from: Paul_123 on May 30, 2023, 11:03:49 AM ---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.
--- End quote ---
Seems like a tricky solution, instead of fixing the root problem.
Paul_123:
--- Quote from: mortegai on May 30, 2023, 11:45:58 AM ---Just curious, what is the cma shared memory driver?
--- End quote ---
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.
--- Quote from: mortegai on May 30, 2023, 11:45:58 AM ---
--- Quote from: Paul_123 on May 30, 2023, 11:03:49 AM ---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.
--- End quote ---
Seems like a tricky solution, instead of fixing the root problem.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version