All Activity

I don't want to say anymore. What a mess.

https://github.com/armbian/build/pull/8447#issuecomment-3195333910

https://github.com/armbian/build/pull/8447#issuecomment-3195333910

Why did you bypassed the github repository?

Why not test it in a github branch , but release into public directly without any comment and test?

Why not test it in a github branch , but release into public directly without any comment and test?

Revert to 6.15. The 6.16 package is useful for A523 only atm. Don't use bleeding edge and complain about things breaking the same time. To answer on your level: Either help fixing things or fuck off and move along.

@jock @MattWestB thank you for you help! Sorry for the late reply. Im did update the dtb files jock said, and usb 3.0 work better now, but not as stable as 100%. Sometimes it still hang on reboot unless i disconnect the device on usb 3.0 port and re-insert power for complete reboot and booting, and sometimes it boot without recognise the device on usb 3.0 port. And sometimes the WiFi drop connection and reconnect repeatedly many times without dmesg errors, and need manual reboot. So maybe im just unlucky getting the bad batch of H96 Max. Due to the needed of stability, especially with the usb port, i switching to Dell Wyse 3040 for now. It's was fun playing with armbian and rockchip. Thank you for your contribution @jock 🥰

Hey phoenix 0025m bro. My Tx3 Mini motherboard is same as yours. Did you have any success installing custom rom on it?

What the hell is kernel 6.16 ( linux-image-edge-sunxi64 (25.8.1) )? Never seen it in git main , no all overlays , who did it? After upgrade, no wifi .

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

Suddenly the 6.16 kernel was released in apt , who did it? why all overlays missed?

I have several of the x96Q V1.3 with H313 using Armbian booting from emmc with no issue. I miss-placed my Armbian SD and burned another one using a cheap SD which was a huge mistake! This caused and SPL -19 error code (can't find mmc) when booting from emmc. this error is printed to the UART (nothing on the HDMI, light stays red). These bad boxes are able to boot from the SD with no issues. I spend many hours trying to figure out the root cause with no success. The interesting thing is that this error persists on these damaged boxes even after reloading them with a Armbian using a good SD and Armbian-install. This good new SD was used on other good boxes and it works fine; they can boot from emmc. Only the boxes that were flashed with the bad SD have this problem. Now this gets even more interesting, I loaded miniarch on one of the bad boxes using dd and with some minor changes (which I can't remember what I did now) but got a bad boxe to boot up from emmc (only tried it on 1 box and it worked). I tried amrbian-install after miniarch booting from emmc and got the same error -19. I tried cloning a good box onto a bad one using dd over ssh and no luck either. I reloaded Android and that works and they boot up Android from emmc with no issues!!! I then installed Armbian after flashing Android but got the same issue. The failure is happening early in the SPL. Idon't think the Brom was touched since Android and miniarch work, I reloaded the bootloader with SPL and no luck either. At this point I can fix this with a hammer but it wold be nice to find the root cause if anyone has an idea or suggestions. Thanks and sorry for the long message. I am not in front of the unit otherwise I would include a screen shot of the error message.

Let's divide it into parts - Bluetooth Bluetooth isn't working. I've tried activating UART7 and GPIO pins 19 and 22, but to no avail. I installed the drivers, but to no avail. Bluetooth isn't communicating! - Audio ES8388 For some unknown reason, the ES8388 has audio disabled by default on the ASA. To fix this, simply go to the terminal and run the command user@user alsamixer Then use the buttons to move around until you find OUT1. Out1 above it says MM (mute), so click M to make it 00 with a green background. Audio problem solved - Language I can't set the language to Portuguese in the Gnome interface even after installing the packages manually and through armbiam-config - Kernel Please, even if kernel 6.1.xx++ does not work, use the latest functional kernel, for me kernel 6.1.115 is very functional. No critical problems.

no worries! and that is even when you try some of the suggestions from https://unix.stackexchange.com/questions/609438/how-can-i-use-a-usb-keyboard-or-mouse-to-wake-from-suspend which I linked above?

Apologies, but what is RooibOS? I'm sure it's got nothing to do with tea ;-)

I don't know this topic very well, either. But here is a link to get you started. https://docs.armbian.com/User-Guide_Autoconfig/

Sorry for the confusion, friends Indeed, the Orange Pi 5 can go into suspend (sudo systemctl suspend) but at this point, the only way to resume it, is to press the physical power button on the Orange Pi 5 itself. No combination of keyboard presses or mouse clicks etc will ever wake it back up

Dear maintainers, First thanks for your work on this SBC... On recent 6.12.35-current-sunxi64, i have the same issue... root@hn-nanopineo2-285:~# uname -a Linux hn-nanopineo2-285 6.12.35-current-sunxi64 #5 SMP Fri Jun 27 10:11:46 UTC 2025 aarch64 GNU/Linux root@hn-nanopineo2-285:~# cat /etc/debian_version 12.11 root@hn-nanopineo2-285:~# dpkg -l |grep armbian ii armbian-bsp-cli-nanopineo2-current 25.8.1 arm64 Armbian CLI BSP for board 'nanopineo2' branch 'current' ii armbian-firmware 25.8.1 all Armbian - Linux firmware root@hn-nanopineo2-285:~# dmesg |head [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.35-current-sunxi64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld ( GNU Binutils for Ubuntu) 2.42) #5 SMP Fri Jun 27 10:11:46 UTC 2025 [ 0.000000] KASLR disabled due to lack of seed [ 0.000000] Machine model: FriendlyARM NanoPi NEO 2 [ 0.000000] OF: reserved mem: Reserved memory: No reserved-memory node in the DT [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000005fffffff] [ 0.000000] NODE_DATA(0) allocated [mem 0x5fed9540-0x5fedb5ff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x000000005fffffff] ..... and later in dmesg ... [ 11.751234] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator [ 11.761267] cpu cpu0: _opp_add: OPP not supported by regulators (960000000) [ 11.768453] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator [ 11.778428] cpu cpu0: _opp_add: OPP not supported by regulators (1008000000) [ 11.785720] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 11.795704] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 11.802988] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 11.812992] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 11.820337] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 11.830340] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 11.837598] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 11.847610] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 11.855491] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 1 failed: -22 [ 11.863260] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 2 failed: -22 [ 11.870979] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 3 failed: -22 [ 11.878719] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 4 failed: -22 Regards

It is almost 2 years old and no info about which kernel. For you, please indicate which ffmpeg you use. You should have done that already in your first post.

Hi everyone, I'm new to creating my own images and I'm learning this just because I'm interested in it. I am trying to build ubuntu 24.04 for my rpi3b using the build configuration for rpi4b. Now I'm trying to automate the process of the first launch (skip the selection of bash, zsh, creating a password for root, creating a regular user, etc.). In one of the topics, I found out that I can delete "rm -rf/root/.not_logged_in_yet" And the system will not ask for the initial setup, but to make all the necessary changes for me, I wrote a small function in customize-image.sh: SettingSystemFirtsRun() { #disable defaut script sudo rm -rf /root/.not_logged_in_yet #setting regul user echo "add user $_userName" sudo useradd -m -c -s /bin/bash "$_userName" "$_userName" -p "$_userPass" #change root pass echo 'change root passssss' echo "root:$_rootPass" | sudo chpasswd # Set hostname permanently echo "Setting hostname to $_Hostname" echo "$_Hostname" > /etc/hostname hostname -b "$_Hostname" # Update hosts file sed -i "s/127.0.1.1.*/127.0.1.1\t$_Hostname/g" /etc/hosts } But when the system starts, I still do not see the directory of the user I am creating in /home, while the user himself is being created. The most important thing is that I really want to implement user creation at the assembly stage, although I am less and less convinced that this is even possible... I do not rule out that there are more concise ways to solve this problem, so I will be glad of any advice, good luck to all. P.S. I read the documentation, but I couldn't find a solution there.

Andrew, thanks for your feedback. I use the dtb released by armbian, I even try to get the dtb from the last image with same kernel, but it is the same. In fact the dtb file for Orange pi 5 is the same that the one I have (sha256 was clear !) I saw this other bug lately : https://github.com/rockchip-linux/kernel/issues/306 You have a Rock5B+ which is not the same thant OrangePI5, I run RK3588s, and you run rk3588. This means that the hardware even if near is not presented to the kernel the same way, ans so this may work for you, ans not for me in 6.1.115. I'm quite sure the issue happened with 6.1.115 kernel, because I encoded x265 easily 1 year ago with previous kernel.

I dropped back to Armbian_24.5.1_Bananapim5_bookworm_current_6.6.31_xfce_desktop.img and while it working, the boot find order of the drives is still random, no two boots is a row report the same lsblk order of disk vs sd* assigbnents. Only by using LABELS have I succeeded in getting them (7 drives) mounted in /etx./fstab. After that dated install an apt upgrade spent about an hour updating 270 some pkgs Just tried to get some of the other partitions mounted and usable, using LABEL= to ID them, got 2 of the 3 on a 1T toshiba drive, but found swapoff -a works, but swapon -a does not, won't even restore whats found at boot. This is from fdisk, also a reboot changed /dev/sdd into /dev/sdb Command (m for help): p Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: MQ01ABD100V Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x481e1363 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 102402047 102400000 48.8G 83 Linux /dev/sdb2 102402048 1748725759 1646323712 785G 83 Linux /dev/sdb3 1748725760 1953523711 204797952 97.7G 82 Linux swap / Solaris but its not swapon-able, note the dos disklable, it s/b gpt, it was done with gparted. ?????? Is there a conversion utility to make gpt or should I wait on working keyboard/mouse kit and let gparted blow it away? So I did, changed 3 parts to 2 and refornatted both and found that swapon should use label's but fails and the reboot to do that moved the toshiba drive from /dev/sdb to /dev/sdd. Howinhell can I stabilize tiis?????

This remembers me a recent set of changes to the DWC3 driver for RK3399 to fix exactly these kind of issues exposed here, including the single-orientation problem, plus some more issues with the displayport over usb type-c functionality. The PR had a lot of comments but finally it got merged because both the author and me tested the whole apparatus and it proved to improve significantly the situation on rk3399: https://github.com/armbian/build/pull/8271 Patches should address some issues in the dwc3 driver in general, and I see from the device tree that rk356x uses the snps,dwc3 compatibility string, so probably also rk356x benefits from them as well. It would although require some device tree tinkering: I tested on Orange PI4 LTS board and the device tree fixes are within this hunk; rk356x-based devices can probably share several declarations but that depends upon the rk356x capabilities. I would start from changing dr_mode to otg and removing regulator-always-on; property from the vbus supply.