Hi,guys, may I ask for some help about how to use i2c bus in Manjaroarm of VIM3. I found there’s a file named “overlay.txt”, but I’v no idea about how to use it .
Hello
You can either add the gpio in the dts for your use case or you can just expose it from userspace.
You can follow a basic guide on how to expose rhe gpio in userspace
https://docs.khadas.com/linux/vim3/Gpio.html
If you can share more information on what exactly do you plan to do then someone can help you future on this topic.
Good luck.
Thanks very much for your help! Well, I test GPIO’s baic operation according to your manual above and I successfully pull and push GPIOs. But how did I do about ‘overlay.txt’ ,do I wite all that shell cmd to that txt file or there is another grammar or special key words?
Hi, I have another question that Wiringpi library doesn’t work well in out Manjaroarm. How did I do if I want to use I2c bus. Thank you.
I2C is well documented in arch linux wiki
https://wiki.archlinux.org/title/I2C
Follow the steps mentioned in the above link.
@Spikerguy Have you tested the firewall on Manajro. Does it have something similar to Ubuntu UFW? Problem with UFW seems to be a couple of the libraries for ARM are not ready or what ever is holding them up.
In the new image we do have a firewall gui application.
Have you tried that? It have worked fine in my test
Thank you for responding to my post about this.
No, I have not tried out Manjaro yet, don’t need a gui the CLI is fine and actually would be the best solution for what we are doing.
Does Manjaro have a headless version?
UPDATE:
Just found and downloaded the minimal image.
What else is needed to install on VIM4?
Vim4?
Need support in mainline linux kernel.
That is what I was afraid you would say about that.
why?
i can understand it if manjaro will provide one universal aarch64 image for all boards, but in fact its diff images diff kernels & bootloaders for diff boards
and whats a problem ?
PS: >Manjaro Kernels - Manjaro - nothing about mainline priority 
PSS: in main page >https://manjaro.org/ again nothing about manjaro is a mainline linux kernel distro
Not sure what you mean by the above message dear.
This documentation is for manjaro x86_64
It is not about manjaro project.
It is about the concept of rolling release which keeps updating app the pkgs.
Can you compile vim4 bsp kernel with gcc version 12?
If yes then I can maintain a custom kernel for vim4 
why not try
If yes then I can maintain a custom kernel for vim4
cool i think all will be happy
PS: if need some assistance please notify us
PSS: some extra ideas
we have build deb packages for vim4 dl.khadas.com - Index of /repos/vim4/pool/main/l/linux-5.4.125/
- may be just prepare some convert script like a deb to manjaro packages special for kernel and uboot
No we try not to put time on hacks.
Ok will give it a try.
Thanks
Cause I know it will fail
mm/vmscan.c: In function ‘get_scan_count’:
mm/vmscan.c:2529:17: error: ‘anon_prio’ undeclared (first use in this function); did you mean ‘bio_prio’?
2529 | anon_prio = anon_prio * anon / (anon + file + 1);
| ^~~~~~~~~
| bio_prio
mm/vmscan.c:2529:17: note: each undeclared identifier is reported only once for each function it appears in
mm/vmscan.c:2529:41: error: ‘anon’ undeclared (first use in this function)
2529 | anon_prio = anon_prio * anon / (anon + file + 1);
| ^~~~
mm/vmscan.c:2529:56: error: ‘file’ undeclared (first use in this function)
2529 | anon_prio = anon_prio * anon / (anon + file + 1);
| ^~~~
mm/vmscan.c:2530:17: error: ‘file_prio’ undeclared (first use in this function); did you mean ‘file_path’?
2530 | file_prio = file_prio * file / (anon + file + 1);
| ^~~~~~~~~
| file_path
make[1]: *** [scripts/Makefile.build:284: mm/vmscan.o] Error 1
make: *** [Makefile:1868: mm] Error 2
make: *** Waiting for unfinished jobs....
arch/arm64/kernel/cpuinfo.c: In function ‘c_show’:
arch/arm64/kernel/cpuinfo.c:195:45: error: ‘machine_model’ undeclared (first use in this function)
195 | seq_printf(m, "Hardware\t: %s\n\n", machine_model);
| ^~~~~~~~~~~~~
arch/arm64/kernel/cpuinfo.c:195:45: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [scripts/Makefile.build:284: arch/arm64/kernel/cpuinfo.o] Error 1
make[1]: *** [scripts/Makefile.build:553: arch/arm64/kernel] Error 2
make[1]: *** Waiting for unfinished jobs....
kernel/extable.c: In function ‘sort_main_extable’:
kernel/extable.c:37:59: error: comparison between two arrays [-Werror=array-compare]
37 | if (main_extable_sort_needed && __stop___ex_table > __start___ex_table) {
| ^
kernel/extable.c:37:59: note: use ‘&__stop___ex_table[0] > &__start___ex_table[0]’ to compare the addresses
cc1: all warnings being treated as errors
make[1]: *** [scripts/Makefile.build:284: kernel/extable.o] Error 1
make[1]: *** Waiting for unfinished jobs....
CC kernel/time/vsyscall.o
CC kernel/sched/membarrier.o
CC kernel/time/timekeeping_debug.o
CC kernel/sched/isolation.o
AR kernel/time/built-in.a
AR kernel/sched/built-in.a
make: *** [Makefile:1868: kernel] Error 2
==> ERROR: A failure occurred in build().
Failed with multiple error within 2 mins.
oky need prepare some patches for gcc v12, i think its easy to search in google
another question why need to use gcc v12?
You can do that and fix the kernel source of vim4 on 5.4.125 and let me know then i can try to compile it again.
I hope you know arch and manjaro are rolling release and all the packages keep updating you cannot use old pkgs.
What is the point in doing that, its way too time consuming to even keep up with kernel / OS upgrades that require so much time and effort to get running. I am looking for usable and stable, we are just wasting so much time trying to fix all the little problems and then test it again.
But manjaro is defined to be a rolling os. It’s not meant to be stable, it remains bleeding edge always
Hi，my friends，may I ask you for a help. I test for manjaro arm of vim3 with version of minial but I found that none of 22.xx version could launch from SDcard. I burning image download from official link using etcher tool when I test. Version of 20.xx works well but size of swap is small，I try the newer version and expire for more sway.