and all are in /usr/lib/firmware/brcm already, except nvram_ap6398s.txt
I also downloaded all these files from the internet from various places, but like I said, they ere already in /usr/lib/firmware/brcm except that one
I don’t really know what to do with them but I was told on IRC that is most likely what I needed. I don’t know how to initialize the proper driver though and/or if I have to blacklist the others (or if so even how).
EDIT: nvram_ap6359sa.txt is already in /usr/lib/firmware/brcm
Not in AUR:
[rkm@Khadas ~]$ yay -Ss brcmfmac_sdio-firmware-aml
[rkm@Khadas ~]$ yay -Ss brcmfmac
aur/gpd-pocket-support-bcm4356-git 0.2.5-2 (+0 0.00%)
Provides an additionally needed firmware file brcmfmac4356-pcie.txt for the Broadcom BCM4356 WiFi in the GPD Pocket. (If you have ‘gpd-pocket-support’ installed you already have this.)
aur/systemd-brcmfmac-git 0.1-1 (+2 0.00%)
Disable the brcmfmac module on shutdown
[rkm@Khadas ~]$
Can I propose we change the topic and category of this Thread to include the VIM2 since we know it works too / as well ? Since I can personally confirm / Verify, although this is on the older v1.2 of the VIM2
You are wrong, he basically can not work properly. Copying a dtb file is not used in modern systems. I suspect you have a very outdated and incorrect version of multi-boot. Update the multi-boot and then you can normally run any external system from any media (SD or USB flash drive).
Importantly. If you use the old multi-boot system, when you try to install any system in eMMC, you will get a brick. Which then have to restore.
How can I be wrong about what I experience? And how am I supposed to update multi-boot, without instructions. Also I don’t use multi-boot I have Ubuntu only on EMMC. And how can you PRETENTIOUSLY, ARROGANTLY, AND PRESUMPTUOUSLY ASSUME, I have a very outdated and incorrect version of anything? I only used what Khadas officially supplied in latest image builds that were available. Dated June 04 2019.
No need to make a separate vim2 image. Enough after capture the image properly configure the DTB to the file (uEnv.ini), you have already written about it. By the way, this image can be run on any device with activated universal multi-boot, for which there is a DTB as part of the image (just as one Armbian image is run on all devices).
You can think whatever you want, but the objective reality is that without a multi-boot, you will not be able to run any system from an external medium.
