piCore15.0 Beta

[yvs]

Errors on libX11-dev, libxcb-dev, libXau-dev, and libXdmcp-dev:
it comes from libvulkan-1.3.283.tcz.dep

Which repo are you speaking of - libvulkan doesn’t have a dep file..

most probably it was my experiments with vulkan builds at that time, so it needs to be skipped (and I already cleaned up my old locally built extensions)

[Juanito]

OK - as an update to the piCore vulkan status, it works on an RPi4 running aarch64 although gtk4 windows are missing various decorations. I haven’t tested on an RPi4 running armhf yet.

[yvs]

OK - as an update to the piCore vulkan status, it works on an RPi4 running aarch64 although gtk4 windows are missing various decorations. I haven’t tested on an RPi4 running armhf yet.

I suppose it will work only in software mode (via llvm) as far gtk4 works with gl3+ only and underlying v4 driver is only gl2 compat

[Juanito]

..but the 32bit RPi4 driver is v3d, no?

[yvs]

..but the 32bit RPi4 driver is v3d, no?

It's about rendering in general, and 2d and 3d.
I cannot say surely about RPi4 (not having one under hands to find out API provided by its VideoCore6 with common V4 driver).

Speaking of RPi3:

Here's what you should get with xorg 3d working using vc4-kms-v3d on an RPi3:

Code: [Select]

inxi -Ga
  API: OpenGL v: 2.1 vendor: broadcom mesa v: 24.1.4 glx-v: 1.4 es-v: 2.0
    direct-render: yes renderer: VC4 V3D 2.1 device-ID: 14e4:ffffffff


The same API versions I've seen with v4-fkms-v3d too.
And needless to say about much newer Vulkan and its support by V4.

[Paul_123]

I just pushed up beta3 images.

Changes:
Update to Kernel 6.6.47  (mainly to pickup a few critical pi5 changes.)
Update 32bit initrd to include udev rule changes.

[Juanito]

As per:

Code: [Select]

sudo e2fsck /dev/sda8
Error: ext2fs library version out of date!
e2fsck 1.47.0 (5-Feb-2023)
        Using EXT2FS Library version 1.46.5, 30-Dec-2021
Perhaps libext2fs.so.2 was updated from piCore-14.x, but not e2fsck?

[Paul_123]

Perhaps, I forgot to copy to initrd.  I'll have to look.  Thanks for reporting.

[Paul_123]

I just burned a fresh piCore15 beta3 image, e2fsck and libs all seem to checkout fine.

What may be special about your system?

[Juanito]

Nothing that I can think of - I updated beta1 -> beta2 by mounting the image and copying the files over.

I'll update to beta3 soon..

[Paul_123]

somehow an old e2fsprogs extension laying around?   Let me know, as I'll push out finals after this.

The only thing I'm planning to change, there was an issue with the udev rule 99-com.rules that was preventing the symlinks for serial0 and serial1 to be created for the serial ports.  Our older version of udev did not handle the single quotes of a sed command in a PROGRAM= script.  And then updating the startserialtty script.

[Juanito]

I updated to beta3 using piCore 32/64 bit kernel on an RPi4 and aarch64 on another RPi4 - everything seems fine and the fsck error did not reappear.

Maybe it would be good to add the following to config.txt:

Code: [Select]

[PI4]
initramfs rootfs-piCore-15.0.gz,modules-6.6.47-piCore-v8.gz followkernel
kernel kernel6647v8.img
arm_64bit=1
#initramfs rootfs-piCore-15.0.gz,modules-6.6.47-piCore-v7l.gz followkernel
#kernel kernel6647v7l.img
#arm_64bit=1


[ovacikar]

duplicate post

[ovacikar]

Picore 15 beta 3, the p1 partition somehow got increased to 128 MB. The content still takes 54.6 MB. How do I shrink it back and reasign to p2 with resize2fs ?

If shrinking and reallocating is not possible, can it be fixed in next release?

Code: [Select]


Linux box 6.6.47-piCore #9 Sat Aug 31 14:48:51 EDT 2024 armv6l GNU/Linux

Filesystem                Size      Used Available Use% Mounted on
/dev/mmcblk0p1          126.0M     54.6M     71.4M  43% /mnt/mmcblk0p1
Previous 15 Beta 1:

Code: [Select]

Filesystem                Size      Used Available Use% Mounted on
/dev/mmcblk0p1           78.8M     54.6M     24.1M  69% /mnt/mmcblk0p1

[Paul_123]

Shrinking and expanding a fat32 partition is not possible.  From what I can see I changed the partition size before I released beta1, and the old size was only 64MB.   Did you manually create a sdcard then copy the contents?

I don't want to release an image with only a 64MB partition, but what is the right number?