Jump to content

sgjava

Members
  • Posts

    374
  • Joined

  • Last visited

Everything posted by sgjava

  1. sgjava

    Odroid C1

    @Markus_ I created a new post that has all the steps
  2. I figure I'd make this a new post. Thanks to @Markus_ and @Igor for their help. I'm still trying to get wifi module 3 working, but I'm happy to at least have an up to date C1 image. git clone --depth 1 https://github.com/armbian/build cd build mkdir -p ./output/debs wget -c -O ./output/debs/linux-u-boot-current-odroidc1_23.02.0-trunk_armhf.deb http://apt.armbian.com/pool/main/l/linux-u-boot-odroidc1-current/linux-u-boot-current-odroidc1_21.02.3_armhf.deb sudo ./compile.sh CLEAN_LEVEL= BOARD=odroidc1 BRANCH=current RELEASE=jammy REPOSITORY_INSTALL= BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no KERNEL_ONLY=no COMPRESS_OUTPUTIMAGE=sha,gpg,img ls ./output/images u-boot has not been able to be built for a while now (last supported image was focal and 5.x kernel). Step 4 copies the last good u-boot to ./output/debs which is created in step 3. Change current in ./output/debs/linux-u-boot-current-odroidc1_23.02.0-trunk_armhf.deb to edge to use edge kernel. Also change build number 23.02.0 to current build number. Step 5 does build without prompting. Change BRANCH=current to BRANCH=edge to build edge branch. If all goes well you should see image with step 6. Issues: Current branch with 5.x kernel corrupts SD. I found this build totally unusable. Current and edge branches RTL8188CUS-GR causes wired Ethernet (onboard or USB) to not be reachable, thus you cannot configure wifi the easy way. RTL8188FTV (RTL8188FU) will not build due to differences in random kernel function and other stuff later on.
  3. sgjava

    Odroid C1

    OK, I got it to build. The secret is REPOSITORY_INSTALL= REPOSITORY_INSTALL (comma-separated list): list of core packages which will be installed from repository Available options: u-boot, kernel, bsp, armbian-bsp-cli,armbian-bsp-desktop,armbian-desktop,armbian-config, armbian-firmware Set to “” to use packages one from local output or build if not available I'll do it from scratch and post final instructions.
  4. sgjava

    Odroid C1

    @Markus_ Using current and jammy I get: sudo ./compile.sh BOARD=odroidc1 CLEAN_LEVEL= KERNEL_KEEP_CONFIG=yes COMPRESS_OUTPUTIMAGE=sha,xz EXPERT=yes REPOSITORY_INSTALL=u-boot [ .... ] Installing from repository [ linux-u-boot-odroidc1-current ] And debug install.log: E: Unable to locate package linux-u-boot-odroidc1-current
  5. sgjava

    Odroid C1

    @Markus_ I'll try this tomorrow, thanks!
  6. sgjava

    Odroid C1

    @Tomasz Grzegurzkocan you give the command line you used? I'll try now. After git pull I get: odroidc arm aml_meson odroidc hardkernel m8b hardkernel/odroidc:DDR3_1GB [ error ] ERROR in function compile_uboot [ functions/cli/cli-entrypoint.sh:109 -> functions/main/build-tasks.sh:278 -> functions/main/build-tasks.sh:145 -> functions/compilation/uboot.sh:131 -> functions/logging/traps.sh:0 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated Using: sudo ./compile.sh BOARD=odroidc1 BRANCH=current RELEASE=jammy BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img
  7. @Markus_ Can you provide the steps to build? It would be interesting to try 6.1.0 kernel since that's LTS like 5.1.0.
  8. sgjava

    Odroid C1

    @Markus_ Just a FYI, the focal image with 5.10 kernel allowed reboot. You can freeze the kernel and upgrade to Jammy that way. Reboot still works.
  9. @SteeManit finally built for me. Boots without wifi, so making progress. Thanks for you help. 5.x image working fine on Jammy now.
  10. @SteeMan 6.x kernel still failing, can you try edge?
  11. uname -a Linux nanopiduo 5.15.81-sunxi #trunk SMP Tue Dec 6 17:19:18 EST 2022 armv7l armv7l armv7l GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy
  12. @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 ]
  13. OK, no matter what the build fails in various places. I'd like to see someone else try nanopiduo build.
  14. OK, I see what I did with docker build. I need nanopiduo, not duo, trying that now.
  15. 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
  16. 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.
  17. 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.
  18. 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 ]
  19. 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
  20. 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
×
×
  • Create New...