Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Today
  2. Unless someone else can confirm this behavior on another N2, you might just have a bad power supply. https://forum.armbian.com/forum/31-sd-card-and-psu-issues/ It may also be worth trying the HardKernel images and see if you can reproduce that fault there, to narrow down whether it's a fault with the image, or with your hardware. Without further information, there's not much here to go on.
  3. Building a Debian or Ubuntu image is relatively easy. But getting the boot sequence right is often time challenging. Often times there's little patches here and there to handle some "little thing" the hardware designers did, and if they didn't mainline whatever they did (which doesn't always happen), you're stuck with resolving changes by both the Linux kernel developers and the vendor's software team. This consumes a fair bit of maintainers' time, and is the primary reason it's not easy to just add one more board. If you can get a shell to the vendor's software image, and can't fi
  4. Guys, try to run your helios in whatever performance but always under 1.4GHz. I have mine set to performance and throttling from 400MHz to 1.4GHz. Uptime is 9 days now. Only two of the CPU cores can run above 1.4GHz (see these posts for reference) and that might be one of the cause of the crashes.
  5. My comment might be late to the party - if there was a possibility to add an optional display and a few user-configurable buttons to the Front Panel, that would be great. I know it would mess a bit with the airflow, but it could be used for system monitoring and few other specific use cases.
  6. Please read the FAQ entry: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first There are a couple of comments in that post that are relevant to your question. 1) balbes is no longer working on amlogic cpus, 2) the current state of the TV box code (espeucally for amlogic) is suitible for server use only, don't expect much graphical support to be working. Also in a comment just a few posts ago, balbes expressed his opinion that he doesn't work with proprietary binary closed source code (like the legacy mali drivers). The open source drivers are only beco
  7. hello dear Arox, hello dear lanefu, first of all: many many thanks for the answer and for the headsup. Arox: thank you Arox - youre right. Lanefu: i am not so familiar with MQTT - protocolls. But i guess youre right. We can do this with MQTT too. we could read the DHT-sensor on BananaPi and mqtt the results. But what if we do it - in other words we can read a sensor like a DHT22 or similar and mqtt the results - (sending the data to GPIO pins) So - we can read a the sensor (DHT22) and then we can MQTT the result t
  8. Dear balbes150 We all appreciate your effort about armbian and Librelec, But all linux projects are GPL licenced, GPL means everybody on earth can use or modify this software. Please stop naming this as theft, if you tried my Debian build linked by AC2N you probable saw that: I build this kernel from direct kernel source, not from your git branch. I build this image using fenix scrip like you, but none of fenix script developers called us thieves. I hope you can understand what I mean, Last word : I added a note on my topic on be-links fo
  9. I successfully run armbian, and I compiled Retroarch in the system, but after running it, I found that the video driver is missing. Can you help me? How should I install or compile the missing video driver
  10. I can confirm, I'm running with a 400MHz to 1.4GHz range; up since 9 days.
  11. @jock Great great work, as usual Jock !!!!
  12. Thanks for finding out the cause of the problem! I just updated all seven nodes of my clusterboard, only to have them not boot... It was probably time to clean them up, but it's still annoying, and affects more than just the clusterboard, but also the Pine64 A64 LTS. I thought I was having trouble with getting this to take, but I was probably being too imatient, and not waiting long enough for the microSD resize to complete... If I understand right, the patch would go in here - https://github.com/armbian/build/tree/master/patch/kernel - but I'm not sure which of the sunxi branches
  13. We are well aware that our support with tips and solutions can save you days, sometimes weeks and moths. But the problem is that we also have to invest time to recall, search, focus on the problem ... while you / public / users don't value this at all. Or in rare occasions. You think it's granted, but it's actually our family time/money that is going away for your/common gain. End users also doesn't support R&D at all, but you have a desire in top support, quick answers all the time, some even dare to demand and complain. Which is why we asks at least for a small compensation https://forum
  14. Lion Wang , Can BPI M5 run armbian with Odroid C4 image without any issue ? no dtb need to change ?
  15. 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)
  16. hi there - good day dear Werner, dear Arox, many thanks for the quick reply. I am very glad to hear from you. I have some Orange-Pi here and besides them also a Banana Pi. So - if i am able to get started with the MQTT - protocoll on one device then i surely will implement it on those systems too. I will work it out - more thoroughly Many thanks to you both - for encouraging me. Have a great day. PS - keep up the great work - it rocks!! i am a big big fan of 'Armbian!
  17. Moved to Common issues / peer to peer technical support
  18. Yesterday
  19. My C4 behaves better with latest u-boot. Its confusing, but @chewittgave me some tips to look into. Sadly time is the problem.
  20. Hi, I came across two similar TV boxes - "Evolveo H4 4k" and "Evolveo Q5 4k" - and found this great Armbian site! Thanks for your great work guys! I set my expectation low and tried with latest "Armbian_20.10_Arm-64_focal_current_5.9.0". The H4 seems to be an S905/p212 2GB/16GB (not sure whether w/ 1Gb lan) board and it boots here with selected: uboot-s905 and FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb (set in extlinux.conf) The Q5 seems to be an S905/p200 2GB/8GB board (lan w/ 1Gb) and it boots here with selected uboot-s905 and FDT /dtb/amlogic/meson-gxbb-
  21. Hey. I'm working on setting up octoprint on my opi zero +2(H5), aiming at running octodash on a small 3.5" spi waveshare clone display. So far I've got the display working fine, as in showing the console text, and also working in xorg. However, I have a bit of trouble with the touch part. I've combed through the forum and followed the guides I could find, and have a fairly good working DTS file, however, I can't seem to get pin number 11 to work. In the overlay files, it seems to be named PA1, but I couldn't get that to work, and there were a bit of oddities wit
  22. Thanks. I tried my luck also with OIBAF PPA but still no joy. All the best!
  23. I might try to bridge the external PSU ground attached to the HDMI external adapter ground to a HDMI ground pin wire and see if it helps. I even tried booting without any usb devices, from the same USB PSU divided in two for the HDMI power mod and the Orange PI psu itself sharing the same ground source from the eletric attached psu. Probably this VGA monitor is more sensible than others inputs.. for example I got a TV with vga input and works as it should.
  24. My NanoPi M4V2 is still throwing I2S errors to console. I for one would be interested in any of your notes on how the I2S clocking is set up in the DTB.
  25. Is anyone noticed that screen sometimes turns black for a second or two, at least on Gnome Shell Wayland session? With Dell UP3017 display (2560x1600) on Linux 5.10 I seen this issue frequently. After upgrade to 5.11 and changing screen resolution to 1920x1200 it's happens rarely, but still happens. Actually, I seen this issues even with ODROID C4 and N2+ (originally reported on Hardkernel forum). Logs: http://ix.io/2Wbc
  26. Try to detach and then attach Ethernet cable, and see if it helps. In my case - it does.
  27. 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)
  1. Load more activity