• Content count

  • Joined

  • Last visited

  1. Le Potato Ethernet Problems

    I think the vendor has fixed the ethernet problem in their release build. Has this fix made it into armbian yet or not? Sorry, it's not clear to me from reading this thread whether that is a definite yes or no.
  2. Le Potato Ethernet Problems

    Hello All, I have been away from this board for a while. Apologies for the very basic question, but how can I obtain or build an image for the Potato with the fixes described here? I read something about Armbian nightly builds no longer being made available (and, even more basic, I don't know where they are. Just the head of the git repo?)
  3. Thanks @Igor. Just asking!
  4. The supported Armbian build environment is Ubuntu 16.04 LTS I know. Is there any strong reason why one should not build now on Ubuntu 17.10?
  5. Le Potato Ethernet Problems

    Hi @TonyMac32 and @Da Xue, How does one obtain this patched image?
  6. Le Potato Ethernet Problems

    Hi Da Xue, Any progress?
  7. Le Potato Ethernet Problems

    I built the latest 5.34 Armbian image for the Le Potato and it still locks up after about an hour or so of ethernet traffic (using turbovnc), rendering this very nice little board unusable. I see others confirming the problem, but are there any people able to run this board successfully? A bit of a puzzle.
  8. I saw references on the site to a countdown in days to a major new release, but that has now disappeared, and I also see various mentions of version 5.34 but I do not know where to obtain this. The highest release in github seems to be 5.24. How does one find this? Apologies if this appears to be a stupid question - I looked everywhere.
  9. Le Potato Ethernet Problems

    Hi @TonyMac32 now confirming that I can indeed confirm that a constant stream of inbound traffic causes the ethernet to lock up after 15 minutes to an hour or so. This test is repeatable and reliable. As to how to provide logs or any further detail, I don't really know.
  10. Le Potato Ethernet Problems

    I have the Libre Le Potato, running the Armbian Ubuntu image [Ubunutu desktop - mainline kernel] from the download page. 2GB model, exactly as the OP has above. I see the same issue - ethernet connectivity reliably just stops after about 15 minutes or so of use, just running turbovncserver and one remote session, nothing too strenuous. Apart from that, it's a wonderful little board and Armbian on it is really excellent. So, just adding more weight to this observation by others.
  11. OPi Plus 2 UART not working

    Builduing any Armbian image, headless or desktop, for any of the Orange Pi series results in a blank orange screen on boot and no futher action. The UART outputs nothing. However, the downloadable prebuilt Armbian image does work. As to the UART problem, I am beginning to suspect a board hardware problem. As to the non-booting issue, I have no idea. I did observe that I could find the IP address and ssh into the machine despite this lack of display output. Are there logs I could find to help diagnose this issue?
  12. No matter what I do, when I use an Armbian image built with I get a blank orange screen on the OPi Plus 2. The downloadable pre-built image from Armbian for the board works fine. Wanting to debug this, I have an Adafruit UART serial cable adapter, known functioning and working. If I attach this to the UART pins on the small header near the power socket I get no output (and I have swapped RX and TX to no avail). How does one enable this UART? Am I using a wrong approach? I have console=both in armbianEnv.txt.
  13. This I did not know, so that's very useful information. I had always thought every ethernet NIC had a burned in MAC address, but now I see that's not the case on these small boards. Thanks!
  14. # armbianmonitor -u: # cat /sys/class/net/eth0/address 46:d5:67:c2:29:8e # grep ethaddr /boot/armbianEnv.txt ethaddr=46:d5:67:c2:29:8e So the system certainly picks up the assigned MAC address just fine. The question arose for me because I am making clones of cards to run multiple board systems on one LAN, so it appears I have to edit armbianEnv.txt for each system individually and provide a different MAC for each board by hand. That's not onerous, but just another step that needs to be done.
  15. Running Armbian Ubuntu Xenial 16.04 on a PineA64, legacy kernel 3.10.105-pine64. Why is it necessary or desirable to put the variable 'ethaddr' in armbianEnv.txt? I thought the hardware mac address would be detected by the kernel. Perhaps not?