All Activity

thanks again, I'll do this soon.

By exiting the docker container and installing qemu-user-static in the host system, I was able to run the build again and progress. Appreciate the tip thank you! One final issue that I notice is when I am attempting to use customize-image.sh to install openssh-server package. As you can see by these logs it reaches "Setting up openssh-server (1:9.2p1-2+deb12u6) ..." but then script hangs and never progresses. [🐳|🔨] Fetched 13.0 MB in 5s (2,701 kB/s) [🐳|🔨] Reading package lists... [🐳|🔨] Reading package lists... [🐳|🔨] Building dependency tree... [🐳|🔨] Reading state information... [🐳|🔨] The following additional packages will be installed: [🐳|🔨] libssl3 (3.0.16-1~deb12u1) [🐳|🔨] openssh-client (1:9.2p1-2+deb12u6) [🐳|🔨] openssh-sftp-server (1:9.2p1-2+deb12u6) [🐳|🔨] openssl (3.0.16-1~deb12u1) [🐳|🔨] Suggested packages: [🐳|🔨] keychain (2.8.5-3) [🐳|🔨] libpam-ssh [🐳|🔨] monkeysphere [🐳|🔨] ssh-askpass (1:1.2.4.1-16) [🐳|🔨] molly-guard (0.7.2) [🐳|🔨] ufw (0.36.2-1) [🐳|🔨] Recommended packages: [🐳|🔨] xauth (1:1.1.2-1) [🐳|🔨] The following packages will be upgraded: [🐳|🔨] libssl3 (3.0.15-1~deb12u1 => 3.0.16-1~deb12u1) [🐳|🔨] openssh-client (1:9.2p1-2+deb12u5 => 1:9.2p1-2+deb12u6) [🐳|🔨] openssh-server (1:9.2p1-2+deb12u5 => 1:9.2p1-2+deb12u6) [🐳|🔨] openssh-sftp-server (1:9.2p1-2+deb12u5 => 1:9.2p1-2+deb12u6) [🐳|🔨] openssl (3.0.15-1~deb12u1 => 3.0.16-1~deb12u1) [🐳|🔨] 5 upgraded, 0 newly installed, 0 to remove and 17 not upgraded. [🐳|🔨] Need to get 4,617 kB of archives. [🐳|🔨] After this operation, 1,024 B of additional disk space will be used. [🐳|🔨] Get:1 http://deb.debian.org/debian bookworm/main arm64 libssl3 arm64 3.0.16-1~deb12u1 [1,812 kB] [🐳|🔨] Get:2 http://deb.debian.org/debian bookworm/main arm64 openssh-sftp-server arm64 1:9.2p1-2+deb12u6 [60.7 kB] [🐳|🔨] Get:3 http://deb.debian.org/debian bookworm/main arm64 openssh-server arm64 1:9.2p1-2+deb12u6 [413 kB] [🐳|🔨] Get:4 http://deb.debian.org/debian bookworm/main arm64 openssh-client arm64 1:9.2p1-2+deb12u6 [937 kB] [🐳|🔨] Get:5 http://deb.debian.org/debian bookworm/main arm64 openssl arm64 3.0.16-1~deb12u1 [1,395 kB] [🐳|🔨] Preconfiguring packages ... [🐳|🔨] Fetched 4,617 kB in 1s (6,157 kB/s) (Reading database ... 26620 files and directories currently installed.)e ... [🐳|🔨] Preparing to unpack .../libssl3_3.0.16-1~deb12u1_arm64.deb ... [🐳|🔨] Unpacking libssl3:arm64 (3.0.16-1~deb12u1) over (3.0.15-1~deb12u1) ... [🐳|🔨] Preparing to unpack .../openssh-sftp-server_1%3a9.2p1-2+deb12u6_arm64.deb ... [🐳|🔨] Unpacking openssh-sftp-server (1:9.2p1-2+deb12u6) over (1:9.2p1-2+deb12u5) ... [🐳|🔨] Preparing to unpack .../openssh-server_1%3a9.2p1-2+deb12u6_arm64.deb ... [🐳|🔨] Unpacking openssh-server (1:9.2p1-2+deb12u6) over (1:9.2p1-2+deb12u5) ... [🐳|🔨] Preparing to unpack .../openssh-client_1%3a9.2p1-2+deb12u6_arm64.deb ... [🐳|🔨] Unpacking openssh-client (1:9.2p1-2+deb12u6) over (1:9.2p1-2+deb12u5) ... [🐳|🔨] Preparing to unpack .../openssl_3.0.16-1~deb12u1_arm64.deb ... [🐳|🔨] Unpacking openssl (3.0.16-1~deb12u1) over (3.0.15-1~deb12u1) ... [🐳|🔨] Setting up libssl3:arm64 (3.0.16-1~deb12u1) ... [🐳|🔨] Setting up openssl (3.0.16-1~deb12u1) ... [🐳|🔨] Setting up openssh-client (1:9.2p1-2+deb12u6) ... [🐳|🔨] Setting up openssh-sftp-server (1:9.2p1-2+deb12u6) ... [🐳|🔨] Setting up openssh-server (1:9.2p1-2+deb12u6) ... The command used in customize-image.sh to install is: apt-get install -y open-ssh Since I used the -y flag I don't think any user input is needed, but I could be wrong. Any tips are greatly appreciate as I troubleshoot. Other than this issue with openssh-server, the build worked out ok! I will write some guides and share for other Qubes OS users.

chatgpt advised to type ":UTC" or ":Europe/Berlin" and it helped.

Same answer as above. Without serial logs impossible to debug. It leaves to mention that this board is not officially supported but configuration has been provided by a community effort. Board status is unknown to the core Armbian team.

No. Yes. This is the most stable and well-developed kernel.

kernel_ramfs is located at /dev/block/mmcblk2p6 Have extracted with dd and copying through wifi adb. Interesting usb debugging is enabled in tvbox, but when connecting usb v3 cable to tvbox, host machine does not see the 'adb device', adb connection over wifi is ok. Has anybody used USB adb on this device?

No, that won’t work. This is a Armbian Linux forum. If you need android support try xda forums.

I also encountered the same situation. I wrote the Ubuntu Orange Pi 5 Max image from the Orange Pi homepage (http://www.orangepi.org/) and it ran normally, but when I wrote the Armbian Ubuntu version from https://www.armbian.com/orangepi-5-max/, the indicator light was only green and nothing appeared on the screen. I also tried writing the Armbian version for the regular Orange Pi 5 or Orange Pi 5 Pro and it could run (although wifi and usb were lost, but I could boot to the desktop), but when I wrote the Armbian version for the Orange Pi 5 Max, it did not run. Is it a bootloader problem?

I found that sun50i-h618-transpeed-8k618-t.dtb is the working one, can I replace boot.img-dtb in the android img with it?

No one answers...... 🤐 I got tired of waiting and set up autologin according to these instructions. Everything is working.😁 You can use it.💯

@jwillb00 there’s a drop down menu on the first page. You’ll see “main” as the first option. Select “v20250306” that’s my more recent and stable release. you can clone my build using git command. git clone https://github.com/NickAlilovic/build.git -branch v20250306 kernel config is located here. Edit the configuration manually. https://github.com/NickAlilovic/build/blob/v20250306/config/kernel/linux-sunxi64-edge.config To compile a new image use the commands cd build ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "tanix-tx6s-axp313" choose "edge" rest is up to you. Your image should be in output/images directory.

I've checked the storage media and it seems to be a NAND - https://files.pine64.org/doc/datasheet/pine64/FORESEE_eMMC_NCEMBSF9-xxG SPEC A0 20150730.pdf Not sure if this is of any use in figuring out why it cannot see the boot partitions.

@Nick AI have been using the TX6s build and it's been working great, but I was curious about the structure of your repository. I saw no files for the TX6s, but I see images for it in the releases? I'm new to all this, but I need to change some kernel config options so I was wondering how I could apply those to your repository.

Well, i have jumped ship on gone to every os i can think of that will run on RPI5 and now IM BACK!!!! Hello again, Jayson Here - And i have decided that Arbian 25 Noble Gnome may be the smallest-strongest multimedia build i can find...so its what i will choose to finish my PI 5 with. I am still wrestling with the sony IMX477 as to produce video. I have just ordered a usb mount for uvc-video rather than csi/cam0-cam1 b/c i cant get it working. at all and need to advance... to the touchscreen which is still just HDMI w/o touch. on the new download of Armbian. its downloading now. I will put pics of the device and more tomorrow. Jay T.

moved

Hi, I try to get my NanoPC-T4 a second life. Therefore I want to (re-) install Armbian but I'm stuck Andi don't know why. I uses USBFlasher to flash the minimal Armbian on it (tried compressed and uncompressed) but the green blinking light indicates me, that he found no bootable device. I tried different images as well. Also differen SD cards, even DietPi image, always the same. The only thing which runs instant is one of the eflasher Images of FriendlyARM. I also tried to change the image that the eflasher writes to the eMMC (by copy the uncompressed .img file to the SD card and renamed it to armbian.raw and changed the config file as the wiki said). While the flash process is working, it does not boot after that. I'm out of ideas... The final solution should be that has the bootloader on the eMMC while the rest of the os should be on the SSD, like it was before. I would be very thankful for help.

Hi guys Just to thank you for the very relevant information I found in this forum. I am posting my experience with armbian. I successfully installed the unofficial armbian version "25.05.0 onecloud noble 6.12.17 xfce desktop" on a generic MXQ TV Box S805 with HTC-MXQ-V4 card. It was hard work! this box calls the aml_autoscript on boot... but need to be adjusted to allow booting. this procedure works for the board i mentioned, i don´t know about others. Use at your risk !!! But booting from SD is a relativelly safe procedure. download "Armbian-unofficial_25.05.0-trunk_Onecloud_noble_current_6.12.17_xfce_desktop.img.xz" uncompress the image (7zip) save to SDcard (8GB recomended) - I have used rufus Two partitions will be created. Two partiotions will be created ... first FAT32 (armbi_boot) and second EXT4 (armbi_root). On FAT32 partition (boot): file: aml_autoscript (copy commands below and put inside aml_autoscript.cmd) # Define boot only from SD Card setenv bootdev "mmc 0" # SD card # Load armbianEnv.txt fatload ${bootdev} 0x10800000 /armbianEnv.txt && env import -t 0x10800000 ${filesize} # Boot Arguments (provided by armbianEnv.txt) #setenv bootargs "" setenv bootargs "${bootargs} rootwait rw" setenv bootargs "${bootargs} ${consoleargs}" setenv bootargs "${bootargs} ${extraargs}" # Booting fatload ${bootdev} 0x14000000 /uImage || exit 1 fatload ${bootdev} 0x15000000 /uInitrd || exit 1 fatload ${bootdev} 0x11800000 /dtb/meson8b-onecloud.dtb || exit 1 bootm 0x14000000 0x15000000 0x11800000 file: armbianEnv.txt (copy parameters below and put inside armbianEnv.txt) consoleargs="console=ttyS0,115200n8 console=tty0 no_console_suspend splash=verbose" bootargs="root=LABEL=armbi_root" extraargs="loglevel=7 rootfstype=ext4 earlyprintk ip=dhcp" On Linux, put aml_autoscript.cmd on an directory and compile "mkimage -C none -A arm -T script -d aml_autoscript.cmd aml_autoscript" Copy both aml_autoscript.cmd and compiled aml_autoscript to root of FAT32 partition Adjust (with above parameters) or create a file and copy armbianEnv.txt to root of FAT32 partition. Rename "meson8b-mxq.dtb" to "meson8b-onecloud.dtb" to be compatible with same name defined on aml_autoscript (you could rename the file ou change the script ... choose) Boot from SDCard (Turn tvBox off, with a toothpick, click the button inside AV conector, hold down and turn on the TV box, hold the button for 5 to 15 seconds ) if everything went well the firt boot occur and your tvbox could boot from SD in armbian Linux with kernel 6.12 The first boot is extremelly slow... a lot of time... Good luck!!

A bit later than planned but finally got round to a system rebuild with 6.12.23 but still encounter the exact same issues as before. Loading a simple "hello_world" module intially appears to load successfully but if trying to removing it we then still get: ~/exp-drivers/hello_world$ sudo rmmod hello rmmod: ERROR: ../libkmod/libkmod-module.c:856 kmod_module_remove_module() could not remove 'hello': Resource temporarily unavailable rmmod: ERROR: could not remove module hello: Resource temporarily unavailable Attempting to call lsmod still spams a load of syslog messages and if we then try to call it again it just hangs. Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 403.890953] Internal error: Oops: 5 [#1] SMP THUMB2 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.312451] Process lsmod (pid: 1638, stack limit = 0x9d250a51) Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.325587] Stack: (0xf0dade00 to 0xf0dae000) Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.337169] de00: c16067b0 00000000 00000000 ffffffff c4103000 e2b03f90 6830fe88 e2b03f90 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.352658] de20: 00000400 c9854d70 00000000 bfa9e044 c9854d88 f0dadeb0 bfa9e044 c0309b0b Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.368148] de40: 00000000 00000000 f0dade98 c9854d98 00000001 c9f81000 2e9f8000 c9918300 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.383626] de60: c4043dc0 00000000 f0dadf80 c3126840 00000000 00000400 00000001 c0b217c4 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.399058] de80: c03522a5 c0309e59 00000400 00000001 01aafca0 00000400 00000001 00000000 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.414440] dea0: f0dade90 00000400 00000001 00000000 c3126840 00000000 00000000 00000000 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.429741] dec0: 00000000 00000000 00000000 00000000 00000000 00000000 00000400 e2b03f90 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.445005] dee0: 00000400 c3126840 c9191400 01aafca0 f0dadf80 c02e61d5 00001a55 c4304068 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.460249] df00: c4304068 00000000 00000000 00000000 ffefe2c0 ef32c434 00000000 e2b03f90 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.475507] df20: b6e79fff f0dadfb0 01ab00a4 00000817 c9191400 00000255 c9918300 c0aca39f Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.490740] df40: 00000000 c0aca39f 00000000 00000000 00000000 e2b03f90 00000000 c3126840 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.506009] df60: c3126840 00000000 00000000 c01002a0 c9191400 00000003 00000000 c02e6a09 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.521213] df80: 00000000 00000000 c01002a0 e2b03f90 be93e100 01aae2e0 000005e8 b6bc5888 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.536430] dfa0: 00000003 c0100061 01aae2e0 000005e8 00000003 01aafca0 00000400 00000001 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.551603] dfc0: 01aae2e0 000005e8 b6bc5888 00000003 0000000a be93e3b4 00000000 00000000 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.566780] dfe0: 00000003 be93e2e0 b6b6037b b6ad9656 40070030 00000003 00000000 00000000 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.581942] Call trace: Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.581955] m_show from seq_read_iter+0xd3/0x37c Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.603084] seq_read_iter from seq_read+0xa5/0xcc Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.614746] seq_read from vfs_read+0x79/0x21c Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.626005] vfs_read from ksys_read+0x45/0x9c Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.637120] ksys_read from ret_fast_syscall+0x1/0x5c Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.648813] Exception stack(0xf0dadfa8 to 0xf0dadff0) Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.660406] dfa0: 01aae2e0 000005e8 00000003 01aafca0 00000400 00000001 Message from syslogd@pcduino2-1 at May 24 00:02:33 ... kernel:[ 404.67Segmentation fault Here is what lsmod looks like before trying to load a custom module and going haywire: Module Size Used by aes_arm_bs 20480 2 crypto_simd 12288 1 aes_arm_bs aes_arm 12288 3 aes_arm_bs ccm 16384 6 sunrpc 360448 1 rtl8xxxu 167936 0 mac80211 667648 1 rtl8xxxu axp20x_adc 16384 0 sun4i_gpadc_iio 12288 0 cfg80211 618496 2 mac80211,rtl8xxxu industrialio 61440 2 sun4i_gpadc_iio,axp20x_adc sun4i_ts 12288 0 rfkill 20480 3 cfg80211 libarc4 12288 1 mac80211 sunxi_cedrus 40960 0 v4l2_mem2mem 16384 1 sunxi_cedrus videobuf2_dma_contig 16384 1 sunxi_cedrus videobuf2_memops 16384 1 videobuf2_dma_contig videobuf2_v4l2 16384 2 sunxi_cedrus,v4l2_mem2mem videobuf2_common 45056 5 sunxi_cedrus,videobuf2_dma_contig,videobuf2_memops,v4l2_mem2mem,videobuf2_v4l2 videodev 188416 3 sunxi_cedrus,v4l2_mem2mem,videobuf2_v4l2 mc 36864 5 sunxi_cedrus,videobuf2_common,videodev,v4l2_mem2mem,videobuf2_v4l2 cpufreq_dt 16384 0 evdev 16384 1 uio_pdrv_genirq 16384 0 uio 16384 1 uio_pdrv_genirq zram 24576 2 zsmalloc 16384 1 zram binfmt_misc 20480 1 dm_mod 98304 0 autofs4 36864 2 ext4 606208 2 mbcache 12288 1 ext4 jbd2 102400 1 ext4 pinctrl_axp209 12288 0 lima 49152 0 gpu_sched 36864 1 lima drm_shmem_helper 16384 1 lima sun4i_gpadc 12288 0 sunxi 12288 0 phy_generic 16384 2 sunxi display_connector 16384 0 gpio_keys 16384 0 uas 20480 0 icplus 12288 1 Maybe it would be a safer bet to build again with 6.6 for the time being or try with 6.14 and hope for the best?

Ok, I'll wait for the release to land and test again. I agree, upgrading away from legacy is good. That said, as things are now this will break any installation that is using wlan when they upgrade their packages and are on the legacy kernel. And it's even worse as the user needs to know to update to latest release and only then swap kernels due to the timing of the wlan fix. To put it in different words, I'm not proposing we fix the legacy kernel. I'm saying we need to make sure that we're not breaking current users who have no way of knowing that things are going to be breaking.

I'm not working on the legacy kernel at all, current and edge only, which are based on mainline. The fix for wifi should be in the upcoming armbian release (25.05). It was merged into the build repository long ago and should've been available in beta already, only now coming into the release. To those who are still using legacy - I recommend switching to current or edge instead.

@Diego Dagum are you using an apt caching mirror like apt-cacher-ng?

The reason who I'm calling this a regression is that most CB1 users are going to be in the legacy track. The legacy track just got updated to 6.6.75, which will effectively break all current installations.

I switched to the current kernel and the wlan is still missing. I'm still waiting for the kernel panic, but so far even with zram enabled the board has remained crash free for about 30 minutes. An update armbianmonitor log is here: https://paste.next.armbian.com/aculomicah

Please throw away this 6.6.75 core. It is no longer supported. Or fix the regressions yourself.

I've just tried rebuilding (at least based on ChatGPT's instructions) and it made no difference. I can't get this to work art all. Looks like I managed to get U-Boot updated, but still won't boot without the SD Card.