Home/Support/Support Forum/Error when rebuild virtual/kernel
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

Error when rebuild virtual/kernel

0 votes
Hi,
I want to change the source code of connectcore6ulsbc project. I edited the files in source-kernel folder in the project and then used the following commands to rebuild:

bitbak virtual/kernel
bitbake dey-image-qt

i have successfully installed the os through the microsd card, but when i start it it gives an error.

ALSA device list:
No soundcards found.
Freeing unused kernel memory: 1024K
platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
Run /init as init process
/init: line 379: mkdir: not found
/init: line 380: mount: not found
/init: line 381: mount: not found
/init: line 382: mount: not found
/init: line 383: mount: not found
/init: line 386: sleep: not found
/init: line 391: mdev: not found
/init: line 394: run-parts: not found
/init: line 397: mkdir: not found
/init: line 400: sysctl: not found
/init: line 406: cat: not found
/init: line 0: can't open '/dev/null': No such file or directory
[RECOVERY] Starting recovery...
/init: line 113: can't create /tmp/psplash_fifo: nonexistent directory
/init: line 114: sleep: not found
ErrKernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f0-
or opening lock file /var/lock/fw_printenv.lock
Error opening lock file /var/lock/fw_printenv.lock
[RECOVERY] [ERROR] No command found
/init: line 113: can't create /tmp/psplash_fifo: nonexistent directory
/init: line 114: sleep: not found
/init: line 125: can't create /tmp/psplash_fifo: nonexistent directory
/init: line 126: sleep: not found
[RECOVERY] The system will now reboot in 10 seconds
/init: line 149: sleep: not found
/init: line 135: sync: not found
Error opening lock file /var/lock/fw_printenv.lock
Error opening lock file /var/lock/fw_printenv.lock
/init: line 135: sync: not found
asked Dec 27, 2021 in Linux by luckystar95 New to the Community (0 points)

Please log in or register to answer this question.

1 Answer

0 votes
Does it work with the stock kernel? Are you just updating the kernel but not other images like rootfs? I recommend building all images and updating them all so kernel and rootfs are from the same build. Please try creating new project and make no changes to it at first. Build and program images. Make sure it boots. now make changes to kernel and rebuild it. Then build all the images (boot.ubifs and rootfs.ubifs) and program them again
answered Jan 2 by LeonidM Veteran of the Digi Community (4,454 points)
...