Tony3

I found how to fix it! If your mesa drivers/chromium have been overwritten by an update, do the following: in rockchip-multimedia-ppu and panfork-mesa-ppu put a priority 1000 instead of 600 Using 1000 instead of 600 apparently forces a reinstallation of them. Then : sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia sudo apt update sudo apt full-upgrade Then reboot. You will then see again the possibility to login with ubuntu using Wayland Hope I did not forgot something.......but still may help for the ones having lost Wayland.

Ok I have now pin the packages, tried to deinstall ubuntu-desktop, but it does not deinstall! Not sure what to do now (to get the wayland option back).

Actually this is what my problem is. After following the instructions, I got kodi running and Wayland. Now after few days I realise that I am not running wayland anymore, and the kodi option (when logging in) has disappeared! How can I get Wayland again?

I did the "Orange Pi 5 Kodi ..." and Kodi working fine with a satellite TV PVR (low CPU usage, thus using hardware acceleration). However Chromium is sluggish, even by scrolling normal web pages with no video! I use the lasted "Armbian jammy" from the 23 January, and chromium comes already installed on it. I have not done anything else special for the chromium configuration, do I need something? Any idea what could be wrong?

Actually I managed to build my wireless module by only using the linx header files. It did not work initially, because I had forgotten to run "make scripts" in the "linux header" directory, after running that, my "_mcount" error disappeared. Thanks for your advices.

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.