• Content Count

  • Joined

  • Last visited

About Quintus23M

  • Rank

Recent Profile Visitors

612 profile views
  1. I'm trying to use the latest nightly Armbian builds with my EspressoBin board (2GByte version). - flashed this u-boot `flash-image-2g-1000_800_boot_sd_and_usb.bin` - flashed SD card with this image `Armbian_5.34.171106_Espressobin_Ubuntu_xenial_default_4.4.96.img` Armbian is booting, but after a minute or two it crashes. Same effect with older images, too. Any help or ideas? Ubuntu 16.04.3 LTS espressobin ttyMV0 espressobin login: [ 64.314460] Unhandled fault: synchronous parity error (0x96000018) at 0xffffffc0009ff6d8 [ 64.322836] Internal error: : 96000018 [#1
  2. Has anybody tried to build and run a mainline Linux kernel on a S912 device? I do have a Beelink GT1 and would like to use a 4.9.x kernel, no graphics required for my headless server, just ethernet and maybe wifi for later. Currently I was able to boot the GT1 with an Armbian image from @balbes150, but this image has only a 3.14.29 kernel. Any advice and pointers are really appreciated.
  3. Just checked it with using VMware Fusion 7.1.3 on my MBP, same problem as with VirtualBox 5.0.14. U-Boot binary seems to be corrupt. Maybe this Mac is quite too fast...
  4. This problem only occurs when I'm using my 2014 MBP (with VirtualBox). On an Window 7 PC with VMware Workstation 10 it produces a correct U-Boot package with exactly the same Vagrantfile and provision script... So, I do have a workaround now.
  5. I'm running running Ubuntu 14.04.4 LTS 64-bit in Vagrant 1.8.1 (Virtualbox Version 5.0.14 r105127) on OS X. Compiler: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.1)
  6. I'm just trying to create a new image for the ClearFog Pro, b/c I need some special kernel modules built-in. Compiling kernel 4.4.4 with my settings works great, but I have problems to boot the image. This is my build command: sudo ./compile.sh BRANCH=next BOARD=armada KERNEL_ONLY=no BUILD_DESKTOP=no PROGRESS_DISPLAY=plain RELEASE=jessie But u-boot complains about starting with the following message. Even the u-boot `help` command doesn't work. ... Board configuration detected:Net: | port | Interface | PHY address | |--------|-----------|--------------| | egiga0 | RGMII | 0x
  7. @Igor, in the meantime, I was able to run some first tests with the ClearFog Pro: 1) Using a fast mSATA SSD Samsung SSD 840 EVO mSATA 500GB Write: 1048576000 bytes (1.0 GB) copied, 3.06723 s, 342 MB/s (write cache=ON) 1048576000 bytes (1.0 GB) copied, 8.91889 s, 118 MB/s (write cache=OFF) Read: 1048576000 bytes (1.0 GB) copied, 1.96029 s, 535 MB/s 2) Ethernet connection over SFP Connecting two ClearFog Pro over a SFP fiber link. # ethtool eth1 Settings for eth1: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Full Supported pause frame use