All Activity

This stream auto-updates     

  1. Past hour
  2. If it is Phantio MX10 it is most likely Allwinner H6 and not rk3328. You may first want to verify this.
  3. Dusted my MX10 and tried to boot focal desktop from, unfortunately doesn't boot.
  4. Definitely will be keeping an eye on it. For now I am looking at the NanoPI 2RS as a Router. Especially since there is OpenWRT build for it. I am happy with the wifi performance I am just not to happy with how long it takes netgear to patch problems... if ever.
  5. Today
  6. I guess they rebranded an armbian image which includes alternative drivers for xradio and added the temperature fix....
  7. Hard to tell without further information. What image are you using? armbianmonitor -u
  8. I was reading about hecking the filesystem / Seems the way is: touch /forcefsck But this action does not fix, so we need 'somewhere': How do i have to do it? Thanks. รวยเร็ว
  9. Hi all. I have a board nanopi neo air with armbian linux on it. We with my colleague try to setting up ffmpeg with cedrus264 for hardware accelerated capturing video from ov5640-like camera device. There is my armbianmonitor. There are my v4l2-ctl -d /dev/videox -D out: After some reconfiguration of dts, we can successfully capture video in low fps with ffmpeg -f v4l2 -framerate 25 -video_size 960x720 -i /dev/video1 output.mkv but with ffmpeg -f v4l2 -channel 0 -video_size 960x720 -i /dev/video1 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4 ffmpeg failed: Ffmpeg was buided from FFmpeg-Cedrus, also we try follow this and use this binaries - result haven't changed. After some inspecting sources of ffmpeg-cedrus we found that ffmpeg try to open /dev/cedar_dev device, which don't exists in our system. Ffmpeg fails on opening device. If we replace /dev/cedar_dev by /dev/video0, where is our cedrus driver, ffmpeg fails on ioctl IOCTL_GET_ENV_INFO. In source, it is 99 or 101 line. We check kernel config for configuration, provided by Sunxi-Cedrus and determine that cedrus was configured right. Also we have tried all described actions on official armbian buster image for nanopi neo air and we have got the same result. What we does wrong?
  10. I installed Orange Pi's version of Ubuntu Bionic server with kernel 5.34.27 mentioned in the tweet refered to by @gounthar above on a Orange Pi Zero LTS V1.5 board, and it has indeed fixed the temperature reporting problem. The onboard wifi is working flawlessly, too.
  11. I would like to confirm that the issue for me is solved by the switch to the last kernel build. 35 days without any issues: ~ $ uptime 13:50:11 up 35 days, 19:27, 1 user, load average: 0.07, 0.18, 0.20 Thanks again to @Igor!
  12. Hello guys, I have a NOVAsom M7+ board with a RTL8723bs module with Wi-Fi and Bluetooth integrated. The Wi-Fi works normally and without problems, however the Bluetooth isn't detected at all. When I try to open the Bluetooth Manager app gives me this error: "Connection to BlueZ failed. BlueZ daemon is not running. blueman-manager cannot continue. This probably means that there were no Bluetooth adapters detected or Bluetooth daemon was not started". I already searched the internet and found some people with problems related to this module and Bluetooth, does anyone know how to solve this? Best regards
  13. How about s905x, can you make it too? Sent from my SM-C9000 using Tapatalk
  14. Glad to hear that I tried running Quake2 on stock frequencies with Mali libraries, it worked but after I while I had issues from Mali kernel driver. It was long ago and also installation was not yet in a stable status. BTW, I'm interested in your clock latency adjustment, can you describe what you did and what problem it addressed? It is my feeling that there is still something not properly right that causes some boxes to be a bit unstable, so I'm looking for any experience that could increase general stability. Thank you!
  15. @balbes150 - are you aware of this one? (but maybe this is what you added):
  16. X3 mini (4gb, 32gb ram, S905x3) only see 2gb of ram... maybe it is fake...
  17. Finally good news! Today (2020-07-14) for ubuntu bionic becomes available mesa update, following packages: libegl-mesa0 libegl1-mesa libgbm1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglx-mesa0 mesa-va-drivers mesa-vdpau-drivers After that, xfce desktop on orangepi2e starts to work flawlessly with kernel 5.4.xx (in my case 5.4.51) again. Exact versions of packages: igor@orangepiplus2e:~/trash/mesa$ dpkg -l | grep 'mesa\|libgbm1' ii libegl-mesa0:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:armhf 20.0.8-0ubuntu1~18.04.1 armhf transitional dummy package ii libgbm1:armhf 20.0.8-0ubuntu1~18.04.1 armhf generic buffer management API -- runtime ii libgl1-mesa-dri:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:armhf 20.0.8-0ubuntu1~18.04.1 armhf transitional dummy package ii libglapi-mesa:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the GL API -- shared library ii libglx-mesa0:armhf 20.0.8-0ubuntu1~18.04.1 armhf free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 8.4.0-1 armhf Miscellaneous Mesa GL utilities ii mesa-va-drivers:armhf 20.0.8-0ubuntu1~18.04.1 armhf Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:armhf 20.0.8-0ubuntu1~18.04.1 armhf Mesa VDPAU video acceleration drivers
  18. I tried using apt to upgrade the system but the problem was still present. I tried downloading the latest release of focal from armbian and running this from a microsd card resolved the brunt of the issue. I notice the kernel is newer than the one apt gives and made a separate forum post regarding this.
  19. The latest image uses kernel sunxi64 5.4.45 but this doesn't install with apt on my older image, and there is no release for this new version available under .
  20. Yes, I did. My power circuit is quite complicated: battery backed SMPS PSU @ 12V, then SMPS converter (rated 3A) to 5V. Switched to other 12/5V converter/cable, same result. Will also try to replace SD card, but they are both Samsung class 10 32GB.
  21. Odd. You could utilize steamroller tactics and place the symlink into conf-enabled directly and see what happens when you restart apache. Maybe there is something wrong with the config file itselt and therefore it is not detected properly.
  22. @balbes150 i tried latest image (Armbian_20.07_Arm-64_focal_current_5.7.8.img). but the OS only see 2GB of ram (17xx mb of ram), my box has 4gb of ram.
  23. same with X3 Mini (4gb). armbian only see 1700mb of ram (Armbian_20.07_Arm-64_focal_current_5.7.8.img)
  24. Well actually it's still a good sign the system can boot up even though it hangs at very early stage. Yes could be a dying power adapter. To confirm, need to measure the voltage point I posted previously.
  1. Load more activity