Jump to content

sgjava

Members
  • Posts

    411
  • Joined

  • Last visited

Everything posted by sgjava

  1. @SteeMan that did the trick: [ o.k. ] Kernel file name [ linux-image-current-sunxi_23.02.0-trunk_armhf.deb ] [ o.k. ] Runtime [ 53:30 min ] [ o.k. ] Repeat Build Options [ ./compile.sh BOARD=nanopiduo BRANCH=current RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img ]
  2. Nice, let me try.
  3. OK, no matter what the build fails in various places. I'd like to see someone else try nanopiduo build.
  4. OK, I see what I did with docker build. I need nanopiduo, not duo, trying that now.
  5. Then I try: ./compile.sh docker KERNEL_ONLY=yes BOARD=duo BRANCH=current KERNEL_CONFIGURE=yes [ warn ] The KERNEL_ONLY key is no longer used. [ KERNEL_ONLY=yes ] [ warn ] Instead, use BUILD_ONLY to select the build target. [ u-boot,kernel,armbian-config,armbian-zsh,plymouth-theme-armbian,armbian-firmware,armbian-bsp ] [ o.k. ] BUILD_ONLY enforced to: [ u-boot,kernel,armbian-config,armbian-zsh,plymouth-theme-armbian,armbian-firmware,armbian-bsp ] /root/armbian/lib/functions/main/config-prepare.sh: line 109: /root/armbian/config/boards/duo.: No such file or directory [ error ] ERROR in function prepare_and_config_main_build_single [ functions/cli/cli-entrypoint.sh:106 -> functions/main/config-prepare.sh:112 -> functions/logging/traps.sh:0 ] [ error ] Board configuration does not define valid kernel config [ o.k. ] Process terminated
  6. Docker spits out: [ error ] Docker container build exited with code: [ 0 ] Using: sudo ./compile.sh docker-shell BOARD=duo BRANCH=current RELEASE=jammy Can you verify if you can build duo local? I'm using a Jammy x86_64 VirtualBox desktop.
  7. Ah, let me try docker.
  8. I used a new Jammy desktop VM. I've tried deleting the build dir, everything. If you can get a duo build to work tell me the steps you used.
  9. Seems to always fail no matter how I build it: ake[3]: *** [scripts/Makefile.build:444: drivers/phy/broadcom/built-in.a] Error 127 make[2]: *** [scripts/Makefile.build:552: drivers/phy/broadcom] Error 2 make[1]: *** [scripts/Makefile.build:552: drivers/phy] Error 2 make: *** [Makefile:1902: drivers] Error 2 make[1]: *** [kernel/Makefile:160: kernel/kheaders_data.tar.xz] Error 125 make: *** [Makefile:1902: kernel] Error 2 [ error ] ERROR in function compile_kernel [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:263 -> functions/main/build-tasks.sh:138 -> functions/compilation/kernel.sh:143 -> functions/logging/traps.sh:0 ] [ error ] Kernel was not built [ @host ]
  10. Let me try that.
  11. Selected current kernel and Jammy (maybe Jammy not supported): [ error ] ERROR in function install_deb_chroot [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:285 -> functions/main/build-tasks.sh:208 -> functions/main/rootfs-image.sh:77 -> functions/rootfs/distro-agnostic.sh:282 -> functions/rootfs/apt-install.sh:22 -> functions/logging/traps.sh:0 ] [ error ] Installation of linux-u-boot-nanopiduo-current failed [ nanopiduo jammy no sunxi ] [ o.k. ] Process terminated
  12. Thanks @Igor, I'm actually building Jammy image now based on current kernel (not CSC). Great minds think alike. Waiting on 6.x kernel though, hahaha
  13. Tried a few builds such as https://github.com/armbian/community/releases/download/202248/Armbian_22.11.0-trunk_Nanopiduo_kinetic_edge_6.0.10.img.xz#nanopiduo and the image doesn't even expand. No heartbeat flaching. Not sure how to troubleshoot this.
  14. I can use echo 0 >/sys/class/leds/status/brightness to turn off the status led (blinking blue one, but I was to turn off the bright ass green one. I assume this is mmc1::, but I cannot turn it off.
  15. Oh well, was worth a try. I tried looking all over and didn't see anything + or - about it. Do you know the PSU barrel size and is it + or - tip. None of my PSUs fit (XU4, C1, etc.).
  16. Can you power Prime with OTG port? Or does only PSU work?
  17. sgjava

    Odroid C1

    Are there any images for the C1? The archive download link is broken.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines