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?