PINE64
Booting Quartz64 Model B - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: Quartz64 (https://forum.pine64.org/forumdisplay.php?fid=166)
+--- Forum: General Discussion on Quartz64 (https://forum.pine64.org/forumdisplay.php?fid=167)
+--- Thread: Booting Quartz64 Model B (/showthread.php?tid=16894)

Pages: 1 2


RE: Booting Quartz64 Model B - CounterPillow - 07-17-2022

(07-17-2022, 04:01 PM)ryankurte Wrote: thanks again for all the assistance! that gets me further (up to mounting the file system), with another kernel panic:

Code:
:: performing fsck on '/dev/mmcblk0p5'
rootfs: clean, 33904/917504 files, 177393/3666688 blocks
:: mounting '/dev/mmcblk0p5' on real root
[    2.861970] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
:: running cleanup hook [udev]
/sbin/init: error while loading shared libraries: /usr/lib/libse[    3.001700] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
ccomp.so.2: file too short
[    3.002834] CPU: 1 PID: 1 Comm: init Not tainted 5.16.13-1-aarch64-ARCH #1
[    3.003639] Hardware name: Pine64 RK3566 Quartz64-B Board (DT)
[    3.004151] Call trace:
[    3.004367]  dump_backtrace+0x0/0x1cc
[    3.004703]  show_stack+0x18/0x24
[    3.004997]  dump_stack_lvl+0x68/0x84
[    3.005324]  dump_stack+0x18/0x34
[    3.005619]  panic+0x138/0x308
[    3.005892]  do_exit+0x3e8/0x3ec
[    3.006182]  do_group_exit+0x38/0xa0
[    3.006498]  __arm64_sys_exit_group+0x18/0x20
[    3.006883]  invoke_syscall+0x48/0x114
[    3.007216]  el0_svc_common.constprop.0+0x44/0xfc
[    3.007629]  do_el0_svc+0x28/0x90
[    3.007925]  el0_svc+0x28/0x80
[    3.008197]  el0t_64_sync_handler+0xa4/0x130
[    3.008575]  el0t_64_sync+0x1a0/0x1a4
[    3.008903] SMP: stopping secondary CPUs
[    3.009255] Kernel Offset: disabled
[    3.009562] CPU features: 0x20,00000203,46600e46
[    3.009968] Memory Limit: none
[    3.010242] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]---

i would think if the `fsck` succeeds the SD card / interface is okay, but will try with another cleanly formatted card in case it's some error in the copying over

that "/sbin/init: error while loading shared libraries: /usr/lib/libseccomp.so.2: file too short" looks like a corrupted file system to me, so starting over with a different SD card would be a good idea.


RE: Booting Quartz64 Model B - ryankurte - 07-18-2022

Quote:that "/sbin/init: error while loading shared libraries: /usr/lib/libseccomp.so.2: file too short" looks like a corrupted file system to me, so starting over with a different SD card would be a good idea.

swapping to a different / new SD card got me all the way to a shell! then i installed a few packages and rebooted and now the file system seems to be corrupted again Undecided


RE: Booting Quartz64 Model B - CounterPillow - 07-19-2022

(07-18-2022, 10:39 PM)ryankurte Wrote: swapping to a different / new SD card got me all the way to a shell! then i installed a few packages and rebooted and now the file system seems to be corrupted again Undecided

Alright, it's best then to try a different image like Manjaro for the Model B for now, I'll try to see if I can reproduce this with a fast SD card. The only case I've seen where a file system corrupts after one reboot like these is when someone made their ext4 partition overlap the u-boot partition, but I doubt you've done this.

Sorry for all the trouble getting started with this, hopefully we can get more images and more testing done to make sure issues like the ones you're running into are ironed out.


RE: Booting Quartz64 Model B - shaggy013 - 07-20-2022

if i am not mistaken it was something with time/date .
i had the same issue with manjaro
and what packages did you update ?


RE: Booting Quartz64 Model B - balbes150 - 01-23-2023

For Moderators.

I propose to divide this topic into two (move the first 4 messages to the topic with the correct name Quartz64 A). The first 4 posts are about Model A (not Model B, as indicated in the topic title). This leads to user confusion. The mention in the first message of the 12V power supply clearly indicates the model A. The model B has a 5V power supply.