Jump to content

gounthar

Members
  • Posts

    415
  • Joined

  • Last visited

Everything posted by gounthar

  1. I know I shouldn't have, but I bought today a Sunvell H3 2GB RAM + 16GB ROM TV Box. I have no idea if this will run Armbian someday, but I had to try...
  2. As I bought it, I may run some tests to help... But for building and all, I have already proved I am useless for the time being (AllWinner H6 for example).
  3. Wow, love your FrankenDell. Thanks for your testimony and advice.
  4. Still a few days to go, and there only one choice for eMMC, which is the 128GB.
  5. Thanks @tkaiser. You're right, the use would be the same (gitlab-runner), except that it would build 64bits binaries. I also thought of using a S912 based TV Box, but I know nothing about its eMMC performances and it looks like it's a pain to install Armbian on these boxes. I will have a closer look to Rock64, thanks ($35.44 is a nice price tag to start). I will try to find a 2.5' SDD.
  6. Hi, as I have trouble with aging SDCards, I was thinking of getting a new SBC with eMMC (I already have Odroid XU4, but it's not cheap). I'm pretty happy with OrangePi Zero, but would love to find a SBC with a 64bits SoC, Gigabit Ethernet, 1GB of RAM (as 512MB implies swapping for my use case) and eMMC. OrangePi have the 3G-IOT (which is only 512MB) and 4G-IOT, but they are not supported, and I don't fancy all the gizmos that are on these boards. NanoPi M1+ almost fits the bill, but it's a 32bits SoC. NanoPi K1+ is almost perfect, but it's pricey (and has 2GB of RAM, which would not be a problem if it was cheaper). Any suggestion? Thanks.
  7. I've been looking at this expansion board for a while now, but I'm still undecided. My first question is: what is the maximum physical size of mSata drives that we can put on the expansion board? 30mmx50mm, 2.5'? What part of the system can we host on this extension? Anything but boot? I guess the Zero can't boot on that? For the time being, the Zero I'd like to upgrade is a gitlab-runner (building ARM binaries and Docker images). I'm not really concerned about speed, but about having a stable solution (no degrading SDCard performance) and a way to swap without killing the storage media. Thanks.
  8. I know I'm supposed to log with armbianmonitor -u, but I can't behind that ***** corporate proxy. So I made a strace. / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) |__ /___ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | / // _ \ '__/ _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | / /| __/ | | (_) | \___/|_| \__,_|_| |_|\__, |\___| |_| |_| /____\___|_| \___/ |___/ Welcome to ARMBIAN 5.38 stable Debian GNU/Linux 9 (stretch) 4.14.18-sunxi System load: 0.11 0.24 0.25 Up time: 6:55 hours Memory usage: 26 % of 493MB Swap usage: 9 % of 127Mb IP: 10.aa.bb.ccc 169.254.6.65 CPU temp: 45°C Usage of /: 31% of 15G Any idea? Thanks.
  9. There is an opensource wm that I'd like to use with Armbian. I have compiled and installed it, but would like to have it as a package. I have forked a repo that makes a .deb of this wm and built it with Shippable (so aarch64). I don't have any Debian mirror to host it... so... What is the standard way to build a package for Armbian? There are also other libraries/tools (like pacman, libarchive) that I have compiled (because I could not find them)... Thanks.
  10. I now can build the image, dpkg-deb: building package 'linux-source-4.17.11-next-sunxi64' in '/home/vagrant/armbian/.tmp/linux-source-next-sunxi64_5.54_all.deb'. [ o.k. ] Creating board support package [ orangepioneplus next ] [ .... ] Fingerprinting [ o.k. ] Building package [ linux-stretch-root-next-orangepioneplus ] [ o.k. ] Building desktop package [ armbian-stretch-desktop_5.54_all ] [ o.k. ] Kernel build done [ @host ] [ o.k. ] Target directory [ /home/vagrant/armbian/output/debs/ ] [ o.k. ] File name [ linux-image-next-sunxi64_5.54_arm64.deb ] [ o.k. ] Runtime [ 61 min ] but I still have some issues with the branches or kernel version... dpkg-genchanges: binary-only upload (no source code included) dpkg-source --after-build linux-4.17.y dpkg-buildpackage: binary-only upload (no source included) dpkg-deb: building package 'linux-source-4.17.11-next-sunxi64' in '/home/vagrant/armbian/.tmp/linux-source-next-sunxi64_5.54_all.deb'. [ o.k. ] Creating board support package [ orangepioneplus next ] [ .... ] Fingerprinting [ o.k. ] Building package [ linux-stretch-root-next-orangepioneplus ] [ o.k. ] Building desktop package [ armbian-stretch-desktop_5.54_all ] [ o.k. ] Kernel build done [ @host ] [ o.k. ] Target directory [ /home/vagrant/armbian/output/debs/ ] [ o.k. ] File name [ linux-image-next-sunxi64_5.54_arm64.deb ] [ o.k. ] Runtime [ 15 min ] I used LIB_TAG="sunxi-4.18" # change to "branchname" to use any branch currently available. in the config file, and I still get error: pathspec 'sunxi-4.18' did not match any file(s) known to git. [...] dpkg-deb: building package 'linux-source-4.17.11-next-sunxi64' in '/home/vagrant/armbian/.tmp/linux-source-next-sunxi64_5.54_all.deb'. Anyway, it's building now, which is way better than what I had beforehands...
  11. It looks like CSI is way more powerful than USB because of bandwith, direct access to GPU, and other reasons. The problem is most of my boards don't have a CSI connector; the Raspberry Pi is the only one. The NanoPi Fire3 has a DVP interface, but the camera choice seems to be smaller... The Renegade Elite will have a CSI interface, but it will not be available before September, and it could take a few months to get it working under Armbian. I will try to understand ISP/CSI/DVP and make a choice...
  12. Thanks @chwe. It doesn't have to work now, as the target solution (DSLR camera, Windows Laptop and proprietary software) has already been found and validated. My goal is to propose a FOSS ARM cheaper alternative... If it doesn't work now, that's not really a problem. I'd like it to work by November; the first solution will be put at work in September, but would be scaled next year. If I ever can find something before the end of the year, that would be nice. As logged in my gist, I have access to: Two Orange Pi Zero Orange Pi One Plus Two Raspberry Pi 3B+ Two Raspberry Pi 3B Odroid XU4 NanoPi Fire3 Renegade Elite in September video converter octopuss Something working with Armbian (at least partially) would be really cool. I still have to investigate on CSI cameras, lenses and so on...
  13. Thanks. I am logging the information there: https://gist.github.com/gounthar/6e207308c05b0c6cf52e14e3c0f778af .
  14. Wow, pretty interesting indeed (for the video encoding part), thanks! Now, if someone had a suggestion on how to generate that video without a DSLR... but a cam that would work directly with a SBC...
  15. Hi Gang, I'm wondering which SBC running Armbian could be good at recording and broadcasting sound and video (for a conference). I asked the question on Twitter too.
  16. I have some problems with the network when working from work because of that damn proxy... [ o.k. ] Downloading sources [ o.k. ] Checking git sources [ u-boot h6-dram ] [ .... ] Checking out [ o.k. ] Checking git sources [ linux-mainline linux-4.17.y ] fatal: unable to connect to git.kernel.org: git.kernel.org[0: 147.75.44.153]: errno=Connection timed out git.kernel.org[1: 2604:1380:4090:1700::1]: errno=Network is unreachable [ .... ] Fetching updates and I have some problems anyway at home... 69.7MiB [ 9.9MiB/s] [=====================================================================================================================================================================] 102% cp: cannot stat 'COPYING': No such file or directory [ o.k. ] Compiling next kernel [ 0 ] [ o.k. ] Compiler version [ aarch64-linux-gnu-gcc 7.2.1 ] [ o.k. ] Using kernel config file [ config/kernel/linux-sunxi64-next.config ] make: *** No rule to make target 'olddefconfig'. Stop. make: *** No rule to make target 'Image'. Stop. [ error ] ERROR in function compile_kernel [ compilation.sh:365 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated
  17. Unfortunately no. I've been having a hectic schedule at work, and my ISP box just stopped working last week. I got my new one yesterday, so I hope to have a look at it this week-end. Thanks.
  18. Tempting, very tempting... Edit: too tempting, booked one.
  19. Any news on these boards? I will maybe buy a board sporting RK3399 or RK3328 if the support of the SoC is ongoing...
  20. I had been told not to use NEXT for these boards, or I did not understand correctly maybe... I would be happy to join, as long as I don't break everything.
  21. Sorry, I am working on a fork (I haven't changed anything yet, I just created a new branch to work on the Ethernet part for the DTS).
  22. Sorry for bothering you with stupid questions, but I launched: vagrant@ubuntu-xenial:~/armbian$ sudo ./compile.sh BOARD=orangepioneplus KERNEL_ONLY=yes RELEASE=stretch EXPERT=yes My config file is : # Read build script documentation http://www.armbian.com/using-armbian-tools/ # for detailed explanation of these options and for additional options not listed here KERNEL_ONLY="no" # leave empty to select each time, set to "yes" or "no" to skip dialog prompt KERNEL_CONFIGURE="no" # leave empty to select each time, set to "yes" or "no" to skip dialog prompt CLEAN_LEVEL="make,debs,oldcache" # comma-separated list of clean targets: "make" = make clean for selected kernel and u-boot, # "debs" = delete packages in "./output/debs" for current branch and family, # "alldebs" = delete all packages in "./output/debs", "images" = delete "./output/images", # "cache" = delete "./output/cache", "sources" = delete "./sources" # "oldcache" = remove old cached rootfs except for the newest 6 files DEST_LANG="en_US.UTF-8" # sl_SI.UTF-8, en_US.UTF-8 # advanced KERNEL_KEEP_CONFIG="no" # do not overwrite kernel config before compilation EXTERNAL="yes" # build and install extra applications and drivers EXTERNAL_NEW="prebuilt" # compile and install or install prebuilt additional packages CREATE_PATCHES="no" # wait that you make changes to uboot and kernel source and creates patches BUILD_ALL="no" # cycle through available boards and make images or kernel/u-boot packages. # set KERNEL_ONLY to "yes" or "no" to build all packages/all images BSPFREEZE="" # freeze armbian packages (u-boot, kernel, dtb) INSTALL_HEADERS="" # install kernel headers package LIB_TAG="orange-one-plus-ethernet" # change to "branchname" to use any branch currently available. EXPERT="yes" and then, I got AR net/built-in.a [ error ] ERROR in function compile_kernel [ compilation.sh:364 ] [ error ] Kernel was not built [ @host ] [ o.k. ] Process terminated I'm sure I missed something, but can't see what for the time being.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines