lanefu

  • Posts

    1177
  • Joined

  • Last visited

Community Answers

  1. lanefu's post in Armbian CI is building v5.10.43 while my local build is making v5.10.45. How can I switch? was marked as the answer   
    Re: binfmt.

    if using lxc the container.
    you need to execute it with more priviledges
     
    if you are already, or are using lxc the VM
    your kernel needs to be ubuntu's -generic kernel rather than the -virtual kernel... -virtual doesn't have binfmt support in it the last time I checked. 


    misc building tips.. I personally hate the LIB_TAG thing.. and prefer to just force it to use whatever branch I'm using.. here's a hint for that https://docs.armbian.com/Developer-Guide_Build-Preparation/#using-alternate-armbian-builder-repos-and-branches

    How to build from the kernel source you want and love armbian builder

    As we mentioned. it's not that the armbian build checkout has changed the minor release. it's that the upstream has (it's a weakness we have).   So you're going to want to specify your own kernel branch/commit/target etc by hand.

    https://docs.armbian.com/Developer-Guide_Build-Preparation/#using-alternate-armbian-builder-repos-and-branches

    So step 1.. we need to figure out what "family" your odroidn2 is

     
    lane@billroyall:~/GIT/build$ fgrep -i FAMILY config/boards/odroidn2.conf BOARDFAMILY="meson-g12b"
    okay.. it's part of the meson-g12b family

    https://github.com/armbian/build/blob/master/config/sources/families/meson-g12b.conf#L1

    hmmmm ---- code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } source "${BASH_SOURCE%/*}/include/meson64_common.inc"
     
    okay lets look at its common include
     
    https://github.com/armbian/build/blob/master/config/sources/families/include/meson64_common.inc#L30-L32

    code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } branch:linux-5.10.y

    alright so.. it's just following the linux-5.10.y branch.. hence the minor release update....  and since no explicit kernel source is specified.. we can assuming it's using the default mainline

    https://github.com/armbian/build/blob/master/lib/configuration.sh#L86

    which means hunting here https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tag/?h=v5.10.43

    and lucky for us there's a tag
     
    so in theory you should be able to create the file  code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } userpatches/sources/meson-g12b.conf
     
    with the contents of

     
    KERNELBRANCH=tag:v5.10.43  
     
     
     
     
  2. lanefu's post in Inconsistent mount point on Banana Pi Pro over SATA was marked as the answer   
    block device names can vary especially on USB.... it's best practices to use UUIDs or LABELS to mount filesystems.
  3. lanefu's post in Help With Understanding Firstrun and Resetting Armbian Images was marked as the answer   
    Doing this should probably trigger it.  https://github.com/armbian/build/blob/master/lib/distributions.sh#L157

    Also take a look at 

    https://github.com/armbian/build/blob/master/lib/distributions.sh#L372-L379

     

    Might be related to https://github.com/armbian/build/blob/master/packages/bsp/common/lib/systemd/system/armbian-firstrun-config.service#L9
     

    Probably best to keep conversation here for now.  Mostly we use issues in GitHub for major bugs / problems
  4. lanefu's post in Bionic apt update "File has unexpected size" was marked as the answer   
    Blerg.  The error is telling the truth.  Most likely mirror sync.     Mirror validation is something for us to work on next.
  5. lanefu's post in Accessibility armbian-config was marked as the answer   
    @peterbmckinleylook at the nmcli command
  6. lanefu's post in Broadcom BCM2711, was marked as the answer   
    Hi @Rein We don't support any Raspberry Pi boards.   We focus on alternate SBCs that have less attention and community.
     
    https://docs.armbian.com/Quick_facts/#what-is-armbian-linux