Search the Community

Is anyone having issues with the Cinnamon desktop version restarting the desktop when using the menu app launcher? Can be repeated by launching with super key and typing anything for search or just launching any application. Happens with all 3 major menu app launchers. menu, cinnamenu and cinnstark Pinebook pro

This is the uart output of the latest image Armbian_21.05.1_Nanopct4_focal_current_5.10.35.img.xz DDR Version 1.24 20191016 In Channel 0: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB Channel 1: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x2020 ch 1 ddrconfig = 0x101, ddrsize = 0x2020 pmugrf_os_reg[2] = 0x3AA0DAA0, stride = 0xD OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 245 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=59238MB FwPartOffset=2000 , 0 StorageInit ok = 153908 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xcc678 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.10-armbian (May 06 2021 - 17:32:09 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: FriendlyElec NanoPC-T4 DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Model: FriendlyElec NanoPC-T4 Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 6 ms (517.6 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 117 bytes read in 6 ms (18.6 KiB/s) 15343864 bytes read in 704 ms (20.8 MiB/s) 28582400 bytes read in 1304 ms (20.9 MiB/s) 77436 bytes read in 16 ms (4.6 MiB/s) 2698 bytes read in 12 ms (218.8 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Moving Image from 0x2080000 to 0x2200000, end=3de0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15343800 Bytes = 14.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f107a000, end f1f1c0b8 ... OK Loading Device Tree to 00000000f0ffe000, end 00000000f1079fff ... OK Starting kernel ... And it just stucks here... No response to any input (except reset botton) Then I tried the image Armbian_20.05.7_Nanopct4_focal_current_5.4.49.img.xz and it boots. DDR Version 1.24 20191016 In Channel 0: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB Channel 1: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x3 MR5=0x1 MR6=0x5 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x2020 ch 1 ddrconfig = 0x101, ddrsize = 0x2020 pmugrf_os_reg[2] = 0x3AA0DAA0, stride = 0xD OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 245 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 66981 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xa66c0 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.04-armbian (Jun 28 2020 - 18:10:11 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: FriendlyElec NanoPC-T4 DRAM: 3.9 GiB PMIC: RK808 MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: FriendlyElec NanoPC-T4 Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 18 ms (171.9 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 166 bytes read in 15 ms (10.7 KiB/s) 14741002 bytes read in 1421 ms (9.9 MiB/s) 21914112 bytes read in 2097 ms (10 MiB/s) 74693 bytes read in 40 ms (1.8 MiB/s) 2698 bytes read in 40 ms (65.4 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14740938 Bytes = 14.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f5113000, end f5f21dca ... OK Loading Device Tree to 00000000f5098000, end 00000000f5112fff ... OK Starting kernel ... [ 7.289300] OF: graph: no port node found in /i2c@ff3d0000/typec-portc@22 [ 7.324967] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4356-sdio for chip BCM4356/2 [ 10.373166] brcmfmac: brcmf_sdio_readshared: invalid sdpcm_shared address 0xFE8B0174 [ 10.374996] brcmfmac: brcmf_sdio_readshared: unable to obtain sdpcm_shared info: rv=-22 (addr=0xfe8b0174) Armbian 20.05.7 Focal ttyS2 nanopct4 login:

Hi, I am trying to disable UAS mode on attached USB HDs (I have quite a good amount of those) to avoid quite common issues. However, it seems that the usb_storage.quirks string is limited to 127 chars! dmesg shows: usb_storage.quirks: string doesn't fit in 127 chars I do not really see the point of limiting the string length to 127 chars..a bit more would be appreciated. Thanks

I suggest adding a small patch for all u-boot for rk33xx. It allows to enable direct booting from USB media and significantly facilitates the use of RK33xx models for users. Allows you to easily launch any system from USB without the need for complex settings and manipulations with existing (main) systems on devices on SD or eMMC. The entire path fits in two lines. https://github.com/150balbes/Build-Armbian/blob/master/patch/u-boot/u-boot-arm-64/u-boot-0010-rk-usb-start.patch#L18

Hello to everyone , We have several T4 boards and can't get the NVMe SSD we currently have - Toshiba KBG30ZMS256GA - working ... Tried different 4.4 kernels and various distros . The SSD itself proofed to be working in Mikrotik RouterBoard RBM33G . Before we buy some other NVMe SSDs to try , I want to ask for advise . Is it ok to get such messages from kernel : # dmesg | grep -i pci PCI I/O : 0xffffffbffee00000 - 0xffffffbfffe00000 ( 16 MB) [ 0.119383] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created [ 1.540416] PCI: CLS 0 bytes, default 64 [ 1.948302] phy phy-pcie-phy.5: Looking up phy-supply from device tree [ 1.948312] phy phy-pcie-phy.5: Looking up phy-supply property in node /pcie-phy failed [ 1.950471] rockchip-pcie f8000000.pcie: GPIO lookup for consumer ep [ 1.950482] rockchip-pcie f8000000.pcie: using device tree for GPIO lookup [ 1.950510] of_get_named_gpiod_flags: parsed 'ep-gpios' property of node '/pcie@f8000000[0]' - status (0) [ 1.950757] rockchip-pcie f8000000.pcie: Looking up vpcie3v3-supply from device tree [ 1.950858] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply from device tree [ 1.950870] rockchip-pcie f8000000.pcie: Looking up vpcie1v8-supply property in node /pcie@f8000000 failed [ 1.950884] rockchip-pcie f8000000.pcie: no vpcie1v8 regulator found [ 1.950892] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply from device tree [ 1.950901] rockchip-pcie f8000000.pcie: Looking up vpcie0v9-supply property in node /pcie@f8000000 failed [ 1.950913] rockchip-pcie f8000000.pcie: no vpcie0v9 regulator found [ 1.971648] rockchip-pcie f8000000.pcie: invalid power supply [ 2.471703] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 2.471905] rockchip-pcie: probe of f8000000.pcie failed with error -110 [ 2.593787] ehci-pci: EHCI PCI platform driver Our system is current Armbian # uname -a Linux boise 4.4.174-rk3399 #31 SMP Sun Feb 10 00:37:23 CET 2019 aarch64 aarch64 aarch64 GNU/Linux The diagnostics is uploaded to http://ix.io/1EIL Many thanks in advance

There are several questions on the topic: Between the moment of transfer of control to the kernel from the u-boot and the moment of start of the kernel operation it takes 1.5 -2 minutes. I assume that during this period of time there is decompression of the code and placement in memory. But why so long? The 4.4.x kernel starts instantly. When I first turned on a nanopc-t4 with a 5.x.x (4.20) kernel, I already thought the kernel was corrupted. And quite accidentally waited for the green LED to blink. Why is there still no sound in fdt for nanopc-t4? I corrected fdt, but I can 't put it in kernel.org. It is possible that my patch goes against the established structure, but now I use sound. Maybe there are some subtle nuances that I 'm not aware of? Why can 't the kernel turn off power? The 4.4.x kernel was fine. It 's a flaw in fdt, in the kernel, something else? Thanks.

Hi, I want to know if there is another way to power the Nanopc-t4 besides the 12V input power jack. As far as I know the 12V power input is the only way but If someone have another idea or way to do power the board, it could be very helpful for me. Thanks.

Has anybody successfully used the USB type-c displayport of the nanopc-t4? How do you configure it? It works on the images provided by friendlyelec, so, I guess it is just a config/install issue ?

Hi, I'm a user of nanoPC T4( RK3399), now i'm using offical ubuntu release. did Armbian for nanoPC T4 support it's MIPI dual camera? ISP? and other media function? thank you!

Hello all, I have this board and It's suffering crashes and reboots all day. I think the logs are stored in RAM because I can't never find anything related to this issue. Is there anything I can do to find the cause? Many thanks. Regards.

So I noticed my NanoPC-T4's will not boot an image made with the latest armbian build script. I did a binary search on the commits and tracked down the breaking change: commit 75d0f64e3d75e7c34466871b9723ef1a238609d8 <- THIS COMMIT AND ANYTHING AFTER IS BROKEN Author: Piotr Szczepanik <piter75@gmail.com> Date: Fri Apr 17 21:30:37 2020 +0200 Switch rk3399 to u-boot v2020.04 (#1873) * Switched rk3399 to u-boot 2020.04-rc4 * Switched rk3399 u-boot to v2020.04, synchronized configs * Updated to u-boot v2020.04 final * Fixed OrangePi 4 device tree reference commit cc98ba3c0d3ff8d84ed08bfbf691b3bc94a6bc2b <- THIS BOOTS FINE Author: Igor Pečovnik <igorpecovnik@users.noreply.github.com> Date: Fri Apr 17 21:29:06 2020 +0200 Disable MESA on bionic (#1895) Also enable xfce4 power manager on some boards Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> I checked the output on the serial console, it looks like the board gets stuck in an infinite boot loop: ######## POWER ON BOARD ######## DDR Version 1.24 20191016 In Channel 0: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB Channel 1: LPDDR3, 800MHz CS = 0 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F CS = 1 MR0=0x58 MR1=0x58 MR2=0x58 MR3=0x58 MR4=0x2 MR5=0x1 MR6=0x6 MR7=0x0 MR8=0x1F MR9=0x1F MR10=0x1F MR11=0x1F MR12=0x1F MR13=0x1F MR14=0x1F MR15=0x1F MR16=0x1F Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=2048MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x2020 ch 1 ddrconfig = 0x101, ddrsize = 0x2020 pmugrf_os_reg[2] = 0x3AA0DAA0, stride = 0xD OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 248 mmc: ERROR: sdhci_complete_adma: transfer error, stat 0x408000, adma error 0, retry 9996026, cmd 0x83a mmc: ERROR: sdhci_complete_adma: transfer error, stat 0x408000, adma error 0, retry 9996025, cmd 0x83a emmc reinit mmc: ERROR: sdhci_complete_adma: transfer error, stat 0x408000, adma error 0, retry 9996026, cmd 0x83a mmc: ERROR: sdhci_complete_adma: transfer error, stat 0x408000, adma error 0, retry 9996027, cmd 0x83a emmc reinit mmc: ERROR: sdhci_complete_adma: transfer error, stat 0x408000, adma error 0, retry 9996021, cmd 0x83a mmc: ERROR: sdhci_complete_adma: transfer error, stat 0x408000, adma error 0, retry 9996022, cmd 0x83a SdmmcInit=2 1 mmc0:cmd5,20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=128001MB FwPartOffset=2000 , 0 StorageInit ok = 121149 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 hdr 0000000003380880 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00, Load OK, addr=0x200000, size=0xad9e8 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will reK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.04-armbian (Apr 26 2020 - 00:46:29 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: FriendlyElec NanoPC-T4 DRAM: 3.9 GiB PMIC: RK808 MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - No block device, using default environment "Synchronous Abort" handler, esr 0x96000045 elr: 0000000000231550 lr : 00000000002314ec (reloc) elr: 00000000f4576550 lr : 00000000f45764ec x0 : 00000000f254a3c0 x1 : 00000000f8000000 x2 : 00000000f82a4000 x3 : 0000000000000000 x4 : 0000000011b3dc40 x5 : 0000000011b3dc40 x6 : 00000000ffffdff1 x7 : 0000000000000128 x8 : 0000000000000129 x9 : 0000000000000008 x10: 0000000000000008 x11: 0000000000000001 x12: 000000000000012a x13: 0000000000005dc0 x14: 0000000000000000 x15: 00000000f252d698 x16: 0000000000008080 x17: 0000000000000032 x18: 00000000f253cdd8 x19: 00000000f254a3c0 x20: 00000000f25415a0 x21: 00000000f252d480 x22: 00000000f45ea6c8 x23: 00000000f45ea6c8 x24: 00000000f254a368 x25: 00000000f254a370 x26: 00000000f254a130 x27: 00000000f254a378 x28: 0000000000000002 x29: 00000000f252d430 Code: 8b020022 eb02003f 54fffee2 b9403403 (b8004423) Resetting CPU ... resetting ... ######## OUTPUT REPATS AT THIS POINT ########

Amrbian does not seem to turn on the NanoPC-T4 fan. I searched the information and turned on the fan on my NanoPC-T4. cd /sys/class/gpio sudo sh -c "echo 150 > export" cd gpio150 sudo sh -c "echo out > direction" sudo sh -c "echo 1 > value" # Fan Is ON. AND sudo sh -c "echo 0 > value" # Fan Is OFF.

Greetings, Here's a quick and very dirty way to use the NVMe disk for the whole system, except the boot files and kernels which will be read from the SDCard. This method is UNSUPPORTED. Meaning that if you follow this procedure and your system broke, catched fire and start attacking you in your sleep, it's on you ! The reason I keep booting on the SDCard are : This makes boot issues easier to deal with since all the files are more easily accessible. It's easy to quickly read a SDCard from a PC using a SDCard reader USB dongle bought from the local store. Meanwhile mounting a NVMe<->USB readers are not that common. It's pretty much guaranteed that the bootloader knows how to boot a SDCard. The procedure is documented here : https://gist.github.com/Miouyouyou/e78f4caa9ce3fea72430dca57a00449b Here's a copy of its content : Moving most of the system (but not the kernel) onto the NVME disk This document describes how to make the system : boot on a SDCARD load the kernel from the SDCARD mount a NVMe partition as / use / for the whole system and applications In this document folder and directory mean the same thing. The whole idea is to be able to edit the boot files easily (kernel, boot configuration, ...) in case something goes wrong, while benefiting from NVMe read/write speeds for you daily application usage. The procedure described is not "THE BEST", just the one I used that worked in my case. Here are the steps I followed to do that : Prepare a SDCARD with an Armbian image, using Etcher. Install a NVMe M.2 disk on the rear side of the NanoPC T4. Put the SDCARD in the NanoPC T4 SDCARD slot. Boot Armbian and configure your first user. Note : The 'root' account password is 1234 on first boot Create a "Linux root (ARM 64)" partition (and maybe a swap partition if you want) on the NVMe disk. Note : Linux root (ARM 64) ID is B921B045-1DF0-41C3-AF44-4C6F280D3FAE Note : The disk can be accessed through /dev/nvme0n1 Note : I used cfdisk for that matter, but any decent partitioning software will do. Format the NVMe root partition using mkfs.ext4 For example, if you just made one partition, the device node will be : /dev/nvme0n1p1 and so the command will be : mkfs.ext4 /dev/nvme0n1p1 Mount your NVMe root partition on /mnt. For example, if you just made one partition, the device node will be : /dev/nvme0n1p1 and so the command will be : mount /dev/nvme0n1p1 /mnt Do a filesystem copy of / into /mnt, while ignoring special files created on boot-time : rsync -a -H --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /mnt Use blkid on your NVMe root partition to get its UUID. For example, if you just made one partition, the device node will be : /dev/nvme0n1p1. And so the command will be : blkid /dev/nvme0n1p1 In my case, the command output was : /dev/nvme0n1p1: UUID="cbe70e76-9690-4f69-ab6e-23b887531628" TYPE="ext4" PARTUUID="c4a2536b-5092-0b4b-8178-c4215a52ac4b" Edit /mnt/etc/fstab and replace the UUID part of the line about / by the UUID of your NVMe root partition, that you just got from the last command. The line in question is somewhat like this : UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 In my case, I modified it so that it looked like this : UUID=cbe70e76-9690-4f69-ab6e-23b887531628 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 Do a copy of /boot/armbianEnv.txt like this : cp /boot/armbianEnv.txt /boot/armbianEnv.working Edit /boot/armbianEnv.txt and replace the UUID in the line rootdev=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx by the UUID of your NVMe root partition. In my case, the line was modified like this : rootdev=UUID=cbe70e76-9690-4f69-ab6e-23b887531628 Reboot and see if it worked. If it didn't, you'll have to remove the SDCard from the NanoPC T4, read it from a Linux PC, mount the boot partition, delete boot/armbianEnv.txt and copy boot/armbianEnv.working over boot/armbianEnv.txt. Then you'll be able to retry the procedure from the point were we get the UUID of the NVMe partition (step 7). If it's working, though, it's not finished ! In order to make kernel upgrades possible, we'll have to link the NVMe root partition /boot folder to the SDCard root partition /boot folder. Use blkid on your SDCard root partition, in order to get its UUID. blkid /dev/mmcblk1p1 In my case the output was : /dev/mmcblk1p1: UUID="c5dcbfc7-886b-4c98-ac2a-4d26eec089e8" TYPE="ext4" PARTUUID="d808ef5d-01" Create a directory /sdcard : mkdir /sdcard Do a backup of your /etc/fstab : cp /etc/fstab /etc/working_fstab Add an entry to /etc/fstab to mount the content of the SDCard boot partition to /sdcard automatically. In my case the UUID of that partition was c5dcbfc7-886b-4c98-ac2a-4d26eec089e8 so the line added was : UUID=c5dcbfc7-886b-4c98-ac2a-4d26eec089e8 /sdcard ext4 defaults,noatime,nodiratime,commit=600,nodev,noexec 0 1 Adapt according to your configuration. Test your /etc/fstab configuration by doing : mount /sdcard If that doesn't work, check back your /etc/fstab. If you messed up, cp /etc/working_fstab /etc/fstab Backup the /boot directory : mv /boot /unused_boot Link your SDCard boot partition boot folder to /boot : ln -s /sdcard/boot /boot Reboot one last time And now you should be able to upgrade your kernel while booted on your NVMe disk, while still being able to access the upgrade kernel and boot configuration from the SDCard. This is very useful when a kernel upgrade broke your system. That way, you just have to remove the SDCard, read it from a Linux computer, replace the broken kernel or edit /etc/armbianEnv.txt to boot temporarily on the SDCARD in order to repair the issue. Improvements /sdcard should only be mounted when boot files have to be updated. This avoid softwares trying to access the SDCard for no reasons.

Hi all, i build the nanopc t4 firmware and the wifi not work. target: ubuntu18.04 desktop kernel: mainline 5.4.17 any suggestions? Thanks.

I'm about to install active cooling fan on my recently delivered nanoPI T4. However, I cannot get what is a type of the soldered 3-pin fan connector on this board? What I see there is visually too small as for standard connector size. Is it something special I have no clue about yet, or it is for future proprietary Friendlyarm's fan designed specially for the board? Any suggestions are welcome! Thanks

Flashed Armbian Buster to eMMc and now want to flash to Armbian Bionic. I know there's instructions using a usbC in the friendlyarm wiki but this just isn't working out... I used the Windows method / tool to erase the eMMC as it says which seemed to work but it still boots from the eMMC :/ Are there any better instructions any where?

Hi, after solving the WIFI issue on my T4, i've tried to setup an AP. With the armbian-config it was pretty easy and i only changed the channel to 1 on for the g mode and the country_code on for n mode: cat /etc/hostapd.conf # # armbian hostapd configuration example # # nl80211 mode # ssid=ARMBIAN interface=wlan0 hw_mode=g channel=1 #bridge=br0 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 wpa=2 preamble=1 wpa_psk=844418fea2e83eea256a88c751f2823c2d5e6d52193b27cfa34234e0d6de0ab9 wpa_passphrase=12345678 wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP auth_algs=1 macaddr_acl=0 noscan=1 ## IEEE 802.11n ieee80211n=1 ht_capab=[DSSS_CK-40][HT20+] country_code=DE ieee80211d=1 ## IEEE 802.11n ## IEEE 802.11a hw_mode=a ## IEEE 802.11a ### IEEE 802.11ac #ieee80211ac=1 #vht_capab= #vht_oper_chwidth=1 #vht_oper_centr_freq_seg0_idx=42 ### IEEE 802.11ac # controlling enabled ctrl_interface=/var/run/hostapd ctrl_interface_group=0 The hostapd service is running and i don't see issues on the logs: journalctl -u hostapd -b0 -- Logs begin at Mon 2020-01-06 16:17:56 CET, end at Mon 2020-01-06 16:21:57 CET. -- Jan 06 16:18:03 monitoring systemd[1]: Starting LSB: Advanced IEEE 802.11 management daemon... Jan 06 16:18:03 monitoring hostapd[2083]: Starting advanced IEEE 802.11 management: hostapd. Jan 06 16:18:03 monitoring systemd[1]: Started LSB: Advanced IEEE 802.11 management daemon. journalctl -u NetworkManager -b0 -- Logs begin at Mon 2020-01-06 16:17:56 CET, end at Mon 2020-01-06 16:21:13 CET. -- Jan 06 16:17:59 monitoring systemd[1]: Starting Network Manager... Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.4818] NetworkManager (version 1.14.6) is starting... (for the first time) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.4819] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf, zz-override-wifi-powersave-off.conf) (etc: 10-ignore-in Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.4838] wifi-nl80211: (wlan0): using nl80211 for WiFi device control Jan 06 16:17:59 monitoring systemd[1]: Started Network Manager. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.5048] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.5090] manager[0xaaaad8373030]: monitoring kernel firmware directory '/lib/firmware'. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.5099] monitoring ifupdown state file '/run/network/ifstate'. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8126] hostname: hostname: using hostnamed Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8127] hostname: hostname changed from (none) to "monitoring" Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8132] dns-mgr[0xaaaad837f130]: init: dns=default, rc-manager=file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8145] rfkill0: found WiFi radio killswitch (at /sys/devices/platform/fe310000.dwmmc/mmc_host/mmc0/mmc0:0001/mmc0:0001:1/ieee80211/phy0/rfkill0) ( Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8149] manager[0xaaaad8373030]: rfkill: WiFi hardware radio set enabled Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8149] manager[0xaaaad8373030]: rfkill: WWAN hardware radio set enabled Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8926] ifupdown: interface-parser: parsing file /etc/network/interfaces Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8927] ifupdown: interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/* Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8929] ifupdown: interface-parser: parsing file /etc/network/interfaces.d/armbian.ap.nat Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8930] ifupdown: interface-parser: finished parsing file /etc/network/interfaces.d/armbian.ap.nat Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8930] ifupdown: interface-parser: finished parsing file /etc/network/interfaces Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8972] ifupdown: guessed connection type (wlan0) = 802-3-ethernet Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.8984] ifupdown: update_connection_setting_from_if_block: name:wlan0, type:802-3-ethernet, id:Ifupdown (wlan0), uuid: 5391eba4-6426-faca-338e-5828 Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9006] ifupdown: addresses count: 1 Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9007] ifupdown: No dns-nameserver configured in /etc/network/interfaces Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9012] ifupdown: management mode: managed Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9013] settings: Loaded settings plugin: SettingsPluginIfupdown ("/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9014] settings: Loaded settings plugin: NMSKeyfilePlugin (internal) Jan 06 16:17:59 monitoring NetworkManager[844]: ((src/settings/nm-settings.c:899)): assertion '<dropped>' failed Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9113] keyfile: new connection /etc/NetworkManager/system-connections/Wired connection 1.nmconnection (4b7772f2-c308-3687-a691-24fb00771bdf,"Wired Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9165] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9169] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9172] manager: Networking is enabled by state file Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9178] dhcp-init: Using DHCP client 'dhclient' Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9311] Loaded device plugin: NMTeamFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-team.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9500] Loaded device plugin: NMBluezManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-bluetooth.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9545] Loaded device plugin: NMWifiFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wifi.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9573] Loaded device plugin: NMWwanFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wwan.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9595] Loaded device plugin: NMAtmManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-adsl.so) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9633] device (lo): carrier: link connected Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9647] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9738] manager: (dummy0): new Dummy device (/org/freedesktop/NetworkManager/Devices/2) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9761] device (eth0): driver '(null)' does not support carrier detection. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9778] device (eth0): driver 'rk_gmac-dwmac' does not support carrier detection. Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9805] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3) Jan 06 16:17:59 monitoring NetworkManager[844]: <info> [1578323879.9897] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0146] device (wlan0): driver supports Access Point (AP) mode Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0158] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4) Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0230] manager: NetworkManager state is now CONNECTED_GLOBAL Jan 06 16:18:00 monitoring NetworkManager[844]: <info> [1578323880.0610] supplicant: wpa_supplicant running Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:00 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:02 monitoring NetworkManager[844]: <info> [1578323882.8956] agent-manager: req[0xaaaad83dcb60, :1.51/org.freedesktop.nm-applet/1000]: agent registered Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0734] device (eth0): carrier: link connected Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0739] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0753] policy: auto-activating connection 'Wired connection 1' (4b7772f2-c308-3687-a691-24fb00771bdf) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0774] device (eth0): Activation: starting connection 'Wired connection 1' (4b7772f2-c308-3687-a691-24fb00771bdf) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0776] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0785] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0794] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0809] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.0862] dhcp4 (eth0): dhclient started with pid 2065 Jan 06 16:18:03 monitoring dhclient[2065]: DHCPREQUEST for 192.168.178.59 on eth0 to 255.255.255.255 port 67 Jan 06 16:18:03 monitoring dhclient[2065]: DHCPACK of 192.168.178.59 from 192.168.178.1 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1639] dhcp4 (eth0): address 192.168.178.59 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1644] dhcp4 (eth0): plen 24 (255.255.255.0) Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1647] dhcp4 (eth0): gateway 192.168.178.1 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1651] dhcp4 (eth0): lease time 864000 Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1655] dhcp4 (eth0): nameserver '192.168.178.1' Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1658] dhcp4 (eth0): domain name 'fritz.box' Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1662] dhcp4 (eth0): state changed unknown -> bound Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1702] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1739] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1748] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jan 06 16:18:03 monitoring dhclient[2065]: bound to 192.168.178.59 -- renewal in 371156 seconds. Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1825] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1883] device (eth0): Activation: successful, device activated. Jan 06 16:18:03 monitoring NetworkManager[844]: <info> [1578323883.1918] manager: startup complete Jan 06 16:18:05 monitoring NetworkManager[844]: <info> [1578323885.3641] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds) Jan 06 16:18:05 monitoring NetworkManager[844]: <info> [1578323885.3766] dhcp6 (eth0): dhclient started with pid 2212 Jan 06 16:18:05 monitoring NetworkManager[844]: <info> [1578323885.3884] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS Jan 06 16:18:06 monitoring dhclient[2212]: XMT: Confirm on eth0, interval 1090ms. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Reply message on eth0 from fe80::218:e7ff:fe8c:47ed. Jan 06 16:18:06 monitoring dhclient[2212]: message status code NotOnLink. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Reply message on eth0 from fe80::5e49:79ff:fecc:7966. Jan 06 16:18:06 monitoring dhclient[2212]: Packet received, but nothing done with it. Jan 06 16:18:06 monitoring dhclient[2212]: XMT: Solicit on eth0, interval 1070ms. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Advertise message on eth0 from fe80::5e49:79ff:fecc:7966. Jan 06 16:18:06 monitoring dhclient[2212]: RCV: Advertise message on eth0 from fe80::218:e7ff:fe8c:47ed. Jan 06 16:18:07 monitoring dhclient[2212]: XMT: Request on eth0, interval 1010ms. Jan 06 16:18:07 monitoring dhclient[2212]: RCV: Reply message on eth0 from fe80::218:e7ff:fe8c:47ed. Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5159] dhcp6 (eth0): valid_lft 4294967295 Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5160] dhcp6 (eth0): preferred_lft 4294967295 Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5161] dhcp6 (eth0): address fd66:cf76:8fa7::89d Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5161] dhcp6 (eth0): nameserver 'fd66:cf76:8fa7::1' Jan 06 16:18:07 monitoring NetworkManager[844]: <info> [1578323887.5162] dhcp6 (eth0): state changed unknown -> bound, event ID="a8:14:15:3c|1578323887" Jan 06 16:18:39 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:39 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Jan 06 16:18:39 monitoring NetworkManager[844]: ((src/settings/nm-settings-connection.c:361)): assertion '<dropped>' failed Also the interface configuration looks goog to me: ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether f6:36:7d:30:a5:ca brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 02:1d:a8:14:15:3c brd ff:ff:ff:ff:ff:ff inet 192.168.178.59/24 brd 192.168.178.255 scope global dynamic noprefixroute eth0 valid_lft 863861sec preferred_lft 863861sec inet6 fd66:cf76:8fa7::89d/128 scope global noprefixroute valid_lft forever preferred_lft forever inet6 2001:16b8:5066:1700:e81e:ea43:845c:cdcb/64 scope global dynamic noprefixroute valid_lft 7064sec preferred_lft 3464sec inet6 fd66:cf76:8fa7:0:26ab:de71:b182:c11b/64 scope global deprecated dynamic noprefixroute valid_lft 7064sec preferred_lft 0sec inet6 fe80::8a25:20f8:3eb5:f90/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether cc:4b:73:5a:4c:cc brd ff:ff:ff:ff:ff:ff inet 172.24.1.1/24 brd 172.24.1.255 scope global wlan0 valid_lft forever preferred_lft forever I've compared this configuration with some other tutorials and i don't see the issue why it's not working. If i scan the wifi no ARMBIAN is shown. Also configuring the WIFI manually don't lead to success (i just want to ensure that it isn't hidden). Any idea?

I am still trying unsuccessfully to get the sound through the rt5651 codec using the main line kernel (I use NanoPC-T4). I corrected the dts/dtb file and assembled the kernel module. The kernel performs i2s bus and codec switching. The corresponding audio device appears on the system. I start a alsamixer. I can change settings. When I change some settings, I can even hear clicks in the dynamic. So the codec chip is powered up. And the codec chip is controlled through the i2c bus. I can switch the audio output through the codec. But there is no sound. I can 't figure out what the reason is. The dts/dtb files for main line kernel and rockchip 4.4.xxx kernel are slightly different. But I don 't see any criticism. Maybe I can 't understand that. The kernel generates several error messages when initializing the audio sub-system. But in my opinion, these mistakes are not critical. It seems that the audio stream is not going on the i2s bus connected to codec. Or the codec chip does not receive the stream. Give advice. What else can I check?

VPU hardware encode/decode appears to not work on the NanoPC-T4. I know it's a WIP. If there is a Post Installation Procedure I could do that would work for me.

Trying to sync latest beta release of Geth Ethereum client and it's filling ram till process crashes. Apparently setting a swap file helps - but sudo swapon -show says /dev/zram1/ 1gb partition already set up... I was going to set up a 4gb swap file on the nvme - what to do? Thanks for any advice.

steps to reproduce: 1. download official stable images and extract 2. write either image (both fail in same way) to sdcard: Armbian_5.91_Nanopct4_Debian_buster_default_4.4.179.img Armbian_5.90_Nanopct4_Ubuntu_bionic_default_4.4.179.img 3. boot sdcard -> works fine 4. run armbian-config -> firmware update 5. (also tried "apt update && apt full-upgrade", same result) 6. reboot -> boot loop happens every time, either the ubuntu or debian versions of armbian. no changes made after booting beyond just doing the update. reliably boot loops (it makes it to booting the kernel, then the board restarts after a while of no output) note: I cannot see the kernel printk messages, because any time I add "console=ttyS2,1500000" last (either by using "console=serial" in armbianEnv.txt or adding it to extraargs), it also boot loops then (even pre-upgrade). ttyS2 works fine as one of the consoles, and getty/login works (via minicom), but it cannot be the primary console (ie the last one specified) or it will boot loop. it may need an earlyprintk argument or something... not sure how to proceed. seems to work fine until updating it... note: the armbianmonitor URL is from *before* reboot obviously since it will not make it to OS init after

Hi folks! Some problems later I just build my ethereum-node using the FriendlyARM NanoPC T4 (Reddit project Ethereum on NanoPC T4). Using it indoor the temperature climbs to 80° celsius with the passive cpu-heatspreader. So I decided to install a fan and found the specs for the 'Cooling Fan interface'. The connector is named BM03B-GHS-TBT. Where can I buy a fan (40x40mm)? I only find fans with 3-pole-molex-adapter. All I know is the name of the male connector (in german): "JST Buchsengehäuse-Kabel GH Polzahl Gesamt 3 Rastermaß: 1.25 mm GHR-03V-S".

I'm setting up a NanoPC T4 as a network server running OpenMediaVault. I wasn't sure where to post this and I thought I'd start here. I'm replacing an existing BananaPi and I have it and the T4 up at the same time. I've used the BananaPi to stream video files to Raspberry Pi clients running Kodi. The BananaPi has been working well with an older version of Linux and OpenMediaVault. What's happening is video served from the T4 starts playing well but then stops shortly after playback has started. The same video file works well on the BananaPi. I've tried placing the file on an NVMe M.2 drive as well as USB 3.0 and USB 2.0 connected hard disks. I've tried this through NFS as well as Samba and the same things happen with both. I tried this with both the nightly Armbian Stretch 4.20.x image and the legacy Armbian Stretch 4.4.x image with the same issue happening. The BananaPi and the T4 are both wired to a router with the T4 directly connected to a router port and the BananaPi connected through a small unmanaged switch. At this point, it looks like it may be some network related issue as this seems like the common point for all of these devices/attempts. I'm not sure how to confirm this and if this is the issue, how it can be corrected. Any help is appreciated. Thank you

Board: NanoPC-T4(rk3399) OS: Welcome to ARMBIAN 5.69 stable Ubuntu 18.04.1 LTS 4.4.167-rk3399 In VLC preferences, i have set video output to OPENGL ES(and here OPENGL ES is soft link to libMali.so). In short hardware accelerated Rendering. Problem Statement: When a video file is played in fullscreen mode it works perfect. But as soon as other x-window(for eg: small sized terminal window) comes in front of this fullscreen window, tearing effect starts. Now i don't understand why this happen. Whether it happens due to libMali and X-server Glamor compositing or something else. i don't have full understanding of linux graphics stack. As per rockchip link: http://opensource.rock-chips.com/wiki_File:Xserver_gpu.png X application and GL application feed data to Kernel with different path(ie. one is libDRM and other is libMali). Where this data is merged before rendering the front buffer? Is it compositor who introduce the tearing effect? If yes, this compositor is at DRM level(kernel space) or userspace(Although i have checked through Window Manager Tweaked, compositing is disabled)? Note: i checked X-server conf file(/etc/X11/xorg.conf.d/01-armbian-defaults.conf) and find -> Option "Dri2Vsync" "true". Please shed some light how this tearing effect can be eliminated. As per my use case i need to render data through GLES and as well need to render some X11 window. I tried to elaborate the problem but still anything missing, please let me know.

Hi, i bought a nanopc t4, then i installed armbian on it's eMmc , after starting os, i plug in a usb flash to it's usb2.0 ports(both usb 2.0 ports) but not working but when i plug in the usb flash to it's usb port 3.0 it will be work, i tried this issue with mouse and keyboard usb and some another usb flashes that has usb 2.0 compatibility, can anyone help me to setup my nanopc t4 usb 2.0 ports?