Active threads

Thanks for sharing, Nick A This image is working on my device. Now I want to know more about how to create this image. Can you plz share with me any tutorial or documentation on this. Thank a lot

Hello everyone, I am creating a custom Armbian build for OPI5 && OPI5b. The task is as follows: install several packages in the system and fully configure it. While there are no issues with installing packages and configuring the network, there is a peculiarity with the login and password. Specifically, sometimes after writing the image to the emmc opi5b or SD card, the system allows me to log in with my pre-configured credentials, but other times, when flashing the same image, the system simply rejects my pre-set data and displays the message “Login Incorrect.” How I set the initial settings for the system: In /root there is a file called .not_logged_in_yet, from which data is pulled when you first log in to the system, thanks to which it is automatically configured (this method was tested on nanopi m6 and RPI 3b+) and everything worked fine, but for some reason, it is with orangepi 5 && orangepi 5b that I get such artifacts. My .not_logged_in_yet looks like this: # Network settings PRESET_NET_CHANGE_DEFAULTS="1" PRESET_NET_WIFI_ENABLED="1" PRESET_NET_WIFI_SSID="MyWiFi" PRESET_NET_WIFI_KEY="MyWiFiPassword" PRESET_NET_WIFI_COUNTRYCODE=“RU” PRESET_CONNECT_WIRELESS="n" PRESET_NET_USE_STATIC="1" PRESET_NET_STATIC_IP="192.168.1.100" PRESET_NET_STATIC_MASK=“255.255.255.0” PRESET_NET_STATIC_GATEWAY="192.168.1.1" PRESET_NET_STATIC_DNS="8.8.8.8 8.8.4.4" # System settings SET_LANG_BASED_ON_LOCATION="n" PRESET_LOCALE="ru_RU.UTF-8" PRESET_TIMEZONE="Europe/Moscow" # Root settings PRESET_ROOT_PASSWORD="mysecretrootpass" # User creation PRESET_USER_NAME="user1" PRESET_USER_PASSWORD="mypassword" PRESET_DEFAULT_REALNAME="User One" PRESET_USER_SHELL="bash" For my Armbian image, I use the VENDOR 6.1 kernel - ubunu 22.04 jammy. What could be the problem?

@Nick AI don't think it's the same issue.Later, I entered the Android system and used the dd command to flash the x96q tvbox IMG file into the mmcblk. It successfully ran the armbian via eMMC.Next, I will try the x98h Wi-Fi chip driver.Thanks

@buzz89 never heard of it. If you have root access you probably can.

@prahal thank you so much for explaining that. I tried downloading the https://fi.mirror.armbian.de/incoming/prahal/rock-5-itx/archive/Armbian_25.8.1_Rock-5-itx_bookworm_vendor_6.1.115_xfce_desktop.img.xz but Balena Etcher would fail at the end of the validation process. However ... from RoobiOS I can enter that path and it successfully downloads the image and appears to write it successfully to the NVMe drive and then reboots but only gives a single flash of blue SATA III lights and no display. I erased the NVMe partition and tried the Armbian_25.8.1_Rock-5-itx_noble_vendor_6.1.115_minimal.img.xz image with the same result. Same with Armbian_25.8.1_Rock-5-itx_bookworm_vendor_6.1.115_minimal.img.xz - no joy. Eventually I just went with the RADXA OS. It installs KDE Plasma so I've booted to command line and removed KDE and associated packages. Hopefully that effectively gives me a CLI image. Now to work through the error messages in the bootup and remove any unnecessary steps... after I manage to set the default font-size to something that doesn't have me squinting like Mr Magoo 🤣🤣

@Piotr si guess this problem doesn’t exist with miniarch. I’ll have to update my build to 6.16 kernel with warpme patches. I’m busy right now so it might take awhile.

Hello everyone, i somehow compiled u-boot for x96q with 1.5Gb DRAM, and i created "instruction", how i managed to compile it: https://gist.github.com/VMTestik/257c836f1602a64fea8c05ecedc650b0 Maybe it will be helpful or useful

@laibsch thank you. @TonyMac32 any ideas? Update: The Bookworm minimal image does fully boot. Just not Trixie.

above PR is merged

Board: ODROID HC4 Kernel: 6.12.42-current-meson64 Issue: PWM fan control completely non-functional despite software appearing to work Problem Summary: The HC4's PWM fan runs at constant speed regardless of PWM settings. Manual PWM control has zero effect on fan speed, even when setting PWM to 0 (fan should stop/slow) or 255 (full speed). What I've Tried: Hardware Testing: Verified fan wiring with schematic (Pin 1=+5V, Pin 2=GND, Pin 3=TACHO, Pin 4=PWM) Tested with Noctua NF-A4x10 5V PWM fan (confirmed working on other systems) Swapped PWM/TACHO wire positions - no change Software Testing: Manual PWM control: echo 0|50|255 > /sys/class/hwmon/hwmon2/pwm1 - no response Direct PWM chip control: /sys/class/pwm/pwmchip0/pwm0/ - no response Tested different PWM chips (pwmchip0, pwmchip1) and channels Stopped fancontrol service to avoid conflicts Verified PWM files exist and accept values Overlay Testing: Tried existing Armbian overlays: meson-g12-pwm-gpiox-5-fan Copied PWM overlays from official ODROID Ubuntu image: fanspeed-full.dtbo, pwm_a-pwmfan.dtbo, etc. Overlays present in filesystem but show no loading errors or effects System Status: PWM driver loaded: meson-pwm ff802000.pwm: using obsolete compatible PWM devices detected: /sys/class/pwm/pwmchip0, /sys/class/pwm/pwmchip1 Device tree shows: cat /proc/device-tree/pwm-fan/compatible = pwm-fan Fan gets power and runs, but zero PWM response Research Findings: Found GitHub discussion showing HC4 PWM was broken in Armbian (August 2023 merge/revert cycle) where "PWM pulse reading was removed from HC4." This appears to be an ongoing regression in 6.x kernels. Similar issue documented in forum post about ODROID C2 where user had PWM files working but "nothing happen" until they manually patched device tree. What I Want to Contribute: I'd like to properly fix HC4 PWM fan control and contribute the solution back to Armbian. This affects anyone wanting quiet operation or proper thermal management. Need Guidance On: I'm relatively new to device tree development and embedded Linux, but I'm motivated to learn and contribute a proper fix. I'd appreciate guidance on: Where to start - What's the best approach for a beginner to debug device tree PWM issues? Learning resources - Any recommended documentation for understanding Amlogic PWM/device tree development? Debugging methodology - How to compare current vs. working device tree for PWM routing? Development workflow - What tools should I learn for creating/testing HC4-specific overlays or patches? Contribution process - How do device tree fixes typically get submitted and reviewed in Armbian?

So 25.05 and 25.5 are the same version? That threw me off for a while...

True, it's not critical to compile the ideal kernel into the image as long as I get one that works, I can always update it later from within the image. But I do prefer to do things right the first time, and to be utilizing the version I think I am and intend to be using. Btw, I boot from grub as well. For my Orange PI 5 Plus, The edge kernel is the only one that's actually useful to me because the Vendor kernel has no GPU acceleration at all, the Mainline kernel has no video output to my DVI monitor, and all 3 kernel branches aren't correctly utilizing the ES8388 analog audio, which I need. The audio volume is barely audible even when all volume controls are maxed out. It's been that way in every operating system I've tried (except those with old barebones Vendor Kernels from Orange PI). So ultimately I want to compile the latest (relatively) stable edge kernel myself, so I can modify the source code in an attempt to fix the audio, and of course share the solution when / if I find it. I've already found that the ES8388 and ES8328 are compatible - hence the es8328 modules used in the kernel for the ES8388. And I've narrowed down where the issue most likely is: Directory: sound/soc/codecs Files: es8328.h, es8328.c, es8328-i2c.c

Thank you for letting us know and polish up our next release. I'm sure @Igor will have a look shortly.

All I can say about the topic is to give you this link: https://wiki.kobol.io/helios64/pwm/

look into understanding what armbian-config does behind the scenes and replicate that. I think that is a better option anyhow. armbian-config is known to royally screw up your system every now and then.

here is the ouput : @Nick A

If I run a update after changing kernel to edge it doesn't matter the version, it breaks boot, idk why, but it is installing dtb for kernel 6.16 even with kernel 6.13 or 14 installed, current kernel does not support analog audio out of the box and I managed to get it working a few times, so I'm stuck with edge kernel, did a update then changed to edge kernel and disabled armbian updates until this bug is fixed

Hi. I am not complaining. I just would like to understand why I must deactivate https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu/ if I want watching video on Youtube. If it's needed to disable this repo for watching video. I am ok. But why I can't read video with package from this repo? https://paste.armbian.com/vaxedisuda

What does: ffmpeg -codecs | grep hevc show? Even if it seems to support rkmpp, you can guess that it is broken. So install/get a dedicated external encoder. 2 people in this topic tread show working options. I can't help you any more, you need to do your homework so to say.

@Igor how often does netplan run? how possible might it be to sneak in a sed -i -e 's/PermanentMACAddress/MACAddress/' /run/systemd/network/* networkctl reload in my bootup sequence? will DHCP [on ethEXT1] or carrier up/down events break this?

https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/page/11/#findComment-224260 wow, that's a bummer... how can I check if this happens also to my configuration?

At some point we will bump edge to 6.17. These bumps always take time since our patchset on top always needs adjustments. There are 3rd party ppa's for newer mesa. I suggest to use kisak since those are briefly tested. Otherwise go for oibaf which are automated untested, therefore latest mesa packages. In terms of Debian, no clue if there is a similar apt repo for such.

My apologies. I started working on this board again and just spent 3 wasted hours getting angry at the previous wipe eMMC instructions only to realize *I* had the wrong version of RKDevTool. Protip - do not do any hardware development angry, hungry, in a rage, or pressed for time. Wow. Here is the issues with your "erase eMMC" instructions (apparently partly taken from the guide to getting Linux on the T95 Plus): -Config file was loaded, loader, parameters and uboot were written. Board usually does not restart when this is done, restarted once out of my many attempts. -There are no instructions about "wipe_part", what partitions to destroy, or how to do this. Using your version of RKDevTool, no partitions are loaded which then appear in the Download Image window (as I assume they are supposed to). -Flashing the other Miniloader file is met with a Waiting for Device Success prompt, which never completes. These instructions obviously worked the first time I did this several months ago. I don't know what at all could have changed, and I'm pretty frustrated as I'm trying to recover from another OMV system crashing and trying to recover data, so the use was/is pretty urgent, and given this forum, it could be a few days before a replay so my system is now sitting hostage to these instructions.

I'm a bit embarassed to say they are confusing to me. I am going to ask Grok and see if it can help me, thank you

I don't think it's an SD card issue. Performance wise it's about twice the requirement. And if it was a bad block, I doubt the issue would be the same across two different images. As for logs... where? I tried running "sudo dmesg -T --color=always --level=err,warn | more" and nothing about AdGuard came up. I checked the AdGuardHome.yaml file and confirmed bind_host was set to 0.0.0.0 (I also tried setting it to 192.168.0.6... no improvement). The command "sudo netstat -tulnp | grep 3000" said command not found, and "journalctl -u AdGuardHome" came back with no entries.