Vim3Pro with ubuntu server

I’m new here, some time ago I decided to buy two khadas vim3 pro and use them with ubuntu server, mainly for k8s. Setup is simple - sbc + system on emmc + new m2x + hp ex900 nvme for data + khadas fan and heatsink.
First attempt with amlogic burning tool and emmc image and ubuntu focal failed - system could not support nvme, it throws tons of errors and dmesg messages, except that most of things seems to work ok. I found here that it maybe related to used kernel, downloaded krescue and started to check other images.
After few attempts I finally got nvme working with image

HP EX900 nvme works ok, fan control is ok too,
At this image I have many errors about wi-fi:

[    3.984669] brcmfmac: F1 signature read @0x18000000=0x17294359
[    3.988766] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
[    6.465231] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4359-sdio for chip BCM4359/9
[    6.468300] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[    6.485247] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4359/9 wl0: Sep 20 2019 20:22:36 version (edb7293@shgit) (r711217) FWID 01-c7feb1ee

I tried gnome based image and same errors there, wifi works with those. Should I use different firmware for wifi? Why it’s throwing errors? Anthennas are attached.

Other warnings I get in dmesg:

[    0.000000] Machine model: Khadas VIM3
[    0.000000] OF: fdt: Reserved memory: failed to reserve memory for node 'secmon@5000000': base 0x0000000005000000, size 3 MiB
[    0.000000] Reserved memory: created CMA memory pool at 0x00000000bc800000, size 896 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool

[    0.029460] KASLR disabled due to lack of seed

[    0.220621] dw-pcie fc000000.pcie: IRQ index 1 not found
[    0.220790] meson-pcie fc000000.pcie: get phy failed, -517

[    1.293205] mmc2: queuing unknown CIS tuple 0x80 (2 bytes)
[    1.296254] zswap: loaded using pool lzo/zbud
[    1.303650] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.313420] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
[    1.313711] VCC_5V: supplied by DC_IN
[    1.320607] USB_PWR: supplied by VCC_5V
[    1.320619] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
[    1.325193] dw-pcie fc000000.pcie: IRQ index 1 not found
[    1.334573] mmc2: queuing unknown CIS tuple 0x81 (9 bytes)
[    1.337054] meson-pcie fc000000.pcie: host bridge /soc/pcie@fc000000 ranges:
[    1.345028] mmc2: queuing unknown CIS tuple 0x8e (9 bytes)
[    1.347250] meson-pcie fc000000.pcie:       IO 0x00fc600000..0x00fc6fffff -> 0x0000000000
[    1.360854] meson-pcie fc000000.pcie:      MEM 0x00fc700000..0x00fdffffff -> 0x00fc700000
[    1.368934] meson-pcie fc000000.pcie: invalid resource
[    1.373971] meson-pcie fc000000.pcie: iATU unroll: enabled
[    1.379398] meson-pcie fc000000.pcie: Detected iATU regions: 4 outbound, 4 inbound
[    1.418101] random: fast init done
[    1.420746] mmc2: new high speed SDIO card at address 0001
[    1.430304] meson-pcie fc000000.pcie: error: wait linkup timeout
[    1.454622] meson-pcie fc000000.pcie: Link up
[    1.454759] meson-pcie fc000000.pcie: PCI host bridge to bus 0000:00

I needed to use USB-SD image because of kernel, should I wait for emmc version? Except hanging on reboot there were no bigger problems with it, fan works in manual and auto mode.
Are any other errors something I should concern?
Can I safely use USB-SD version on eMMC?

Hello @dominik
there is no issue with using the mainline external image on eMMC, that is not relevant in the case

other than dmesg errors, please try nmcli or nmtui to connect to the Wifi, does that work ?

Wifi seems to connect and work, I haven’t tested this very intensive (rather using ETH)
If USB-OTG version is ok for eMMC it’s wise to mark that somehow, I started with images with eMMC because I was not sure if others would work. :slight_smile: