Distro: Debian 12 bookworm, xfce;

Board: Orange Pi 4 LTS;

Screen: Samsung SyncMaster 923NW, 1440x900_60, VGA.

Using hdmi to vga adapter with vga cable. Tried one piece hdmi to vga cable. Tried other all in one adapter that goes in to the screen and goes to hdmi cable.

The problem.

While running armbian distro screen resolution is set to be 1080p by default. Using xrandr I can not set it to suggested 900p. Every time I set any other resolution - screen turns black until I set it back to 1080p. It is not a hardware issue, because right now I am running headless Debian bullseye from orange pi and the resolution is set 900p by default, it works.

I have tried adding new modes, tried other resolutions and most of them have led me to the black screen.

Brothers, I am confused. Any help is welcome.

The October Home Assistant update completely broke my H.A., it stopped running completely, and when I tried to reinstall it, it threw up errors due to broken dependencies.
I tried to repair them, but nothing worked.
I simply started looking for a newer version, since the current requirements for H.A. are at least Debian 12.

I decided to try Harmony 13 with the XFCE desktop.
Everything works great. I installed H.A., Plex, Samba, etc.
It took me three days straight to get my entire home automation system back up and running in H.A.
H.A.'s encrypted backups took me hours until I found where the key was stored.
It later turned out that the full backup wasn't much use since all the sensors had a different ID, and 90% of the things were broken, and the add-ons weren't even in the backup.

After a week of struggling, I managed to get everything 100% working.
Debian 13 can turn my screen off and back on by touching it with a finger. This is great for quickly interacting with H.A.

The screen looks terrible and there are no resolution modes.

By default, Debian boots at 1024x768@60Hz.
On the Orangepi OS, it runs perfectly at this resolution and everything looks great.
It also has another 16:9 resolution mode at 848x480@60Hz.

But in Armbian, I only have two modes:

1024x768@60
800x600@60

The first mode, which looks great on OrangePi OS, here has a shaky, blurry image. The second mode, 800x600, looks perfect, but it's too small.

The monitor displays signal information.
In Armbian, when it boots at 1024x768@60, it appears to be in a different resolution: 987x768@57Hz.

That's why it looks so bad. When running at 57Hz, the image shakes, and when rescaling, the screen loses all detail.

I followed many tutorials and none of them worked:

Use cvt to calculate different resolutions and xrandr to create them.
However, any resolution created results in an error when trying to use it.

sudo apt install xrandr

cvt 1024 600 60
# 1024x600 59.85 Hz (CVT) hsync: 37.35 kHz; pclk: 49.00 MHz
Modeline "1024x600_60.00"   49.00  1024 1064 1168 1312  600 603 613 624 -hsync +vsync

xrandr --newmode "1024x600_60.00"   49.00  1024 1064 1168 1312  600 603 613 624 -hsync +vsync
xrandr --addmode HDMI-1 "1024x600_60.00"
xrandr --output HDMI-1 --mode "1024x600_60.00"

Use CVT and GTF to calculate the resolutions. I've tried countless resolutions, and it always fails and reverts to the previous one.

I can't find a way to make the screen look the way it should.

Does anyone have any ideas on how to fix this?
I suspect this is a kernel-level issue.

Sorry, but I'm using Google Translate.

------------------------------------------------------------------------------------

v25.11 rolling for Orange Pi 4 LTS running Armbian Linux 6.12.53-current-rockchip64

 Packages:     Debian stable (trixie)
 Support:      for advanced users (rolling release)
 Containers:   addon_491eb00d_hamh, addon_core_duckdns, addon_core_mosquitto, hassio_multicast, hassio_audio, hassio_dns, hassio_cli, homeassistant, hassio_observer, hassio_supervisor

 Performance:

 Load:         2%                Uptime:       15:06            
 Memory usage: 56% of 2.90G      Zram usage:   7% of 1.45G
 CPU temp:     38°C              Usage of /:   23% of 57G
 RX today:     184 MiB
-------------------------------------------------------------------------------------
 

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?

After long debugging we've found that 24-pin FPC cable that connects Orangepi and official connector board (PCIE-SOCKET-OPI4-4B) does not pass PERST signal from Orangepi. Instead, it is high by default and the only way to temporarily set it to low is by pressing physical button on connector board.
As far as I understand, PERST signal basically tells the connected device that power and clocks are stable and it can begin link training sequence. Normally, this signal would be controlled from driver code (pcie_rockchip_host.c, rockchip->perst_gpio field) and is assigned to GPIO2_4 pin. During startup sequence it must first be set to low for some time before being set to high after all PCIe clocks are initialized.
However, since we don't connect PCI-e directly to rk3399 but through connector cable/board, this code does nothing and instead PERST signal is always high as soon as power is on, leading to link training errors.

Simple method to verify the problem:

1. Build custom image (or only kernel) using armbian-build. In kernel configuration, set pcie_rockchip_host module to be compiled as loadable module (<M>) instead of built-in by default.
2. When system fails to see connected PCI-E device at boot, press the reset button on connector board.
3. Execute (you can try this first without pressing button but it will not work):

   sudo modprobe -vr pcie_rockchip_host && sudo modprobe -v pcie_rockchip_host 

4. `lspci` command should now show your device.

Thankfully, 24-pin FPC cable does pass GPIO1_A0 signal which we can use as a workaround. By default it is configured as vcc3v3-pcie power regulator, which basically means that it is always on. If we reconfigure it to act as PERST signal, it will become controlled by pcie_rockchip_host Linux driver, which seems to fix the problem.

So, the fix is to build custom image/kernel with dts patch below applied (it removes vcc3v3-pcie-regulator nodes and modifies ep-gpios in &pcie0 to use GPIO1_A0):

From 8abd7c990fc6f052f335b71df009ec8b88f57a88 Mon Sep 17 00:00:00 2001
From: ArXen42 <arxen42@tutanota.com>
Date: Sun, 13 Apr 2025 19:05:52 +0300
Subject: [PATCH] Changed GPIO1_A0 on Orangepi 4 LTS from static power
 regulator to PCI-E PERST pin

---
 .../dt/rk3399-orangepi-4-lts.dts              | 20 +------------------
 1 file changed, 1 insertion(+), 19 deletions(-)

diff --git a/patch/kernel/archive/rockchip64-6.14/dt/rk3399-orangepi-4-lts.dts b/patch/kernel/archive/rockchip64-6.14/dt/rk3399-orangepi-4-lts.dts
index c79940457..41eece5a4 100644
--- a/patch/kernel/archive/rockchip64-6.14/dt/rk3399-orangepi-4-lts.dts
+++ b/patch/kernel/archive/rockchip64-6.14/dt/rk3399-orangepi-4-lts.dts
@@ -128,17 +128,6 @@
 		};
 	};
 
-	vcc3v3_pcie: vcc3v3-pcie-regulator {
-		compatible = "regulator-fixed";
-		enable-active-high;
-		gpio = <&gpio1 RK_PA0 GPIO_ACTIVE_HIGH>;
-		pinctrl-names = "default";
-		pinctrl-0 = <&pcie_drv>;
-		regulator-always-on;
-		regulator-boot-on;
-		regulator-name = "vcc3v3_pcie";
-	};
-
 	vcc3v3_sys: vcc3v3-sys {
 		compatible = "regulator-fixed";
 		regulator-name = "vcc3v3_sys";
@@ -899,7 +888,7 @@
 
 &pcie0 {
 	status = "okay";
-	ep-gpios = <&gpio2 4 GPIO_ACTIVE_HIGH>;
+	ep-gpios = <&gpio1 0 GPIO_ACTIVE_HIGH>;
 	num-lanes = <4>;
 	max-link-speed = <1>;
 };
@@ -1095,13 +1084,6 @@
 		drive-strength = <12>;
 	};
 
-	pcie {
-		pcie_drv: pcie-drv {
-			rockchip,pins =
-				<1 RK_PA0 RK_FUNC_GPIO &pcfg_pull_none>;
-		};
-	};
-
 	hdmi {
 		/delete-node/ hdmi-i2c-xfer;
 	};
-- 
2.49.0

While this doesn't address schematic problem (we still don't control PERST signal directly), this seems to work nontheless. I think it works because now the following happens:
1) Driver powers off PCIe device (thinking it set PERST signal to low)
2) Driver sets clocks and other PCIe machinery necessary
3) Driver powers on the board, but this time the clock signals are already up and running, so Wi-Fi/SSD/whatever chip initializes propely.

At least, that's how I interpret what's happening in driver code below.

static int rockchip_pcie_host_init_port(struct rockchip_pcie *rockchip)
{
	struct device *dev = rockchip->dev;
	int err, i = MAX_LANE_NUM;
	u32 status;

	gpiod_set_value_cansleep(rockchip->perst_gpio, 0); // <--- this powers off PCIe device

	err = rockchip_pcie_init_port(rockchip);
	if (err)
		return err;

	/* Fix the transmitted FTS count desired to exit from L0s. */
	status = rockchip_pcie_read(rockchip, PCIE_CORE_CTRL_PLC1);
	status = (status & ~PCIE_CORE_CTRL_PLC1_FTS_MASK) |
		 (PCIE_CORE_CTRL_PLC1_FTS_CNT << PCIE_CORE_CTRL_PLC1_FTS_SHIFT);
	rockchip_pcie_write(rockchip, status, PCIE_CORE_CTRL_PLC1);

	rockchip_pcie_set_power_limit(rockchip);

	/* Set RC's clock architecture as common clock */
	status = rockchip_pcie_read(rockchip, PCIE_RC_CONFIG_LCS);
	status |= PCI_EXP_LNKSTA_SLC << 16;
	rockchip_pcie_write(rockchip, status, PCIE_RC_CONFIG_LCS);

	/* Set RC's RCB to 128 */
	status = rockchip_pcie_read(rockchip, PCIE_RC_CONFIG_LCS);
	status |= PCI_EXP_LNKCTL_RCB;
	rockchip_pcie_write(rockchip, status, PCIE_RC_CONFIG_LCS);

	/* Enable Gen1 training */
	rockchip_pcie_write(rockchip, PCIE_CLIENT_LINK_TRAIN_ENABLE,
			    PCIE_CLIENT_CONFIG);

	msleep(PCIE_T_PVPERL_MS);
	gpiod_set_value_cansleep(rockchip->perst_gpio, 1); // <--- this powers PCIe device back on after all clocks are set up

	msleep(PCIE_T_RRS_READY_MS);

	/* 500ms timeout value should be enough for Gen1/2 training */
	err = readl_poll_timeout(rockchip->apb_base + PCIE_CLIENT_BASIC_STATUS1,
				 status, PCIE_LINK_UP(status), 20,
				 500 * USEC_PER_MSEC);
	if (err) {
		dev_err(dev, "PCIe link training gen1 timeout!\n");
		goto err_power_off_phy;
	}

If you continue to encounter problems with this approach, one other option left is to modify the board itself by rerouting GPIO1_A0 signal to PERST, and leaving 3v power always on, but this will require some soldering work.

Changed-GPIO1_A0-on-Orangepi-4-LTS-from-static-power-to-PERST.patch

Images with 5.15.x kernels dont have this issue. 

Help me out, please. Begginer 

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!

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.

I was experimenting with all ARM images (Manjaro, Fedora, Arch, etc) i could find to test with the Orange Pi 4 LTS SBC board, and when i was about to return to armbian, it didnt boot anymore, not even from the SD card flashed with a proper image. I' currently using UART USB to TTL debug device to see whats happening with the board and it returns this:

NOTE: [At the moment of this screenshot the board was with a SD card flashed with the default orange pi debian server image]

Does anyone know how to reset this board and get it booting again from any ARM images?

Would really appreciate any help on this to discover what i did mess up...

Thanks in advance

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.

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

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? 

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?

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

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?

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!!

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

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

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

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!

The pi is an orange 4 LTS with 3gb RAM and 16gb EMMC.

I have a 2tb crucial SSD attached through the usbc port.

It is powered by a 4A supply through the DC port.

it's purpose is to be a dedicated mythtv back end; it is wired by ethernet but also has wifi active.

armbian-hardware-monitor.log is at https://paste.armbian.com/axayequliz 

it isn't showing up as a disk, as near as I can tell:

Quote

 

mythbackend:~:% ls /dev/disk/by-id   

mmc-AJTD4R_0x81704fbd  mmc-SC16G_0x9345afab  mmc-SC16G_0x9345afab-part1

 

the first is the EMMC, I believe, and the second my sandisk card.

I haven't used linux since the late 90s when I switched to FreeBSD, and so much has changed . . .

https://paste.armbian.com/fecegemiwe

What can I do with it?

Just FYI I am seeing the same thing on an Orange Pi 4 LTS that I am setting up, what worked for me was to unplug the keyboard to let the boot start, then plug it in later.

I tried 2 keyboards and both USB 2 & 3 ports, and the problem is consistent, if I boot with the kb plugged in the HDMI remains dead.

Franck

The bundled kernel with the OS image does not kernel panic. (However this image only has around a 5% chance of mounting any nvme drive)

Output:
 

Quote

[   22.057154] Kernel Offset: disabled
[   22.057155] CPU features: 0x800820f1,20000846
[   22.057159] Memory Limit: none
[   22.081651] ---[ end K panic - not syncing: Asynchronous SError Interrupt ]---
[   22.521737] ------------[ cut here ]------------
[   22.5217] WARNING: CPU: 4 PID: 1559 at kernel/sched/core.c:3027 set_task_cpu+0x168/0x230
[   22.521748] Modules linked in: hci_uart btqbtrtl btbcm btintel bluetooth dw_hdmi_i2s_audio dw_hdmi_cec snd_soc_hdmi_codec snd_soc_rockchip_2s snd_soc_rockchip_pcm hantro_v rockchip_vdec(C) rockchip_iep v4l2_h264 rockchip_rga videobuf2_dma_contig snd_soc_simple_card snd_soc_es8316 snd_soc_simple_card_utils videobuf2_vmalloc v4l2_mem2mem videobuf2_dma_sg videobufemops fusb302 tcpm typec videobuv4l2 snd_soc_core videobuf2_commdeodev snd_pcm_dmaengine snd_pcm mc cpufreq_dt snd_timer snd soundcore tcp_bbr binfmt_misc sch_fq ads7846 fbtft(C) sprdwl_ng nfs80211 auth_rpcgss nfs_acl lockd sprdbt_tty grace rfkill sunrpc ramoops ree   22.521832] CPU: 4 PID: 1559 Csmartd Tainted: G         C        5.15.79-rockchip64 #trunkac_rk spidev stmmac_platfostmmac pcs_xpcs adc_keys pwm_bl
[   22.521836] Hardware name: OrangePi 4 LTS (DT)
[   22.521841] pc : set_task_cpux168/0x230 -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[   22.521845] lr : try_to_wake_up+0x1a4/0x584
[   22.521849] sp : ffff800009dfbd80[   22.521850] x29: ffff800009df80 x28: ffff0000f77832c0 x27: ff00bb3b7e0
[   22.521855] x26: ffff80000973d008 x25: ffff800009aadbf0 x24: 0000000000000005
[   22.521859] x23: ffff0000061c24a22: 00000000000000c0 x21: 0000000000000020
[   22.521864] x20: 0000000000000005 x19: ffff0000061c1d80 x18: fffffffffffee708
[   22.521868] x17: ffff8000ee041000 x16: ffff800009dfc000 x15: 00000000004000
[   22.521872] x14797341203a676e69 x13: 2d2d2d5d20747075 x12: 727265746e492072
[   22.521876] x11: 000000000000000 x10: ffff8000ee041000 x9 : 0000000000000004
[   22.521881] x8 : 0000000000000020 x7 : ffffffffffffe0 x6 : 0000000000000005
[   22.521885] x5 : 00000000000004 : 0000000000000001 x3 : 000000000000003f
[   22.521889] x2 : ffff0000061c1d80 x1 : ffff80000999e8 x0 : 0000000000000000
[   .521893] Call trace:
[   22.521894]  set_task_cpu+0x168/0x230
[   22.521899]  try_to_wake_up+01a4/0x584
[   22.521902]  wake_up_process+0x18/0x2c
[   22.521rtimer_wakeup+0x20/0x40
[   22.521913]  __hrtimer_run_queues+0x17c/0x340
[   22.521915]  hrtimer_interrupt+0xf4/0x250
[   22.918]  arch_timer_handler_phys+0x34/0x44
[   22.521923]  handle_percpu_devid_irq+0xa4/0x240
[   22.521929]  handle_domain_irq+0x98/0xe4
[   22.521932]  gic_handle_irq+0x54/0x130
[   22.521936]  call_on_irq_stack+0x28/0x5c
[   22.521940]  do_interrupt_hx54/0x60
[   22.521943]  el1_interrupt+0x30/0x80
[   22.521947]  el1h_64_irq_handler+0x18/0x24
[   22.521951]  el1h_64_irq+0x0x7c
[   22.521953]  __delay+0x90/0xb0
[   22.521958]  __const_udelay+0x2c/0x40
[   22.521961]  panic+0x324/0x35c
[   22.521]  nmi_panic+0x8c/0x90
[   22.521966]  arm64_serror_panic+0x64/0x74
[   22.521969]  do_serror+0x58/0x60
[   22.521971]  el1h_64_error_handler+0x30/0x50
[   22.521976]  el1h_64_error+0x78/0x7c
[   22.521978]  preempt_count_sub+0x44/0xdc
[   22.521981]spin_unlock+0x1c/0x44
[   22.521984]  nvme_submit_cmd+0xf0/0x110
[   22.521987]  nvme_queue_rq+0x380/0x8f0
[   22.521990]  blq_dispatch_rq_list+0x124/0x7ec
[   22.521992]  __blk_mq_sched_dispatch_requests+0xb4/0x154
[   22.521995]  blk_mq_sched_dispatch_requests+0x38/0x74
[   22.521998]  __blk_mq_run_hw_queue+0x5/0x90
[   22.522003]  __blk_mq_delay_run_hw_queue+0x1bc/0x1e0
522007]  blk_mq_run_hw_queue+0x94/0xfc
[   22.522011]  blk_mq_sched_insert_request+0xf4/0x120
[   22.522014]  blk_execute_rq_nowait+0x5c/0x90
[   22.522018]  blk_execute_rq+0x48/0xf0
[   22.522021]  nvme_execute_passthru_rq+0x6c/0x2e0
[   22.522025]  bmit_user_cmd+0x23c/0x3d0
[   22.522029]  nvme_user_cmd+0x13c/0x240
[   22.522032]  nvme_dev_ioctl+0xf0/0x260
[   22.522036] rm64_sys_ioctl+0xac/0xf0
[   22.522041]  invoke_syscall+0x48/0x114
[   22.522044]  el0_svc_common.constprop.0+0x44/0xec
[   222048]  do_el0_svc+0x24/0x90
[   22.522052]  el0_svc+0x20/0x60
[   22.522055]  el0t_64_sync_handler+0xe8/0x114
[   22.522060]  el0t_64_sync+0x1a0/0x1a4
[   22.522062] ---[ end trace 66009970b353284 ]---

Dump from 'armbianmonitor -U'

https://tmpfiles.org/dl/314994/dump.txt.tar

(The Armbian self-hosted system seems to be a bit moody when it wants to work)

Unfortunately the whole time I've owned this device - doing a kernel update via armbian-config will just stop your device from booting and even outputting to the display.

Is there a repo just with the precompiled kernels in .deb form?

I downloaded Armbian 22.05 Jammy XFCE for Desktop.

When I boot up my Orange Pi 4 LTS everything looks good.

The first problem was a Wi-Fi 5G password (system dont recognize my password), only 2.4G works.

The second problem (and the main problem) was a display - when X start, my display turn off (I have HDMI-connection).

What I am doing wrong?