Hello shann,
Yes, having a look at the root of the rootfs I saw you created a symlink lib64
to lib
. So maybe the problem is different. In Next64 lib64
existed but wasn't created by tazusb
when creating the rootfs.
I boot again the broken rootfs; here is the error message:
Kernel panic - not syncing: No working init found. Try passing init option to kernel
Last Current core update:
2024-07-02 19:57:30 - Installed - libegl-mesa (21.3.5) - 2e2fd673d5d5abdac5e26a7c73f7ddc4
2024-07-02 19:57:31 - Installed - libglvnd (1.3.3) - 9ef1751495b376e3175501ed0946f718
2024-07-02 19:57:33 - Installed - libgbm-mesa (21.3.5) - 0edcf5708bc82be66924f1a01399a8c8
2024-07-02 19:57:34 - Installed - libglapi-mesa (21.3.5) - a5afffe2dc7136a2dc4eab208f42fa87
2024-07-02 19:57:34 - Installed - libglx-mesa (21.3.5) - b8c53bec7e731829c7447a670d7cfb05
2024-07-02 19:57:36 - Installed - libopencl-mesa (21.3.5) - 301f91e52200eff8bb8b7be42cf5a593
2024-07-02 19:57:55 - Installed - llvm-lib (13.0.0) - 5edb233b12b607c0464def1cf54f0aab
2024-07-02 19:57:55 - Installed - libos-mesa (21.3.5) - 4eadf35d79bf7fd6ae583c27127dd800
2024-07-02 19:57:57 - Installed - libdrm-nouveau (2.4.109) - e9b6468bec26cf0538e24ce5a422d5df
2024-07-02 19:57:58 - Installed - libdrm-radeon (2.4.109) - fb3814e0db0b2f5ce170aa8ecabb2c2f
2024-07-02 19:57:59 - Installed - libxvmc-mesa (21.3.5) - 37d8f4fe421545d9ca663a0485880568
2024-07-02 19:58:00 - Installed - libxatracker-mesa (21.3.5) - d5e9ff8ff5a7f1679edc008df3676dad
2024-07-02 19:58:01 - Installed - mesa-vulkan (21.3.5) - df62914faa415e89d5c8bff5454147c9
2024-07-02 19:58:03 - Installed - mesa (21.3.5) - b69cc5cb835c1dde5d8d24292caf82f8
2024-07-02 19:58:05 - Installed - webkitgtk (2.4.11) - 6af6c534abd246700d3f75cdb17dbc1b
The increase of the rootfs is caused by the new mesa
deps (libglvnd, libgbm-mesa, libglapi-mesa, libglx-mesa, libopencl-mesa, libos-mesa, libxvmc-mesa, libxatracker-mesa, mesa-vulkan) and subdeps (llvm-lib, libdrm-nouveau, libdrm-radeon)
:(
Two other things with Core:
- My layout in PCManFM Preferences: Home folder, Trash can and Filesystem root.
When I open the file manager (right click, Favorite Applications > File Manager); click on Filesystem Root opens a new tab with Documents. Then PCManFM will work normally till I close it... this never happens when I open PCManFM from the Documents icon of the desktop or with Applications > System Tools > File Manager PCManFM. Really strange, can you reproduce it?
- Seems my computer boots too fast in frugal mode, I needed to add
sleep 1
after action 'Configuring loopback...'
in network.sh
to have my Wi-Fi working after boot