Igor

  • Content Count

    11707
  • Joined

  • Last visited

About Igor

  • Rank
    Embedded member

Profile Information

  • Gender
    Male
  • Location
    Ljubljana

Recent Profile Visitors

21240 profile views
  1. RTFM https://docs.armbian.com/Developer-Guide_Build-Preparation/ https://github.com/armbian/build#support
  2. It builds on all boards and already that was resourceful enough to secure. We don't check how implementation works, but we might when you will need this badly enough to help us. Armbian has close to nothing to do with this 3rd party file system. We provide ZFS as a out of the tree module, which you build and use whatever you like. You should ask such question at ZFS project, not here or at Hardkernel forum. They are not even on our level. Since many years we provide BTRFS install from our armbian-config. We could ofc some day provide ZFS as well, but adding
  3. Nice catch. I have mitigated this problem this way: https://github.com/armbian/build/pull/2839/files and remove combinations at the end since i didn't find a better way https://github.com/armbian/build/pull/2848/files Well, all this has to be done automagically ...
  4. Random behaviour is because there is no more per branch BSP. Decisions has to be refactored for runtime. I keep forgetting we still have legacy stuff here ... so this will complicate a bit https://armbian.atlassian.net/browse/AR-779
  5. By opening a ticket https://armbian.atlassian.net/browse/AR-776 my job is done. I have other troubles to deal with.
  6. Aha, I see. Problem was introduced here: https://github.com/armbian/build/pull/2791 even there was a lot of testings.
  7. Yes. But if you haven't, its something else. Trying to reason why this happened. It looks like you are missing Device tree package, which comes in a separate package: linux-dtb-legacy-rockchip ... if you install that package or copy the content to your failed session, it should boot up. Tinker or Tinker S can use same settings, from S model.
  8. You have perhaps jumped between legacy and modern kernels?
  9. this project is supported only with 1/1000 of needed resources. It is not possible to fix all issues you find. Not even close. People doesn't know what is our work or what not and there are "1000 people" before you asked for something. We don't know if that is a problem of our work or just something in 3rd party part. it is impossible to diagnose troubles without logs. I am sure we agree on that, but since this support is paid from our pocket, dealing with you is my direct expense, we choose what you need to provide or we pull out our scarce resource to problems where our time is respect
  10. If it so hard to follow https://www.armbian.com/bugs/ and provide logs we are requesting? Things you thinks that are important, might not be enough. tl;dr; Without logs, you are alone dealing with this problem.
  11. Agree. Start working on to imrove your communication, play by the rules we set to not waste our time in such a great extend ... When users have a problem, users transfer in uncontrollable blood sucking beast towards people that contribute. How about that perspecitve, which is not seen if you only think about your small self / problem? Read again: https://forum.armbian.com/topic/16469-overlayroot-not-working-as-expected/?do=findComment&comment=125163
  12. Which image exactly? (how to properly report a problem https://www.armbian.com/bugs/ )
  13. Thank you! As you can see our graphics elements are poor. We had some initial setup by people that are skilled at this mainly for website, the rest is more or less amateur made. We are good in tinkering hardware, sw development, but graphics ... as you can see Beside our store - Twitter has almost no branding, we have no release template graphics - for twitter / forum / elsewhere, official wallpapers might need some refreshment, perhaps just playing with colors. Device pictures are also prepared by amateurs, we might need overall refreshment and order in our stationary + wallpapers which