nachoparker Posted May 10, 2018 Posted May 10, 2018 Hello, I noticed that the official armbian images for this board(s) are based on Jessie -> https://www.armbian.com/odroid-hc1/ NCP only supports Stretch, but that is ok, because I build the armbian images from source. The Odroid XU4/HC1/HC2 NCP images I build ( https://ownyourbits.com/downloads ) are using Stretch and everything seems to be working fine so far. My question is, what is your testing procedure to consider an image stable? Would it help if I built the plain Armbian image as well so it can be shared in https://www.armbian.com/odroid-hc1 ? I would be happy to help with this Apologies if this has been asked before. Couldn't find it.
Igor Posted May 10, 2018 Posted May 10, 2018 1 hour ago, nachoparker said: NCP only supports Stretch, but that is ok, because I build the armbian images from source. The Odroid XU4/HC1/HC2 NCP images I build ( https://ownyourbits.com/downloads ) are using Stretch and everything seems to be working fine so far. My question is, what is your testing procedure to consider an image stable? Would it help if I built the plain Armbian image as well so it can be shared in https://www.armbian.com/odroid-hc1 ? I would be happy to help with this Odroid XU images can be rebuild. I'll do them. They can't be worse than current and stock.
Igor Posted May 10, 2018 Posted May 10, 2018 Actually not. I test the latest build and something is wrong ...
nachoparker Posted May 10, 2018 Author Posted May 10, 2018 They work just fine according to my testing. Of course, I mainly tested NextCloudPlus... that's why I ask: if you have some criteria for image acceptance I can generate and/or test the image. I can also help with the rock64 image if you guys want, time permitting.
Igor Posted May 10, 2018 Posted May 10, 2018 16 minutes ago, nachoparker said: They work just fine according to my testing. Did you use "development" branch, NEXT and you come out with kernel 4.14.40? I just made an image and it sometimes hangs on boot. I tried XU4 and HC1 ... I am still investigating what's wrong. Well, we seek "board data maintainers" and Rock64 is free of duties, also Odroids It's little work but you need to be up2date with the board. Keep the data accurate here: https://www.armbian.com/rock64/, perhaps add some valuable info or links like https://www.armbian.com/pine64/ (but not that much) and keep that up to date. I am your backup in case you can't follow up or mixup something. You can recommend and rearrange recommended images, but they have to exist on the dl.armbian.com first. Stable images are done manually by me, while you can enable/disable beta images at any time and they are remade in next rebuild cycle. Usually in less than 24h. CLI_BETA_TARGET="jessie,xenial,stretch,bionic:next" This would build both Debian and both Ubuntu images with NEXT (4.14.y) kernel. In case you are up for this, I'll make your login credentials to the webpage.
nachoparker Posted May 10, 2018 Author Posted May 10, 2018 Just now, Igor said: Were you use "development" branch, NEXT and you come out with kernel 4.14.40? The one I built ( https://ownyourbits.com/downloads ) was created with these parameters ./compile.sh docker \ BOARD=odroidxu4\ BRANCH=next\ KERNEL_ONLY=no\ KERNEL_CONFIGURE=no\ RELEASE=stretch\ BUILD_DESKTOP=no\ CLEAN_LEVEL=""\ NO_APT_CACHER=no No hangs that I saw or that anyone else reported. Personally tested on my Odroid HC1 # uname -r 4.9.85-odroidxu4
Recommended Posts