Firefly Open Source Community

Title: Linux SDK Build Error [Print This Page]
Author: tm-mec    Time: 5/10/2022 22:23
Title: Linux SDK Build Error
Last edited by tm-mec In 5/10/2022 22:36 Editor

Hello,
I'm using the Linux SDK, an rk3566 aio board.

I build it with this commands:
./build.sh aio-3566-jd4-ubuntu.mk
./build.sh

But when building it the device doesn't start and is throwing an error, does someone have an idea?

  1. mount: mounting /dev/mmcblk1p6 on /root failed: Invalid argument
  2. done.
  3. Begin: Running /scripts/local-bottom ... done.
  4. Begin: Running /scripts/init-bottom ... [    4.651715] vendor storage:20190527 r                                                                                                                                                             et = -1
  5. [    4.835173] rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x3
  6. Warning: overlayroot: configuring overlayroot with driver=overlay mode=device op                                                                                                                                                             ts='dev=PARTLABEL=userdata,fstype=ext4,mkfs=1' per kernel cmdline
  7. [    4.963550] EXT4-fs (mmcblk1p7): recovery complete
  8. [    4.965832] EXT4-fs (mmcblk1p7): mounted filesystem with ordered data mode. O                                                                                                                                                             pts: (null)
  9. mount: mounting /root on /root-ro failed: Invalid argument
  10. Failure: overlayroot: failed to move root away from /root to /root-ro
  11. mount: mounting /dev on /root/dev failed: No such file or directory
  12. mount: mounting /dev on /root/dev failed: No such file or directory
  13. Warning: Something odd, no /lib/modules/4.19.219 in initramfs.
  14. done.
  15. mount: mounting /run on /root/run failed: No such file or directory
  16. run-init: current directory on the same filesystem as the root: error 0
  17. Target filesystem doesn't have requested /sbin/init.
  18. run-init: current directory on the same filesystem as the root: error 0
  19. run-init: current directory on the same filesystem as the root: error 0
  20. run-init: current directory on the same filesystem as the root: error 0
  21. run-init: current directory on the same filesystem as the root: error 0
  22. run-init: current directory on the same filesystem as the root: error 0
  23. No init found. Try passing init= bootarg.


  26. BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)
  27. Enter 'help' for a list of built-in commands.

  29. (initramfs) [    5.848415] rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x3
  30. [    6.861753] rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x3
  31. [    7.875081] rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x3
  32. [    8.888413] rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x3
  33. [    9.901730] rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x3
  34. [   10.915082] rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x3
  35. [   11.928402] rk-pcie 3c0000000.pcie: PCIe Link Fail
  36. [   11.928469] rk-pcie 3c0000000.pcie: failed to initialize host
  37. [   32.061826] vcc5v0_otg: disabling
  38. [   32.061903] vcc3v3_lcd0_n: disabling
Copy the code
Author: Liuth    Time: 5/11/2022 09:26
have you put the ubuntu rootfs under SDK/ubuntu_rootfs/ and rename it to rk356x_ubuntu_rootfs.img ?
https://wiki.t-firefly.com/en/Co ... d-ubuntu-filesystem
Author: tm-mec    Time: 5/11/2022 14:22
Liuth Posted at 5/11/2022 09:26
have you put the ubuntu rootfs under SDK/ubuntu_rootfs/ and rename it to rk356x_ubuntu_rootfs.img ?
...

yes
Author: katata    Time: 10/1/2025 12:50
Ugh, a Linux SDK build error with that `Invalid argument` mount issue sounds super frustrating! Debugging complex problems reminds me a bit of cooking – you need the right ingredients and steps. Speaking of recipes, I've been really into looking up Grow a Garden Recipes lately for some fresh ideas!
Author: katata    Time: 7 day before
Okay, so it's a "Linux SDK Build Error" thing on the Firefly forum. Verification succeeded though, that's good! But where's the juicy error details? I was hoping to find some blue lock rivals wiki level deep dives on this. Maybe they should focus on helping us "outplay our rivals" in the build process instead of just mentioning the error.



Welcome Firefly Open Source Community (https://bbs.t-firefly.com/) Powered by Discuz! X3.1