dbsharpe

You may have seen some other messages skipping past at boot complaining about mmcblk meaning the dbt/kernel is not recognising the sdcard or its controller. In single user mode, busybox blkid and cat /proc/partitions may show them missing.

Looks like the nvram file is now brcmfmac-ap6330-sdio.txt in focal Ubuntu package armbian-firmware according to apt-file search brcmfmac-ap6330-sdio.txt . There are various versions of brcmfmac4330-sdio.bin (and others with different file names) so experiment with different ones to see which is best. I don't know if the ones in packages armbian-firmware, armbian-firmware-ful & linux-firmware are identical. You will probably find a few different ones in under android /etc/wifi which you could try - you'll have to rename etc the binary file to brcmfmac4330-sdio.bin. See also this previous post.

The tv box name (TX3 mini) like a lot of boxes has little relation to the hardware inside. Try this forum post - seems to have worked for quite a few different boxes having wifi issues.

I've seen these permission issue posts a few times before but never had them myself or know why they occur. stat /usr/bin/sudo on my system shows 4755 owned by root. After logging in, try the su - command instead of sudo winch will switch you to root (or login as root). See this link about single user mode to change permissions (chmod 4755 /usr/bin/sudo ; chown roor:root /usr/bin/sudo). Bit elementary but the only help I can offer.

When I had wifi and firmware issues in Armbian, I used the firmware found running under Android. I'd also look at the linux kernel source code for the particular module loaded to find out the firmware file names, usually defined in the .h header files

If it was NTFS (and not a FAT derivation that has a size limit of about 4Gb file size), I would suggest creating an empty file about 20Gb in size with dd if=/dev/zero of=./20gb_filesystem.img.ext4 bs=4k iflag=fullblock,count_bytes count=20G . Format the file with mkfs.ext4 ./20gb_filesystem.img.ext4 and mount with mount ./20gb_filesystem.img.ext4 /mnt which will give you a linux filesystem in a file.

Is the disk under /media/root/Seagate NTFS? It needs to be Linux ext3/4 etc and make sure /media/root/Seagate/armbianbuild has chmod a+rwx to rule out any permissions issues. If I was encountering issues I could not fix, I'd use strace -f -o /tmp/trace-build.txt ./compile.sh and examine /tmp/trace build.txt at the end.

Put debug at the end of the APPEND string might make initrd become more verbose. Also the word single to use single user mode in APPEND with root=LABEL=ROOTFS removed my be of some use.

Yes, I am building on a H96 max x3 TV box (AML S905X3) running Focal arm64. You can build on a tv box running Armbian booted from sdcard but the location for storage before issuing the command git clone https://github.com/150balbes/Build-Armbian should be internal flash/EMMC/NAND, high speed external wired storage or network storage (ie from your 'computer'). About 10Gb needed. Might take half a day.

At the same time these post appeared, I was able to natively compile balbes150 Armbian under Focal arm-64/aarch64. Haven't tried recently. Top tip, make sure CCACHE isn't using slow sdcard storage. I used a H96 max x3 and pointed it to a folder in /tmp as it boots with RAM Memory: 2429544K/3535872K available.

Sorry, the thread starter by the author has a disclaimer: "For all. I don't support s905x3". There are specific forums for this box and AML chip.

> I've managed to successfully boot an MXQPro 4k (Amlogic S905X p212 board) from SD Card, however upon running the installation script Armbian, it doesn't seem to find the internal eMMC. I think it might be covered by this previous reply - and the post after it.

As far as packages go, I find focal seems to have less than bionic. As a work around for other none specific packages, you could download the from the bionic repo with wget and install with dpgk. If you get complaints about dependcies, you could manualy copy in the files after extracting them from the package with ar x pkg.deb ; tar -xvf data.tar.xz

Having taken a quick look at the ssv6x5x sources available, there is no way you'll get a 3.4.x kernel driver working on a 5.x system as the interfaces have changed. Anyway, wifi drivers beginning s**** are pretty much toxic on this forum and other aftermaket O/S boards.

In the absence of a u-boot file, this is how I was able to work round it but you still need to boot from sdcard but run root from flash. You will need to restore an operable android image with USB Burning Tool or restore full backup of internal flash. On my p201 S905X device, I was able to format all (most) of the internal flash apart from the first 108Mb (arbitrary value) which excludes the bootloader (something like mke2fs -F -t ext4 -m 0 -L ROOT_EMMC -E offset=113246208 /dev/mmcblk1 [ -< device for internal flash] ) You can get your flash layout from dmesg after booting into android. You will also need to know how to unpack & pack uInitrd. Your custom boot uInitrd will get overwritten if you install or upgrade certain debian packages. I no longer have the RAM issue and was able to make some use of those fake microsd cards I've collected over the years.