Andro

Members
  • Content count

    23
  • Joined

  • Last visited

  1. Le Potato Ethernet Problems

    Hi Da Xue, Any progress?
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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?
  7. No matter what I do, when I use an Armbian image built with compile.sh 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.
  8. 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!
  9. # armbianmonitor -u: http://sprunge.us/jUbU # 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.
  10. 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?
  11. Ether address in armbian.txt

    Sorry - wrong forum. Moved to Allwinner A64.
  12. 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?
  13. Add Support for RK3399 (2xA72+4xA53)

    Reading the above thread, is there any support for the Videostrong 6 core RK3399 board? Can Armbian run on that system?
  14. After some work I now have this usb wireless device working just fine. For others looking to use it, here's a brief synopsis of what I did, running Armbian 5.32 for Pine64, kernel 3.10.105-pine64, and building directly on the PineA64, not in the Ubuntu Armbian user build system. Obtain the most recent, fixed driver source from: https://github.com/xtknight/mt7610u-linksys-ae6000-wifi-fixes To get the built module to load properly, you have to correct the value UTS_RELEASE to add -pine64 in the linux headers file: /usr/src/linux-headers-3.10.105-pine64/include/generated/utsrelease.h change #define UTS_RELEASE "3.10.105" to: #define UTS_RELEASE "3.10.105-pine64" Make and make install. The kernel module that gets built and installed and loaded is mt7610u_sta. This can be confusing as the device is referred to as the RT2870STA, but it uses the Mediatek chip and driver. To provide enough kernel memory for the module to load, add coherent_pool=6M to the line setenv bootargs in /boot/boot.cmd and regenerate boot.scr int he usual way. To configure, one way is to edit the file: /etc/Wireless/RT2870STA/RT2870STA.dat The file README_STA_usb in the source tree describes all the configuration values in quite good detail. The device will appear as ra0 and can be set up as per any normal internet connection from /etc/network/interfaces, and so on. I have probably left out some steps here, but the gist of how to do this should be clear. I am a newcomer to Armbian user builds, so I am not sure how to do this out of tree and provide this code at the user build stage, but I will look into that. On reflection what I did is probably entirely the wrong way to go about this, but I hope this information is useful one way or another. At the very least it proves that this excellent usb wireless adapter works nicely with the Pine A64.
  15. I believe the TP-Link AC600 wireless usb adapter uses the Mediatek chipset. Has anybody got this running on a Pine A64?