Active threads

Share your displaying configuration by running "neofetch" and post it here. If your X11 is running on top of framebuffer, instead of DRM, it wont work. I also would like to get more debug from cedrus, linux's v4l2... but at least you can add -v to mpv to get more debug You only need the ffmpeg plugins offered by the original poster of the v4l2-request thread This is tested with mpv player only. v4l2-util and -ctl are only useful for webcams and video capture devices. v4l2loopback is not involved here. I don't have it I have an orange pi zero LTS, but I havent tested it there (I would use an SPI LCD, since it doesn't have an HDMI prot)

For debian problems, do what I do: Get the cheapest raspberry Recreate the problem Ask the question in the raspberry forum Apply solution to Armbian XD

Oh, sorry, I didn't notice the non-existent 6 and read it as Helios64. Of course, my description of the boot method is not limited to Rockchip devices; it works on all for which a mainline U-Boot is available. I have used it on iMX6, LX2160A and S922X devices, but my remaining devices are all based on Rockchip. The solutions are too varied to present a turnkey solution here. However, I am sure that only a corresponding configuration for implementation is required to achieve the desired behavior, but for that, the U-Boot documentation must be consulted to decide which solution should be chosen.

If tester is not available, I'd try powering failing ports with their respective cables but feeding them from pins powering other ports (eg with wires from some molex cable, just need to be careful with polarity and shortcuts) and then powering working ports from pins on the board feeding failing ports - to exclude failure of the power rail feeding these ports on the board. If cables are faulty, I'd check them for electrical connections and if they are ok, would replace capacitors.

What I like to do in such a case is link to archive.org. some spam got posted to this thread which I removed, so I felt like I might as well add an answer at the same time

fair enough, no idea where i would get the right android image from for my unknown box so I guess I am stuffed putting Armbian on my box. never mind, will repurpose an old laptop when corelec updates for the s905x2 stop thanks for the help

HP Pavilion8 core processor, 32Gig RAM laptop. I wanted to limit information to limit time for digging into it, but here they are: log-build-322ed1c8-a4db-4873-85ac-be8e6a87fbd6.log.ans summary-build-322ed1c8-a4db-4873-85ac-be8e6a87fbd6.md

dig through the github actions, how the images are compiled is public information ;-)

probably time for the serial console my suspicion tells me that it will be hard to get proper logs otherwise my suspicion is that some umounts does not come back. <- try to unmount everything you can before the reboot and see if that helps.

This is great. Apparently mine didnt persist after reboot either, yours seems to be permanent and working even better. Thanks!

spendist is the maintainer of the Nanopi Neo. Maybe he has something to say. Did you try another kernel? Another OS?

A google search indicates that the MXQ Pro 4K 5G often uses a RK3229 quad-core CPU

@dale it seems like vfd-convert has not worked well. Perhaps because of some mix between script version and the template files version. Whatsoever, I've looked closer at the patch link you previously posted, this is the older pre-review dt-bindings syntax. You should be go to start with something like: /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&gpio 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&gpio 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&gpio 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; titanmec,digits = [00 01 02 03]; titanmec,segment-mapping = [03 01 02 06 04 05 00]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_ALARM; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_USB; }; led@4,2 { reg = <4 2>; function = "play"; }; led@4,3 { reg = <4 3>; function = "pause"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = LED_FUNCTION_LAN; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_WLAN; }; }; }; }; Note that I haven't tested it, just made it from some copy-paste. If it doesn't work, even partially, you would most likely need to replace &gpio with the right reference to the gpio controller wired to the display.

Hello, I am new to arm board, I had this android tv stick called S moon mx10 5G, it have rk322x cpu, 2GB Ram, and ap6330 wifi chip. I tried armbian on this device but wifi chip was not detected, I tried using "rockchip-rk3318-box-wlan-ap6330.dtbo" as user_overlays, but still not working, could anyone tell me how to make this wifi chip working on rk322x armbian?. I attached some files for information: dmesg.txt s_moon_mx10_5g.dts

Hey Guys, I know this post is old but I have some questions. I was following @Jaybyrd's instructions and I have a question pertaining to the Plugin USB-C to the power on the device "I am assuming that is on The OPi5 device." Am I supposed to plug in something else? Because it says to open a terminal "what terminal? On what device?" Thank you for your time, Michael

I wouldn't be so categorical - I have rock pi 4b, which never saw android or any os other than armbian, which has same thing- two boot devices on emmc. Since it doesn't bother me, I didn't investigate further.

If the card still mounts, try running fsck first. If it’s clean but won’t boot, you can copy fresh /boot files from the same Armbian release. Otherwise, reinstalling to a new SD and restoring your data may be the safer route.

I faced a similar Ethernet throughput issue on Armbian under high latency. One thing that helped was using a USB Ethernet dongle instead of the onboard NIC. To simulate latency, you can use the tc command: sudo tc qdisc add dev eth0 root netem delay 200ms sudo tc qdisc del dev eth0 root For more solutions, check out this.

I have a ssh connection with my TV BOX (it is a AMLOGIC with S912), in my etc/ssh/sshd_config I have "UsePAM yes" and without any delay for connection, and probably it was not the problem of your delay in the start connection. In addition, I installed a vnc service to work remotely using the graphical interface. Either ssh and vnc Viewer (xtightvncviewer in my Debian Desktop) run pretty well. Please, check your basic network services, as well, fix the IP in the TV BOX. In my case I did some adjusts such: cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.15.22 netmask 255.255.255.0 gateway 192.168.15.1 dns-nameservers 8.8.8.8 1.1.1.1 There are some network services that can be impling in your delay by ssh (it is robust, old and fast application of Linux) I hope to help you too.

Hi everyone, i manage to extract the .dtb file from the recovery partition of the rk3528-X88pro13-android. This is the board number : X88PRO 13-D4-V1.1 (2023-04-12). Maybe it will be useful to someone 😉 rk3528-x88pro13-android.dtb

Overlay was renamed at some point to just uart5 `/boot/dtb/allwinner/overlay/sun50i-h616-uart5.dtbo` (without `ph5`), so `overlays=uart5` works and is available at /dev/ttyS1

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

nice, thank you for your feedback

hi, I am unable to boot Armbian on Gamebox G11 Pro. I am able to boot CoreElec and Emuelec easily via sd card. I have tried every tip and trick to boot it, lot of Armbian versions and forks. Can you suggest a suitable armbian dtb file for the same. The most reliable method to boot it.

Great to see continued development for RK3318/RK3328 boards, Armbian support really helps unlock their full potential for lightweight Linux projects.