Tiny Core Base > piCore Test Releases

piCore14.0 Beta

<< < (12/24) > >>

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

--- Quote ---[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
--- End quote ---

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:

--- Quote from: mortegai on May 31, 2023, 06:42:12 AM ---For piCore32 the libffi6 extension is needed for backward compatibility with: glib2, wayland, ...

--- End quote ---

lots of old extensions in 32 bit.

Paul_123:

--- Quote from: aus9 on May 30, 2023, 10:06:04 PM ---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

--- End quote ---
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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version