Search the Community

Hello, I'm having issues with my Orange Pi 4 LTS. I cannot get any HDMI output at the moment. Neither with the Debian flashed on the eMMC, or with Armbian running of the SD card. In both cases I can SSH into the Orange and run commands normally. The HDMI worked just a day before, but in the meantime I was flashing different systems and it stopped working. I tried different monitors and cables. Any ideas what can I do?

I've compiled mainline kernel 6.6 which runs well on my OrangePi/RK3399. The only problem left is getting H.264 decoding working. Unfortunately, when I query /dev/video1 which is the node created by the hantro-vpu driver, only MPEG2 and VP8 are shown as supported codecs for decoding. No H.264, even though I've read many places that the mainline hantro driver supports H.264. Has anyone else had this problem? Is there something else I need to do to get this working?

I've noticed that some system images will start the OrangePi with 4:2:2 output on HDMI instead of 4:4:4. This causes artifacts, especially when there's white text on a red background. What's the interface or method to change this? Does this have to be done via U-Boot or can it be done in userspace?

Hi all, reporting a regression in new Armbian 24.2.1 kernel version. New kernel is causing Orange Pi 4 LPS not to boot most of the time, when it boots, then there is no network. Kernel hangs with oops errors on the screen, and all debugging stuff. Sorry that I did not caught any of them on my phone, but it would have been incomplete anyway. How to reproduce: Install any 24.2.1 based system on Orange Pi 4 LTS Upon first boot, you will have issues. No Ethernet network. Second boot will most likely not succeed no matter what you do and system will brick permanently, by not booting at all (no video output), or booting and then showing kernel crash. I've tested: Armbian_24.2.1_Orangepi4-lts_jammy_current_6.6.16_xfce_desktop.img.xz (system booted into desktop only once, never managed to do it again. No network in first boot) Armbian_24.2.1_Orangepi4-lts_jammy_current_6.6.16.img.xz (kernel crash in terminal on second boot, no network on first boot) Armbian_23.8.1_Orangepi4-lts_bookworm_current_6.1.50.img.xz - here I installed older image, all was good, network good, reboots good, so I upgraded all packages, upon restart everything was broken again) Armbian_23.8.1_Orangepi4-lts_bookworm_current_6.1.50.img.xz - formatted the card again, got it working again, I went to armbian config tool and marked Armbian kernel packages to freeze, not going to upgrade them unless regression is confirmed to be gone. Notes: I've tested this with nothing connected to the board except for HDMI cable and some GPIO pins. Nothing on USB etc. New kernel 6.6.16. on Armbian 24.2.1 is experiencing this regression. Kind regards

New 6.x based kernels for OPI 4 LTS seems to be a hit or miss for HDMI monitors. Some work, and others especially TVs dont output video at all. Images with 5.15.x kernels dont have this issue.

I create a file 98-use-serial.rules under folder /etc/udev/rules.d . But symlink not created . My purpose is to fix USB port names, As COM1 COM2 COM3 This is the content of 98-usb-serial.rules: SUBSYSTEM=="tty",ATTRS{busnum}=="1",ATTRS{devnum}=="2",SYMLINK+="COM1" SUBSYSTEM=="tty",ATTRS{busnum}=="4",ATTRS{devnum}=="2",SYMLINK+="COM2" SUBSYSTEM=="tty",ATTRS{busnum}=="5",ATTRS{devnum}=="2",SYMLINK+="COM3" I used to fix the USB port on Asus Tinker S, Khada_VIM3 , all worked fine. I have no idea why Orange Pi 4 LTD not working.

Hello! I would like to connect orangepi-4-lts to ili9341. I have new blank Armbian. $ uname -a Linux orangepi4-lts 5.15.52-rockchip64 #22.05.4 SMP PREEMPT I did overlay based on allwinner: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3399"; fragment@0 { target = <&gpio1>; __overlay__ { ili9341_pins: ili9341_pins { pins = "PC7", "PD0"; function = "gpio_out", "gpio_out"; }; }; }; fragment@1 { target = <&spi1>; __overlay__ { status = "okay"; cs-gpios = <&gpio1 10 1>; ili9341: ili9341@0 { compatible = "ilitek, ili9341"; reg = <1>; pinctrl-names = "default"; pinctrl-0 = <&ili9341_pins>; spi-max-frequency = <16000000>; rotate = <90>; bgr; fps = <25>; buswidth = <8>; reset-gpios = <&gpio1 23 1>; dc-gpios = <&gpio1 24 0>; debug = <0>; }; }; }; }; Setting /boot/armbianEnv.txt verbosity=1 bootlogo=true extraargs=systemd.unified_cgroup_hierarchy=0 overlay_prefix=rockchip fdtfile=rockchip/rk3399-orangepi-4-lts.dtb rootdev=UUID=ce86a0ca-f0e5-4dba-af37-15cc3fb2f4e0 rootfstype=ext4 param_spidev_spi_bus=1 param_spidev_spi_cs=0 user_overlays=ili9341 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Restart, TFT not turn on. I watch debugiing uart, no errors: ## Executing script at 00500000 Boot script loaded from mmc 1 320 bytes read in 4 ms (78.1 KiB/s) 16356833 bytes read in 696 ms (22.4 MiB/s) 30540288 bytes read in 1295 ms (22.5 MiB/s) 81458 bytes read in 14 ms (5.5 MiB/s) 1233 bytes read in 7 ms (171.9 KiB/s) Applying user provided DT overlay ili9341.dtbo 2698 bytes read in 9 ms (292 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Moving Image from 0x2080000 to 0x2200000, end=3fc0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16356769 Bytes = 15.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f4f65000, end f5efe5a1 ... OK Loading Device Tree to 00000000f4ee8000, end 00000000f4f64fff ... OK Starting kernel ... Watching system boot log: grecha@orangepi4-lts:~$ sudo dmesg | grep spi [ 2.053302] rockchip-spi ff1d0000.spi: cs1 >= max 1 [ 2.053318] spi_master spi1: spi_device register error /spi@ff1d0000/ili9341@0 [ 2.053345] spi_master spi1: Failed to create SPI device for /spi@ff1d0000/ili9341@0 grecha@orangepi4-lts:~$ sudo dmesg | grep ili9341 [ 2.053318] spi_master spi1: spi_device register error /spi@ff1d0000/ili9341@0 [ 2.053345] spi_master spi1: Failed to create SPI device for /spi@ff1d0000/ili9341@0 Please, help me. Why is this overlay not working?

Well, I am trying to flash armbian to my board, but after I run upgrade_tool ef in mistake. I can't do anything via maskrom/loader at all wherever Windows or linux. Then I try to unbrick it via flash the "MiniLoaderAll.bin" via "upgrade_tool db" and "ul" but them don't work at all(Timeouted),How can I do with it?

I have owned numerous Raspberry Pi boards over the years, and I have always have ran Kodi on one of them. For years I have been wanting to upgrade my RPi 3 as it cannot play any of my H.265/HEVC videos. With all the shortages, and how old the Raspberry Pi 4 is getting, I made a rather spontaneous purchase for this Orange Pi 4 LTS board. Getting it all setup is easy enough, but of course, the video (even with H.264!) nearly maxes all 6 cores and the video is chunky as it's just doing everything without any video acceleration. Even navigating the menu seems slow and delayed. I have been scouring these forums and other sources for about 12 hours now, and I am still unsure which route to go. Just as a test, I ran Kodi as root and it was much smoother in the menu system and seemed to do H.264 (in software of course, so it was working really hard). But broke Pulseaudio, as Pulse is hardcoded to not accept connections from root when it's not setup as a system-wide service. Anyway, that's not an option. Kodi doesn't need to, and shouldn't run as root. I was very excited, then extremely let down when I found this post: A custom image with custom repositories? Plus, I don't want X11 or Wayland plus a window manager, I don't need it! Either way, it *seems* to be tied to a completely different chipset. I've been up all night working on this, and I am starting to go delirious, so any help would be appreciated.

Hello everyone, Thank you for stopping buy and reading this thread. I have Orange Pi 4 LTS with the latest Armbian Jammy image (Armbian_23.8.1_Orangepi4-lts_jammy_current_6.1.50). But I also want to mention that I've tried the same thing on the "official" Ubuntu image from OrangePi website and it was the same. I need to decode and show RTSP video stream, h264 encoded. First of all, I've tried gstreamer with v4l2 codecs. I was using v4l2slh264dec from gst_plugins_bad. This is the only hardware codec in gstreamer for my device (at least available by default) and it worked fine until I started encountering a strange bug when my video getting stuck into 0.5-1 second loop forever. Anyway, I thought that I could bypass this issue by building libav/FFmpeg with v4l2 features and using it instead. However, I couldn't, and this is my problem. I am building FFmpeg from source like this: First of all, I made sure that there is no FFmpeg on my system. Then: sudo apt install libv4l-dev libsdl2-dev -y git clone https://github.com/FFmpeg/FFmpeg.git cd FFmpeg/ ./configure --enable-libv4l2 --enable-libdrm No errors/warnings. h264_v4l2m2m is in "Enabled decoders". make -j6 sudo make install sudo ldconfig ffplay -vcodec h264_v4l2m2m rtsp://192.168.0.125:8554/stream It gives me the following error: If I do not specify v4l2m2m decoder - it works just fine, but with software decoding. Drivers are present: And I have no idea how to fix this issue I will appreciate a lot any help!

Hello community! Orange pi 4 LTS with Armbian 22.11 Jammy CLI, there is a problem with launching the screen with resolutions: 1024x600 - there is no image 1024x768 - the image is there, there are ripples 1920x1080 - everything is fine Tell me how to solve this problem. uname -a Linux orangepi4-lts 5.15.80-rockchip64 #22.11.1 SMP PREEMPT Wed Nov 30 11:12:47 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux /boot/armbianEnv.txt verbosity=1 bootlogo=false overlay_prefix=rockchip fdtfile=rockchip/rk3399-orangepi-4-lts.dtb rootdev=UUID=72cc3f82-2e76-4495-99fd-8cc46a4a21db rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Link: armbianmonitor 1024x600 Link: armbianmonitor 1024x768

After booting up armbian 23.02.2 on my orange pi 4 LTS, cpu temp goes up to 95 deg celcius when stress testing (no heatsink or fan installed at all) and the device reboots shortly afterwards. I ran `armbianmonitor -m` when stress testing and found out that some of the cores are not throttling. I examined the default trip point settings coming with the image in the file /boot/dtb/rockchip/rk3399-orangepi-4-lts.dtb: trips { cpu_alert0 { temperature = <0x14c08>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5a>; }; cpu_alert1 { temperature = <0x17318>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5b>; }; cpu_crit { temperature = <0x186a0>; hysteresis = <0x7d0>; type = "critical"; phandle = <0xf3>; }; }; These temperature settings do not match the vendor images' settings, and I changed them to match the vendor images' settings as follows: trips { cpu_alert0 { temperature = <0x11170>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5a>; }; cpu_alert1 { temperature = <0x14c08>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5b>; }; cpu_crit { temperature = <0x1c138>; hysteresis = <0x7d0>; type = "critical"; phandle = <0xf3>; }; }; After making this change, I no longer have any reboots caused by overheating and `armbianmonitor -m` shows that the cpu is correctly throttled at 85 deg celcius when stressing testing without heatsink or fan. Is this the right way to solve this issue? If so, can someone make a PR for this? Thanks.

Hi I want to use the I2S GPIO output pins ( 26 pins ) on Orange Pi4 LTS to connect multi channel DAC. Is it possible to overlay some pins?

Hello, I would like to know how they reduce the size of the images and then, when the microSD cards are inserted into a card, they expand to fill the entire space. In other words, the same thing that Armbian images do when we use them for the first time: they are small, and then they occupy all the storage space.

Hi, does anyone know how to get hardware video acceleration on orange 4 lts? I've looked around and I saw that rk3399's multimedia support can be enabled using the rk3399 legacy multimedia framework. But that requires a legacy buster image, which doesn't exist for the orange pi. I've tried to compile it myself, but it seems the compile script won't allow it. Is it really impossible to compile a legacy kernel for orange pi 4 lts?

I have recently purchased an Orange Pi 4 LTS and attempted to run Armbian 23.02 Cinnamon version on my board. However, I could only able to connect into the network with 2.4Ghz. Everytime when I connect to the 5Ghz Network, it failed with some authentication issues (such as WPA3). I am sorry I am new to Linux.May I ask if anyone now how can I resolve the problem?

I have a usb sound card on my sbc. Im only getting left channel audio. Ive tried a different usb sound card and different cable with no luck. I run the command below with no luck, only get audio through the left speaker. speaker-test -t wav -c 2 Any ideas how to fix this?

Hello! Recently i bought an Orange Pi 4 LTS. I choosen armbian for my os. I installed it to sd card, but I wanted more. I decided to flash the system to eMMc. It was a mistake. Instead armbian-config tool, i executed armbian-install, and flashed bootloader to eMMc 🤦‍♂️. After that, i was checking the sd card, reading the logs, nothing helped. I have official 5v 4a dc adapter, factory new sd card, but my board only shines with a red LED, and does not boot into the system.

Hi Team, Greetings. I am using OPi4 LTS Emmc with 16 GB version. kernel: Linux orangepi4-lts 5.15.93-rockchip64 #23.02.2 SMP PREEMPT Fri Feb 17 23:48:36 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux. installed Armbian in Emmc worked like charm. Issue: I connected the SSD WD SN570 and format with nand -sata-install on Armbian to boot and use SSD boot. then I got successful msg all done and ready to reboot. once after the reboot I got this msg. then I tried root it doesn’t work and control-d comes back to same screen. Troubleshooting with a gentleman's assistance: 1. Booted with SD card which has Manjaro. 2. Here are the results of fstab, lsblk, fdisk etc. Suspecting that the Armbian script is broken, I purchased the 1 TB SSD for productivity purposes; however, now either the EMMC or the SSD are starting up. Any help would be appreciated!!

Hi There, Details: Linux orangepi4-lts 5.15.93-rockchip64 #23.02.2 SMP PREEMPT Fri Feb 17 23:48:36 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux I got issues from the Armbian when with Opi 4 LTS. 1.USB 3.0 or USB C not working with the kernel with WD Blue SN570 1TB (1.00)SSD failed in OPI 4 LTS. only works when i connect in USB 2.0. HW is OK, but suspecting problem with drivers (kernel). Tried below options: 1. Tried different cable but no luck in USb 3.0 port or USB c type. 2. same cable works fine in Windows and USB 2.0 3. Only not working detected in USB 3.0 port hub. Attached screenshot. Tried various trouble shooting steps in the orange Pi forum, finally suggested by expert post here. Attached the chat we had on the OrgangePi telegram and few photos of the issue. messages.html

Hi all, After a restart and after a few days go by my My Orange Pi 4 LTS randomly loses its ability to make outbound network connections. I can ssh into the box, however for some reason the routing tables are empty: > ping 192.168.1.53 ping: connect: Network is unreachable > netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface The box is connected through an ethernet cable, configured to used DHCP, but I see no IPv4 address in the interface configuration: > ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 2a01:cb15:81c2:e500:6cba:b008:2761:e29a prefixlen 64 scopeid 0x0<global> inet6 2a01:cb15:81c2:e500:e971:fd8d:4d26:e65 prefixlen 64 scopeid 0x0<global> inet6 fe80::9935:bbd1:a503:c83a prefixlen 64 scopeid 0x20<link> inet6 2a01:cb15:81c2:e500:681d:5fa0:94fd:9e1a prefixlen 64 scopeid 0x0<global> ether 72:d7:a6:97:4b:cf txqueuelen 1000 (Ethernet) RX packets 195548 bytes 16128189 (16.1 MB) RX errors 0 dropped 13442 overruns 0 frame 0 TX packets 22932 bytes 2779612 (2.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 31 I am new to armbian, and not sure where to go to troubleshoot from there. /etc/networks/interfaces is empty, how is eth0 configured? I can resolve the issue by issuing > sudo ip link eth0 down && sudo ip link eth0 up ... and I have added a cron entry doing just that, but obviously I would like to understand where the issue is coming from. Here is some system information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy Linux orangepi4-lts 5.15.76-rockchip64 #22.08.8 SMP PREEMPT Sun Oct 30 10:57:32 CET 2022 aarch64 aarch64 aarch64 GNU/Linux Thanks! Franck EDIT: here is what I find in journalctl, it looks like the eth0 interface goes down shortly (4mn) after a reboot and never comes back up correctly: Apr 17 06:17:28 orangepi4-lts NetworkManager[1626]: <info> [1681705048.7753] dhcp4 (eth0): state changed new lease, address=192.168.0.102 <normal network manager startup> Apr 17 06:17:28 orangepi4-lts NetworkManager[1626]: <info> [1681705048.8306] device (eth0): Activation: successful, device activated. ... Apr 17 06:17:29 orangepi4-lts nm-dispatcher[2142]: /etc/network/if-up.d/resolved: 12: mystatedir: not found Apr 17 06:17:32 orangepi4-lts kernel: rk_gmac-dwmac fe300000.ethernet eth0: Link is Down Apr 17 06:17:32 orangepi4-lts systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.3960] device (eth0): carrier: link connected Apr 17 06:17:36 orangepi4-lts kernel: rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.3968] device (eth0): ip:dhcp4: restarting Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4136] dhcp4 (eth0): canceled DHCP transaction Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4138] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4139] dhcp4 (eth0): state changed no lease Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4144] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4305] dhcp4 (eth0): state changed new lease, address=192.168.0.102 <from this point on, outbound connections are failing, e.g. Apr 17 06:17:38 orangepi4-lts telegraf[1790]: 2023-04-17T04:17:38Z E! [agent] Error writing to outputs.influxdb_v2: failed to send metrics to any configured server(s) > Apr 17 06:17:42 orangepi4-lts systemd[1]: systemd-hostnamed.service: Deactivated successfully. Apr 17 06:17:46 orangepi4-lts systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Apr 17 06:18:28 orangepi4-lts NetworkManager[1626]: <info> [1681705108.9445] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:18:28 orangepi4-lts NetworkManager[1626]: <info> [1681705108.9446] dhcp4 (eth0): state changed no lease Apr 17 06:18:58 orangepi4-lts systemd-resolved[794]: eth0: Bus client set search domain list to: home Apr 17 06:18:58 orangepi4-lts systemd-resolved[794]: eth0: Bus client set DNS server list to: 192.168.0.254, 2a01:cb15:81c2:e500:7ec1:77ff:fe90:48f0 Apr 17 06:18:58 orangepi4-lts systemd[1]: Starting resolvconf-pull-resolved.service... Apr 17 06:18:58 orangepi4-lts sh[2217]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf Apr 17 06:19:14 orangepi4-lts systemd-resolved[794]: eth0: Bus client set DNS server list to: 2a01:cb15:81c2:e500:7ec1:77ff:fe90:48f0

Hello, i just bought new display from orangepi. But i have problem get it work with armbian 23 jally with kernel 5.15. I try get files from orange pi os with no success. Does somebody have working dts for this type of display ? Orange Pi RK3399 10.1inch LCD Touch Screen & Display Panel screen - OP1102 DTS

Hi I am wondering if anyone has had any luck using a mini PCIe to SATA adapter with an Orange Pi 4 LTS to attach a SATA hardrive? If yes, which adapter did you use? I would like to throw the OPi 4 LTS and a hard drive in a box and make a mini fanless NAS box. thanks

Hi, Wifi stops working after some time. Output from armbianmonitor -u : https://paste.armbian.com/iqukawifes Only reboot help. In dmesg I see: [ 6793.969484] WCN: stop_loopcheck [ 6806.513278] sprdwl:[WIFI_CMD_TX_DATA]timeout [ 6806.514120] sprdwl:ctx_id:0 cmd: WIFI_CMD_TX_DATA[72] rsp timeout (mstime = 6802912), num=3304 [ 6809.589395] sprdwl:[WIFI_CMD_TX_DATA]timeout [ 6809.589823] sprdwl:ctx_id:0 cmd: WIFI_CMD_TX_DATA[72] rsp timeout (mstime = 6805981), num=3305 [ 6812.661554] sprdwl:[WIFI_CMD_TX_DATA]timeout [ 6812.661979] sprdwl:ctx_id:0 cmd: WIFI_CMD_TX_DATA[72] rsp timeout (mstime = 6809057), num=3306 [ 6812.662786] sprdwl:sprdwl_atcmd_assert ctx_id:0, cmd_id:72, reason:3, cp_asserted:0 [ 6812.663492] WCN: mdbg_assert_interface:[CMD] WIFI_CMD_TX_DATA, [REASON] CMD_RSP_TIMEOUT_ERROR [ 6812.663505] sdiohal:carddump flag set[1] [ 6812.663931] sdiohal:disable rx int for dump [ 6812.663956] sdiohal:chn8 tx push old, cmdid=72, mstime=6805981, record_time=6805982 [ 6812.663984] chn8 tx push old: 00 00 00 00 10 48 46 00 dd d9 67 00 00 00 00 00 .....HF...g..... [ 6812.663995] sdiohal:chn8 tx denq old, cmdid=72, mstime=6805981, record_time=6805982 [ 6812.664012] chn8 tx denq old: 00 23 00 08 10 48 46 00 dd d9 67 00 00 00 00 00 .#...HF...g..... [ 6812.664022] sdiohal:chn22 rx dispatch old, cmdid=5, mstime=6788866, record_time=6788867 [ 6812.664038] chn22 rx dispatch old: 3f 06 00 0a 00 05 0c 00 02 97 67 00 00 24 00 00 ?.........g..$.. [ 6812.664048] sdiohal:chn8 tx push new, cmdid=72, mstime=6809057, record_time=6809057 [ 6812.664064] chn8 tx push new: 00 00 00 00 10 48 46 00 e1 e5 67 00 00 00 00 00 .....HF...g..... [ 6812.664074] sdiohal:chn8 tx denq new, cmdid=72, mstime=6809057, record_time=6809057 [ 6812.664090] chn8 tx denq new: 00 23 00 08 10 48 46 00 e1 e5 67 00 00 00 00 00 .#...HF...g..... [ 6812.664100] sdiohal:chn22 rx dispatch new, cmdid=5, mstime=6788901, record_time=6788906 [ 6812.664116] chn22 rx dispatch new: bf 06 00 0a 00 05 0d 00 25 97 67 00 00 26 00 00 ........%.g..&.. [ 6812.664384] WCN: dap_sel_btwf_lite DJTAG_DAP_SEL:0x0 [ 6812.664592] WCN: dap_sel_btwf_lite DJTAG_DAP_SEL:0x2 [ 6812.664793] WCN: dap_sel_btwf_lite 2:DJTAG_DAP_SEL:0x2 [ 6812.664991] WCN: apb_eb_lite APB_EB:0x463 [ 6812.665193] WCN: apb_eb_lite APB_EB:0x463 [ 6812.665393] WCN: apb_eb_lite 2:APB_EB:0x463 [ 6812.665689] WCN: check_dap_is_ok :0x24770011 [ 6812.665704] WCN: btwf dap is ready [ 6812.667995] WCN: read_core_reg ****R[0]: 0x0**** [ 6812.669144] WCN: read_core_reg ****R[1]: 0x0**** [ 6812.670487] WCN: read_core_reg ****R[2]: 0x8001000c**** [ 6812.671644] WCN: read_core_reg ****R[3]: 0x0**** [ 6812.672794] WCN: read_core_reg ****R[4]: 0x4083c000**** [ 6812.674078] WCN: read_core_reg ****R[5]: 0x1e694c**** [ 6812.675222] WCN: read_core_reg ****R[6]: 0x3**** [ 6812.676359] WCN: read_core_reg ****R[7]: 0x0**** [ 6812.677545] WCN: read_core_reg ****R[8]: 0x40130000**** [ 6812.678703] WCN: read_core_reg ****R[9]: 0x10d69c**** [ 6812.679842] WCN: read_core_reg ****R[10]: 0x40088000**** [ 6812.680985] WCN: read_core_reg ****R[11]: 0x1e6954**** [ 6812.682309] WCN: read_core_reg ****R[12]: 0x11fc64**** [ 6812.683457] WCN: read_core_reg ****R[13]: 0x1a0ef8**** [ 6812.684605] WCN: read_core_reg ****R[14]: 0x1e605b**** [ 6812.685831] WCN: read_core_reg ****R[15]: 0x1e67ee**** [ 6812.686971] WCN: read_core_reg ****R[16]: 0x6100000b**** [ 6812.688108] WCN: read_core_reg ****R[17]: 0x1a0ef8**** [ 6812.689248] WCN: read_core_reg ****R[18]: 0x117bd8**** [ 6812.689262] WCN: ------------[ ARM REG ]------------ [ 6812.689269] WCN: [R0 ] = 0x00000000 [ 6812.689278] WCN: [R1 ] = 0x00000000 [ 6812.689287] WCN: [R2 ] = 0x8001000c [ 6812.689295] WCN: [R3 ] = 0x00000000 [ 6812.689303] WCN: [R4 ] = 0x4083c000 [ 6812.689312] WCN: [R5 ] = 0x001e694c [ 6812.689320] WCN: [R6 ] = 0x00000003 [ 6812.689329] WCN: [R7 ] = 0x00000000 [ 6812.689337] WCN: [R8 ] = 0x40130000 [ 6812.689345] WCN: [R9 ] = 0x0010d69c [ 6812.689353] WCN: [R10] = 0x40088000 [ 6812.689362] WCN: [R11] = 0x001e6954 [ 6812.689371] WCN: [R12] = 0x0011fc64 [ 6812.689379] WCN: [R13] = 0x001a0ef8 [ 6812.689387] WCN: [R14] = 0x001e605b [ 6812.689395] WCN: [R15] = 0x001e67ee [ 6812.689403] WCN: [PSR] = 0x6100000b [ 6812.689412] WCN: [MSP] = 0x001a0ef8 [ 6812.689420] WCN: [PSP] = 0x00117bd8 [ 6812.689428] WCN: ------------[ ARM END ]------------ [ 6812.689874] WCN: marlin_hold_cpu reset reg val:0x0 [ 6812.690269] WCN: CP DCACHE ENABLE [ 6812.718084] WCN: section[0] [0x100000 0x1e73ff 0x240] [ 6812.718121] WCN: section[1] [0x40880000 0x40880053 0xe7640] [ 6812.718133] WCN: section[2] [0x4083c000 0x4083c353 0xe7694] [ 6812.718146] WCN: section[3] [0x40130000 0x401303ff 0xe79e8] [ 6812.718157] WCN: section[4] [0x40088000 0x4008828b 0xe7de8] [ 6812.718169] WCN: section[5] [0x40844200 0x40844343 0xe8074] [ 6812.718180] WCN: section[6] [0x40844000 0x40844047 0xe81b8] [ 6812.718192] WCN: section[7] [0x40140000 0x4014ffff 0xe8200] [ 6812.718203] WCN: section[8] [0x400f0000 0x400f011f 0xf8200] [ 6812.718214] WCN: section[9] [0x400f1000 0x400fe0ff 0xf8320] [ 6812.718226] WCN: section[10] [0x40300000 0x4034a7ff 0x105420] [ 6812.718238] WCN: section[11] [0x400a0000 0x400a0057 0x14fc20] [ 6812.718250] WCN: section[12] [0x400b0000 0x400b0387 0x14fc78] [ 6812.718261] WCN: section[13] [0x400b1000 0x400b1153 0x150000] [ 6812.718273] WCN: section[14] [0x400b2000 0x400b2a8b 0x150154] [ 6812.718284] WCN: section[15] [0x400b3000 0x400b30af 0x150be0] [ 6812.718295] WCN: section[16] [0x400b4000 0x400b4a6f 0x150c90] [ 6812.718307] WCN: section[17] [0x400b7000 0x400b7617 0x151700] [ 6812.718318] WCN: section[18] [0x40240000 0x402408f3 0x151d18] [ 6812.718329] WCN: section[19] [0x40246000 0x40246737 0x15260c] [ 6812.718341] WCN: section[20] [0x40248000 0x4024809f 0x152d44] [ 6812.718352] WCN: section[21] [0x4024a000 0x4024a21b 0x152de4] [ 6812.718364] WCN: section[22] [0x4024f000 0x4024f30f 0x153000] [ 6812.718375] WCN: section[23] [0x40200000 0x402001ff 0x153310] [ 6812.718386] WCN: section[24] [0x40204000 0x402041ff 0x153510] [ 6812.718398] WCN: section[25] [0x40208000 0x402092a3 0x153710] [ 6812.718409] WCN: section[26] [0x40200c00 0x4020c343 0x1549b4] [ 6812.718420] WCN: section[27] [0x40210000 0x40212fff 0x1600f8] [ 6812.718432] WCN: section[28] [0x40214000 0x40216fff 0x1630f8] [ 6812.718443] WCN: section[29] [0x40218000 0x402182cf 0x1660f8] [ 6812.718454] WCN: section[30] [0x4021c000 0x4021c5bf 0x1663c8] [ 6812.718466] WCN: section[31] [0x40241000 0x402413ff 0x166988] [ 6812.718478] WCN: section[32] [0x40242000 0x402423ff 0x166d88] [ 6812.718489] WCN: dumpmem_rx_callback [ 6812.722261] WCN: dumpmem_rx_callback [ 6812.722298] WCN_ERR: dumpmem_rx_callback open error no.-21 retry:1 [ 6812.726612] WCN: dumpmem_rx_callback [ 6812.730406] WCN: dumpmem_rx_callback [ 6812.734087] WCN: dumpmem_rx_callback [ 6812.737727] WCN: dumpmem_rx_callback [ 6812.741301] WCN: dumpmem_rx_callback [ 6812.745201] WCN: dumpmem_rx_callback [ 6812.749095] WCN: dumpmem_rx_callback [ 6812.752831] WCN: dumpmem_rx_callback [ 6812.756544] WCN: dumpmem_rx_callback [ 6812.760444] WCN: dumpmem_rx_callback [ 6812.764345] WCN: dumpmem_rx_callback [ 6812.767988] WCN: dumpmem_rx_callback [ 6812.771603] WCN: dumpmem_rx_callback [ 6812.775420] WCN: dumpmem_rx_callback [ 6812.779174] WCN: dumpmem_rx_callback [ 6812.782903] WCN: dumpmem_rx_callback [ 6812.786607] WCN: dumpmem_rx_callback [ 6812.790268] WCN: dumpmem_rx_callback [ 6812.793926] WCN: dumpmem_rx_callback [ 6812.797536] WCN: dumpmem_rx_callback [ 6812.801115] WCN: dumpmem_rx_callback [ 6812.805021] WCN: dumpmem_rx_callback [ 6812.808953] WCN: dumpmem_rx_callback [ 6812.834246] WCN: dumpmem_rx_callback [ 6812.838115] WCN: dumpmem_rx_callback [ 6812.919411] WCN: dumpmem_rx_callback [ 6812.923281] WCN: dumpmem_rx_callback [ 6812.951213] WCN: dumpmem_rx_callback [ 6812.951259] WCN: mdbg dump ram 947200 ok! [ 6812.951523] WCN: dumpmem_rx_callback [ 6812.951538] WCN: mdbg dump aon ahb 84 ok! [ 6812.951878] WCN: dumpmem_rx_callback [ 6812.951892] WCN: mdbg dump aon_apb 852 ok! [ 6812.952176] WCN: dumpmem_rx_callback [ 6812.952191] WCN: mdbg dump btwfahb 1024 ok! [ 6812.952497] WCN: dumpmem_rx_callback [ 6812.952511] WCN: mdbg dump btwfapb 652 ok! [ 6812.952768] WCN: dumpmem_rx_callback [ 6812.952781] WCN: mdbg dump aonclk 324 ok! [ 6812.953006] WCN: dumpmem_rx_callback [ 6812.953020] WCN: mdbg dump predivclk 72 ok! [ 6812.962557] WCN: dumpmem_rx_callback [ 6812.968142] WCN: dumpmem_rx_callback [ 6812.968189] WCN: mdbg dump sdio 65536 ok! [ 6812.968421] WCN: enable_cp_pll rd CLK_CTRL0 reg val:0x2fdf [ 6812.968839] WCN: enable_cp_pll enable CLK_CTRL0 val:0x2fdf [ 6812.969464] WCN: check_wifi_power_domain_ison CHIP_SLP reg val:0xc430 [ 6812.969488] WCN: WIFI MAC have power down [ 6812.971279] WCN: check_wifi_power_domain_ison WIFI_ENABLE reg val:0xa023 [ 6812.971315] WCN: WIFI_en and wifi_mac_en is disable [ 6812.972007] WCN: dumpmem_rx_callback [ 6812.976547] WCN: dumpmem_rx_callback [ 6812.979493] WCN: dumpmem_rx_callback [ 6812.983143] WCN: dumpmem_rx_callback [ 6812.986775] WCN: dumpmem_rx_callback [ 6812.991332] WCN: dumpmem_rx_callback [ 6812.994996] WCN: dumpmem_rx_callback [ 6812.998628] WCN: dumpmem_rx_callback [ 6813.002260] WCN: dumpmem_rx_callback [ 6813.005868] WCN: dumpmem_rx_callback [ 6813.009414] WCN: dumpmem_rx_callback [ 6813.014692] WCN: dumpmem_rx_callback [ 6813.018279] WCN: dumpmem_rx_callback [ 6813.021871] WCN: dumpmem_rx_callback [ 6813.021895] WCN: mdbg dump wifi 360448 ok! [ 6813.022129] WCN: dumpmem_rx_callback [ 6813.022143] WCN: dump cp reg section[11] ok! [ 6813.022490] WCN: dumpmem_rx_callback [ 6813.022508] WCN: dump cp reg section[12] ok! [ 6813.022824] WCN: dumpmem_rx_callback [ 6813.022839] WCN: dump cp reg section[13] ok! [ 6813.023408] WCN: dumpmem_rx_callback [ 6813.023422] WCN: dump cp reg section[14] ok! [ 6813.023641] WCN: dumpmem_rx_callback [ 6813.023655] WCN: dump cp reg section[15] ok! [ 6813.024195] WCN: dumpmem_rx_callback [ 6813.024209] WCN: dump cp reg section[16] ok! [ 6813.024623] WCN: dumpmem_rx_callback [ 6813.024636] WCN: dump cp reg section[17] ok! [ 6813.025234] WCN: dumpmem_rx_callback [ 6813.025247] WCN: mdbg dump fm 2748 ok! [ 6813.025791] WCN: dumpmem_rx_callback [ 6813.025806] WCN: mdbg dump btacc 2292 ok! [ 6813.026218] WCN: dumpmem_rx_callback [ 6813.026232] WCN: mdbg dump btjal 1848 ok! [ 6813.026448] WCN: dumpmem_rx_callback [ 6813.026462] WCN: mdbg dump bthab 160 ok! [ 6813.026733] WCN: dumpmem_rx_callback [ 6813.026746] WCN: mdbg dump btlejal 540 ok! [ 6813.140006] sdiohal err:dt read fail ret:-110, system_addr=0x4024f000 [ 6813.140636] sdiohal:sdio dump_aon_reg entry [ 6813.140738] sdiohal:pmu sdio status:[0x140]:0x6b [ 6813.140807] sdiohal:pmu sdio status:[0x141]:0x3c [ 6813.140871] sdiohal:pmu sdio status:[0x142]:0xe1 [ 6813.140936] sdiohal:pmu sdio status:[0x143]:0x0 [ 6813.141000] sdiohal:pmu sdio status:[0x144]:0x0 [ 6813.141065] sdiohal:pmu sdio status:[0x145]:0x0 [ 6813.141115] sdiohal:pmu sdio status:[0x146]:0x0 [ 6813.141165] sdiohal:pmu sdio status:[0x147]:0x0 [ 6813.141215] sdiohal:pmu sdio status:[0x148]:0x60 [ 6813.141266] sdiohal:pmu sdio status:[0x149]:0x0 [ 6813.141317] sdiohal:pmu sdio status:[0x14a]:0x0 [ 6813.141366] sdiohal:pmu sdio status:[0x14b]:0x0 [ 6813.141414] sdiohal:pmu sdio status:[0x14c]:0x0 [ 6813.141463] sdiohal:pmu sdio status:[0x14d]:0x0 [ 6813.141513] sdiohal:pmu sdio status:[0x14e]:0x0 [ 6813.141623] sdiohal:pmu sdio status:[0x14f]:0x0 [ 6813.141830] sdiohal:cm4d haddr 0:[0x144]:0x0 [ 6813.141885] sdiohal:cm4d haddr 0:[0x145]:0x60 [ 6813.141938] sdiohal:cm4d haddr 0:[0x146]:0x19 [ 6813.141990] sdiohal:cm4d haddr 0:[0x147]:0x0 [ 6813.142198] sdiohal:cm4i haddr 1:[0x144]:0xf8 [ 6813.142251] sdiohal:cm4i haddr 1:[0x145]:0x67 [ 6813.142302] sdiohal:cm4i haddr 1:[0x146]:0x1e [ 6813.142355] sdiohal:cm4i haddr 1:[0x147]:0x0 [ 6813.142556] sdiohal:cm4s haddr 2:[0x144]:0x4c [ 6813.142608] sdiohal:cm4s haddr 2:[0x145]:0x0 [ 6813.142660] sdiohal:cm4s haddr 2:[0x146]:0x1e [ 6813.142712] sdiohal:cm4s haddr 2:[0x147]:0x40 [ 6813.142913] sdiohal:dmaw haddr 3:[0x144]:0x0 [ 6813.142964] sdiohal:dmaw haddr 3:[0x145]:0x0 [ 6813.143016] sdiohal:dmaw haddr 3:[0x146]:0x0 [ 6813.143067] sdiohal:dmaw haddr 3:[0x147]:0x0 [ 6813.143270] sdiohal:dmar haddr 4:[0x144]:0x0 [ 6813.143323] sdiohal:dmar haddr 4:[0x145]:0x0 [ 6813.143376] sdiohal:dmar haddr 4:[0x146]:0x0 [ 6813.143427] sdiohal:dmar haddr 4:[0x147]:0x0 [ 6813.143640] sdiohal:aon_to_ahb haddr 5:[0x144]:0x0 [ 6813.143692] sdiohal:aon_to_ahb haddr 5:[0x145]:0x0 [ 6813.143743] sdiohal:aon_to_ahb haddr 5:[0x146]:0x0 [ 6813.143795] sdiohal:aon_to_ahb haddr 5:[0x147]:0x0 [ 6813.143998] sdiohal:axi_to_ahb haddr 6:[0x144]:0x4 [ 6813.144050] sdiohal:axi_to_ahb haddr 6:[0x145]:0xf0 [ 6813.144102] sdiohal:axi_to_ahb haddr 6:[0x146]:0x24 [ 6813.144153] sdiohal:axi_to_ahb haddr 6:[0x147]:0x40 [ 6813.144361] sdiohal:hready_status haddr 7:[0x144]:0xcf [ 6813.144415] sdiohal:hready_status haddr 7:[0x145]:0xff [ 6813.144467] sdiohal:hready_status haddr 7:[0x146]:0xf9 [ 6813.144519] sdiohal:hready_status haddr 7:[0x147]:0x50 [ 6813.144532] sdiohal:val:0xc [ 6813.144653] sdiohal:after reset hready status:[0x144]:0xcf [ 6813.144704] sdiohal:after reset hready status:[0x145]:0xff [ 6813.144752] sdiohal:after reset hready status:[0x146]:0xf9 [ 6813.144803] sdiohal:after reset hready status:[0x147]:0x50 [ 6813.144814] sdiohal:sdio dump_aon_reg end [ 6813.144821] sdiohal:sdiohal_abort [ 6813.144829] sdiohal:carddump flag set[1] [ 6813.144905] sdiohal:disable rx int for dump [ 6813.144914] sdiohal:chn8 tx push old, cmdid=72, mstime=6805981, record_time=6805982 [ 6813.144935] chn8 tx push old: 00 00 00 00 10 48 46 00 dd d9 67 00 00 00 00 00 .....HF...g..... [ 6813.144945] sdiohal:chn8 tx denq old, cmdid=72, mstime=6805981, record_time=6805982 [ 6813.144961] chn8 tx denq old: 00 23 00 08 10 48 46 00 dd d9 67 00 00 00 00 00 .#...HF...g..... [ 6813.144972] sdiohal:chn22 rx dispatch old, cmdid=5, mstime=6788866, record_time=6788867 [ 6813.144989] chn22 rx dispatch old: 3f 06 00 0a 00 05 0c 00 02 97 67 00 00 24 00 00 ?.........g..$.. [ 6813.144999] sdiohal:chn8 tx push new, cmdid=72, mstime=6809057, record_time=6809057 [ 6813.145015] chn8 tx push new: 00 00 00 00 10 48 46 00 e1 e5 67 00 00 00 00 00 .....HF...g..... [ 6813.145024] sdiohal:chn8 tx denq new, cmdid=72, mstime=6809057, record_time=6809057 [ 6813.145040] chn8 tx denq new: 00 23 00 08 10 48 46 00 e1 e5 67 00 00 00 00 00 .#...HF...g..... [ 6813.145049] sdiohal:chn22 rx dispatch new, cmdid=5, mstime=6788901, record_time=6788906 [ 6813.145066] chn22 rx dispatch new: bf 06 00 0a 00 05 0d 00 25 97 67 00 00 26 00 00 ........%.g..&.. [ 6813.145077] WCN_ERR: mdbg_dump_data dump memory error:-110 [ 6813.145652] WCN: mdbg dump bt modem 0 ok! [ 6813.145664] WCN_ERR: read HCI_ARM_WR_RD_MODE reg error:-1 [ 6813.146184] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.146674] WCN: mdbg dump bt_cmd buf 0 ok! [ 6813.146696] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.150664] WCN: mdbg dump btevent buf 0 ok! [ 6813.150702] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.151207] WCN: mdbg dump bt_lmp_tx_buf 0 ok! [ 6813.151229] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.151717] WCN: mdbg dump bt_lmp_rx_buf 0 ok! [ 6813.151739] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.152227] WCN: mdbg dump bt_acl_tx_buf0 ok! [ 6813.152249] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.152736] WCN: mdbg dump bt_acl_rx_buf 0 ok! [ 6813.152757] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.153244] WCN: mdbg dump bt_sco_tx_buf 0 ok! [ 6813.153265] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.153790] WCN: mdbg dump bt_sco_rx_buf 0 ok! [ 6813.153817] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.154309] WCN: mdbg dump bt_bb_tx_buf 0 ok! [ 6813.154330] WCN_ERR: mdbg_dump_data dump memory error:-1 [ 6813.154818] WCN: mdbg dump bt_bb_rx_buf 0 ok! [ 6813.201603] WCN: dumpmem_rx_callback [ 6813.201629] WCN: dump str finish! [ 6813.201637] WCN: mdbg dump memory finish [ 6813.201733] sprdwl:sprdwl_atcmd_assert ctx_id:0, cmd_id:72, reason:3, cp_asserted:1 [ 6813.202462] sprdwl:sprdwl_atcmd_assert ctx_id:0, cmd_id:72, reason:3, cp_asserted:1 [ 6814.325605] ------------[ cut here ]------------ [ 6814.325632] NETDEV WATCHDOG: wlan0 (unisoc_wifi): transmit queue 0 timed out [ 6814.325759] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:478 dev_watchdog+0x390/0x398 [ 6814.325798] Modules linked in: tls tcp_diag inet_diag xt_nat xt_tcpudp veth wireguard libchacha20poly1305 poly1305_neon libcurve25519_generic ip6_udp_tunnel udp_tunnel xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge aufs algif_hash algif_skcipher af_alg bnep hci_uart btqca btrtl btbcm btintel bluetooth dw_hdmi_i2s_audio dw_hdmi_cec snd_soc_hdmi_codec hantro_vpu(C) rockchip_vdec(C) rockchip_iep v4l2_h264 rockchip_rga videobuf2_dma_contig v4l2_mem2mem videobuf2_dma_sg videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_soc_simple_card snd_soc_rockchip_i2s fusb302 videobuf2_common snd_soc_es8316 snd_soc_rockchip_pcm snd_soc_simple_card_utils tcpm snd_soc_core typec snd_pcm_dmaengine snd_pcm videodev snd_timer mc snd soundcore cpufreq_dt lz4hc lz4 sch_fq_codel zram sprdwl_ng cfg80211 sprdbt_tty rfkill ramoops pstore_blk reed_solomon [ 6814.326338] pstore_zone ip_tables x_tables autofs4 panfrost motorcomm gpu_sched dwmac_rk stmmac_platform stmmac pwm_bl pcs_xpcs adc_keys [ 6814.326430] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C 5.15.80-rockchip64 #22.11.1 [ 6814.326448] Hardware name: OrangePi 4 LTS (DT) [ 6814.326458] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 6814.326475] pc : dev_watchdog+0x390/0x398 [ 6814.326493] lr : dev_watchdog+0x390/0x398 [ 6814.326509] sp : ffff800009de3d60 [ 6814.326516] x29: ffff800009de3d60 x28: ffff000008c4dc80 x27: 0000000000000004 [ 6814.326545] x26: 0000000000000140 x25: 00000000ffffffff x24: 0000000000000003 [ 6814.326573] x23: ffff800009a97000 x22: ffff000008d6141c x21: ffff000008d61000 [ 6814.326601] x20: ffff000008d614c0 x19: 0000000000000000 x18: 0000000000000000 [ 6814.326629] x17: ffff8000ee035000 x16: ffff800009de4000 x15: 000000000000096d [ 6814.326656] x14: ffff800009de3a70 x13: 00000000ffffffea x12: ffff800009b2fd10 [ 6814.326685] x11: 0000000000000003 x10: ffff800009b17cd0 x9 : ffff800009b17d28 [ 6814.326713] x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001 [ 6814.326740] x5 : ffff8000ee035000 x4 : 0000000000000000 x3 : 0000000000000103 [ 6814.326767] x2 : 0000000000000102 x1 : 01cf58aa292ccd00 x0 : 0000000000000000 [ 6814.326795] Call trace: [ 6814.326803] dev_watchdog+0x390/0x398 [ 6814.326821] call_timer_fn+0x30/0x1d0 [ 6814.326840] run_timer_softirq+0x27c/0x518 [ 6814.326855] _stext+0x160/0x3f8 [ 6814.326870] irq_exit+0xc8/0x100 [ 6814.326890] handle_domain_irq+0x94/0xd8 [ 6814.326909] gic_handle_irq+0xb8/0x134 [ 6814.326925] call_on_irq_stack+0x28/0x54 [ 6814.326942] do_interrupt_handler+0x58/0x68 [ 6814.326958] el1_interrupt+0x30/0x78 [ 6814.326974] el1h_64_irq_handler+0x18/0x28 [ 6814.326988] el1h_64_irq+0x74/0x78 [ 6814.327001] arch_cpu_idle+0x18/0x28 [ 6814.327016] default_idle_call+0x40/0x184 [ 6814.327037] do_idle+0x1fc/0x270 [ 6814.327054] cpu_startup_entry+0x24/0x68 [ 6814.327070] secondary_start_kernel+0x154/0x168 [ 6814.327089] __secondary_switched+0x90/0x94 [ 6814.327105] ---[ end trace acf1365498026f79 ]--- My wife use 2.4 and 5 GHz. Please help me to fix this problem. Thank you!

Excuse my ignorance all but I'm not familiar with this type of thing. I got my OP 4 lts running with the latest jammy HOWEVER, the resolution is wrong for the 5" HDMI screen I'm using, The screens touch function is not working, and I can't SSH into it via wifi because I can't seem to find what port it is on. If any of you can help me out here, I'd appreciate it.