siffland

Members
  • Content Count

    7
  • Joined

  • Last visited

About siffland

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have had this image running on one of my sopine boards (in my clusterboard) for about 18 hours. I have done apt upgrades and rebooted several times and so far i have not had any networking issues. $ cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=pine64so BOARD_NAME="SoPine A64" BOARDFAMILY=sun50iw1 VERSION=5.82 LINUXFAMILY=sunxi64 BRANCH=next ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image Thanks, Sean
  2. I use my cluserboard as a docker swarm, works pretty nice. See my post above about the solution i found with the custom u-boot version. I just burn armbian to a micro sdcard and then dd the custom u-boot to the card and everything works fine. The second link from the jan willies github explains how to do this and doing a diff from his github shows the changes he has to make to u-boot. I dont know if this can be submitted upstream to u-boot, i wish i knew a lot more about u-boot. So this is a u-boot problem. on a totally off topic note, the clusterboard and sopine modules are better performing than the raspberry pi modules and any backplane board i have found for them and way cheaper (the modules are about the same price but $99 for the backplane with Gb ethernet is a great deal and it is matx form factor so you can actually mount it in a case). Thanks, Sean
  3. Before i tried the u-boot in the fix above (form the pine64 forums) i did compile mainline u-boot and that did not work, i also compile mainline kernel 5.0-rc3 and that didnt fix the issue (although it runs fine) . Just wanted to add that.
  4. Following this post on the pine pages with the same issue: https://forum.pine64.org/archive/index.php?thread-5581-3.html and using this u-boot (referenced from the above link) fixed the issue for me. https://github.com/janwillies/u-boot/releases/tag/v2019.01-cb-1 So which method is the best fix for this. I would think your driver method is, but this u-boot modification also worked. Thanks, Sean
  5. I also tried the debian strech 5.69 image and had the same results. Is there anything else i can try? Thanks, Sean
  6. 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