Werner

  • Content Count

    2239
  • Joined

  • Last visited

Everything posted by Werner

  1. Maybe some day we can switch back to mainline for Allwinner but at this moment it makes more sense to use megi's pre-patched sources.
  2. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system)
  3. $ sha256sum Armbian_21.02.4_Odroidn2_buster_current_5.10.27.img.xz aff027c69e1e855ba408703ff6a3c3dd9574ee9e500073640657b1e5adc7492d Armbian_21.02.4_Odroidn2_buster_current_5.10.27.img.xz
  4. I can do that for you if you like...
  5. You should ask at their place since both nm and openvpn are userspace packages which Armbian is not involved in. Seems incomplete.
  6. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system)
  7. There has been an attempt to do that: https://github.com/armbian/build/pull/2620
  8. https://github.com/armbian/build/pull/2759
  9. Hm was not the case when I took a look. Now I can see it too. Odd.
  10. Unfortunately there is no way at the moment to create supported images by your own. At a certain point when we think things are stable enough official images are created, then master branch moves along. Tags are created every release but since Armbian heavily relies on 3rd party repositories which are not nailed down to a specific branch/tag they move forward too and our tag might break. Due to very limited human resources we cannot afford to continuously watch closely for those repos and tag them as well when releasing a new version of Armbian.
  11. Either you tie two jumper wires to each red and black of the USB cable or use a charger with two USB outputs. pin connector wise you can use 2 and 4 for 5V and like 6 and 14 for GND. However just try with one pair of wires connected and if it works just fine you dont have to do anything. Only if you recognize strange behavior try with double feed.
  12. correct. no. What he meant to say is that it might be necessary to feed the board with 2x 5V and 2x GND in order to compensate voltage drop across connectors and wire. Boards start to behave weird and malfunction due to under-voltage.
  13. Aight, weird situation. I tried both buster and focal and both failed for me. - tried different sd cards - tried different device and OS for flashing - tried a freshly built image from master too for Rich both images work fine. My board is perfectly fine since it boots from a known to work older sd.
  14. Moved to proper location You really want to pick up such a thing Make sure it can handle 1,5Mbaud Edit: Confirmed. Something is wrong. ID:0x805 N In DDR4 333MHz Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=15 CS=1 Die Bus-Width=16 Size=1024MB ddrconfig:14 OUT Boot1 Release Time: May 13 2019 17:34:36, version: 2.50 ChipType = 0x11, 248 mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 SdmmcInit=2 1 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=60906MB FwPartOffset=2000 , 0 StorageInit ok = 28775 Raw SecureMode = 0 SecureIni
  15. I see both the images and the checksums there. Retry with glasses
  16. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system)
  17. Actually that is what I would do at first try.
  18. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system)
  19. Moved to Common issues / peer to peer technical support since not a valid bug report.
  20. Should work by applying 5V to pin2 and GND to pin6 Check pin diagram here: http://wiki.friendlyarm.com/wiki/index.php/NanoPi_M4V2 Did not try on a Nanopi board myself before but since the pins are the same as on OPi boards I assume it is just fine. You could solder or try to get your hands on some jumper wires and plug those in Edit: Yeah should work according to wiki:
  21. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system)
  22. All supported boards are listed here: https://www.armbian.com/download/ I think @TonyMac32 tinkered with the TB2 a while ago but not sure.