Search the Community

I finally found an official source code on the download page of OrangePI that has a version of wiring pi with support for the Orange PI 5 - unfortunately that code is not on the github of orangepi yet. What would be the best way to get this code and the gpio tool into armbian? Build a PPA and package for that one? I don't mind forking their repo and adding the mods but I'm not familiar with generating debian packages.

I know this driver should be part of the recent kernel releases (and definitely avail for 5.10) but I am not sure how/why/where this driver would be in the armbian release. I also did install the firmware files but I don't see the module in the /usr/lib/module section. Any suggestions to build or enable this driver? Thanks

I have created a micro desktop case. It's an open design that is still in the creation phase. The shell is 3d printed, the sides are acrylic, and the opi5 mount panel can be 3d printed or made from acrylic. I'm looking for feedback with design suggestions/needs. This is the first real opi5 micro tower design currently for OPI5. My cad drawing of the OPI5 mainboard is 99.9% accurate, so if someone wants to use that as a footprint for other projects by all means. https://github.com/berin-aquaquad/orange-pi-5 I am using DesignSpark Mechanical a free cad software that is on par with Fusion360. The shell has been designed as a split body so smaller 3d printers can create it. Again, this is a work in progress, and nothing is set in stone. Planned design additions for consideration: Headphone jack front or back. USB on front. Stats LCD on front. 3D printed power button to press power button on OPI5 motherboard. GPIO header for external access, "custom design or standard web link to example, I need feedback ". RTC battery holder to make use of the onboard RTC. RGB Micro Desktop case LIGHTING options?

I'm really struggling to get chromium to work correctly with hardware acceleration. 1) I have custom kernel image from master branch last week. Which maybe could cause some issues? 2) I added the two repos (panfork and mesa) sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia 3) I've ran all the updates 4) I installed ubuntu desktop to enable Wayland which is working nicely 5) I've added the HDMI audio output 6) My default chromium configuration does already have the egl enabled. When I start Chromium, I get the following errors 39610:39643:0125/091804.694008:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal /desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser” [39610:39643:0125/091804.694207:ERROR:select_file_dialog_linux_portal.cc(242)] Failed to read portal version property libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [39655:39655:0125/091804.826811:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [39655:39655:0125/091804.829891:ERROR:gl_display.cc(508)] EGL Driver message (Error) eglQueryDeviceAttribEXT: eglQueryDeviceAttribEXT [39655:39655:0125/091804.830069:ERROR:gl_angle_util_vulkan.cc(189)] Failed to retrieve vkGetInstanceProcAddr [39655:39655:0125/091804.830187:ERROR:vulkan_instance.cc(91)] Failed to get vkGetInstanceProcAddr pointer from ANGLE. [39655:39655:0125/091807.500915:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [39655:39655:0125/091809.004733:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [39655:39655:0125/091829.513030:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! I cannot figure out the "Passthrough" error. Sounds like egl should be enabled... What am I missing? libva error - this is usually because there is no LIB_VA - but from what I've seen there is no lib va available for Orange PI 5. Correct or am I missing something?

Kodi on Orange Pi 5 with GPU Hardware Acceleration and HDMI Audio Huge thanks to user @roykon the Armbian forums for the directions on this in their various forum posts and Armbian forum user @amazingfate for maintaining the PPAs and software builds required for GPU acceleration. I have simply listed below, for the reference of others, the minimum Steps used to get Kodi running with GPU hardware acceleration (for x264/x265 decode) plus HDR auto switching and with HDMI Audio output*. (I am using the Orange Pi 5 with a Samsung 4K TV) *No instructions added yet for enabling HDMI passthrough. ** No instructions added yet for enabling HDMI CEC. Step 1 (SD card image creation) Download the image below, uncompress it and write it to an SD card. https://github.com/armbian/build/releases/download/23.02.0-trunk.0173/Armbian_23.02.0-trunk.0173_Orangepi5_jammy_legacy_5.10.110_xfce_desktop.img.xz#orangepi5 Step 2 (First boot) Boot the SD card image and complete the on-screen prompts for user & password creation. Note down the IP address of the Orange Pi 5, you will need it in step 3. Step 3 (SSH into the Orange Pi 5) SSH to the IP address of your Orange Pi 5 and login using the user account and password you set up in Step 2. Step 4 (Enable PPAs and install other elements required for GPU hardware acceleration) At the command line, enter the following commands (highlighted in Blue): sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia sudo apt update sudo apt full-upgrade sudo apt install ubuntu-desktop kodi When prompted on-screen if you wish to use gdm or lightdm, select gdm. Step 5 (Configuration file additions & changes) At the command line, enter the following commands (highlighted in Blue): sudo mv /usr/share/xsessions/kodi.desktop /usr/share/wayland-sessions/kodi-wayland.desktop sudo nano /etc/udev/rules.d/11-rockchip-multimedia.rules KERNEL=="mpp_service", MODE="0660", GROUP="video" KERNEL=="rga", MODE="0660", GROUP="video" KERNEL=="system-dma32", MODE="0666", GROUP="video" KERNEL=="system-uncached-dma32", MODE="0666", GROUP="video" RUN+="/usr/bin/chmod a+rw /dev/dma_heap" sudo nano /etc/gdm3/custom.conf Add the line below and save the file. WaylandEnable=true sudo nano /usr/share/alsa/cards/HDMI-OUT.conf Add all of the content below and save the file. # configuration for HDMI connection which just expose the # audio out device <confdir:pcm/hdmi.conf> HDMI-OUT.pcm.hdmi.0 { @args [ CARD DEVICE CTLINDEX AES0 AES1 AES2 AES3 ] @args.CARD { type string } @args.DEVICE { type integer } @args.CTLINDEX { type integer } @args.AES0 { type integer } @args.AES1 { type integer } @args.AES2 { type integer } @args.AES3 { type integer } type hw card $CARD } sudo nano /usr/share/alsa/cards/aliases.conf Add the line below and save the file. rockchip-hdmi0 cards.HDMI-OUT Step 6 (Reboot and Start Kodi) At the command line, enter the following commands (highlighted in Blue): sudo reboot At the login screen, select “kodi” in the bottom right hand corner menu. Now login using your username and password. Kodi should now load. Step 7 (Adjust Kodi settings) From within Kodi goto Settings -> Player -> Videos goto the bottom left corner of the screen and change it from Standard to Expert. From within Kodi goto Settings -> Player -> Videos, Playback, and change Adjust display refresh rate to “On start/stop” From within Kodi goto Settings -> Player -> Videos, Processing, enable "Allow using DRM PRIME decoder" and "Allow hardware acceleration with DRM PRIME". And set "PRIME Render Method" to "Direct To Plane" From within Kodi goto Settings -> System -> Display, and change the resolution to 1920x1080p From within Kodi goto Settings -> System -> Audio, and change the Audio output device to “Built in Audio Digital Stereo (HDMI),HDMI / DisplayPort (PULSEAUDIO)” Step 8 (Test video playback and check that GPU acceleration & HDMI Audio are working) During video playback, press ‘o’ on the keyboard, and it should show Video decoder: ff-hevc_rkmpp-drm_prime (HW) During video playback, if you have a Samsung TV, press the “Info” button on your Samsung TV remote to show the current playback resolution, frame rate and whether or not HDR is in use. (Depending on the video content being played) Thank you again to Armbian forum users @royk and @amazingfate

Hi there, Just got Orange Pi 5 8GB and have no idea where to begin. I have a microSD card available, but no writer. I had the idea to boot from USB thumbstick and then write the SD card using the port on the Orange Pi 5, then I can boot from SD card. Is this possible? What image and method do I need to follow in order to boot from a simple 32GB USB Sandisk thumbstick? Thank you!

I saw that you now have a stable release of armbian for opi5. I installed Armbian 23.02.0-trunk.0112 Bullseye a week ago. Now I'm wondering if it is possible to switch back to the stable version without reinstalling the system. The OPI is now running in production and I have several containers running on it. This is what I tried -> armbian-config -> system -> nightly after that back to stable -> armbian-config -> system -> stable ->armbian-config -> system -> other -> linux-image-legacy-rockchip-rk3588=22.11.4 But after login I always see: Welcome to Armbian 23.02.0-trunk.0112 Bullseye with Linux 5.10.110-rockchip-rk3588 No end-user support: work in progress Is something bad about this? Do I receive updates with this settings? Thank you, Nico

I did a bit of reading - to prevent ubuntu packages to update the rockchip optimized packages, you need to pin the packages. There is a simple way to do that. 1. Create a file called rockchip-multimedia-ppu in /etc/apt/preferences.d with Package: * Pin: release o=LP-PPA-liujianfeng1994-rockchip-multimedia Pin-Priority: 600 2. Create a file called panfork-mesa-ppu in /etc/apt/preferences.d with Package: * Pin: release o=LP-PPA-liujianfeng1994-liujianfeng1994-panfork-mesa Pin-Priority: 600 You can verify that the apt configuration is working correctly with sudo apt policy chromium-browser which should return chromium-browser: Installed: 1:105.0.5195.125-0ubuntu1~jammy~rkmpp20221209 Candidate: 1:107.0.5304.62-0ubuntu1~ppa1~22.04.1 Version table: 1:107.0.5304.62-0ubuntu1~ppa1~22.04.1 500 500 http://apt.armbian.com jammy/jammy-desktop arm64 Packages 500 http://ppa.launchpadcontent.net/saiarcot895/chromium-beta/ubuntu jammy/main arm64 Packages *** 1:105.0.5195.125-0ubuntu1~jammy~rkmpp20221209 400 400 https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy/main arm64 Packages 100 /var/lib/dpkg/status 1:85.0.4183.83-0ubuntu2 500 500 http://ports.ubuntu.com jammy/universe arm64 Packages

My experience so far: 1. Booting up (Jammy/Bullseye) from SD, HDMI out to 1440p display cuts off text at the bottom. It affects installation and later use. I need to press ENTER several times to all questions until text moves up in the buffer and becomes visible, and then blindly type the answer to proceed to the next step, then several ENTERs to scroll again, and so on. Looking at fbset and stty output: me@opi:~$ fbset -i mode "2560x1440" geometry 2560 1440 2560 1440 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : rockchipdrmfb Address : 0 Size : 14745600 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 1 YPanStep : 1 YWrapStep : 0 LineLength : 10240 Accelerator : No me@opi:~$ stty size 28 100 After installation, I can set proper console columns and rows corresponding to the font size: me@opi:~$ stty rows 67 cols 240 And to make it persist on boot: /etc/default/console-setup SCREEN_HEIGHT="67" SCREEN_WIDTH="240" 2. X server resolution only goes up to 1920x1080 on the same 2560x1440 display. 3. After switching monitor inputs and going back to OPi5, X server resets the resolution from 1920x1080 to 720x576. 4. In 1920x1080 everything looks abnormally scaled and huge. Decreasing DPI below the "default" 96 in Xfce helps a little but it still doesn't look right. 5. Finally, there are file conflicts among packages: firmware-misc-nonfree vs armbian-firmware and armbian-firmware-full. This was reported back in 2019 but not addressed. https://github.com/armbian/build/issues/1359

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.

Has anyone tried GPIO access on the latest armbian? I noticed that the custom wiringPi https://github.com/orangepi-xunlong/wiringOP.git doesn't compile on armbian. It is missing GPIO constants.

How do I get DVB drivers to work. I have a Technotrend TT Connect S2-3650-CI. All DVB drivers are missing

Orange Pi 5 is a new board using RK3588S. I think it would be really nice to support it http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-5.html

I found this amazing page https://linux-sunxi.org/Sunxi-Cedrus#VLC that explains alot on VLC and hardware accelleration but I cannot clearly figure out if my playback is using hardware acceleration. I did follow all the steps to optimize chromium with the ppu sources - chromium doesn't work well yet for me - so not sure if that install worked as expected. My playback of h264 in VLC is super smooth but I have around 20-35% cpu usage (1080p videos) - I know h264 is more demanding than AV1 but someone reported AV1 with 15% CPU usage and 4k. Is there anything I can do to make sure the hardware acceleration is working (aka the VA-API is used)?

I'm trying to setup LIRC on my OPI5 but I can't find any details on how that would be possible. I checked the kernel configuration and I cannot see any references to LIRC either. The module list has nothing obvious - is this feature completely disabled? Any suggested alternatives?

I originally posted this on reddit after seeing a lot of posts trying to use a SATA M.2 SSD and saying it wouldn't boot with replies telling them to go buy a NVME M.2 SSD which isn't necessary when the board does support SATA M.2 with flashing the correct bootloader. This guide has 3 different sections, 1 being booting with Orange pi OS and 2 being with Armbian OS Orange Pi OS Instructions Download Orange Pi OS Ubuntu or Debian from their website http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-5.html unzip the 7z file to get the .img file and flash it to your sd card with your preferred flasher i.e balenaetcher. Once flashed put it into orange pi 5 and boot from sd card first once booted, the rest will be done in a terminal. go ahead and do your usual update sudo apt update sudo apt upgrade -y 3. then make sure to wipe your SPI of any previous bootloader (give it time to complete, you'll know it's done when you get your cursor back in terminal) sudo dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=1 4. Write sata bootloader to SPI sudo dd if=/usr/share/orangepi5/rkspi_loader_sata.img of=/dev/mtdblock0 && sudo sync 5. Edit boot file on sd card to recognize sata by adding overlays line to the bottom, save then reboot sudo nano /boot/orangepiEnv.txt overlays=ssd-sata sudo reboot 6. On reboot you will still boot into SD card but now you should see "sda" (your sata SSD) show up on your list of devices when typing: lsblk 7. Put the same Orange Pi OS image you used in step 1 in any directory on your orange pi making sure it is unzipped and is in .img format. I just used the web browser in orange pi os to redownload from the website which for me put it in directory /home/orangepi/Downloads 8. Flash your downloaded .img to your sata ssd with this command (substitute with your directory to .img) sudo dd bs=1M if=/path/your/orangepi.img of=/dev/sda status=progress && sudo sync 9. Mount your ssd so you can edit the ssd’s boot file to support sata and reboot sudo mount /dev/sda1 /mnt/ sudo nano /mnt/boot/orangepiEnv.txt overlays=ssd-sata sudo umount /mnt/ && sudo sync sudo poweroff 10. Remove SDcard, turn on orange pi and it should boot orange pi OS from your M.2 sata ssd now Armbian OS Instructions Relatively same instructions with different file names write armbian .img file to your sd card with balenaetcher, I chose to use the more up to date imags from their github here https://github.com/armbian/build/releases/ make sure to unzip boot armbian from sd card, wipe spi sudo dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=1 3 Download sata spi bootloader from orange github, place it on your sd card (mine is in downloads directory) and write to spi https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/packages/bsp/rk3588/usr/share/orangepi5/rkspi_loader_sata.img sudo dd if=/home/pi/Downloads/rkspi_loader_sata.img of=/dev/mtdblock0 status=progress && sudo sync 4. Edit boot file to recognize sata then reboot sudo nano /boot/armbianEnv.txt overlays=opi5-sata sudo reboot 5. Once rebooted you can check sda shows up with command: lsblk 6. download the same armbian.img you used for step 1 to your orange pi making sure it's unzipped in .img format, then flash it to your ssd sudo dd bs=1M if=/path/your/armbian.img of=/dev/sda status=progress && sudo sync 7. Mount /boot/ of ssd so you can edit the ssd’s boot file to support sata and reboot sudo mount /dev/sda1 /mnt/ sudo nano /mnt/boot/armbianEnv.txt overlays=opi5-sata sudo umount /mnt/ && sudo sync sudo poweroff 8. Remove SDcard and start SBC, resize filesystem to use all available space sudo systemctl enable armbian-resize-filesystem

i was not able to build RTL8821CU driver, keep getting the following error : /usr/bin/aarch64-linux-gnu-ld: drivers/net/wireless/rtl8811cu/core/crypto/aes-internal-enc.o: in function `aes_encrypt': aes-internal-enc.c:(.text+0x74): multiple definition of `aes_encrypt'; lib/crypto/aes.o:(.text+0x7c4): first defined here make: *** [Makefile:1286: vmlinux] Error 1 There seems to be a duplicate implementation of aes_encrypt function between rtl8811cu source code and linux_rockchip64 kernel source code which blocking the armbian build. any suggestion how to fix this ?

I am attempting to install the file Armbian_23.02.0-trunk.0112_Orangepi5_jammy_legacy_5.10.110_cinnamon_desktop.img from https://www.armbian.com/orangepi-5/ but the installation hangs at the point where the root password should be entered. The same happens with the file Armbian_23.02.0-trunk.0112_Orangepi5_jammy_legacy_5.10.110_minimal.img. If i use the file Armbian_22.11.3_Orangepi5_jammy_legacy_5.10.110_cinnamon_desktop.img from the Github archive the installation completes. I have tried to raise a bug but the only solution for not booting are hardware and the installation has not progressed far enough to enter any commands. Any assistance welcomed.

Expected Behavior: I am able to enter sleep mode, either graphically or using systemctl suspend, and then wake from sleep mode by typing on the keyboard or pressing the power button Current Behavior: The system appears to enter sleep fine, but once in sleep pressing the power button or pressing buttons on the keyboard seems to do nothing (pressing keys on my keyboard causes it to light up, however my mouse does not light up). The display remains blank and the green led does not blink. I have to do a forced shutdown by holding the power button or unplugging the power supply. Note: the behavior is the same no matter if I suspend from a desktop session or a text console. uname -a Linux orangepi5 5.10.110-rockchip-rk3588 #trunk SMP Thu Jan 5 13:38:53 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

I was trying to install armbian on an ssd on my orange pi5, and when I ran the armbian-config program I saw that the firmware was frozen. I chose to unfreeze it, but I think should not have done that. Can I reinstall the frozen firmware packages and then hold those packages again? If so, how? Thanks.

Not sure if the rolling release includes the UART dtb yet, but when I build my own image (jammy xfce kernel 5.10.110) I don't have the UART dtbs in /boot/dtb/rockchip/overlay/ . As a result, I couldn't add uart0-m2 to /boot/armbianEnv.txt and get /dev/ttyS0 when I was following the official user manual to enable UART. After some researching I managed to solve this by copying the dtb file from orange pi's official ubuntu image to /boot/overlay-user and enable UART with user_overlays=rk3588-uart0-m2 in armbianEnv.txt . Rebooted and it works. However, I suppose it would be better to include the dts files in kernel patches? I'm posting this because I don't know what's the best practice for this.

The OPI5 has an onboard RTC. On the back of the board near the RTC chip there are two pcb "test points". One says RTC1, the other says GRD1, I would assume a CR2032 could be connected to those points to maintain RTC function. I don't dare do anything till I get a solid answer. Can anyone give me any feedback as to options.

Hello, I'm planning on running a k3s cluster with Rook storage with a few of the Orange Pi 5 that I got. A prerequisite for rook however is RBD module. I've been able to recompile the kernel including RBD support, however I've been unable to get the device to boot from the new kernel. Rebooting after kernel has been built and installed still reports Linux 5.10.110-rockchip-rk3588. Any help would be appreciated. I've since wiped the boxes clean and have a fresh install booting from SSD with the OS installed on the NVMe attached so I will be able to provide any information required. Thanks!

In the original PR for Orange PI 5 I recall someone mentioned that the Jammy had somekind of glitch with USB on the OPI5 but is that still the case? From the threads here, it looks like the distribution has many patches and fixes. Is Bullseye the recommended distribution?

I want to install the usb wifi/bluetooth card drivers but I keep getting an error during compilation. What to do? below code: DKMS make.log for rtl8812au-5.13.6 for kernel 5.10.110-rockchip-rk3588 (aarch64) Tue Jan 10 08:48:19 PM CET 2023 make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/5.10.110-rockchip-rk3588/build M=/var/lib/dkms/rtl8812au/5.13.6/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_debug.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_io.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ioctl_query.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ioctl_set.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ieee80211.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mlme_ext.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mi.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_wlan_util.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_vht.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_pwrctrl.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_chplan.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/monitor/rtw_radiotap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_recv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sta_mgt.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/wds/rtw_wds.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh_pathtbl.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/mesh/rtw_mesh_hwmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_xmit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_p2p.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rson.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_tdls.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_br_ext.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_iol.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_sreset.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_btcoex.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_beamforming.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_odm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm_fsm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_ft.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_wnm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_mbo.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_rm_util.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/efuse/rtw_efuse.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_roch.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-internal.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-internal-enc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-gcm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-ccm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-omac1.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/ccmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/gcmp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-siv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/aes-ctr.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256-internal.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/sha256-prf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/crypto/rtw_crypto_wrap.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/core/rtw_swcrypto.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/usb_intf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/usb_ops_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/xmit_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/mlme_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/recv_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/ioctl_cfg80211.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_cfgvendor.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/wifi_regd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_android.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_proc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/nlrtw.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/os_dep/linux/rtw_rhashtable.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_intf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_com.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_com_phycfg.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_phy.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_dm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_dm_acs.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_btcoex_wifionly.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_btcoex.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_mp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_mcc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/hal_hci/hal_usb.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/led/hal_led.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/led/hal_usb_led.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/HalPwrSeqCmd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/Hal8812PwrSeq.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/Hal8821APwrSeq.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_xmit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_sreset.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_hal_init.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_phycfg.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_rf6052.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_dm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_rxdesc.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/rtl8812a_cmd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/usb_halinit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/rtl8812au_led.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/rtl8812au_xmit.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/rtl8812au_recv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/usb/usb_ops_linux.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/efuse/rtl8812a/HalEfuseMask8812A_USB.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/rtl8812a/hal8812a_fw.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_debug.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_antdiv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_soml.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_smt_ant.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_antdect.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_interface.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_phystatus.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_hwconfig.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_dig.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_pathdiv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_rainfo.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_dynamictxpower.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_adaptivity.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_cfotracking.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_noisemonitor.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_beamforming.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_direct_bf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_dfs.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/halcomtxbf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/haltxbfinterface.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/phydm_hal_txbf_api.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_adc_sampling.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_ccx.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_psd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_primary_cca.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_cck_pd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_rssi_monitor.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_auto_dbg.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_math_lib.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_api.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_pow_train.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_lna_sat.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_pmac_tx_setting.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_mp.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/phydm_cck_rx_pathdiv.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_debug.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halphyrf_ce.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_powertracking_ce.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_powertracking.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_kfree.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/halrf_psd.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/halhwimg8812a_mac.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/halhwimg8812a_bb.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/halhwimg8812a_rf.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/halrf/rtl8812a/halrf_8812a_ce.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/phydm_regconfig8812a.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/rtl8812a/phydm_rtl8812a.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/hal/phydm/txbf/haltxbfjaguar.o CC [M] /var/lib/dkms/rtl8812au/5.13.6/build/platform/platform_ops.o LD [M] /var/lib/dkms/rtl8812au/5.13.6/build/8812au.o MODPOST /var/lib/dkms/rtl8812au/5.13.6/build/Module.symvers ERROR: modpost: module 8812au uses symbol kernel_write from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. ERROR: modpost: module 8812au uses symbol kernel_read from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. ERROR: modpost: module 8812au uses symbol filp_open from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it. make[2]: *** [scripts/Makefile.modpost:169: /var/lib/dkms/rtl8812au/5.13.6/build/Module.symvers] Error 1 make[2]: *** Deleting file '/var/lib/dkms/rtl8812au/5.13.6/build/Module.symvers' make[1]: *** [Makefile:1822: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' make: *** [Makefile:2504: modules] Error 2