Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Past hour
  2. Ok thanks but the dtb files are in 2 folders: dtb dtb-3.10.108 Wich folder should i get the dtb? for every single file in one of the 2 folders i will copy in the root folder of the SD renaming it to "dtb.img" Is that correct? Thank you again
  3. If @martinayotte likes it, would you create a Pull-Request on Github?
  4. Okay, I gave it a try. First I tried to improve the Bill-of-Materials form Hijax. I tried to identify the SMT parts (added a column in the attached file and put some text into it what I have changed). Then I searched for the parts of the BOM here: LED and Resistor I have identified based on Hijax given size and jlcpcb categories. However, Multiplexer and such is way above my knowledge. There are only 9-10 parts to check in total, I have done the ground work. Can you help please?? If JLCPCB doesn't fit, but we have the parts list ready (checked and amended from you) we can try others like Bill_of_material_0rr.xlsx Edit: just thinking, would a Google doc be better to edit together?
  5. Today
  6. OK, Armbian_20.02.7_Cubox-i_bionic_current_5.4.28_desktop.7z downloaded and played a little with it on my quadcore cubox-i. It is working for me like as for igor. As logging is suppressed as much as possible let's try to increase it in a next step. To do this create in the boot directory a new directory named "extlinux" and copy the attached extlinux.conf file in. Boot the image and report the logging. This is a "WARNING: CPU: 0 PID: 1 at arch/arm/mm/dump.c:248 note_page+0x160/0x324 arm/mm: Found insecure W+X mapping at address 0xe0839000". I also get it since some time with recent kernels but was to lazy to track it down and it seem to do no harm. extlinux.conf
  7. Hello, I am getting following error when compilining KDIR=/usr/src/linux-source-4.19.57-meson64/ ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- ./ make: Entering directory '/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali' make ARCH=arm64 -C /usr/src/linux-source-4.19.57-meson64/ M=/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali modules make[1]: Entering directory '/usr/src/linux-source-4.19.57-meson64' CC [M] /root/mali/meson_gx_mali_450/driver/src/devicedrv/mali/linux/mali_osk_atomics.o /bin/sh: 1: scripts/basic/fixdep: Exec format error scripts/ recipe for target '/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali/linux/mali_osk_atomics.o' failed make[2]: *** [/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali/linux/mali_osk_atomics.o] Error 2 make[2]: *** Deleting file '/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali/linux/mali_osk_atomics.o' Makefile:1517: recipe for target '_module_/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali' failed make[1]: *** [_module_/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali] Error 2 make[1]: Leaving directory '/usr/src/linux-source-4.19.57-meson64' Makefile:191: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali' cp: cannot stat '/root/mali/meson_gx_mali_450/driver/src/devicedrv/mali//mali.ko': No such file or directory uname Linux lepotato 4.19.57-meson64 #5.90 SMP PREEMPT Sat Jul 6 15:54:33 CEST 2019 aarch64 GNU/Linux I am compiling it to enable GPU to be used with mpv.
  8. this is my u-boot version readed from file (grep -a --null-data U-Boot /dev/mmcblk0) U-Boot SPL 2019.10-armbian (Feb 17 2020 - 02:53:18 +0100) If it's not enough tomorrow I will connect BPi to HDMI.
  9. Jack953

    Orange pi 4

    Thank you, very usefull, I guess its safe to test, when doing nothing. But its a risk when both devices are on high load.
  10. Switch is not committed :
  11. For boards that doesn't have HDMI you need to use serial console to login. On this board you have two. 1. Via 3 pin connection 2. Via mUSB. Simply power the board via PC USB port and you will get a new serial console to which you connect with a Putty or similar terminal program. That's all.
  12. @balbes150 followed you in my first approach to run "linux" on an old amlogic 805 with only 512 ( 384... ) mega of ram and the following you in the project of "one armbian for different platforms" But this answer leaves me a bit puzzled. Nobody here is wasting time or wanting others waste time, but some form of explication of this arguments could be usefull
  13. yes...many ! :-(. I´m still waiting for progress and hoped to get news with this post it´s annoying :-(. regards arel
  14. @Anna Vahtera sorry my delay... First test was with 20m long CAT5 Cable. It was working without issues, so no need for me to measure the voltage. In real scenario I use a 15 meter cable.
  15. Hello, I have found an issue with the audio device on allwinner H2+/H3 boards. The internal audio DAC works just fine on Armbian Stretch, but on Armbian Buster the audio device appears as mono-only in pulseaudio. When trying to run 'speaker-test -c 2' the audio channels appear to be flipped? I figured this is an issue with the device tree? This seems to be a common issue: my post: This issue affects the Buster and Bionic builds. I have a few extra SD cards, so I can test stuff out or give you any required console outputs.
  16. Hi Igor, Thanks for the Reply. Is there any processor with openGL support and core support like imx8. Is there any porting can be done wrt other processor Please suggest
  17. Myy

    Mainline VPU

    Got it. It's this one :
  18. Great find - I also have some instability issues with my OrangePi PC2 (especially in load situations (like extracting an archive)). How can I check the current DRAM PLL value so I know if this fix would help me? Until now only reducing the clock speed seems to work. Thanks!
  19. Can you link me a guide or explain me some steps? I achieve to connect to a wifi hotspot with armbian-config but i need to configure it as AP for an router that as PEAP WPA2 security. For what I've tested this security is not supported out of the box for Linux... Thank you in advance for your patience
  20. I tested two of the boards I received a few days ago. There is a 1s gap between main power loss and batteries starting to give power. I still have a few different boards to try.
  21. I got the same problem with the same setup. In v. 5.4.28 is still this problem. So, we as new armbian user can only wait for a stable version or downgrade to 4.4?
  22. I get the same problem with Kernel 5.4.x on a NanoPi M4v2. I switched for tests to 4.4.x and there is working stable. Did your logs getting spammed with this too? I got this every 4s. Apr 6 14:47:33 nanopi brcm_patchram_plus_rk3399[1498]: writing Apr 6 14:47:33 nanopi brcm_patchram_plus_rk3399[1498]: 01 03 0c 00
  23. But again, what are the differences that you found ? (I was looking quickly at both GigaDevice and Winbond datasheets, and I didn't found any difference until now)
  24. @piter75 Maybe the mic need fix,I see the OrangePi_4_schematic_v1.3.pdf,I found MIC_IN1P not link to IN1P.It causes the recording to be abnormal. This is a dts overlay,I tested recording better,I am not sure it is correct(because orangepi4 include two mic,one from board,one from jack). mic-opi4.dts
  1. Load more activity