Tony3

I feel stupid now. I think the SD card was not inserted properly! (when there is no SD card, you see an "Orange PI screen")

I received my new orange pi 5 plus. I installed the official Orange PI 5 Plus Ubuntu on a SD card and it worked great. Then I installed the "Armbian_23.8.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome_desktop" on SD card (Yes I took the image from the page with the "archive for orange Pi 5 plus"), and it get stuck on a screen displaying "Orange PI" (I do not see any armbian logo) , and nothing else happens (the blue light on the board does not blink). Why is that? How can I see what is happening? I installed in the past Armbian on an Orange Pi 5 with no issue, so I am really wondering what is going on there. Your view/ideas will be appreciated, thanks in advance,

I will receive soon a Orange Pi 5 Plus. I have setup completely an Orange PI5 with Armbian. I had to recompile kernel, compile drivers ...... it took some time. If I run the Orange PI5 plus with the same SD card as the Orange Pi 5, would it work? If not, is there an easy thing to do to make it work? I think there is a device tree file hardware specific , but is it read when compiling the kernel or dynamically? I am asking because processors are very similar, and it would make my life easier! Your view will be appreciated. Thanks.

Ok, good then

Just wondering, does the GPU acceleration works?

And if not in kernel, simply compile one as a module

I extracted a wifi module from an old skybox that I found in the street on the pavement, compiled the ath6 driver, and it works great! (ok not really out of the box......only out of a sky box!)

May I know why using suspend? It creates so many issues when you have devices attached.......better to boot!

I am after compiling a module for a wireless card. I got plenty of errors, thus decided to go to the basis and test the creation of a "hello" module. I am using the image: Armbian_22.11.4_Orangepi5_jammy_legacy_5.10.110_xfce_desktop.img vi hello.c ------------------------------------------------- #include <linux/init.h> #include <linux/module.h> static int hello_init(void) { printk("Hello Orange Pi -- init\n"); return 0; } static void hello_exit(void) { printk("Hello Orange Pi -- exit\n"); return; } module_init(hello_init); module_exit(hello_exit); MODULE_LICENSE("GPL"); ------------------------------------------ orangepi@orangepi:~$ vim Makefile ifneq ($(KERNELRELEASE),) obj-m:=hello.o else KDIR :=/lib/modules/$(shell uname -r)/build PWD :=$(shell pwd) all: make -C $(KDIR) M=$(PWD) modules clean: rm -f *.ko *.o *.mod.o *.mod *.symvers *.cmd *.mod.c *.order endif ------------------------------------------------ Then try to compile the module : make -C /lib/modules/$(uname -r)/build M=$(pwd) modules Running that command the first time after a fresh install of the jammy image, I realised that the directory /usr/src/linux-headers-5.10.110-rockchip-rk3588//scripts/mod was missing the modpost program. So I created it with the command: sudo make M=scripts/mod Then I run again make -C /lib/modules/$(uname -r)/build M=$(pwd) modules and got the log -------------------------------- make: Entering directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' arch/arm64/Makefile:44: Detected assembler with broken .inst; disassembly will be unreliable CC [M] /home/eric/installed/TestCompileModule/hello.o MODPOST /home/eric/installed/TestCompileModule/Module.symvers ERROR: modpost: "_mcount" [/home/eric/installed/TestCompileModule/hello.ko] undefined! make[1]: *** [scripts/Makefile.modpost:169: /home/eric/installed/TestCompileModule/Module.symvers] Error 1 make[1]: *** Deleting file '/home/eric/installed/TestCompileModule/Module.symvers' make: *** [Makefile:1822: modules] Error 2 make: Leaving directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' ------------------------------------ There are few errors in it: - "assembler with broken .inst; disassembly will be unreliable", is this important? - "ERROR: modpost: "_mcount"", This seems blocking as there is no .ko generated Any idea about what I am missing? Thank you.