Search the Community

Hi everybody and thanks the armbian team for your work. I'm owning a SOPine module (SOPine-A64-Rev C) with a SOPine Baseboard (Model A Rev B), with the 16Go eMMC module sold by Pine64. I tried these builds with the same issue: Armbian_20.02.1_Pine64so_buster_current_5.4.20.img (All the provided logs are from this build) Armbian_20.02.1_Pine64so_bionic_current_5.4.20.img Armbian_19.11.6_Pine64so_buster_current_5.4.7.img I tried at first to write the image direclty to the eMMC before noticing it wasn't the right way to do => I removed all the partitions from the eMMC. When writing the image to the microSD card: If I insert microSD card only => System boots properly If I insert microSD card + eMMC module => Boot hangs after U-boot at : Loading, please wait... starting version 241 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Loading root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems I also tried the image Armbian_20.05.0-trunk.117_Pine64so_focal_dev_5.6.5_minimal.img. This image however hangs 1 or 2 minutes at: Loading, please wait... starting version 245.4-4ubuntu3 But ends by booting! I have 2 relevant devices under /dev/: mmcblk0: mmcblk0p1 mmcblk2: mmcblk2boot0 mmcblk2boot1 I would like to use if possible the Debian base, than the Ubuntu dev.. While in U-boot console (with eMMC inserted): With Armbian_20.02.1_Pine64so_buster_current_5.4.20.img: => version U-Boot 2019.10-armbian (Feb 17 2020 - 09:28:03 +0100) Allwiner Tchnology aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0 GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321 => mmc dev switch to patitions #0, OK mmc0 is current device => mmc list mmc@1c0f000: 0 (SD) mmc@1c11000: 1 => mmc dev 1 switch to patitions #0, OK mmc1 (part 0) is current device => mmc list mmc@1c0f000: 0 (SD) mmc@1c11000: 1 (eMMC) => I have to change device for eMMC to be recognised ? With Armbian_20.05.0-trunk.117_Pine64so_focal_dev_5.6.5_minimal.img: => version U-Boot 2020.04-armbian (Apr 26 2020 - 09:12:13 +0200) Allwiner Tchnology aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0 GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321 => mmc dev switch to patitions #0, OK mmc0 is current device => mmc list mmc@1c0f000: 0 (SD) mmc@1c11000: 1 (eMMC) => eMMC recognised automatically. Similar issues:

I just upgraded (using a fresh image with the 5.69 image) one of my SOPINE A64 modules from Armbian Xenial - legacy kernel 3.10.y to Armbian Bionic - mainline kernel 4.19.y. The onboard ethernet will no longer work. The sopine module is connected to a clusterboard instead of a sopine baseboard, but the NIC is on the module so it should not make a difference. On Xenial 3.10.y kernel the driver loaded for the NIC is the sunxi_geth driver, on bionic 4.19.y kernel it is the st_mac100 driver. Here is the output of the lshw for 4.19.y *-network:0 description: Ethernet interface physical id: 6 logical name: eth0 serial: 02:ba:9b:53:82:7a size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=st_mac100 driverversion=Jan_2016 duplex=full link=yes multicast=yes port=MII speed=1Gbit/s I have a USB dongle plugged in and that works to get the machine online for testing. In the same clusterboard i have more modules still on the old image and they have no issues with networking. Let me know what other information i can supply. Thanks, Sean

I am using a system I built from the trunk of Armbian for the pine64so. After booting up the mouse does not do "smooth mouse tracking". The movement of the mouse lags behind where it should be and has to "catch up" which takes several seconds. I consider it unusable doing this. This is Version "20.04.1 LTS (Focal Fossa)" Armbian 20.08.0-trunk Focal 5.7.17-sunxi64 #trunk Mon Aug 24 03:00:31 PDT 2020 aarch64

The Volumio team is currently investigating whether our sopine64 based motivo board (https://volumio.org/epic-journey-called-volumio-motivo/) could boot from usb using SPI flash. I'm aware of the sunxi SPI developments in u-boot and mainline kernel, and that we theoretically should be able to flash the SPI-NOR chip with the correct u-boot version using FEL mode. I also read that armbian has been prepared for booting from usb (as @martinayotte mentioned in other places). My question is, did anyone actually do anything in this direction, is there something I could help testing with? I know how to compile u-boot as I've done this with armbian's u-boot version 2019-04 which works fine with our motivo board. I must admit i'm not skilled enough to get this done on my own, any help or pointer in the right direction would be very much appreciated. Cheers - Gé

I usually build a new armbian full os image, apply some kernel options and have no problems booting a sopine64. The last known good version for me was: Armbian 5.51 / Kernel 4.14.54 The latest (and starting with 5.57) with Kernel 4.17.16 only seem to 'half boot' - they start up uboot but fail to load the OS and instead attempt to do a network boot over TFTP. The errors go by so fast that I can't really read it and have to resort to trying to video capture it and the monitor seems to be slow to initialize and i only see the tail end of the errors scroll by. I am sure a lot changed between 5.51 and 5.57 - I noticed a new version of uboot. Somewhat at a loss as to how to resolve this.. I tried rebuilding an image every few days in hoping a fix was merged back into the code base.

Hi all, looking for jessie img for Pine64so, found it for Pine64 but not for SOPINE thanks