Reddwarf

Members
  • Content Count

    253
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by Reddwarf

  1. I don't know but you could try to download one of the images for Odroid C2 and see if there is a DTB, then try to use that DTB with Balbes image(s). BTW: Does the C2 have the same cpu type as the Amlogic TV-boxes?
  2. There is a separate build for Odroid C2, https://www.armbian.com/odroid-c2/
  3. Easy enough if you know where they are found. This should be cleaned out by the build script as a first step. Not good enough. Besides, the "build" directory of /lib/modules/<vesion>/ needed for compiling 3rd party drivers is completely missing from Armbian...
  4. So why nag about dtb's when the problem is with the packages, I don't follow the reasoning.
  5. debs and DTB's are not the same, or what? Emptying the output folders should be done by the script, that's the accepted way of doing things, or there should be a "make clean" option. Now, I'v done a lot more testing and it turns out that if you enable an option with build error, resetting the configuration dos not help, the script will crash on the next build. Even deleting the whole Build-Armbian folder and cloning it fresh does not help. This suggests that there are temp- or working-folders left behind that are not cleared before the next build. So some more work needed on the script(s). Since I have no way of knowing where those resides the only way of resetting I found is to delete the whole virtual machine and create it again. Anyway, the script works for some kernel configurations but some (useful ones) crashes.
  6. I can't imagine what would be different, I set up a virtual environment with Ubuntu 18.04.2 64bit desktop, plenty of virtual disk space and the needed resources. can't see what's wrong with that as that is the recommended. Any other ideas is greatly appreciated
  7. I would appreciate some tip about what and where to look. I have done exactly as described, not changed any config and still it does not work.
  8. No matter what version I try to build I get this error, even if I don't touch the kernel configuration, so the script for building Armbial is obviously useless. @balbes150 Can you please fix it since I need to build my own image? [ .... ] Creating packages /bin/bash ./scripts/package/mkdebian scripts/package/Makefile:79: recipe for target 'bindeb-pkg' failed Makefile:1439: recipe for target 'bindeb-pkg' failed mv: missing destination file operand after '/home/karstein/Build-Armbian/output/debs/' Try 'mv --help' for more information. [ error ] ERROR in function compile_kernel [ compilation.sh:429 ] [ error ] Failed moving kernel DEBs [ o.k. ] Process terminated karstein@ceres:~/Build-Armbian$
  9. The exact same thing happens even if I don't touch the kernel configuration at all. I'm trying to build Armbian Ubuntu disco with kernel 5.2
  10. Yeah, I can see the obvious! But why oh why? I thought this was a tested reliable procedure?
  11. WHAT NOW?? scripts/package/Makefile:79: recipe for target 'bindeb-pkg' failed Makefile:1442: recipe for target 'bindeb-pkg' failed mv: missing destination file operand after '/home/karstein/Build-Armbian/output/debs/' Try 'mv --help' for more information. [ error ] ERROR in function compile_kernel [ compilation.sh:429 ] [ error ] Failed moving kernel DEBs [ o.k. ] Process terminated karstein@ceres:~/Build-Armbian$
  12. Im' trying to build a new image with full DVB support from Balbes150's fork, but I ran into this error. Could it be that the kernel gets too big or is this something different? CC include/net/netfilter/nf_tables_offload.h.s scripts/Makefile.build:304: recipe for target 'include/net/netfilter/nf_tables_offload.h.s' failed Makefile:1080: recipe for target 'include' failed [ error ] ERROR in function compile_kernel [ compilation.sh:380 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated karstein@ceres:~/Build-Armbian$
  13. Here's a snippet from the content of .config from /lib/modules/build/<version>/ # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.15.0-54-generic Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_MMU=y CONFIG_ARCH_MMAP_RND_BITS_MIN=28 CONFIG_ARCH_MMAP_RND_BITS_MAX=32 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_ARCH_HAS_FILTER_PGPROT=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_HAVE_INTEL_TXT=y CONFIG_X86_64_SMP=y CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_PGTABLE_LEVELS=4 CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y CONFIG_THREAD_INFO_IN_TASK=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y It seems that the build directory is a link so possibly is the .config file somewhere else but I don't know Linux well enough to make a guess
  14. That is NOT extra, it is standard content on ALL other Linux distributions. And there was actually an option to include DVB support when I configured, but the kernel was the old 4.19...
  15. @balbes150 I Cloned into Armbian as instructed on Github and build an image, but even thou Armbian is 5.91 the kernel is just 4.19. Isn't the source updated on the repo? Still, I got no .build in /lib/modules/<version>/, can you include it in the next build please? Edit: It also produced just one ext4 partition in the image, annnnnnnd - it does not boot.
  16. You could try booting from usb again, mount the emmc partition rw, then as root (sudo -s) change ownership back to root.
  17. Have you tried the default (meson-g12a-x96-max.dtb) dtb on Armbian-5.91 image?
  18. The build directory and .config is created when modules are compiled, but for some reason it is either deleted or omitted on Armbian. Can you rebuild the image and not omit/delete the build directory?
  19. Are you running the latest image, and what other dtb's have you tried?
  20. Depends on your box and dtb, on my MiniMx-III and MiniM8S it works fine
  21. It needs the .config file which should be in /lib/modules/5.2.0-aml-g12/build/. It is present in all new releases of Linus (Mint 19, Ubuntu 18.04 etc)