Tiny Core Base > piCore Test Releases
piCore15.0 Beta
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: ---[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
--- End code ---
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: ---
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
--- End code ---
Previous 15 Beta 1:
--- Code: ---Filesystem Size Used Available Use% Mounted on
/dev/mmcblk0p1 78.8M 54.6M 24.1M 69% /mnt/mmcblk0p1
--- End code ---
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?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version