Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender

Contact Methods

  • Website URL
  • Github
  • Discord
  1. Nexus

    Odroid M1

    Yep, this builds! Thanks for the help!
  2. Nexus

    Odroid M1

    Hello again. Thanks for that tip. I spun up an x86 Ubuntu 22.04 VM and tried again on armbian-next. Still, no luck, with this time the issue being the unavailability of the file `jammy-cli-arm64.4adfa3833e0441b5fb7bfe6607347039.tar.zst` on Armbian mirrors. Any clue on what mirror to get this/where to find it (if that is actually the issue here)? I've tried numerous different mirrors on different machines and in different configurations. Logs are attached. Thank you very much for your help with this. logs.tar.zst
  3. Package `gcc-riscv64-linux-gnu` should be added as a dependency for usage in Docker, else it errors out with it missing. Based on how the depends are configured, it seems as if the intention was that this package would be provided by the distro or built by the user? Is Docker intended to build this toolchain itself?
  4. Nexus

    Odroid M1

    Hello. Is anyone else having issues compiling desktop images for this platform? Attached are the 2 error logs that the compile script produces. I used build files from rpardini's repository; specifically the "extensions" branch. Is this the incorrect one? Thanks for any help. Logs produced
  5. Hi. Around a month ago, my Rock 3A arrived and I got to playing with it. I noticed that there was a community build configuration for it, so I set up an Armbian build environment and got to building it. The image built without error and before I knew it my device had booted. However, since then, a few changes have been made to the Rock 3A (including receiving a proper Armbian maintainer), and now it seems to be completely broken. This issue seems to be reproducible, with people both being able to boot the board with old images as well as not being able to boot with fresh images. There seems to be some work happening towards fixing u-boot (which seems to be the issue) on GitHub, but it has been completely silent for almost two weeks. I realize that stuff like this takes time, as well as the fact that all of this work is community-driven. My main goal for asking this is so that I can contribute to the development for this board myself. I can't tell why booting this board isn't working from boot logs (available throughout this thread on the Radxa forum), so I'm largely at the mercy of those more knowledgeable about this part of Armbian and Linux than I am. Any and all info would be greatly appreciated. Thanks.
  • Create New...