All Activity

You have the lspci verbose output so you can work back to get the non-verbose output as well. Should I have anything connected to the PCI lane or not? I know my USB devices work, at least with the internal controller, the question was about what exactly is the output/situation you need me to test.

No risk of "starting a war," as I quite frankly don't give a damn about your opinion. The mitigations the devs have posted are easy to apply, so this is solved as far as I'm concerned. You must be really fun at parties, bedna

I dont need details just lsusb and lspci without switches to see what my image 7.1 discovers on your board Of course you can pług on USB stick to see if it works also make steps like mentioned above to fix wifi aic driver

I'm not sure what "nothing to see with you project" means but above you I've included the most complete lspci there is. I'll send lsusb too, but there won't be much there as it works properly. Do you want me to have something connected to the USB or just print it without anything (it would be one line, unless you want verbose).

@sr4armbian Thanks for your response. I found a way to build the vendor release for my box with kernel 6.xxx. SD card and USB 2.0 flash drive are tested, and HDMI audio, HDMI video, Ethernet, and the front LED display are working so far. I am running it on my eMMC, but the built-in Wi-Fi and Bluetooth modules are not working. I have modified a bit of scripts to remove the HAOS part and create a firmware image that can be flashed directly via the factory flash tool using using usb cable in maskrom mode.

I see it is this board, quite new: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-4A.html You can see at https://github.com/armbian/build/commits/main/config/boards/orangepi-4a.csc that no manintainer is defined, so up to yourself to figure out what is wrong. You need to start with attaching a serial debug cable (see 3 pins next to power key) Also I see this board has SPI-flash, there might be an old U-Boot variant in there that does not work together with mainline based 7.0.x kernel.

To my knowledge, there are two versions of this device: the "old" version and the new version, which has a 6031 Wi-Fi chip. Here are the two DTS files extracted from the original android tv firrmware for each hardware version. Hope it helps. Tanix_TX1_6031_DTS.txt Tanix_TX1_DTS.txt

@Fit Girl The image available here works from emmc. I could not test this with SD card. Please be informed that there is no HDMI display post boot. You have to find out the IP address from your DHCP Server/Router once the box got booted. Post boot you are working on a blind box with command lines. It is working for me though without much issues so far.

Hi guys 1: First, I'm happy to register on your forum. 2: I needed to root my TECLAST T60 IA tablet to test it with some software, and I found this post on your forum. 3: My problem is: #: I followed the rooting steps up to step 5. #: Thinking it was better to install the new firmware first and then proceed with rooting. #: My big mistake was starting the firmware update with PhoenixSuit and the bootloader unlocked. After a while, I got a firmware error, and after restarting, I got this message. 4: I tried to enter fastboot mode by pressing the power button, volume down button, and volume up button, but I can't get into fastboot mode. I hope you can help me figure out how to enter fastboot mode, install the firmware, and then try to root the device.

There is nothing to see with you project. I wish only to know the output from lsusb and lspci. For wifi you probably have to apply Fix 7.1 as above. Driver for aic8800 is not yet supported

Hi everyone. I have this RK3318 chip box running Ubuntu, but I can't enable SSH to reinstall it. It doesn't have a display output port. Is there any way to reinstall the OS without desoldering the eMMC to reflash it? (I don't know how to put it back if I take it off). I've already tried flashing via USB and the RX/TX/GND lines, but neither worked. Model: AROP-01 CPU: Quad-core ARM processor Memory: 2GB System Storage: 64GB eMMC Network Interface: 1 × Ethernet USB Interface: 1 × USB Type-C Power: 5V/2A Dimensions: 103 × 103 × 20 mm Package Contents: 1 × Manual, 1 × Ethernet Cable, 1 × Power Cable Thank you.

Great question — I’d really like to know too! Have you tried a lightweight Android image like LineageOS-microG inside Waydroid, or tweaked the GPU rendering settings?

Today I noticed that last Sunday a community version of Armbian was released with Orange Pi 4A support. I tried to flash it in different ways just in case, but it just wouldn't boot. I used BalenaEtcher, Rufus and Armbian Imager and neither of them worked. Im new in this stuff, so I wanted to know if someone could tell me if it is something I'm doing wrong.

Here's lspci -vvv with an older Radeon: https://paste.armbian.com/zisezuqoza.yaml and boot UART log (it boots but no display is visible) https://paste.armbian.com/asizofulux.sql Here's the same with Radeon RX 550: https://paste.armbian.com/ovinibafux.yaml The kernel complained about missing firmware (for polaris11), which actually was not missing. I had to regenerate initramfs using initramfsctl. After regenerating, the board stopped booting with the card connected: https://paste.armbian.com/qitiwiwoge.yaml Not sure how useful lsusb would be. So it's not super stable yet. I saw that you made these modules built-in. This is not necessary, selecting [M] is enough because then they can be loaded or unloaded (to try passing the card through to a VM I need to blacklist the module, which doesn't work for built-in modules). This is something I can try to do to get display output. Oh and WiFi isn't detected at all but that's probably not a surprise.

Hi, I am assuming that you have a standard Q1 TV Box (Allwinner H313 based). 1) Download Armbian Imager here; 2) Install the version for your operating system; 3) After installing, choose "Manufacturer=ALLWINNER", Board="X96Q TV BOX", Operating system="minimal Trixie current" and Storage ( I suggest a good quality Class 10 SD card); 4) After writing the image, insert the SD card into the available SD slot; 5) Insert a wooden toothpick or a Q-tip into AV/Reset input; 6) Click (kindly) and hold the toothpick and connect the TV Box power supply to the power entry; 7) Release the toothpick after 8-10 seconds. if the HDMI connector is plugged you should see the Armbian initial boot process Note: some TV Boxes don't need items 5, 6 and 7. I hope it helps.

Hi. I've also been having issues with my Orange Pi 5. It seems the problem is that the module was removed from the kernel, but I haven't looked into it in detail yet. The folks at NixOS seem to have solved this issue https://github.com/waydroid/waydroid/issues/2094 I have this specific problem waydroid show-full-ui [22:49:14] Starting waydroid session [22:49:14] RuntimeError: Command failed: % /usr/lib/waydroid/data/scripts/waydroid-net.sh start vnic is waydroid0 sudo /usr/lib/waydroid/data/scripts/waydroid-net.sh start modprobe: FATAL: Module ip_tables not found in directory /lib/modules/6.18.10-current-rockchip64 iptables v1.8.11 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. Failed to setup waydroid-net. My system user@orangepi5:~$ uname -a Linux orangepi5 6.18.10-current-rockchip64 #2 SMP PREEMPT Wed Feb 11 12:42:01 UTC 2026 aarch64 GNU/Linux I'm not a network expert, so I hope someone can help. Are you having the same problem?

Yes, of course, but as you said yourself, there are issues with ethernet on mainline. So you can just use a dongle as a temporary workaround to get a stable (or any) connection.

@iav The kobol dtbs (rk3399-kobol-helios64.dtb) linked in the messages before are patched in the following way having the effect that helios64 is finally stable (see here) : The opp-microvolt values in opp-table-1 are just replaced by the ones given below (for all linux kernel versions). opp-table-1 { compatible = "operating-points-v2"; opp-shared; phandle = <0x0d>; opp00 { opp-hz = <0x00 0x18519600>; opp-microvolt = <0xdbba0 0xdbba0 0x1312d0>; clock-latency-ns = <0x9c40>; }; opp01 { opp-hz = <0x00 0x23c34600>; opp-microvolt = <0xdbba0 0xdbba0 0x1312d0>; }; opp02 { opp-hz = <0x00 0x30a32c00>; opp-microvolt = <0xdbba0 0xdbba0 0x1312d0>; }; opp03 { opp-hz = <0x00 0x3c14dc00>; opp-microvolt = <0xe7ef0 0xe7ef0 0x1312d0>; }; opp04 { opp-hz = <0x00 0x47868c00>; opp-microvolt = <0xfa3e8 0xfa3e8 0x1312d0>; }; opp05 { opp-hz = <0x00 0x54667200>; opp-microvolt = <0x10c8e0 0x10c8e0 0x1312d0>; }; opp06 { opp-hz = <0x00 0x5fd82200>; opp-microvolt = <0x11edd8 0x11edd8 0x1312d0>; }; opp07 { opp-hz = <0x00 0x6b49d200>; opp-microvolt = <0x1312d0 0x1312d0 0x1312d0>; }; };

@humanus Are we talking about the A7S? Doesn't it already have a ethernet port? 😂

@iav individual dts files attached , the other part of the dtb at the top of this thread is to run the eMMC in HS400 mode but that's already in the mainline. The source is this post rockchip-rk3399-l2-cache.dts rockchip-rk3399-op1-opp.dts

Oh Thanks, I'll give a try this way.

Can you give a link to the patches you are talking about? Preferably not on a dropbox or pastebin-like, but to their original source — a repository or mailing list.

Hello, I use this patch since many year now, me and my brother, with out it, our helios64 are unstable and unusable... with it, our helios64 work fine for more than two year, my opinion is, push the file in mainline or distrib the file in mainline with a script that install it fast with only one command run as soon has possible when not crash on the boot.. Bye.

@iav @prahal are you the maintainers of the Helios64 bsp ? I'd be happy to test builds if you don't have physical hardware. My motivation is that it would be useful to be able to download the current image and run it without it hanging or throwing a kernel panic because the build is unstable without patches for the RK3399K on this board. Cheers, Jon

Join us next week in Utrecht for RustWeek! We'll be running a SuperTuxKart tournament to showcase Tyr, the Rust driver for Arm Mali GPUs. Come and see if you've got what it takes! View the full article