Search the Community

The Wi-Fi network was working fine, I saw all the wireless connections. But I did something in the upper right corner of the system (in my opinion, I unchecked the Wi-Fi network) and as a result I can't restore the WiFi network. I only have wired internet now., and in the upper right corner, please help me solve the problem.

Hi there! I've just compiled from armbian buil tools a new image for Orange Pi 3 LTS. Then flash it on sdcard, anything was well, but armbian doesn't start at all. Nothing on the HDMI, nothing on the debug serial. Also LED doesn't light. I've tried two images: ubuntu jammy with GNOME and next case XFCE. Both cases didn't work. I've downloaded prebuilt image from armbian.org and it starts well. In my opinion, some problem with custom images in u-boot. but I don't know how to give a diagnosis.

Under kernel 4.9, using a usb3.0 to Gigabit interface with RTL8153b card, the upstream and downstream speed can reach Gigabit. But with kernel5.10, the speed can't reach gigabit, and the driver file has been changed to the latest version, but still no effect. kernel5.10 Speed measurement root@orangepi3-lts:~# iperf3 -c 192.168.3.201 Connecting to host 192.168.3.201, port 5201 [ 5] local 192.168.3.146 port 44376 connected to 192.168.3.201 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 24.8 MBytes 208 Mbits/sec 0 147 KBytes [ 5] 1.00-2.00 sec 23.5 MBytes 198 Mbits/sec 0 147 KBytes [ 5] 2.00-3.00 sec 23.5 MBytes 197 Mbits/sec 0 147 KBytes [ 5] 3.00-3.15 sec 3.66 MBytes 202 Mbits/sec 0 147 KBytes root@orangepi3-lts:~# iperf3 -c 192.168.3.201 -R Connecting to host 192.168.3.201, port 5201 Reverse mode, remote host 192.168.3.201 is sending [ 5] local 192.168.3.146 port 44380 connected to 192.168.3.201 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 47.5 MBytes 399 Mbits/sec [ 5] 1.00-2.00 sec 48.4 MBytes 406 Mbits/sec [ 5] 2.00-2.99 sec 48.1 MBytes 406 Mbits/sec root@orangepi3-lts:~# lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

With Armbian 22 (kernel 5.15 and bullseye/jammy) the Orange PI 3 LTS worked great including WiFi, ETH, Bluetooth. Partly thanks to @Ukhellfire and @going. Downloadable here: https://xogium.performanceservers.nl/archive/orangepi3-lts/archive/ Below is what I find the status is for the new Armbian 23 images provided for here : https://www.armbian.com/orangepi3-lts/ Branch current: Main downloads Armbian 23 with kernel 6.1 bookworm: It boots, but every 3rd or 4th keystroke is ignored. No ETH, no WiFi. Armbian 23 with kernel 6.1 jammy: It boots, keystrokes are OK, ETH is OK, but WiFi doesn't work. Branch edge: Rolling release downloads Armbian 23 with kernel 6.4 bookworm: Doesn't boot, no board lights come on. Armbian 23 with kernel 6.4 lunar: Doesn't boot, no board lights come on. Branch edge: When I build myself There doesn't seem to be any selection to make edge boot regardless of kernel (5.15, 6.1 or 6.4) or bookworm/bullseye. Branch current: When I build myself I found a way to get a good build of Armbian 23: use branch current with legacy kernel 5.15: 1) Checkout the last current commit: https://github.com/armbian/build/commit/6af50cfcdd46661038fd30c71548362012df6438 2) Edit config/boards/orangepi3-lts.csc and add support for legacy kernel: KERNEL_TARGET="legacy,current,edge" 3) Build legacy bullseye: ./compile.sh build BOARD=orangepi3-lts BRANCH=legacy RELEASE=bullseye @Igor I can send free Orange PI 3 LTS boards to US based Armbian contributors if it can improve community support of this board.

Hello everyone! Yesterday I downloaded "Armbian 23.5 Jammy". Unfortunately the integrated wifi module does not work. I tried several alternatives but with the same problem. I am not an expert on the subject. Any solution? I'm trying to compile and in one of the steps it tells me that the "Orange Pi 3 LTS - H6" is no longer supported. If anyone knows and can help would be appreciated. https://paste.armbian.com/varepekose Original: Hola a todos! En el dia de ayer descargue "Armbian 23.5 Jammy". Lamentablemente no funciona el modulo wifi integrado. Probe con varias alternativas pero con el mismo problema. No soy un experto en el tema. Alguna solucion? Estoy probando de compilar y en uno de los pasos me toma que la "Orange Pi 3 LTS - H6" ya no esta soportada. Si alguien sabe y puede se agradece la ayuda.

Hi, my Armbian Reports as 23.02.2 with Kernel 5.15.93. According to website there is already 23.5 with Kernel 6.x. How can I upgrade my existing installation? I tried apt update dist-upgrade and the "Update all packages and firmware" option in armbian-config. best regards thommy

I use Armbian_23.5.1_Orangepi3-lts_bookworm_current_6.1.30. I'm trying to download in armbian-config kernel headers, but linux-headers-5.15.93-sunxi64 are downloaded. How to download kernel headers 6.1.30.?

Hello everyone, I encountered an issue while using SPI with my Orange Pi 3 LTS, and now I'm going to share some solutions. Perhaps the Armbian Team can assist me in resolving the final problem. These tests were conducted on Armbian 23.02.2 Bullseye with Linux 5.15.93-sunxi64. The initial step I took to ensure the appearance of `spidev` on the Orange Pi 3 LTS was to include these configurations in `/boot/armbianEnv.txt`. overlays=spi-spidev1 param_spidev_spi_bus=0 param_spidev_spi_cs=0 Note: If `spi-spidev` and `spi-spidev1` are added together, it will not work, and the `spidev` will not appear when using the `ls /dev/sp*` command. After performing the above steps, I executed the `sudo reboot` command, and `/dev/spidev1.0` appeared. root@orangepi3-lts:~/wiringOP# ls /dev/sp* /dev/spidev1.0 However, this alone was insufficient to ensure proper functionality of SPI. I attempted to send a message to an ATMega 168p using a Python script that utilizes the `spidev` library. The script is below: import spidev spi = spidev.SpiDev() spi.open(1, 0) spi.max_speed_hz=10000 payload = [0x0c, 0x00] spi.xfer(payload) print(*payload[1:]) The ATMega 168p occasionally received the message, and sometimes it did not. I suspected that the issue might be related to the MISO or MOSI connections. To investigate further, I directly connected the MISO pin of the Orange Pi 3 LTS to its MOSI pin, testing whether I would receive an echo in the script provided earlier. Indeed, I received the echo successfully. Considering the observations so far, my remaining suspicion lies with the CS (Chip Select) line. If the CS line is not functioning properly, it may fail to select the specific device, resulting in issues with the request/response process (similar to what I experienced). Hence, I proceeded to install wiringOp, on my device. This allowed me to read all the GPIOs of my Orange Pi 3 LTS and check for any anomalies. After successfully building it, I ran the command `gpio readall` and observed the following output: root@orangepi3-lts:~/wiringOP# gpio readall +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 122 | 0 | SDA.0 | OFF | 0 | 3 || 4 | | | 5V | | | | 121 | 1 | SCL.0 | OFF | 0 | 5 || 6 | | | GND | | | | 118 | 2 | PWM.0 | OFF | 0 | 7 || 8 | 0 | OFF | PL02 | 3 | 354 | | | | GND | | | 9 || 10 | 0 | OFF | PL03 | 4 | 355 | | 120 | 5 | RXD.3 | OFF | 0 | 11 || 12 | 0 | OFF | PD18 | 6 | 114 | | 119 | 7 | TXD.3 | OFF | 0 | 13 || 14 | | | GND | | | | 362 | 8 | PL10 | OFF | 0 | 15 || 16 | 0 | OFF | PD15 | 9 | 111 | | | | 3.3V | | | 17 || 18 | 0 | OFF | PD16 | 10 | 112 | | 229 | 11 | MOSI.1 | ALT2 | 0 | 19 || 20 | | | GND | | | | 230 | 12 | MISO.1 | ALT2 | 0 | 21 || 22 | 0 | OFF | PD21 | 13 | 117 | | 228 | 14 | SCLK.1 | ALT2 | 0 | 23 || 24 | 0 | OFF | CE.1 | 15 | 227 | | | | GND | | | 25 || 26 | 0 | OFF | PL08 | 16 | 360 | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ I noticed that the CS pin (GPIO 227) is currently set to `OFF` and needs to be configured as `ALT2` along with `MOSI.1`, `MISO.1`, and `SCLK.1` . This information gave me a clear direction on how to solve my problem. To investigate further, I began checking the device tree configuration using the following commands: `sudo armbian-config` -> `System` -> `Dtc`: ... spi1-pins { pins = "PH4\0PH5\0PH6"; function = "spi1"; phandle = <0x2b>; }; spi1-cs-pin { pins = "PH3"; function = "spi1"; phandle = <0x2c>; }; ... spi@5011000 { compatible = "allwinner,sun50i-h6-spi\0allwinner,sun8i-h3-spi"; reg = <0x5011000 0x1000>; interrupts = <0x00 0x0b 0x04>; clocks = <0x04 0x53 0x04 0x51>; clock-names = "ahb\0mod"; dmas = <0x2a 0x17 0x2a 0x17>; dma-names = "rx\0tx"; pinctrl-names = "default"; pinctrl-0 = <0x2b 0x2c>; resets = <0x04 0x20>; status = "disabled"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x72>; }; ... Upon examining the pinout diagram, I realized that the Orange Pi 3 LTS utilizes SPI1, and all the SPI pins (H3, H4, H5, H6) were correctly configured in the device tree. This led me to speculate that the issue might not be in the device tree itself but rather in the `spi-spidev1 overlay`. To investigate further, I decompiled the `sun50i-h6-spi-spidev1.dtbo` file located at `/boot/dtb/allwinner/overlay/` into a `.dts` file using the command `dtc -I dtb -O dts sun50i-h6-spi-spidev1.dtbo -o sun50i-h6-sp i-spidev1.dts`. Next, I edited the `pinctrl-0` section of the `sun50i-h6-spi-spidev1.dts` file, adding the addresses `0x2b` and `0x2c` (similar to what was done in spi@5011000). /dts-v1/; / { compatible = "allwinner,sun8i-h3-spi"; fragment@0 { target-path = "/aliases"; __overlay__ { spi1 = "/soc/spi@5011000"; }; }; fragment@1 { target = <0xffffffff>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <0x2b 0x2c>; status = "okay"; #address-cells = <0x01>; #size-cells = <0x00>; spidev@0 { compatible = "armbian,spi-dev"; reg = <0x00>; spi-max-frequency = <0xf4240>; }; }; }; __fixups__ { spi1 = "/fragment@1:target:0"; spi1_pins = "/fragment@1/__overlay__:pinctrl-0:0"; }; }; Compiled the modified `sun50i-h6-spi-spidev1.dts` file into a `.dtbo` using the command `dtc -O dtb -I dts sun50i-h6-spi-spidev1.dts -o sun50i-h6-spi-spidev1.dtbo`. Then, I rebooted the Orange Pi 3 LTS. After the reboot, I ran the `gpio readall` command again to check the GPIO pin status: root@orangepi3-lts:~# gpio readall +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | 122 | 0 | SDA.0 | OFF | 0 | 3 || 4 | | | 5V | | | | 121 | 1 | SCL.0 | OFF | 0 | 5 || 6 | | | GND | | | | 118 | 2 | PWM.0 | OFF | 0 | 7 || 8 | 0 | OFF | PL02 | 3 | 354 | | | | GND | | | 9 || 10 | 0 | OFF | PL03 | 4 | 355 | | 120 | 5 | RXD.3 | OFF | 0 | 11 || 12 | 0 | OFF | PD18 | 6 | 114 | | 119 | 7 | TXD.3 | OFF | 0 | 13 || 14 | | | GND | | | | 362 | 8 | PL10 | OFF | 0 | 15 || 16 | 0 | OFF | PD15 | 9 | 111 | | | | 3.3V | | | 17 || 18 | 0 | OFF | PD16 | 10 | 112 | | 229 | 11 | MOSI.1 | ALT2 | 0 | 19 || 20 | | | GND | | | | 230 | 12 | MISO.1 | ALT2 | 0 | 21 || 22 | 0 | OFF | PD21 | 13 | 117 | | 228 | 14 | SCLK.1 | ALT2 | 0 | 23 || 24 | 0 | ALT2 | CE.1 | 15 | 227 | | | | GND | | | 25 || 26 | 0 | OFF | PL08 | 16 | 360 | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+ OPi 3 +---+------+----------+-----+------+ The SPI functionality is now operational, but this solution is not definitive. To address the underlying issue, I need assistance as device trees, kernels, and other aspects of Linux are not within my area of expertise. It seems that the problem with the CS pin is related to an error during the boot process, resulting in an incorrect address assignment. Well, I hope this information proves helpful to others who are experiencing the same issue as I did. Remember: English is not my first language, so there may be some errors.

I'm using Armbian 23.02 Bullseye CLI. I didn't want the HDMI to show the boot system log and TTY1 login screen. According to the armbian documentation, I changed "console=both" to "console=serial" in /boot/armbianEnv.txt. I checked /boot/boot.cmd related to console, and I confirmed that this modification is OK, but it cannot start, uboot printed "Starting kernel..." After that, there is no output, and the power supply is only 5V 170mA. The following is the printing of the serial port. If anyone has been in a similar situation, please give me a little help, thank you very much. U-Boot SPL 2022.07-armbian (Feb 17 2023 - 22:32:08 +0000) DRAM: 2048 MiB Trying to boot from MMC2 NOTICE: BL31: v2.2(debug):a04808c1-dirty NOTICE: BL31: Built : 22:32:01, Feb 17 2023 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc086990, model: OrangePi 3 LTS INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 NOTICE: PMIC: AXP805 detected INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2022.07-armbian (Feb 17 2023 - 22:32:08 +0000) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: OrangePi 3 LTS DRAM: 2 GiB Core: 50 devices, 14 uclasses, devicetree: separate WDT: Not starting watchdog@7020400 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3259 bytes read in 2 ms (1.6 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 204 bytes read in 1 ms (199.2 KiB/s) MMC: no card present ** Bad device specification mmc 0 ** 37640 bytes read in 4 ms (9 MiB/s) 3844 bytes read in 3 ms (1.2 MiB/s) Applying kernel provided DT fixup script (sun50i-h6-fixup.scr) ## Executing script at 45000000 17091365 bytes read in 844 ms (19.3 MiB/s) 21803016 bytes read in 1077 ms (19.3 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=41730000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17091301 Bytes = 16.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 48fb3000, end 49fffae5 ... OK Loading Device Tree to 0000000048f41000, end 0000000048fb2fff ... OK Starting kernel ...

Hi, Is it possible to remap the i2c1 to use the i2c0 default pins via armbianEnv,txt ?. What I want to achieve is to have the PD25 and PD26 to appear as bus 1. Thank you.

Hi, When I scan the I2C with i2cdetect, I get the following, without connecting any i2c device. May I know which device on the motherboard is taking up the three addresses. Thank you sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- 54 -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --

My OPI will turn on but it shows android os via hdmi. I don't have a micro SD card and would like to install bullseye via usb instead. i've attempted ssh into the OPI via wifi and direct usb connect, but it denies the connection. I have the OPI on wifi and can see it on my network. i've tried using android adb to no use. is there a way to install armbian WITHOUT using a micro SD at all?

i am normal write the sd card by rufus, can boot into system, when i use armbian-config install system in emmc boot in emmc after copy i try shut down and remove the sd-card, boot fail, power led no on, how to fix, thanks

Hi all! After upgrading to 6.1.24-sunxi64 on my Orange Pi 3 LTS I lost sound at the audio output. dmesg shows this: platform sound_ac200: deferred probe pending I am a newbie to linux - can you, please, provide me a hint how to install the sound card back or revert to the older kernel with a working sound? Thank you!

Hi all! Sorry about my English. I just started learning Armbian. Please don't scold me for my ignorance. I have an Orange Pi 3-lts. I installed an "Armbian_23.02.2_Orangepi3-lts_bullseye_current_5.15.93" OS on it. Transferred everything to EMMC. Installed Clipper. I started experimenting with the rotation of the display. (everything seems to have turned out as I wanted!) But damn! Wanted more! I wanted the startup process log to not be displayed on the screen when the OS was started. I read somewhere on the Internet: change in armbianenv.txt console = botn on console = serial. I listened and changed. And now I can't manage my OPI. I can't connect via terminal because OPI won't connect to WiFi. I've tried with a network cable. No luck. Please tell me. Is there any way to restore the functionality of my OPI (it has all the clipper settings, I did not have time to make a backup). Or do I just have to start all over again? Thank you in advance for your help!

Hello, I have a problem on my orange pi 3 lts. Namely, I have armbian 23.03 Jammy Xfce installed and on some screens it shows normally, on others the image does not appear. I also tried using the Uart converter and it loads everything normally, but then the following message starts appearing every second. [ 161.905394] panfrost 1800000.gpu: js fault, js=0, status=INSTR_INVALID_PC, head=0xa005bc0, tail=0xa005bc0

How to enable kvm/virtualisation on orange pi 3 lts? I want run windows for arm on qemu with kvm, but in the kernel there is no kvm module . How i can add this module to kernel? I know that the allwinner h6 has support for virtualisation.

I have good temps and was thinking to overclock it but have no idea how to do it.

So I got a new orange pi 3 lts and I have installed armbian bullseye on it, but I can't seem to make it work with my crt TV like my raspberry pi 3 b+, even though I am using the same cable and TV and it still works with my raspberry pi I have tried: -Changing the resolution -Changing the aspect ration But nothing works What am I supposed to do to make my armbian work on my CRT tv??

EDIT: I tried to plug it directly in router and speed is OK now. Weird, but it's fine now. Please close this topic. Hello, I just bought Orange Pi 3 LTS to set it up as small off-site backup using OMV and USB HDD. I installed Armbian_23.02.2_Orangepi3-lts_bullseye_current_5.15.93.img on eMMC and installed OMV using armbian-config. I noticed SMB and FTP speeds are slow (around 90 Mbps) so I installed iperf to test it properly and speed is capped on 94 Mbps. I have gigabit switch and interface is connected with GE, if I plug the cable to other device, it works just fine. So there must be some issue on Orange Pi 3 LTS. I searched the internet and speed should be indeed higher with this device, so maybe there is something that needs to be configured? I tried to reboot and power cycle it, nothing helped, speed is always stucked on 94 Mbps. Anyone have idea, where might be the problem?

Hello there, I am beyond my expertise (that which is already limited) have found a guide. Now the guide uses ili9486 so it was substitute it will ili9341 as well as the build they used official build am using Armbian_22.11.1_Orangepi3-lts_bullseye_current_5.15.80 and int with a new one found in the fbtft library. I also need to translate for Russian with chrome not their are photos of it working but all I get is a white screen. here is my version of the overlay. /dts-v1/; /plugin/; / { compatible = "xunlong,orangepi-3-lts","allwinner,sun50i-h6"; fragment@0 { target-path = "/aliases"; __overlay__ { spi0 = "/soc/spi@5010000"; spi1 = "/soc/spi@5011000"; }; }; fragment@2 { target = <&r_pio>; __overlay__ { spi1_cs1_pin: spi1_cs1_pin { pins = "PA8"; /* - real use PL8 but... error in calculate pin number 360!!!!*/ function = "gpio_out"; output-high; }; }; }; fragment@3 { target = <&spi1>; __overlay__ { pinctrl-names = "default", "default"; pinctrl-1 = <&spi1_cs1_pin>; cs-gpios = <0>, <&r_pio 0 8 0>; /* PL8 */ status = "okay"; debug = <0>; #address-cells = <1>; #size-cells = <0>; spidev@0 { reg = <0>; /* Chip Select 0 */ compatible = "spidev"; spi-max-frequency = <100000000>; status = "disabled"; }; spidev@1 { reg = <1>; /* Chip Select 1 */ compatible = "spidev"; spi-max-frequency = <12000000>; status = "disabled"; }; }; }; fragment@4 { target = <&pio>; __overlay__ { ili9341_pins: ili9341_pins { pins = "PD21", "PD16"; /*RESET, DC_RS*/ function = "gpio_out", "gpio_out" ; }; }; }; fragment@5 { target = <&spi1>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; cs-gpios = <0>, <&r_pio 0 8 0>; /* PL8 */ status = "okay"; ili9341: ili9341@0 { compatible = "ilitek,ili9341"; spi-max-frequency = <32000000>; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&ili9341_pins>; status = "okay"; debug = <0>; txbuflen = <32768>; rotate = <90>; bgr; fps = <60>; buswidth = <8>; regwidth = <16>; reset-gpios = <&pio 3 21 0>; /*RST= PD21 */ dc-gpios = <&pio 3 16 0>; /*LCD_RS PD16 */ init = <0x1000001 0x2000005 0x1000028 0x10000cf 0x00 0x83 0x30 0x10000ed 0x64 0x03 0x12 0x81 0x10000e8 0x85 0x01 0x79 0x10000cb 0x39 0x2c 0x00 0x34 0x02 0x10000f7 0x20 0x10000ea 0x00 0x00 0x10000c0 0x26 0x10000c1 0x11 0x10000c5 0x35 0x3e 0x10000c7 0xbe 0x100003a 0x55 0x1000036 0x28 0x10000b1 0x00 0x1b 0x1000026 0x01 0x10000f2 0x08 0x1000026 0x01 0x10000e0 0x1f 0x1a 0x18 0x0a 0x0f 0x06 0x45 0x87 0x32 0x0a 0x07 0x02 0x07 0x05 0x00 0x10000e1 0x00 0x25 0x27 0x05 0x10 0x09 0x3a 0x78 0x4d 0x05 0x18 0x0d 0x38 0x3a 0x1f 0x10000b7 0x07 0x10000b6 0x0a 0x82 0x27 0x00 0x1000011 0x2000064 0x1000029 0x2000064>; }; xpt2046: xpt2046@1 { compatible = "ti,ads7846"; reg = <1>; status ="okay"; spi-max-frequency = <1000000>; interrupts = <0 10 2>; /* high-to-low edge triggered */ interrupt-parent = <&r_pio>; /* PL10<-----> TP_IRQ= PD24 -irq not possible!*/ pendown-gpio = <&r_pio 0 10 0>; ti,keep-vref-on = <1>; ti,x-min = /bits/ 16 <00>; ti,x-max = /bits/ 16 <0xFFF>; ti,y-min = /bits/ 16 <00>; ti,y-max = /bits/ 16 <0xFFF>; ti,x-plate-ohms = /bits/ 16 <60>; ti,pressure-max = /bits/ 16 <255>; ti,swap-xy = <0>; }; }; }; }; now i did a dmesg | grep spi and the touch is loading but not the tft just not sure how to fix it I also read though a lot of forums for some sort of template for this device but still stumped. [ 2.806604] sun6i-spi 5011000.spi: there is not valid maps for state default [ 2.808054] sun6i-spi 5011000.spi: chipselect 1 already in use [ 2.808076] spi_master spi1: spi_device register error /soc/spi@5011000/spidev@1 [ 2.808097] spi_master spi1: Failed to create SPI device for /soc/spi@5011000/spidev@1 [ 8.667723] SPI driver ads7846 has no spi_device_id for ti,tsc2046 [ 8.667753] SPI driver ads7846 has no spi_device_id for ti,ads7843 [ 8.667756] SPI driver ads7846 has no spi_device_id for ti,ads7845 [ 8.667759] SPI driver ads7846 has no spi_device_id for ti,ads7873 [ 8.668043] ads7846 spi1.1: supply vcc not found, using dummy regulator [ 8.679835] SPI driver fb_ili9341 has no spi_device_id for ilitek,ili9341 [ 8.680032] fb_ili9341 spi1.0: fbtft_property_value: regwidth = 16 [ 8.680043] fb_ili9341 spi1.0: fbtft_property_value: buswidth = 8 [ 8.680049] fb_ili9341 spi1.0: fbtft_property_value: debug = 0 [ 8.680054] fb_ili9341 spi1.0: fbtft_property_value: rotate = 90 [ 8.680060] fb_ili9341 spi1.0: fbtft_property_value: fps = 60 [ 8.680066] fb_ili9341 spi1.0: fbtft_property_value: txbuflen = 32768 [ 8.684745] ads7846 spi1.1: touchscreen, irq 67 [ 8.705549] input: ADS7846 Touchscreen as /devices/platform/soc/5011000.spi/spi_master/spi1/spi1.1/input/input1 [ 9.090648] graphics fb0: fb_ili9341 frame buffer, 320x240, 150 KiB video memory, 32 KiB buffer memory, fps=62, spi1.0 at 32 MHz The guide I used https://4pda.to/forum/index.php?act=search&source=pst&result=posts&sort=dd&subforums=1&username=Ochkariky&noform=1&st=20

Hello everyone, I am new to the world of Orange Pi 3 LTS 1.4 and Armbian. I have very recently installed this os on my Orange, it turns out to work almost everything correctly except Wifi and bluetooth. It is really important for me to get Wifi working for various projects I have in mind and I find armbian very reliable and supported. When I try to connect the Network Manager interface returns: On the net I found various discussions about this but no real solution. Does this happen to you as well? It seems not to recognize the wifi chip. Below is the armbianmonitor: https://paste.armbian.com/iteheqokov NAME UUID TYPE DEVICE Wired connection 1 b8c3175c-4553-3687-b24b-637891fa2ca5 ethernet eth0 FASTWEB-QX8T8v db3814be-0944-404b-b223-580cd79febe4 wifi -- IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY I thank you in advance.

sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2023-02-25 16:50:52 IST; 1h 41min ago Docs: man:bluetoothd(8) Main PID: 1131 (bluetoothd) Status: "Running" Tasks: 1 (limit: 2209) Memory: 1.3M CPU: 402ms CGroup: /system.slice/bluetooth.service └─1131 /usr/lib/bluetooth/bluetoothd Feb 25 16:50:51 orange systemd[1]: Starting Bluetooth service... Feb 25 16:50:52 orange bluetoothd[1131]: Bluetooth daemon 5.64 Feb 25 16:50:52 orange systemd[1]: Started Bluetooth service. Feb 25 16:50:52 orange bluetoothd[1131]: Starting SDP server Feb 25 16:50:52 orange bluetoothd[1131]: Bluetooth management interface 1.21 initialized Feb 25 18:30:10 orange bluetoothd[1131]: Failed to set mode: Failed (0x03) When I try.. I would appreciate any help. sudo rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth bluetooth unblocked unblocked 1 wlan phy0 unblocked unblocked 2 bluetooth hci0 unblocked unblocked bluetoothctl scan on Failed to start discovery: org.bluez.Error.NotReady

Hi, I've got a pair of OrangePi 3 LTS boards running the CLI only install of Debian Bullseye with a kernel of 5.15.89-sunxi64 and all the latest updates applied. But when I run the 'top' command, I always see a load of 1.0 or higher. Even when the system is completely idle. I'm running the system of the eMMC, not SDcards. I realize that this is really more of a cosmetic issue, but I was hoping someone had a suggestion on how to fix it. The system is mostly idle, it's a test box or remote management system, so it's not really critical, and the load doesn't go high anyway. Cheers, John

Hello. Connected via PuTTY. I'm trying to connect to WIFI and I get an error: Connection activation failed: (53) The Wi-Fi network could not be found. Further, all Wi-Fi networks disappear, appear only after a reboot.