Can it work in conjunction with the soc temperature sensor?
Your question is too broad to answer - the board in question isn’t on supported list.
But If your board can load the generic image - then scripts will most likely work as well.
1 Like
Will have to look into t4 schematic to see if it is a pwm controlled fan or just direct voltage.
If its a pwm fan header then it should be configured to work with soc temperature speed.
1 Like
Although it says I built an ARM image of Manjaro, my Nanopc T4 hasn’t arrived yet. I want to know if the image of Manjaro can be installed and used normally on Nanopc T4 now?
NanoPC-T4 has a dedicated circuit for driving a 12V fan from PWM1,
so let’s add that along with some rough empirically-derived thermal
settings for the benefit of anyone determined enough to hook one up.The vendor does not currently offer a suitable fan, but this seems as
good a place as any to note that pre-terminated 3-pin JST GH connectors
are readily available online, and if you even have to ask, then splicing
one of those really will be orders of magnitude cheaper and simpler than
getting set up to crimp the teeny-tiny things by hand.
It looks like the kernel already supports pwm fans for nanopc T4, what else needs to be done?
Yes it will work out of the box as it already have the needed support in the mainline kernel.
Try our Official T4 image and share your feedback, if you face any issue then report it back to me so I can look into it, I have the device for testing.
Wifi does not work on the newer revision as they seem to have changed the wifi chip, but we can just add the needed firmware to make it work.
U-Boot TPL 2021.10-2 (Dec 25 2021 - 23:04:28)
Channel 0: LPDDR3, 933MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR3, 933MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2021.10-2 (Dec 25 2021 - 23:04:28 +0000)
Trying to boot from MMC1
U-Boot 2021.10-2 (Dec 25 2021 - 23:04:28 +0000) Manjaro Linux ARM
SoC: Rockchip rk3399
Reset cause: POR
Model: FriendlyElec NanoPC-T4
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - No block device, using default environment
In: serial
Out: serial
Err: serial
Model: FriendlyElec NanoPC-T4
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
258 bytes read in 4 ms (62.5 KiB/s)
1: Manjaro ARM
Retrieving file: /initramfs-linux.img
7885483 bytes read in 338 ms (22.2 MiB/s)
Retrieving file: /Image
30702080 bytes read in 1301 ms (22.5 MiB/s)
append: rootflags=subvol=@ initrd=/initramfs-linux.img console=ttyS2,1500000 root=PARTUUID=186fe6bd-a6c6-4619-826d-3e5a03ab0f56 rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtbs/rockchip/rk3399-nanopc-t4.dtb
78058 bytes read in 11 ms (6.8 MiB/s)
Moving Image from 0x2080000 to 0x2200000, end=4020000
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f1792000, end f1f172ab ... OK
Loading Device Tree to 00000000f177b000, end 00000000f17910e9 ... OK
Starting kernel ...
:: running early hook [udev]
Starting version 250.4-1-arch
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/mmcblk1p2'
:: mounting '/dev/mmcblk1p2' on real root
:: running cleanup hook [udev]
Failed to send exit request: Connection refused
Welcome to Manjaro ARM!
[ 32.013160] watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [10-arch:279]
[ 60.013158] watchdog: BUG: soft lockup - CPU#1 stuck for 52s! [10-arch:279]
[ 92.013158] watchdog: BUG: soft lockup - CPU#1 stuck for 82s! [10-arch:279]
[!!!!!!] Failed to start up manager.
[ 95.213448] systemd[1]: Freezing execution.
[ 120.013159] watchdog: BUG: soft lockup - CPU#1 stuck for 108s! [10-arch:279]
[ 148.013158] watchdog: BUG: soft lockup - CPU#1 stuck for 134s! [10-arch:279]
[ 176.013158] watchdog: BUG: soft lockup - CPU#1 stuck for 160s! [10-arch:279]
[ 204.013158] watchdog: BUG: soft lockup - CPU#1 stuck for 187s! [10-arch:279]
[ 232.013158] watchdog: BUG: soft lockup - CPU#1 stuck for 213s! [10-arch:279]
[ 272.013158] watchdog: BUG: soft lockup - CPU#1 stuck for 250s! [10-arch:279]
It seems that the system is frozen.
Please share the link of the image file you used.
I will download the same and test it on my device tomorrow.
The latest manjaro arm build, seems to be due to a hardware failure, the kernel doesn’t work properly, and my UART debug port also seems to only output some useless gibberish, and the HDMI doesn’t output any video signal, so I decided to return it.
There is no released builds for the NanoPC T4. So what image exactly did you use? The generic one?
sudo buildarmimg -d nanopc-t4 -e kde-plasma
So a self built image. Alright. You should have said that. 
At least for normal use, there is no need to do more configuration, just build the image manually.
Although the buildarmimg build image had some glitches due to my PC Linux kernel being updated to 5.17, so I wasted a night, and today this arm development board, seems to be broken, I wasted more time .
But the main reason is that the NVME SSD performance of the RK3399 is still too bad, my PM981a only has 400MB/s read and write performance on this device, which is really shocking, and it seems that the heat dissipation of the NVME SSD on this device is also very bad . 
I was almost scalded when I came into contact with nvme SSD. To be honest, the temperature is not very high now. I’m worried about whether this arm device will burn my pm981a when midsummer comes. 
1 Like
Did you try Official images from friendly arm to make sure that the hardware is the issue?
I tried the official Android and Ubuntu images of nanopc t4 and it worked the day before yesterday, but it doesn’t work anymore.
Sounds like a hardware issue in that case… 
I bought another NANOPC-T4, hoping to use manjaro normally, and I am now building an image.
I want to change the value of BUILDSERVER by passing in a variable, can I do it?
You can set the buildserver (which is just what mirror you want to build the image from) in the config file /etc/manjaro-arm-tools/manjaro-arm-tools.conf.
1 Like
U-Boot TPL 2021.10-2 (Dec 25 2021 - 23:04:28)
Channel 0: LPDDR3, 933MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR3, 933MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2021.10-2 (Dec 25 2021 - 23:04:28 +0000)
Trying to boot from MMC1
U-Boot 2021.10-2 (Dec 25 2021 - 23:04:28 +0000) Manjaro Linux ARM
SoC: Rockchip rk3399
Reset cause: POR
Model: FriendlyElec NanoPC-T4
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 3, mmc@fe320000: 1, mmc@fe330000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: FriendlyElec NanoPC-T4
Net:
Error: ethernet@fe300000 address not set.
No ethernet found.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
239 bytes read in 5 ms (45.9 KiB/s)
1: Manjaro ARM
Retrieving file: /initramfs-linux.img
7906375 bytes read in 342 ms (22 MiB/s)
Retrieving file: /Image
30427648 bytes read in 1297 ms (22.4 MiB/s)
append: initrd=/initramfs-linux.img console=ttyS2,1500000 root=PARTUUID=4c99411b-2bd2-4f14-a00e-2572d3cc143a rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtbs/rockchip/rk3399-nanopc-t4.dtb
78058 bytes read in 12 ms (6.2 MiB/s)
Moving Image from 0x2080000 to 0x2200000, end=3fe0000
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f178d000, end f1f17447 ... OK
Loading Device Tree to 00000000f1776000, end 00000000f178c0e9 ... OK
Starting kernel ...
:: running early hook [udev]
Starting version 250.5-1-arch
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/disk/by-partuuid/4c99411b-2bd2-4f14-a00e-2572d3cc143a ...
ERROR: device 'PARTUUID=4c99411b-2bd2-4f14-a00e-2572d3cc143a' not found. Skipping fsck.
:: mounting 'PARTUUID=4c99411b-2bd2-4f14-a00e-2572d3cc143a' on real root
mount: /new_root: can't find PARTUUID=4c99411b-2bd2-4f14-a00e-2572d3cc143a.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
It looks like the UUID of the rootfs partition is not detected by the kernel.
Maybe my SD card is broken.
wifi really doesn’t work.
sudo dmesg | grep "brcmfmac"
[ 7.792025] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-sdio for chip BCM4356/2
[ 7.800656] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4356-sdio.friendlyarm,nanopc-t4.bin failed with error -2
[ 7.827357] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4356-sdio.friendlyarm,nanopc-t4.txt failed with error -2
[ 7.827491] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac4356-sdio.txt failed with error -2
[ 7.855593] usbcore: registered new interface driver brcmfmac
About the radiator test.
I bought an official active cooler and I used fft to test it for stability, at least the fan is working.
stress-ng --cpu 6 --cpu-method fft
sudo sensors
gpu_thermal-virtual-0
Adapter: Virtual device
temp1: +52.2°C (crit = +95.0°C)
tcpm_source_psy_4_0022-i2c-4-22
Adapter: rk3x-i2c
in0: 0.00 V (min = +0.00 V, max = +0.00 V)
curr1: 0.00 A (max = +0.00 A)
cpu_thermal-virtual-0
Adapter: Virtual device
temp1: +63.8°C (crit = +95.0°C)
1 Like
The wifi issue is due to missing firmware file.
I will share the wifi fix tomorrow as its late night here.
Is it pwn fan and does it trip correctly?