All Activity

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,

Thanks @laibsch, I took a look at the build framework, bvut couldn't see how to use/build a specific kernel version. I need to experiment with kernels 6.2 - 6.5

Steam games are working now, I tested some games a week ago. But the steam client alone took ~5gb. So, I would not recomend unless you have a 16gb board.

I am using hangover-10.18, which is Fex-Emu 2510. https://github.com/AndreRH/hangover/releases/tag/hangover-10.18 I didn't benchmark. But I think rn, the main bottleneck is the GPU (PanVk driver is now only ~60% performance of the libMali driver).

Another video you'd like to see.

So, would I replace that line with ${PWD:<my_password>}?

Yes I have been upgrading for several years. I really appreciate the effort you've gone to to send me these commands, but would the best solution be to start again with a fresh install? It would be a lot of work on my part, but if it will give the best outcome?

I tried FEX-emu, but on our devices it's slower. It is optimised for snapdragon while box64 is more optimised for the lower-end SBC ARM-SOC. Here a video I once made about it. Things have changed a lot, fex-emu has matured at lot in this time. I didn't know it was build for steam back then so didn't test that. Also have no steam games that would run.

Have you guys ever try FEX-emu instead of box64? I heard FEX is 10%~20% faster than box64

Hi @wolf7250, You can download the package without installing as follows: cd /tmp/ mkdir fliepeltje cd /tmp/fliepeltje/ apt-get download armbian-bsp-cli-helios4-current dpkg -x armbian-bsp-cli-helios4_*.deb ${PWD:?} Then backup the current bootscript as follows: cd /boot/ sudo cp boot.cmd boot.cmd~org sudo cp boot.scr boot.scr~org Then copy the new bootscript and convert it to U-Boot script format as follows: cd /boot/ sudo cp /tmp/fliepeltje/usr/share/armbian/boot.cmd ${PWD:?} sudo mkimage -C none -A arm -T script -d boot.cmd boot.scr Then reboot to check if all went well. Gr, PS syntax is on purpose, of course you can replace ${PWD:?} with . but that might be easy to miss when reading the instruction.

Hi, Seems you have upgraded for several years already? Perhaps something has changed over the years, meaning that the armbian-bsp-cli package did not get installed somehow. I am not sure what will happen if you DO install that package now, so the safest best would be to just get the bootscript from the package and convert it on your machine. Gr,