Jump to content

Werner

Administrators
  • Posts

    4464
  • Joined

  • Last visited

Everything posted by Werner

  1. I assume WOL (wake on LAN) is not supported at this time.
  2. The software you are trying to install/update is userspace and therefor out of scope from Armbian. Support is only possible for software that Armbian ships.
  3. Depending on how to interpret things: - board does not start -> topic in wrong place and no logs via UART provided - board does start (indicated by mentioned dhcp lease aquired) connecting via SSH should be possible. If not line above. btw. RK is 1,5Mbaud
  4. 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) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  5. Still odd nevertheless. One a block device is assigned it should be consistent across those very basic commands, shouldn't it?
  6. If somebody finds time to bump sunxi-edge to 5.12 or 5.13-rc then we could probably retry.
  7. 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) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  8. Forums language is English. Use translator tool if necessary.
  9. If somebody is willing to provide a PR that makes necessary changes sure thing.
  10. The reason might be that the Allwinner H3 does not support SSE2 instructions.
  11. Imagine a new SBC is developed specifically designed for computing tasks and clustering but should also be available for a rather low price. Which features should it have or not have? What do you think? Is it even possible?
  12. 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) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  13. The vendor image works but has, like it often was the case, design flaws. For example you will notice that the board will run a constant load >1 for no reason.
  14. 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) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  15. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  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) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  17. Make sure Tx line isn't broken. Try setting verbosity to 7 in your /boot/armbianEnv.txt to get more info about what is going on until stuck.
  18. Moved to Common issues / peer to peer technical support
  19. Yeah and I think it was upstreamed. Could not make it to boot though so I did not further investigate:https://github.com/armbian/build/tree/push_ATF_H616
  20. Moved to Common issues / peer to peer technical support
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines