All Activity

Hi Igor, I recently updated to Armbian 25.11.2 bookworm aarch64 with kernel Linux odroidhc4 6.12.58-current-meson64. This should be a working version? There I still get the same connect-debounce error. Do you have any advice?

Hi all, i've been going this forum long enough to try and root a tv box that i buyed recently, but this one is HEAVILY locked up, like nothing i have seen before. My objective here is to access 'su' so i can have access to rooting/overclocking this thing for emulators, and after that adding a heatsink, active cooling, etc. I tried ADB over all USBs (4 in total) but nothing. then i tried to see if root was available through some leftover app or vulnerability, but nothing. Then i tried following the specs from this thread (pretty similar in design to my PCB) but my UART displays nothing. (I leave the images from my setup below), i tried switching the wires, i tested the voltages and they return 3.3v, so they are ok. I tried the toothpick method to access recovery, but it has 2 buttons. 1 does nothing (AFAIK) and the other one goes directly to updating, so no menu. Any help is appreciated, as i'm out of any ideas. I leave my pictures below, and my specs: CPU: Alwinner H313 RAM: 1GB ROM: 8GB PCB: Z01S-v13.3, 2025.05.20 OS: Android 7-8 ish

Well, this version of the PCB seems the most locked up of all. I tried ADB with all USBs, no dice, no root, i soldered the wires to the UART test pins (See image below) but with my setup (also see image below) i could not get any logs via TIO in Linux. Also, the toothpick method does not shows a menu, but goes straight to updating, so ALSO there is locked up, so i cannot go to recovery. Any ideas? i'm pretty out of ideas at this point. Are the wires badly soldered? both shows 3.3V, so i suppose not. Is my USB-To-TTL badly configured? Btw, my PCB is Z01S-v13.3, 2025.05.20. Any help is appreciated.

$ grep TARGET config/boards/pine64.conf KERNEL_TARGET="current,edge,legacy" KERNEL_TEST_TARGET="current" So, you can compile either current, edge or legacy for your board. Stick the desired string in the BRANCH switch and off you go. What kernel that is depends on the board or board family and in your case you can check config/sources/families/include/sunxi64_common.inc to find that as of today edge=6.16, current=6.12 and legacy=6.6. So, 6.2 to 6.5 is not an option. But you could always go back to an earlier git state of the build framework or add your own targets. Why do you need those specific kernels?

Also, interesting to see your updates. I keep seeing a lot related to GStreamer, will need to look more into that.

I think you are looking for the "kernel" build command. Have a look at some of the others as well like kernel-config or dts-check.

Thank you for your thoughts @usual user. I'm stuck with how to use Fedora as a root filesystem with Armbian. I'm reading that it's possible to use Fedora with the SBC, and I'm understanding it will work successfully with 6.18, but I think the expectation is to start with the raw distro, not anything Armbian related. Would be happy to learn I'm missing something, but current expectation is to skip Armbian and start with Fedora and build it all from the ground up.

Thank you for sharing your findings with the community!

thank you for your work, @Nick A Is this being pushed back to Armbian itself eventually?

not sure what the current state of this is, but i think megi always had a hack to make it working in their trees - maybe just try to apply the corresponding patch from the last commits of https://codeberg.org/megi/linux/commits/branch/pbp-6.18 to your kernel build and see if it works? good luck and best wishes - hexdump

Rebuilding all the image doesn't represent much more time than the time to recompile the kernel. I can't advise to download the linux source to the armbian SBC, because you would also need the armbian patches. One thing I use for debugging of DTS (and maybe linux kernel modules) taking control of GPIO is: sudo cat /sys/kernel/debug/gpio

Yes. Try the latest kernel. The latest is always the one with the most corrections (unless someone discovers an error). How do you select a H616 vs H618 kernel? I always select Unsupported Board > Orange Pi Zero 3

Urgently go back to the previous selection of dtbos in armbian-config. Just having 1 undesired dtbo may interfere with everything else. Then try adding: overlays=analog-codec in armbianEnv.txt And check the lsmod again

I am lost, confused by your explanation. Are you trying to use the Orange Pi zero 3 and RED LCD ili9488? The solution is: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-208446 What did you mean by "booting to 16 bit"?

That photo tells me that you have the SPI and GPIO configuration right. Keep that. The completed solution for orange pi zero 3 and ili9341 is: https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#comment-204672 Copy the parts within the ili9341:ili9341@0 {} section, while keeping your gpio

Okay, trying another HDMI cable fixed it, although on radxa's debian it worked with the same cable but thanks.

This also happens on other kernels. Issue is present on final 6.18.0 kernel as well as on the older 6.12 kernel. It seems to be related to some kernel options that are set to "m". Need to figure out which kernel options would need to be set to "y" (built-in) on Armbian to avoid this issue on power-on.

I do not have your board but have you tied looking in armbian-config?

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + GE-proton-10.25 (https://github.com/GloriousEggroll/proton-ge-custom) + DXVK-stripped v1.6.1 ~60fps@1080p Half Life 2

Because the compatibility, I can't get the libMali driver to work with 32bit games (DXVK specifically). Also, although 64bit games work with the libMali, most of the games I have tested are black screen, or missing textures. Thanks for the sharing, I will try it later.

I ran into a similar issue, I think it was related to having the wifi usb adapter plugged in at the same time. after a second reboot with the adapter unplugged I was able to get to the first run setup screen and set the root password and create my local user account. new to armbian, replaced a failed image from the stock odroid c1+ ubuntu 18 release with the latest, was happy to get it up and running, as we used this board to drive our home 3d printer. unrelated - i did apply to be a board maintainer, happy to help if/when/where I can

Hello, electronics enthusiasts, I can't figure out how to activate the i2s bus and enable audio input and output, for example pcm5102(DAC) and pcm1808(ADC) My board Nano pi neo2

Sorry I am an amateur on rk3588. If libMali have better performance. But why most of you are using PanVk?

Hey @Sergey Lepeshkin, your information proved very helpful! I have a tv box in the same vein as yours, but mine is version Z01S-V13.3, so they probably revised it a little bit. Thanks for finding the UART pins! I will try it out and post what I find! My objective here is to overclock it, install active cooling and a heatsink, and see how it runs some emulators. Btw, quick question, performance wise the box would be faster on Armbian or Android? Thanks!

Hi @wolf7250, The $PWD is an environment variable that represents the current working directory. The lone period "." also represents the current working directory. $PWD has nothing to do with your password - unless your folder names are the same as your password and/or vice versa. As to your question, yes, I would think a fresh reinstall from scratch is going to be the best way forward. But I have no idea how easy that will be with transferring OMV settings from old to new etc. OMV is unbeknownst to me. On the other hand, if the workaround with the new load addresses in `armbianEnv.txt` work (and they seem to work just fine) it's more of a matter of how "correct" you want your situation to be. Things seems to be working. Groetjes,