[WIP]

Schematics

Pros:

- board vendor provides dev samples and documentation

- working with latest mainline kernel

- many variants by the same vendor

- official SDK/BSP currently on 4.4

- no unreliable shitty Micro USB for DC-IN but GPIO by default

Cons:

- new platform needing more initial work

- not many active developers

I'm incurring in a issue with updates of the board to Armbian 26.8.

The new kernel or updates break the board connectivity gets lost, since the board boots up, the LAN port blinks but it doesn't set any IP Address.

The board works in headless mode with the Debian 13 CLI UFS image, so I can't debug it using a monitor.

Has anyone the same issue?

How to reproduce

1.Flash the recommended Debian 13 Trixie CLI Image from Armbian Website

2.Start the board normally, in headless mode

3.login with ssh

4.set a new user account

5.Run apt update && apt dist-upgrade -y and then reboot

6.Board is not reachable anymore via ssh, board has no IP address, even when setting static IP

If possible, I would like to flash/replace the boot loader that is not specific for pfsense, but I am a total beginner with arm boards and boot loaders. Not as easy as installing various Linux distros...

 

Marvell>> printenv
arch=arm
baudrate=115200
board=mvebu_armada-37xx
board_name=mvebu_armada-37xx
boot_file=efi/boot/bootaa64.efi
bootcmd=run setLED; run mmcboot; run scsiboot; run usbboot; run net;
bootdelay=2
cpu=armv8
dmi_board_mfg=Silicom
dmi_board_name=xxxxxxxx
dmi_board_serial=xxxxxxxx
dmi_board_ver=R301
dmi_chassis_mfg=Silicom
dmi_chassis_serial=xxxxxxxx
dmi_chassis_ver=R301
dmi_sys_mfg=Silicom
dmi_sys_name=SG-2100
dmi_sys_serial=xxxxxxxx
dmi_sys_ver=R301
dtb_name=armada-3720-sg2100.dtb
eth1addr=xxxxxxxx
ethact=neta@xxxxxxxx
ethaddr=xxxxxxxx
ethprime=eth0
fdt_addr_r=0xc00000
fdtcontroladdr=7f623360
gatewayip=xxxxxxxx
ipaddr=0.0.0.0
kernel_addr_r=0x1000000
load_dev=usb
loadaddr=0x1000000
mmcboot=mmc rescan; setenv load_dev mmc; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi;
net=dhcp; tftp ${fdt_addr_r} ${dtb_name}; tftp ${kernel_addr_r} loader.efi; fdt addr ${fdt_addr_r}; fdt set / sn ${dmi_sys_serial}; bootefi ${kernel_addr_r} ${fdt_addr_r};
netgateid=xxxxxxxx
netmask=255.255.255.0
pfsenseboot=load ${load_dev} 0:2 ${fdt_addr_r} ${dtb_name}; load ${load_dev} 0:1 ${kernel_addr_r} ${boot_file}; fdt addr ${fdt_addr_r}; fdt set / sn ${dmi_sys_serial}; bootefi ${kernel_addr_r} ${fdt_addr_r};
pxefile_addr_r=0x2000
ramdisk_addr_r=0x2000000
rootpath=/srv/nfs/
scsiboot=scsi reset; setenv load_dev scsi; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi;
serverip=0.0.0.0
setLED=i2c dev 1; i2c reset; i2c mw 67 ff 0; i2c mw 67 0 1; i2c mw 67 f 20; i2c mw 67 3 40; i2c mw 67 26 0; i2c mw 67 10 0;
soc=mvebu
stderr=serial@12000
stdin=serial@12000
stdout=serial@12000
usb_pgood_delay=4000
usbboot=usb reset; setenv load_dev usb; if fatls ${load_dev} 0:2 /; then run pfsenseboot; fi;
usbrecovery=mmc erase 0 400000; run usbboot
vendor=Marvell

however, I can't find them on the downloads page. I also don't currently own an RPMini, I am tempted to buy one but I wanted to make sure it was supported first. What's the state of support right now?

Thanks to the work of many, there is now a real opportunity to run the Armbian system with the main core on Jetson Nano, and more importantly, it is easy to integrate the image build process into the official GIT Armbian. In the near future, I plan to post ready-made images with the latest kernel 5.10.22 on the download site. To run them, you need to update u-boot to Jetson Nano. This is very easy to do, just run the latest official version of Ubuntu for Jetson Nano from the SD card, it will update itself in SPI (?) u-boot to the latest version (2020.04), after that you can run Armbian from any SD card or USB media. The new u-boot supports automatic system startup from both media or over the network. Also, now you can build an Armbian image for Jetson Nano yourself, easily build the latest kernel with the necessary options, etc.  

https://users.armbian.com/balbes150/

https://mega.nz/#F!j9QSDQSQ!6WpasOlbZYIInfw6yo4phQ

https://disk.yandex.ru/d/XBRXnig7F1M4rw?w=1

I am running into an issue when trying to compile an image for a SM8250 device.

Most of the process is working fine until it gets to the Grub Section, at which point I get the following error: " cp: cannot stat '/usr/lib/linux-image-6.18.24-current-sm8250/qcom/sm8250-retroidpocket-rp5.dtb': No such file or directory"

I have attached the logs, and would love to know if anyone has had a similar issue when trying to build an image for any device, and if so what you have done to solve it.

Thanks all in advance for the support

I am trying to confirm the actual status of UART support on the Banana Pi BPI-R4.

Does the hardware UART work reliably and appear as a character device (e.g., /dev/uart*) under Armbian Linux?

Also, what is the maximum baud rate supported by this port?

And one more question:

Does Armbian support the Quectel EP06 modem (LTE, mini PCIe)?

Thank you in advance,

SY, Serge

I have downloaded this https://dl.armbian.com/cubox-i/Noble_current_server and verified that I got what I was supposed to (ASC, SHA).

I have used a brand new usbimager to install it on various freshly formatted (brand new SD Formatter) and verified working Samsung Evo 32GB, SanDisk Extreme Plus 16GB, Extreme Plus 32GB.

All the formatting, imaging and installation done on an Ubuntu 25.04 laptop.

After usbimager is done, if I use the Ubuntu Disks application to look at the drive, the first partion shows as free space, which seems suspicious.

When I insert the newly-set up SD cards in the Cubox-i4, I see the bootloader start and then do its handoff to the operating system... and then nothing.  No more signal on the HDMI cable, nothing out on ssh, nothing.  The Cubox-i4 tries to reboot every few minutes with no more successful outcome.

This same Cubox-i4 runs fine with the last SD card system disk I built for it using the previous Debian server image.

Does anyone have any ideas?

Thanks in advance!

But given my situation, I set up two Ethernet interfaces. I haven't tested them at full capacity, but I can ping from both networks...

myd lt527m 16e2d 180 e sx

Thanks a lot.

I am working with the TQ mba8mpxl-ras314 (i.MX8MP) board and trying to use an LVDS display: AUO G150XAN02.0 (1024×768).

I have built Armbian from source using:

./compile.sh build \
  BOARD=mba8mpxl-ras314 \
  BRANCH=current \
  RELEASE=jammy \
  BUILD_DESKTOP=yes \
  BUILD_MINIMAL=no \
  DESKTOP_ENVIRONMENT=xfce \
  DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base \
  KERNEL_CONFIGURE=no

I created a custom LVDS DTS overlay with the correct timing from the display datasheet (65 MHz pixel clock, 1024×768, proper porch and sync settings), and added it to

 

However, after booting the image, the LVDS output still stays at 1280×800, which is the default panel configuration for the Tianma panel used in TQ’s reference device tree.

The expected resolution 1024×768 does not apply, even though:

The overlay compiles correctly

The .dtbo file is present

The build finishes successfully

I am unsure whether:

My overlay is not being applied

The correct panel node name is different from &display

Another overlay overrides mine

The i.MX8MP LVDS binding needs a different structure

Armbian’s mba8mpxl-ras314 base DTS is overriding the timing

Unfortunately all of the AX25 kernelmodules have been left out of official builds. I have a commit ready to add them back, yet I am not sure what the actual process is to submit a PR. As I understood I need to open an issue first yet I cannot figure out which category this fits in.

I attached a patch file for current kernel.

Thank You,

Geoffrey 

ax25.patch

Launching the desktop and displaying the image on the screen can take 30-80 seconds, depending on the speed of the media.

https://disk.yandex.ru/d/gedMM0eLiURrjA

Armbian-unofficial 25.05.0-trunk Noble ttyAMA2 

orion-o6 login: root
Password: 
    _             _    _                             __  __ _    _      _ 
   /_\  _ _ _ __ | |__(_)__ _ _ _ ___ _  _ _ _  ___ / _|/ _(_)__(_)__ _| |
  / _ \| '_| '  \| '_ \ / _` | ' \___| || | ' \/ _ \  _|  _| / _| / _` | |
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|   \_,_|_||_\___/_| |_| |_\__|_\__,_|_|
                                                                          
 v25.05 rolling for Orion O6 running Armbian Linux 6.1.44-legacy-media-cix

 Packages:     Ubuntu stable (noble)
 Support:      DIY (custom image)
 IPv4:         (LAN) 192.168.1.47 (WAN) 185.213.138.150 

 Performance:  

 Load:         21%              Up time:       0 min
 Memory usage: 4% of 14.86G 
 CPU temp:     32°C              Usage of /:   40% of 14G    
storage/:      1% of 253M   
 RX today:     6 MiB        
 Commands: 

 Configuration : armbian-config
 Monitoring    : htop

root@orion-o6:~# 


Disk /dev/ram14: 40 MiB, 41943040 bytes, 81920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 40 MiB, 41943040 bytes, 81920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: MTFDHBA256TCK-1AS1AABHA                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E146202C-4719-46E5-B98F-3B8E899D01FD

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      2048    206847    204800   100M EFI System
/dev/nvme0n1p2    206848    239615     32768    16M Microsoft reserved
/dev/nvme0n1p3    239616 499049968 498810353 237.9G Microsoft basic data
/dev/nvme0n1p4 499050496 500115455   1064960   520M Windows recovery environment


Disk /dev/sda: 14.32 GiB, 15376000000 bytes, 30031250 sectors
Disk model: Ultra Fit       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: AC0DE29F-BE91-413F-B3A6-7A9DF368C41D

Device      Start      End  Sectors  Size Type
/dev/sda1    8192   532479   524288  256M EFI System
/dev/sda2  532480 30031216 29498737 14.1G Linux root (ARM-64)


Disk /dev/zram0: 7.43 GiB, 7979745280 bytes, 1948180 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

@chainsx might you be able to divulge where you forked it from?

I'm thinking of getting https://www.beagleboard.org/boards/beagley-ai

I see there is this page for it

https://www.armbian.com/beagley-ai/

I also see references to it in the code: https://github.com/search?q=org%3Aarmbian+beagley&type=code

Are there any pre-built images available for it? Or would I have to build one?

and tracking down that platform_install.sh yields

dd if="$SRC"/cache/sources/arm-trusted-firmware/mtksoc-20250212/build/mt7988/release/bl2.img of=$2 bs=512 seek=34 status=noxfer > /dev/null 2>&1;

Note that cache/sources/arm-trusted-firmware does not appear to exist, and [although this may be my lack of knowing what to look for] I find no evidence it attempted to fetch this repo or build the firmware.

Yes, this board is only recently submitted, so some problems may be expected. I did wait for the automated build, but no luck there.

or maybe I'm screwing up the build somehow. Using docker, but it's on a Debian11 host, which I know isn't supported as a build platform.

./compile.sh build BOARD=bananapir4 BUILD_MINIMAL=yes RELEASE=bookworm DEBUG=yes KERNEL_CONFIGURE=no BRANCH=current

Full build log here: https://paste.armbian.com/isidematup

@chainsx looks to be the guy who submitted the pull-request.

Hello,
 

I'm developing a Custom Armbian for the RSB-4411 (the motherboard that uses like the Raise3D E2).
 

For the moment, it's in the experimental phase because I can't get it to boot.

It goes CRC-ERROR when I boot into the debug port on my motherboard.
 

Source codes

• Armbian build: https://github.com/AstromanGaming/build
• Linux Kernel: https://github.com/AstromanGaming/Linux-i.MX-Fork
• U-boot: https://github.com/AstromanGaming/U-boot-i.MX-Fork
   

If someone or I manage to make it boot, that would be great! 🙂
 

PS: I'm new to this community, if I do something wrong, please let me know.

For a few hours now, as of today 2025-05-29 1418 North America/Pacific, I have been unable to update apt, receiving the following two error messages:

E: Failed to fetch http://beta.armbian.com/dists/bookworm/Contents-armhf File has unexpected size (2085376 != 51213). Mirror sync in progress? [IP: 23.186.113.5 80]
E: Failed to fetch http://beta.armbian.com/dists/bookworm/Contents-all File has unexpected size (44878 != 8029). Mirror sync in progress? [IP: 23.186.113.5 80]

I suppose it is possible that the "mirror sync" mentioned is taking a very long time, but this seems unlikely to me.

Does anyone have any ideas?

i've compiled udoo quad image using armbian build framework. The kernel is 6.x.x.

When i boot the image on sdcard, usb ports don't start: the mouse's led don't turn on and keyboard too.

What can i do to solve this problem?  what paramaters do i have to enable?

thanks

Looking for assistance with getting an old SmartQ5 Mobile Internet Device running with Armbian. I was able to locate Github page (https://github.com/tpruvot/smartq-magicsd) which references booting from SD but need assistance getting armbian compiled and configured for the device. Any help is appreciated!

SPECS:

    Samsung Mobile Application Processor S3C6410 based on ARM11 core at 667 MHz/800 MHz
    128 MB DDR 133/333 MHz SDRAM
    1 GB NAND FLASH (256 MB usable for storage)
    AC97 audio codec & PCM 24-bit audio
    SoC graphics unit, OpenGL ES 1.1/2.0, 4M triangles/sec @133Mhz (Transform only)
    Integrated Wi-Fi 802.11b/g
    Integrated Bluetooth 2.0 + EDR
    800x480 resolution resistive touchscreen LCD, 4.3", 16.7 million colors
    SDHC card slot (up to 32 GB)
    Headphone output power up to earphone 40 mW, frequency Response 20 Hz-20.000 Hz SNR 94dB
    Internal microphone
    USB 2.0 OTG port (480 Mbit/s)
    Runs Ubuntu Linux
    2000mAH rechargeable lithium polymer battery
    Dimensions: 120x74x14mm
    Weight: 160 g

I'm trying to install nvidia graphic card driver to the Jetson Nano after I successfully started bookwork on it. I have nouveau running and I don't understand how/if it is possible to switch to nvidia one.

Can you guys please help me to understand whether it is possible at all? Am I missing something? Probably was Googling wrong keywords. For now I understand that Nvidia SDK supported by nvidia requires too old version of their ubuntu-based l4t linux which I don't like at all.. Thanks in advance!

already many things still can't resolve it. If have any suggestion please let me know.

When using etcher to flash to usb, it will flash but fail at validation step say "Cannot validate, the image could be corrupt" or something like that.

If still use that usb in WDK, it won't boot. The lite version Armbian_community_24.8.0-trunk.554_Wdk2023_bookworm_wdk2023_6.7.0-rc6_minimal.img.xz is still working fine.

for the past few days I've been trying to install k3s on a Jetson Nano machine with the legacy Kernel 4.9, which I managed to recompile with EBPF support, but it seems there are some Kernel EBPF errors. So, I tried to install Armbian, which also doesn't have EBPF support compiled into the Kernel. I've tried to boot from many images from the Jetson Nano archive on the Armbian site, but none of them work. Is there any documentation on how I could compile the kernel on Armbian - Jetson Nano machine? Why can't I boot from any of the Armbian - Jetson Nano images from the archives? I have updated the legacy OS from Nvidia with the latest drivers boot loaders etc ... I also build https://github.com/marketplace/actions/rebuild-armbian a custom Armbian Image that not booting 

I found out about Armbian only recently and decided to give it a try for my T113-S3 based board I bought on Aliexpress. It looks like it's some kind of a MangoPi MQ clone, at least judging by schematics.

I managed to create a new configuration for my board, together with required U-Boot patches. I built two images, for "current" and "edge" kernel. For some time I was under impression that Linux doesn't boot at all (serial console output was stuck at "Starting kernel ..."), until I added earlycon=on to armbianEnv.txt. Then I finally saw some output from kernel being booted. But at some point it looks like it's stuck, or just doesn't show login prompt? It's hard to say.

Logs from the "current" image look like this:

Logs from "edge" image don't even come to that point:

What could be wrong, or what could I be forgetting to set? I'd be grateful for any help, especially knowing that this board is not either officially nor unofficially supported.

EDIT: I might have not been precise enough, I'm trying to login through serial console since I can't connect any screen to my board at the moment. I guess the lack of login prompt might be connected to this: "Warning: unable to open an initial console". It is connected with /dev/console device file, which might be needed for the serial console to work in userspace. I tried to track the warning down by adding some debug logs into kernel code and what I confirmed:
- /dev/console device is created successfully
- at the same time, while opening it (from within the kernel), open operation fails with ENODEV error
What's going on?

       I recently started "porting" linux to my Huawei mate 9. Its one of those projects plagued with silly issues and a sad lack of docs and unreliable hearsay. I was hopeful someone may have started something similiar, or maybe commit logs/discussions from when Hikey960 support was added. Ive found commits but praying that maybe more exists. I just have a handful of basic questions, most unfortunately involve things like the android bootloader. Which partitions related to boot can safely be replaced with non signed images, how do i stop fastboot from combining the appended dtb with those in dts partition. Just to give a general sense of what im looking for. Thanks in advance, always loved and respected Armbian and the importance of the work you do.

I'm trying to generate an Armbian image for a custom board. I generated configuration files for card and family, with the necessary information for u-boot and kernel. I need to have separate boot partition in FAT and I added BOOTFS_TYPE="fat".

Using the compile.sh in the Armbian "build" repo I get an image, but flashing it on the sdcard does not start uboot. In the boot partition I find not only the kernel and dtb, but also the u-boot scripts. How do you generate an image that contains everything correctly?

Thanks in advance

Riccardo

 I would like to run Linux5 or Linux6 on Jetson nano, display using HDMI-DVI adapter. It worked fine with Jetpack4 (=Linux4).

When I boot with armbian/Linux5.10, which is linux-image-current-jetson-nano, the display tells me it is out of sync then I would force the display as 1280x1024@60Hz, since it looks like Linux fb or X11 are trying to use 1280x1024@75Hz, so that I need edid/1280x1024.bin (maybe with video=1280x1024@60) using {linux-source}/tools/edid to maintain the resolution and sync.

I tried both of gcc-10 and gcc-9 to build it, but failed with below error:

edid.S: Assembler messages:
edid.S:274: Error: cannot represent BFD_RELOC_8 relocation in this object file format

Any workaround? or is this plan never work?

Thank you.

Recently I have been trying Armbian 23.5 as alternative for NVIDIA official images. Tried both Ubuntu Gnome desktop and Debian Cinnamon desktop builds but somehow non of them discovers HDMI output.

When Jetsno Nano is booting up I can see official "NVIDIA" screen for a while and then information about missing input (from TV on a TV).

The hardware itself works OK - when I change SD card to one with an official image or another one with Debian 11 official - it works just fine.

It's seems like a problem with Armbian build itself.

Any advice is much appreciated.

Kuba

Logs:

https://paste.armbian.com/omiheramof

In addition to tle logs - please see X -configure output.

I'm looking into the feasibility of using the Armbian build system to generate OS images for the Avnet MicroZed board. This board is based on the Xilinx Zynq 7000 platform, which is a SoC made up of a dual core 500 MHz CPU, and a Artix-7 generation FPGA. The CPU is nothing to write home about, but the FPGA opens up an interesting array of possibilities. Just in case you need an ARM board with 100+ GPIO, over two dozen serial ports, or your own function generator. Really, you're limited only by pin count, FPGA fabric usage, and what you can manage in Vivado. Xilinx also has an active presence on GitHub, and branches for kernels as new as 5.12, so sees active support.

The big rub, is that the Zynq CPU boots off a VFAT partition, that contains a file named "boot.bin". This boot file combines the first stage bootloader (FSBL) and u-boot, and needs to execute a C application to assemble this file. The application is recently open sourced, and previously existing open source software also exists. But I'm not sure how best to integrate that with the build system, or identify that the platform u-boot package depends on this extra package.

I took the contents of the Armbian_23.8.1_Jetson-nano_bookworm_current_6.1.50 image and put it on my NFS server in an attempt to network boot my Jetson Nano device. After making some adjustments to the pxelinux.cfg so that it points to the correct files on my tftp server, the device fails to boot with the following u-boot output:

Tegra210 (P3450-0000) # pxe boot
1:	Armbian
Retrieving file: /boot/jetson-nano-1/uInitrd
Using eth_rtl8169 device
TFTP from server 192.168.123.4; our IP address is 192.168.123.38
Filename '/boot/jetson-nano-1/uInitrd'.
Load address: 0x83200000
Loading: #################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#########################
	840.8 KiB/s
done
Bytes transferred = 32807968 (1f49c20 hex)
Retrieving file: /boot/jetson-nano-1/Image
Using eth_rtl8169 device
TFTP from server 192.168.123.4; our IP address is 192.168.123.38
Filename '/boot/jetson-nano-1/Image'.
Load address: 0x84000000
Loading: #################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	#################################################################
	##############################################
	847.7 KiB/s
done
Bytes transferred = 27390464 (1a1f200 hex)
append: root=/dev/nfs nfsroot=192.168.123.4:/rz2pool0/jetson-nano-nfs-1,vers=4.1,proto=tcp ip=dhcp console=ttyS0,115200n8 console=tty0 rw rootwait no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles
Retrieving file: /boot/jetson-nano-1/dtb/nvidia/tegra210-p3450-0000.dtb
Using eth_rtl8169 device
TFTP from server 192.168.123.4; our IP address is 192.168.123.38
Filename '/boot/jetson-nano-1/dtb/nvidia/tegra210-p3450-0000.dtb'.
Load address: 0x83000000
Loading: ######
	847.7 KiB/s
done
Bytes transferred = 84279 (14937 hex)
## Loading init Ramdisk from Legacy Image at 83200000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    32807904 Bytes = 31.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid

I have verified that the uInitrd file and the vmlinuz files sha256 checksums match the ones from the Armbian image:

62ce5b826c319c4032e1bd973ba3675580990f228c7589be7e0991edc2079cab  Image
1d8923fdaff529c62d6794b186b4b92d66ca6f2cacf8d0616da975e0d432ac68  initrd.img-6.1.50-current-media
bdf62ae60589860cff80fc95b46998ad79d207649b92617c2b211d7f5793d585  System.map-6.1.50-current-media
f22abfce4344c22bdb59087e8fa778c668c06839d010665933cd5499aa2ed104  uInitrd
f22abfce4344c22bdb59087e8fa778c668c06839d010665933cd5499aa2ed104  uInitrd-6.1.50-current-media
62ce5b826c319c4032e1bd973ba3675580990f228c7589be7e0991edc2079cab  vmlinuz-6.1.50-current-media

It does take quite a bit of time for the Bad Data CRC error to appear, and the Data Size does not match the Bytes transferred listed earlier in the messages but that looks like it may be normal from my investigation thus far. I also noted that when trying to boot via SD card the GRUB2 bootloader is used and not the pxelinux loader, but I am unsure how to make an EFI bootloader work over the network. I also tried booting off a USB device, which works but a USB reset issue and/or switch from usb-storage to uas causes the system to become unusable because the boot device moves when systemd is not expecting it. I do have a good quality barrel jack 12V 4A power supply connected and no other devices in my network boot environment (when testing with the USB booting, there was only a USB SATA adapter attached). If anyone has any ideas, I would love to hear them.

• I have the Mekotronics R58 mini plastic version (there is also metal box that has better cooling but same internals)
• RK3588 8 core Rockchip CPU
• 4Gb RAM
• File System transferred to 120Gb SSD with armbian-config
• Measured it uses 2.1 watt during idle
• I seem to have everything working except HW acceleration. On the download page it says to execute some PPA scripts (to add repositories) but these fail
• And everything works rather GREAT very nice silent mini PC

Should I wait till subsequent updates will fix HW acceleration? Or run the provided scripts? But alas, these scripts run into errors like below.

E: De pakketbron 'https://ppa.launchpadcontent.net/liujianfeng1994/panfork-mesa/ubuntu bookworm Release' heeft geen Release-bestand.
N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet.
N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant.
E: De pakketbron 'https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu bookworm Release' heeft geen Release-bestand.
N: Bijwerken van de pakketlijst uit een dergelijke pakketbron kan niet veilig gebeuren en is daarom standaard uitgezet.
N: Zie de man-pagina apt-secure(8) voor details over het aanmaken van een pakketbron en over de configuratie langs gebruikerskant.
 

Do you use R58? Let's help each other! 

Bas

I have an orange Pi i96, and I can't find a USB device. In /dev, I have a serial folder, then by-id in which I have : usb-1a86_USB_Serial-if00-port0 But it doesn't disappear when I remove the USB device ... And the USB output doesn't change whether the device is plugged in or not.

Dmedg gives nothing related to usb and lsusb gives this:
 

Bus 001 Device 002: ID 1a86:7523 QinHeng Electronics CH340 serial converter

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And it doesn't change depending on whether the USB port is busy or not.

Am I missing something? Have a nice day

I know it's the wrong tag for this post, but there isn't one for the i96...

now i want to reset everything so i can make a new project on it

because of the limitation on storage..

can i know how to do that?

and without change any kernel/firmware

i'm beginner on linux ecosystem...

Someone mentioned Armbian to me. I got everything running except I now have a new issue. I am using klipperscreen a simple gui with touch controls. before installing I could use my screen without issues and I installed everything on the screens terminal.

Now that klipperscreen is installed I see the boot sequence and than the signal gets lost. I already checked the klipperscreen guides and forums and if it doesnt report errors its the os doing weird dings with dpms or signal routing or something.

Does someone know why the screen suddenly just loses signal. when I uninstall klipperscreen I get it back.

I downloaded my os from here.

odroidn2

And this is my screen

screen

any help or ideas are welcome. thanks in advance

I am working with an Olinuxino A20 micro, but I have issues with the SPI bus.

I hope somebody can help me to find a solution.

I used Armbian 23.5 Bookworm with kernel 6.1
In sclk signal i have a pulse before to start the data transmission, I required the SPI to communicate a  LoRa module but the pulse before of data generate that doesn´t work the LoRa module.

I attached the signals.

I have armbian (Armbian_23.02.2_Rk3318-box_bullseye_current_5.15.93) installed on a TV box with a Rockchip RK3318 inside it. I am using a microsd card and EVERYTHING is running wonderfully!

I have also attached a 500GB USB hard disk 

(output from fdisk-l)

Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: 5000BEV External
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I ran armbian-config and tried to move the os to the hard disk while keeping the boot from sd card choice. That failed and I got the message "There is not enough free capacity on /dev/sda mmcblk2. Please check your device.

I tried mounting sda, deleteing all artitions on it ... etc but nothing worked. Any ideas?

Thanks

Here's what I tried:

- enabling spi-spidev through armbian-config, but this option doesn't exist in armbian-config as it does for other releases for devices

- making a custom device tree dts file and pointing extlinux.conf to it (below is the relevant snippet):
 

spi@7000d400 {
        compatible = "nvidia,tegra210-spi\0nvidia,tegra114-spi";
        reg = <0x00 0x7000d400 0x00 0x200>;
        interrupts = <0x00 0x3b 0x04>;
        #address-cells = <0x01>;
        #size-cells = <0x00>;
        clocks = <0x03 0x29>;
        clock-names = "spi";
        resets = <0x03 0x29>;
        reset-names = "spi";
        dmas = <0x24 0x0f 0x24 0x0f>;
        dma-names = "rx\0tx";
        status = "okay";

        num-chipselects = <5>;
        cs-gpios = <0x22 0x13 0>, <0x22 0x14 0>, <0x22 0x95 0>, <0x22 0xc8 0>, <0x22 0x26 0>;

        spidev@0 {
            compatible = "spidev";
            reg = <0>;
            spi-max-frequency = <0x1f78a40>;
            status = "okay";
        };

        spidev@1 {
            compatible = "spidev";
            reg = <1>;
            spi-max-frequency = <0x1f78a40>;
                status = "okay";
        };

        spidev@2 {
            compatible = "spidev";
            reg = <2>;
            spi-max-frequency = <0x1f78a40>;
                status = "okay";
        };

        spidev@3 {
            compatible = "spidev";
            reg = <3>;
            spi-max-frequency = <0x1f78a40>;
                status = "okay";
        };

        spidev@4 {
            compatible = "spidev";
            reg = <4>;
            spi-max-frequency = <0x1f78a40>;
                status = "okay";
        };
    };

- looking at device tree overlays as explained here (https://docs.armbian.com/User-Guide_Allwinner_overlays/#using-custom-overlays) but armbian-add-overlay doesn't exist and there is no /boot/dtb/nvidia/overlay/ folder

commit 369e69a55390f59c2299c98c09bf3d805ac59335 (HEAD -> main, origin/main, origin/HEAD)
Author: Ricardo Pardini <ricardo@pardini.net>
Date:   Mon Apr 3 13:15:54 2023 +0200

    artifact-armbian-bsp-cli: hash more variables included in `/etc/armbian-release`

Using the edge branch to compile for my renegade board, which has the rk3328 chip:

./compile.sh BOARD=renegade BRANCH=edge RELEASE=bullseye BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,img 

It blocks when start to boot the kernel:
 

U-Boot 2022.07-armbian (Apr 17 2023 - 23:29:15 +0800)

Model: Firefly roc-rk3328-cc
DRAM:  1022 MiB
PMIC:  RK8050 (on=0x50, off=0x01)
Core:  227 devices, 23 uclasses, devicetree: separate
MMC:   mmc@ff500000: 1, mmc@ff520000: 0
Loading Environment from MMC... Card did not respond to voltage select! : -110
*** Warning - No block device, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Firefly roc-rk3328-cc
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
Card did not respond to voltage select! : -110
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3252 bytes read in 3 ms (1 MiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
117 bytes read in 2 ms (56.6 KiB/s)
20639437 bytes read in 468 ms (42.1 MiB/s)
29397504 bytes read in 666 ms (42.1 MiB/s)
63592 bytes read in 7 ms (8.7 MiB/s)
2698 bytes read in 6 ms (438.5 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Unknown command 'kaslrseed' - try 'help'
Moving Image from 0x2080000 to 0x2200000, end=3ea0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    20639373 Bytes = 19.7 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 3cb6f000, end 3df1de8d ... OK
   Loading Device Tree to 000000003caf7000, end 000000003cb6efff ... OK

Starting kernel ...

efi_free_pool: illegal free 0x000000003cf20040
efi_free_pool: illegal free 0x000000003cf1d040

I don't know what happen, the boad is ok using the old version.

when booting Armbian Sid minimal rolling 6.1.11, there is no serial console login.

Console output:

Found U-Boot script /boot/boot.scr
1993 bytes read in 146 ms (12.7 KiB/s)
## Executing script at 12000000
93 bytes read in 94 ms (0 Bytes/s)
38318 bytes read in 2603 ms (13.7 KiB/s)
33621022 bytes read in 3482 ms (9.2 MiB/s)
11215360 bytes read in 1257 ms (8.5 MiB/s)
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    33620958 Bytes = 32.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c5ad

Starting kernel ...

Is there a way to enable console login to use the device headlessly?

Thanks

Do you have any idea?

the boot fails after switching the kernel through armbian-config. Further investigation needed.

//Edit 1: the dtb file is missing.

ls -la /boot
insgesamt 32336
drwxr-xr-x  2 root root     4096  8. Dez 19:03 .
drwxr-xr-x 21 root root     4096 12. Jan 2022  ..
-rw-r-----  1 root root      111  8. Dez 18:47 armbianEnv.txt
-rw-r-----  1 root root        0 29. Dez 2021  armbianEnv.txt.out
-rw-r--r--  1 root root     1536  7. Aug 2019  armbian_first_run.txt.template
-rw-r--r--  1 root root    38518  7. Aug 2019  boot.bmp
-rw-r--r--  1 root root     4882  7. Aug 2019  boot-desktop.png
-rw-rw-r--  1 root root    12548  7. Aug 2019  boot.ini
-rw-r-----  1 root root        0 29. Dez 2021  boot.ini.out
-rw-r--r--  1 root root   190980 30. Nov 12:07 config-6.0.9-odroidxu4
lrwxrwxrwx  1 root root       21  6. Dez 18:42 dtb -> dtb-5.4.225-odroidxu4
lrwxrwxrwx  1 root root       22 15. Apr 2020  dtb.old -> dtb-4.14.176-odroidxu4
-rw-r--r--  1 root root 11217641  8. Dez 19:03 initrd.img-6.0.9-odroidxu4
-rw-r--r--  1 root root        0  8. Dez 19:03 .next
-rw-r--r--  1 root root  3672734 30. Nov 12:07 System.map-6.0.9-odroidxu4
lrwxrwxrwx  1 root root       23  8. Dez 19:03 uInitrd -> uInitrd-6.0.9-odroidxu4
-rw-r--r--  1 root root 11217705  8. Dez 19:03 uInitrd-6.0.9-odroidxu4
-rwxr-xr-x  1 root root  6724096 30. Nov 12:07 vmlinuz-6.0.9-odroidxu4
lrwxrwxrwx  1 root root       23  8. Dez 19:03 zImage -> vmlinuz-6.0.9-odroidxu4

It seems that the armbian-config does not install the dtb and because of its enforced reboot, it kills the boot process.

* a kernel config called linux-virtual-current.config

* a board called virtual-qemu.wip

The result is a full HVM accelerated armbian image with a kernel compiled with all the virtio drivers for disk, network and video.   Also a u-boot.bin made for qemu that can boot the image when used as the qemu bios/firmware

I've ran it as a VM on ubuntu using plain qemu on a Ampere eMag box.. and using UTM (qemu) on Apple M1 in MacOS

this is using u-boot, not uEFI.. and you need to copy the u-boot.bin manually from cache/sources/u-boot...../u-boot.bin and use it as your chosen bios for qemu.  I left some quick breadcrumbs on how to launch within the board config file.

I want to keep the u-boot option, but obviously we need this to support uEFI booting to be viable for the masses.

Next steps:

* automatically resize and convert resulting image to qcow2 format

* solve how to add cloud-init to image

* solve for installing grubEFI for booting and whatever partition layout is needed

* figure a proper way to write uboot to the image so thet qemu can boot without loading as a bios

* strip extra hardware drivers out of kernel and make this thing lean

PS Did I mention Desktop Works too?

 

Unfortunately I have two small problems. Firstly, there is no linux header for the kernel used for compiling.

Secondly, unfortunately I can't add a network interface in openmediavault. That always gives me an error. It works on Debian with Openmediavault. unfortunately this surprises me.

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color systemd-networkd 2>&1' with exit code '1': NAS-Steinke:

Please forgive me if anything is incorrectly formatted or so, I have tried to provide as much detail as I can. If I didn't provide something, please tell me and I will do my best to resolve the issue. Additionally, I know this board is CSC status and not supported. I am not asking for support with anything in the OS, I am simply trying to build a new kernel for the device.

Here are the exact steps required to produce the issue.

1. Install Ubuntu 22.04 on bare metal/VM and install git from apt

2. Run

git clone --depth 1 https://github.com/armbian/build; cd build; ./compile.sh

3. Select "Full OS build for flashing"

4. Select "Show a kernel configuration menu before compiling" (but I never got this far so it probably doesn't matter)

5. Show CSC and pick nanopifire3 from list

6. Pick bullseye (I believe all of them error the same but my target is bullseye)

7. Pick image with server interface and standard/minimal image (both error same)

8. The error shown below will be produced when compiling u-boot.

Error log from console
 

[ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-s5p6818 ]
[ o.k. ] * [l][c] script-loading.patch
[ o.k. ] * [l][c] update-nanopi-fire3-support.patch
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/zconf.lex.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
  HOSTLD  scripts/kconfig/conf
#
# configuration written to .config
#
scripts/kconfig/conf  --silentoldconfig Kconfig
#
# configuration written to .config
#
  CHK     include/config.h
  UPD     include/config.h
  GEN     include/autoconf.mk
  GEN     include/autoconf.mk.dep
  CHK     include/config/uboot.release
  CHK     include/generated/timestamp_autogenerated.h
  UPD     include/generated/timestamp_autogenerated.h
  UPD     include/config/uboot.release
  CFG     u-boot.cfg
  CHK     include/generated/version_autogenerated.h
  UPD     include/generated/version_autogenerated.h
  CC      lib/asm-offsets.s
  CC      arch/arm/lib/asm-offsets.s
  CHK     include/generated/generic-asm-offsets.h
  CHK     include/generated/asm-offsets.h
  UPD     include/generated/generic-asm-offsets.h
  UPD     include/generated/asm-offsets.h
  HOSTCC  tools/bmp_logo
  HOSTCC  tools/img2srec
  HOSTCC  tools/mkenvimage.o
  HOSTCC  tools/os_support.o
  WRAP    tools/lib/crc32.c
  HOSTCC  tools/aisimage.o
  HOSTCC  tools/atmelimage.o
  HOSTCC  tools/fip_create/fip_create.o
  HOSTCC  tools/nexell/SECURE_BINGEN.o
  HOSTCC  tools/default_image.o
  WRAP    tools/common/bootm.c
  WRAP    tools/lib/fdtdec_common.c
  WRAP    tools/lib/fdtdec.c
  HOSTCC  tools/nexell/BOOT_BINGEN.o
  HOSTCC  tools/fit_common.o
  HOSTCC  tools/fit_image.o
  HOSTLD  tools/nexell/SECURE_BINGEN
  HOSTLD  tools/nexell/BOOT_BINGEN
  HOSTLD  tools/fip_create/fip_create
  HOSTCC  tools/gpimage.o
  HOSTCC  tools/gpimage-common.o
  WRAP    tools/common/image-fit.c
  HOSTCC  tools/image-host.o
  WRAP    tools/common/image.c
  LDS     u-boot.lds
  HOSTCC  tools/imagetool.o
[ error ] ERROR in function compile_uboot [ main.sh:595 -> main.sh:481 -> compilation.sh:241 -> general.sh:0 ]
[ error ] U-boot compilation failed
[ o.k. ] Process terminated

Full output log (/build/output/debug/output.log) here https://files.electrohaxz.host/file/d240f5c497e8db0f53dbf940329fb4f6/output.log

I've tried the steps in

https://docs.armbian.com/User-Guide_Basic-Troubleshooting/

https://docs.armbian.com/User-Guide_Recovery/

but it appears that the there is something going on with the Linux kernel?

changing the verbosity doesn't provide any new information.

I have even tried 20.05.1 and still the same behavior.

Any thoughts on possible next steps?

I'm new to embedded linux. To start with, I have nanopi fire 3 and smart 6818 cards, but I cannot access gpio pins with any gpio library. Why doesn't the NPi-GPIO library work with these cards? At first I was using the lubuntu version, I tried a lot there, but I couldn't. Now I'm trying to do something using armbian version 21.04. I'll post the problem I'm facing below. Thank you in advance for your help.

Traceback (most recent call last):
File "npigpio.py", line 1, in
import NPi.GPIO as GPIO
File "/usr/local/lib/python3.7/dist-packages/NPi.GPIO-0.5.8.6-py3.7-linux-aarch64.egg/NPi/GPIO/init.py", line 1, in
from NPi._GPIO import *
RuntimeError: Is not NanoPi based board.

I downloaded Armbian for a CuBox i4P from https://redirect.armbian.com/region/EU/cubox-i/Bionic_current_desktop.

uname -a reports: 

Linux cubox-i 5.10.12-imx6 #21.02.1 SMP Wed Feb 3 21:02:35 CET 2021 armv7l armv7l armv7l GNU/Linux

However this image is working really fine, for a 7yo hardware. Thank you, Developers  2D software rendering is fast, Desktop windows are transparent. Great work!

I tried Armbian Focal desktop mainline first, but it didnt show the desktop never again after first reboot, so i was happy with Bionic!

Found similar problem here 

and i think i just need the correct xorg driver. Thanks for any hints, maybe the solid-run repo can help?

I would love to use RetroArch there or play Videos with mpv, i would die for hardware support 

 (+) Video --vid=1 (*) (h264 1280x720 49.866fps)
 (+) Audio --aid=1 --alang=und (*) (aac 2ch 44100Hz)
libEGL warning: DRI2: failed to authenticate
[vo/opengl] Suspected software renderer or indirect context.
[vo/opengl] Suspected software renderer or indirect context.
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
[vo/vdpau] Error when calling vdp_device_create_x11: 1
[vo/xv] No Xvideo support found.
[vo/sdl] Using opengl
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
[vaapi] libva: va_getDriverName() failed with unknown libva error,driver_name=(null)
AO: [pulse] 44100Hz stereo 2ch float
VO: [sdl] 1280x720 yuv420p
AV: 00:00:00 / 01:29:07 (0%) A-V:  0.031 Dropped: 1

Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).

AV: 00:00:01 / 01:29:07 (0%) A-V:  5.800 Dropped: 82

In /var/log/Xorg.0.log I read:

[  2510.968] (II) AIGLX: Screen 0 is not DRI2 capable
[  2510.968] (EE) AIGLX: reverting to software rendering
[  2511.333] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[  2511.340] (II) IGLX: Loaded and initialized swrast
[  2511.340] (II) GLX: Initialized DRISWRAST GL provider for screen 0

LIBGL_DEBUG=verbose glxgears  -info says:

libGL: screen 0 does not appear to be DRI2 capable
libGL: MESA-LOADER: dlopen(/usr/lib/arm-linux-gnueabihf/dri/swrast_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/nimda/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/nimda/.drirc: No such file or directory.
GL_RENDERER   = llvmpipe (LLVM 10.0.0, 128 bits)
GL_VERSION    = 3.1 Mesa 20.0.8
GL_VENDOR     = VMware, Inc.
GL_EXTENSIONS = GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_ATI_fragment_shader GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp GL_NV_fog_distance GL_APPLE_packed_pixels GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert GL_MESA_ycbcr_texture GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc GL_ARB_texture_float GL_ARB_texture_rectangle GL_ATI_texture_compression_3dc GL_EXT_packed_float GL_EXT_pixel_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_ARB_framebuffer_object GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_packed_depth_stencil GL_ARB_vertex_array_object GL_ATI_separate_stencil GL_ATI_texture_mirror_once GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_texture_array GL_EXT_texture_compression_latc GL_EXT_texture_integer GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_OES_EGL_image GL_EXT_texture_buffer_object GL_AMD_texture_texture4 GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_texture_buffer_object GL_ARB_texture_rg GL_ARB_texture_swizzle GL_ARB_vertex_array_bgra GL_EXT_texture_swizzle GL_EXT_vertex_array_bgra GL_NV_conditional_render GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_compatibility GL_ARB_debug_output GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_provoking_vertex GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_shader_stencil_export GL_ARB_shader_texture_lod GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_multisample GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_uniform_buffer_object GL_ARB_vertex_type_2_10_10_10_rev GL_EXT_provoking_vertex GL_EXT_texture_snorm GL_MESA_texture_signed_rgba GL_ARB_draw_indirect GL_ARB_get_program_binary GL_ARB_robustness GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_texture_compression_bptc GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_viewport_array GL_EXT_direct_state_access GL_AMD_multi_draw_indirect GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ARB_base_instance GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_internalformat_query GL_ARB_map_buffer_alignment GL_ARB_shader_atomic_counters GL_ARB_shader_image_load_store GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_texture_storage GL_ARB_transform_feedback_instanced GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_transform_feedback GL_AMD_query_buffer_object GL_AMD_shader_trinary_minmax GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_clear_buffer_object GL_ARB_compute_shader GL_ARB_copy_image GL_ARB_explicit_uniform_location GL_ARB_fragment_layer_viewport GL_ARB_framebuffer_no_attachments GL_ARB_invalidate_subdata GL_ARB_multi_draw_indirect GL_ARB_program_interface_query GL_ARB_shader_image_size GL_ARB_shader_storage_buffer_object GL_ARB_stencil_texturing GL_ARB_texture_buffer_range GL_ARB_texture_query_levels GL_ARB_texture_storage_multisample GL_ARB_texture_view GL_ARB_vertex_attrib_binding GL_KHR_debug GL_KHR_texture_compression_astc_ldr GL_ARB_buffer_storage GL_ARB_clear_texture GL_ARB_enhanced_layouts GL_ARB_indirect_parameters GL_ARB_internalformat_query2 GL_ARB_multi_bind GL_ARB_query_buffer_object GL_ARB_seamless_cubemap_per_texture GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shading_language_include GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_stencil8 GL_ARB_vertex_type_10f_11f_11f_rev GL_EXT_shader_integer_mix GL_ARB_clip_control GL_ARB_conditional_render_inverted GL_ARB_cull_distance GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_get_texture_sub_image GL_ARB_pipeline_statistics_query GL_ARB_transform_feedback_overflow_query GL_EXT_polygon_offset_clamp GL_KHR_context_flush_control GL_ARB_parallel_shader_compile GL_ARB_shader_atomic_counter_ops GL_KHR_no_error GL_KHR_texture_compression_astc_sliced_3d GL_MESA_shader_integer_functions GL_ARB_polygon_offset_clamp GL_KHR_parallel_shader_compile GL_EXT_EGL_image_storage GL_EXT_texture_sRGB_R8 GL_EXT_EGL_sync
VisualID 471, 0x1d7
135 frames in 5.0 seconds = 26.971 FPS
188 frames in 5.0 seconds = 37.301 FPS
188 frames in 5.0 seconds = 37.476 FPS
213 frames in 5.0 seconds = 42.545 FPS
206 frames in 5.0 seconds = 41.120 FPS
209 frames in 5.0 seconds = 41.777 FPS
211 frames in 5.0 seconds = 41.999 FPS
212 frames in 5.0 seconds = 42.257 FPS
211 frames in 5.0 seconds = 42.183 FPS

dmesg shows kernel support:

[    9.153996] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops ipu_crtc_ops [imxdrm])
[    9.154250] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops ipu_crtc_ops [imxdrm])
[    9.154457] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops ipu_crtc_ops [imxdrm])
[    9.154652] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops ipu_crtc_ops [imxdrm])
[    9.156540] imx-drm display-subsystem: bound 120000.hdmi (ops dw_hdmi_imx_ops [dw_hdmi_imx])
[    9.163648] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0
[    9.491734] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device
[    9.586462] etnaviv etnaviv: bound 130000.gpu (ops gpu_ops [etnaviv])
[    9.606796] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv])
[    9.612502] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv])
[    9.612523] etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
[    9.617660] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
[    9.617784] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
[    9.617796] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
[    9.655944] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 1

System diagnosis information will now be uploaded to http://ix.io/2zH6

dmesg | grep eth0
[    4.667327] fec 2188000.ethernet eth0: registered PHC device 0
[   22.369472] fec 2188000.ethernet eth0: Unable to connect to phy

nlcli
wlan0: connected to sketch-wlan
        "Broadcom BCM4330"
        wifi (brcmfmac), 6C:AD:F8:1D:36:25, hw, mtu 1500
        ip4 default
        inet4 10.1.0.41/22
        route4 0.0.0.0/0
        route4 10.1.0.0/22
        route4 169.254.0.0/16
...
eth0: unavailable
        "eth0"
        ethernet (fec), D0:63:B4:00:87:DD, hw, mtu 1500
...

nmcli con
NAME              UUID                                  TYPE      DEVICE          
br-4ba53c1beb78   580cd8d0-4b87-432d-b072-7b2191fc3dc8  bridge    br-4ba53c1beb78
br-667404d55215   21ae2dad-0462-4880-98f2-8b56ae09dafa  bridge    br-667404d55215
br-7d46b681eda0   3dc1b651-2795-45fe-9821-7b33111d038c  bridge    br-7d46b681eda0
my-wlan           5d87696c-418b-404b-a6be-a85fd10c89cf  wifi      wlan0           
Armbian ethernet  0a5bb1f6-799d-476f-9fe4-2ecc7f4fe055  ethernet  --

nmcli con up 'Armbian ethernet'
Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because device has no carrier).

sudo ip a
...
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether d0:63:b4:00:87:dd brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 6c:ad:f8:1d:36:25 brd ff:ff:ff:ff:ff:ff
    inet 10.1.0.41/22 brd 10.1.3.255 scope global dynamic noprefixroute wlan0
       valid_lft 85910sec preferred_lft 85910sec
...

sudo ip link set eth0 up
RTNETLINK answers: No such device

EDIT: this is link to armbianmonitor after downgrading back to 5.7.15 and ethernet (eth0) working once again

http://ix.io/2zHa

Is there some way to powerfoff cubox? My current system is nightly, but I also tried stable with latest kernel.

$ uname -r
5.10.21-imx6
$ cat /etc/os-release
PRETTY_NAME="Armbian 21.08.0-trunk.26 Buster"

For some reason my nanopi fire 3's gigabit ethernet is very unstable. When connected to my local machine directly, the ping latency is insanely high and irregular:

PING 10.42.0.101 (10.42.0.101) 56(84) bytes of data.
64 bytes from 10.42.0.101: icmp_seq=1 ttl=64 time=112 ms
64 bytes from 10.42.0.101: icmp_seq=2 ttl=64 time=333 ms
64 bytes from 10.42.0.101: icmp_seq=3 ttl=64 time=350 ms
64 bytes from 10.42.0.101: icmp_seq=4 ttl=64 time=203 ms
64 bytes from 10.42.0.101: icmp_seq=5 ttl=64 time=1014 ms
64 bytes from 10.42.0.101: icmp_seq=6 ttl=64 time=423 ms
64 bytes from 10.42.0.101: icmp_seq=7 ttl=64 time=93.4 ms
64 bytes from 10.42.0.101: icmp_seq=8 ttl=64 time=345 ms
64 bytes from 10.42.0.101: icmp_seq=9 ttl=64 time=358 ms
64 bytes from 10.42.0.101: icmp_seq=10 ttl=64 time=49.6 ms
64 bytes from 10.42.0.101: icmp_seq=11 ttl=64 time=1021 ms
64 bytes from 10.42.0.101: icmp_seq=12 ttl=64 time=299 ms
64 bytes from 10.42.0.101: icmp_seq=13 ttl=64 time=305 ms
64 bytes from 10.42.0.101: icmp_seq=14 ttl=64 time=318 ms
64 bytes from 10.42.0.101: icmp_seq=15 ttl=64 time=300 ms
64 bytes from 10.42.0.101: icmp_seq=16 ttl=64 time=1008 ms
64 bytes from 10.42.0.101: icmp_seq=17 ttl=64 time=290 ms
64 bytes from 10.42.0.101: icmp_seq=18 ttl=64 time=306 ms
64 bytes from 10.42.0.101: icmp_seq=19 ttl=64 time=211 ms
64 bytes from 10.42.0.101: icmp_seq=20 ttl=64 time=1023 ms
^C
--- 10.42.0.101 ping statistics ---
21 packets transmitted, 20 received, 4.7619% packet loss, time 20085ms
rtt min/avg/max/mdev = 49.608/418.113/1022.521/312.908 ms, pipe 2

The nanopi fire 3 is directly connected to my desktop computer via a CAT6 cable, and the desktop computer's network adapter supports gigabit ethernet. Note that it is a direct cable connection and I am getting <1ms with my other boards such as the odroid xu4.

I have also tried connecting the nanopi fire 3 directly to a netgear switch behind a router. Still terrible ping.

Surprisingly if I force nanopi fire 3 to use 100Mbps ethernet connection, the ping latency is suddenly normal.

I've tested the ethernet cable and it is working fine. And the nanopi fire 3 has a stable PSU(5.1V with no load and 5.05V under load).

To investigate further, I tested Friendlyarm's friendlycore (seems to be ubuntu 18.04, kernel 4.4, aarch64) on the fire 3. And the gigabit ethernet is working with full speed. I also tested all history versions of armbian on the nanopi fire 3, and NONE OF THEM HAVE WORKING STABLE GIGABIT ETHERNET. This makes me think that there is something wrong in the gigabit ethernet code with armbian's s5p6818 4.14 kernel, since friendlyarm's 4.4 kernel does not have that issue.

Also something worth noticing: nanopi fire 3 running armbian has less power draw(0.5 W) than friendlyarm's kernel, so it is possible that its network adapter attempted but cannot draw enough power to enable gigabit ethernet, thus the random and irregular ping.

Tl;dr: There are some bugs in Armbian's 4.14 kernel for Nanopi Fire 3 that prevents gigabit ethernet from working properly.

I'm trying to boot latest releases of of Armbian (following images: Armbian_21.02.3_Cubox-i_buster_current_5.10.21.img and Armbian_21.02.3_Cubox-i_focal_current_5.10.21.img) on a Solid-Run Hummingboard2 Gate V1.4 board. (Board V1.2 freeze during Uboot) 

I'm getting to the "Starting kernel" message but after that things stop.

Switching on the verbose output in ArmbianEnv.txt result in the output below where the kernel always stop at message:

[    0.000000] Freeing unused kernel memory: 2048K

Do anyone have any thoughts/ideas here on what could possibly be the problem stopping the kernel from booting?

U-Boot SPL 2018.01-armbian (Mar 08 2021 - 10:51:22)
Trying to boot from MMC1

U-Boot 2018.01-armbian (Mar 08 2021 - 10:51:22 +0000)

CPU:   Freescale i.MX6SOLO rev1.3 996 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 38C
Reset cause: POR
Board: MX6 HummingBoard2
       Watchdog enabled
DRAM:  512 MiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   FEC
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2091 bytes read in 104 ms (19.5 KiB/s)
## Executing script at 12000000
0 bytes read in 72 ms (0 Bytes/s)
147 bytes read in 88 ms (1000 Bytes/s)
37976 bytes read in 1600 ms (22.5 KiB/s)
21327224 bytes read in 19315 ms (1.1 MiB/s)
10707456 bytes read in 650 ms (15.7 MiB/s)
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    21327160 Bytes = 20.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c457

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.10.21-imx6 (root@hirsute) (arm-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #21.02.3 SMP Mon Mar 8 07:05:20 UTC 2021
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: SolidRun Cubox-i Dual/Quad
[    0.000000] printk: debug: ignoring loglevel setting.
[    0.000000] Memory policy: Data cache writeback
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Size (0x10000000) of region at 0x80000000 exceeds limit (0x30000000)
[    0.000000] cma: Failed to reserve 256 MiB
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000010000000-0x000000002fffffff]
[    0.000000]   Normal   empty
[    0.000000]   HighMem  empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000010000000-0x000000002fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000010000000-0x000000002fffffff]
[    0.000000] On node 0 totalpages: 131072
[    0.000000]   DMA zone: 1152 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 131072 pages, LIFO batch:31
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] percpu: Embedded 19 pages/cpu s46924 r8192 d22708 u77824
[    0.000000] pcpu-alloc: s46924 r8192 d22708 u77824 alloc=19*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 129920
[    0.000000] Kernel command line: root=UUID=17df30e5-6838-4ce3-b871-47f297687856 rootfstype=ext4 rootwait  console=ttymxc0,115200 consoleblank=0 video=mxcfb0:dev=hdmi,1920x1080m60,if=RGB24,bpp=32 coherent_pool=2M cma=256M@2G rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi vt.global_cursor_default=0 loglevel=7 usb-storage.quirks= earlyprintk ignore_loglevel
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000] Memory: 476608K/524288K available (10511K kernel code, 2391K rwdata, 5352K rodata, 2048K init, 532K bss, 47680K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] random: get_random_u32 called from __kmem_cache_create+0x28/0x324 with crng_init=0
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 47647 entries in 94 pages
[    0.000000] ftrace: allocated 94 pages with 5 groups
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000]  Rude variant of Tasks RCU enabled.
[    0.000000]  Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC physical location is 0xa01000
[    0.000000] L2C-310 erratum 769419 enabled
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 16 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 16 ways, 512 kB
[    0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76450001
[    0.000000] Switching to timer-based delay loop, resolution 333ns
[    0.000000] sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns
[    0.000000] clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=3000)
[    0.000000] pid_max: default: 32768 minimum: 301
[    0.000000] LSM: Security Framework initializing
[    0.000000] Yama: becoming mindful.
[    0.000000] SELinux:  Initializing.
[    0.000000] TOMOYO Linux initialized
[    0.000000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000000] CPU: Testing write buffer coherency: ok
[    0.000000] CPU0: Spectre v2: using BPIALL workaround
[    0.000000] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.000000] Setting up static identity map for 0x10300000 - 0x103000ac
[    0.000000] rcu: Hierarchical SRCU implementation.
[    0.000000] EFI services will not be available.
[    0.000000] smp: Bringing up secondary CPUs ...
[    0.000000] smp: Brought up 1 node, 1 CPU
[    0.000000] SMP: Total of 1 processors activated (6.00 BogoMIPS).
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] devtmpfs: initialized
[    0.000000] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.000000] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.000000] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.000000] pinctrl core: initialized pinctrl subsystem
[    0.000000] DMI not present or invalid.
[    0.000000] NET: Registered protocol family 16
[    0.000000] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[    0.000000] audit: initializing netlink subsys (disabled)
[    0.000000] thermal_sys: Registered thermal governor 'fair_share'
[    0.000000] thermal_sys: Registered thermal governor 'step_wise'
[    0.000000] thermal_sys: Registered thermal governor 'user_space'
[    0.000000] cpuidle: using governor menu
[    0.000000] CPU identified as i.MX6DL, silicon rev 1.3
[    0.000000] imx6q_suspend_init: failed to get iomuxc base -19!
[    0.000000] imx6_pm_common_init: No DDR LPM support with suspend -19!
[    0.000000] No ATAGs?
[    0.000000] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.000000] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.000000] debugfs: Directory 'dummy-iomuxc-gpr@20e0000' with parent 'regmap' already present!
[    0.000000] imx6q-pinctrl 20e0000.pinctrl: initialized IMX pinctrl driver
[    0.000000] Serial: AMBA PL011 UART driver
[    0.000000] Kprobes globally optimized
[    0.000000] audit: type=2000 audit(0.052:1): state=initialized audit_enabled=0 res=1
[    0.000000] cryptd: max_cpu_qlen set to 1000
[    0.000000] raid6: skip pq benchmark and using algorithm neonx8
[    0.000000] raid6: using neon recovery algorithm
[    0.000000] vcc_3v3: supplied by v_5v0
[    0.000000] v_usb2: supplied by v_5v0
[    0.000000] v_usb1: supplied by v_5v0
[    0.000000] iommu: Default domain type: Translated
[    0.000000] vgaarb: loaded
[    0.000000] SCSI subsystem initialized
[    0.000000] libata version 3.00 loaded.
[    0.000000] usbcore: registered new interface driver usbfs
[    0.000000] usbcore: registered new interface driver hub
[    0.000000] usbcore: registered new device driver usb
[    0.000000] pps_core: LinuxPPS API ver. 1 registered
[    0.000000] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.000000] PTP clock support registered
[    0.000000] EDAC MC: Ver: 3.0.0
[    0.000000] NetLabel: Initializing
[    0.000000] NetLabel:  domain hash size = 128
[    0.000000] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.000000] NetLabel:  unlabeled traffic allowed by default
[    0.000000] clocksource: Switched to clocksource mxc_timer1
[    0.000000] VFS: Disk quotas dquot_6.6.0
[    0.000000] VFS: Dquot-cache hash table entries
                                                  [    0.000000] Segment Routing with IPv6
[    0.000000] NET: Registered protocol family 17
[    0.000000] ThumbEE CPU extension supported.
[    0.000000] Registering SWP/SWPB emulation handler
[    0.000000] registered taskstats version 1
[    0.00000scrypt registered
[    0.000000] Key type fscrypt-provisioning registered
[    0.000000] Btrfs loaded, crc32c=crc32c-generic
[    0.000000] Key type encrypted registered
[    0.000000] ima: No TPM chip found, activating TPM-bypass!
[    0.000000] ima: Allocated hash algorithm: sha256
[    0.000000] ima: No architecture policies found
[    0.000000] Freeing unused kernel memory: 2048K

I have recently tried a more recent kernel  5.10.x for my HummingBoard with imx6 solo. After playing with GPU/OpenGL acceleration I have noticed that there is no H.264/MJPEG Video acceleration present in the kernel. The video codec Chips&Media 960 driver module (kernel option VIDEO_CODA) is simply not build in.

Why is that? Can it be enabled by default for future IMX6 builds?

Thanks for your support!!

I've seen this ones mentioned:

• CuBox-i1
• CuBox-i2
• CuBox-i2eX
• Cubox-i 4x4
• CuBox-i4Pro
• CuBoxTV

Are there more?

  First thanks fo rthe hard work, but as in other threads here every now and again we get an issue moving up kernel versions.

  Mostly this is a post to flag up I had issues, so might you and that reverting the kernel fixed it for me.

  I did an apt-get update; apt dist-upgrade (I run this every other day normaly) and it did a kernal update

from

   Linux cubox 5.9.14-imx6 #20.11.3 SMP Fri Dec 11 20:57:51 CET 2020 armv7l GNU/Linux

to

   Linux version 5.10.12-imx6

It appears to all work.... however I use my Cubox-i to be a server for Kodi.

When I play flac files (which are quite big) it down loads them and uncompresses them and plays them ( kodi 2.2.6 on a rpi3B)

But I get what sounds like scrathes and static in the play back on 5.10.12 but not on 5.9.14.

Now the file system on the server is Btrfs, and kodi uses NFS to mount the files is plays.

I did run a memory test on the rpi runing kodi all good, I did a btrfs scrub (verifies the data on disk) and even an md5sun between my master file copy and one on server all OK.

Nothing in syslog, or kernel log nor anywhere else I looked :-(

Hence I revert back to the previous kernel 5.9.14 and Kodi plays my flac files all good again !!!

I do notice quite a few fixes landing still for 5.10, so we might get a working version in a while, but I can only test by trying it out as no errors reported on Kodi nor cubox-i server.

-----

So my question I did search for a nightly option, I can see one in armbian-config, but how do I find out what version of the kernel it would install before I do so?

Otherwise I'll just stick on 5.9.14 until 5.11 comes out (I see some ethernet driver fixes applied for cubox as in the other thread here, maybe they are related... but things not as 5.9.14 runs for me)

-----

Again I would like to thank all at Armbian for the Cubox-i builds I have been using them for many years and they are GREAT, but as Igor has stated before every now and again the upstream kernel  breaks something. I just want to sahre my experience in case someone else is strugling with an issue and is thing is them, as no one has said they see an issue.. I did :-)

JB

My Solidrun Cubox I1-300-D has been running Armbian for quite some time (Samsung EVO SD card). However, I tried to update/upgrade, and my version was non-supported anymore (19.04?), so time for a fresh new image.

I've tried three times (download image from https://www.armbian.com/cubox-i/, sha256 check, burn image with etcher, inspect file structure (looks good), and boot), but each time this happens:

"Armbian universal operating system" + text ("Executing script at ...") splash screen, then a black screen, and then my TV says "no signal", and then nothing anymore.

At the ethernetconnector, there is red LED on / flashing when the eternetcable is connected.

I've let the box run for hours, but no effect.

Keyboard eventually connected, but no effect.

So ... tips?

Is the Cubox I1-300-D still supported? 

Is there an older image (16.04?) that I can try?

Does Armbian write anything to the SD card when it boots? Like "Hello, here I am"  or dmesg? Because if so, I could check for that on the SD card in my laptop

... anything else?

EDIT:

I downloaded and installed sr-imx6-debian-buster-20191020-cli.img from https://images.solid-build.xyz/IMX6/Debian/, and the Cubox boots perfectly from that install. So proof Cubox,  SDcard, method, power, HDMI etc are OK.

I tried both latest cubieboard images, Fokal and Buster, both stops booting here:

U-Boot SPL 2020.10-armbian (Nov 23 2020 - 16:05:27 +0100)
DRAM: 1024 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from MMC1

U-Boot 2020.10-armbian (Nov 23 2020 - 16:05:27 +0100) Allwinner Technology

CPU:   Allwinner A10 (SUN4I)
Model: Cubietech Cubieboard
I2C:   ready
DRAM:  1 GiB

Yes, I tried different power supplies and SD cards.

Any idea what could I do?

Thans

Chris

I deployed the latest image "Armbian Buster mainline based kernel 5.8.y" and after initial setup, I cannot activate the analog sound card.

What I did:

The "Hardware" section in "Settings" section of armbian-config was missing, so I installed the following packages: "linux-dtb-current-sunxi/buster 20.11.0-trunk.28 armhf Linux DTB, version 5.9.5-sunxi, linux-dtb-dev-sunxi/buster 20.11.0-trunk.28 armhf Linux DTB, version 5.10.0-rc2-sunxi"

and after that changed: /boot/armbianEnv.txt by adding overlay_prefix: "sun8i-h3". This was the only way I could make armbian-config to correctly display the "Hardware" device tree. I tried to put: imx6q, imx6q-quad, imx6q-quad-hdmi (also copied all imx6q-udoo.dtb) to /boot/dtb, since after installinx *sunxi packages, the sunxi became the default dtb folder. The only way to make it properly display the HW menu was with "sun8i-h3".

With "imx6q-udoo" it displayed this error: "Loading error: expected at least 6 tokens for --checklist, have 4. use --help to list options. submodule ..."

I tried to enable "analog audio" with "sun8i-h3" (since only with this option I could properly see the Hardware section) but of course it didn't worked, and this is normal since there are different boards with different Device Tree Overlays.

The question is what should I do, in order to have the properly DT for my board (Udoo Quad)?

I decompiled the DTB file but I didn't see any VT1613 or analog audio in there...

Please help me with some clues.

Thanks a lot!

Cristi

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.55 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.18 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.06 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.70 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=6.50 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=3.42 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=5.48 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=6.84 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=3.41 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=4.34 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=5.94 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=6005 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=4998 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=3990 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=2982 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1974 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=966 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=3.58 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=3.26 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=5.30 ms
 

Steps to reproduce:

1. Install Armbian Focal with Kernel 4.4.y (Armbian_20.08.1_Rockpi-s_focal_legacy_4.4.228_minimal.img.xz)

2. Complete the standard installation/setup using wired ethernet

3. Configure and enable WIFI access using armbian-config on the wlan0 interface (note: same issue occurs when p2p0 is used)

4. Disconnect the eth0 cable

5. SSH to Rockpi S using WIFI/wlan0

6. Execute ping command to another device on the local network

Not sure where else to look to see if I can identify the cause, any pointers would be appreciated.

I therefore want to blow Vivi away and load a clean Armbian.

My issue is that the boards have no SD cards soldered to the board. They have power, 2xUSB,  RJ45, HDMI connectors. They must therefore boot from eMMC. I found info on the board manufactures website., SolidRun, on how to use jumpers to select boot type. It was set to eMMC so I set it to USB and flashed a SD card with Armbian 20.20 and rebooted. Alas it didn't work, it didn't even try and read the USB port with the flashed SD card.

I then hooked up an FTDI to the onboard UART and got connected. I don't have the password so had to stop it booting and try and access the system that way.

My problem is after the boot interruption it doesn't have any file structure so I can't edit files to change boot sequence or passwords.  I can't mount the eMMC to edit the files to remove the root password or anything like that.

Any suggestions as to how I can unlock this board and load a normal Armbian on to it?

Cheers

The device currently/by default runs Android 4.4.2. I'm able to flash customized 4.4 images via fastboot and have ADB control (Android Debug Bridge) via USB and Wifi.

I've identified the following key components:

• Freescale i.MX6 SoloLite
  (MCIMX6L8DVN10AB) CPU. Version with GPU and EPDC (Electrophoretic Display Controller; a feature-rich, low power, and high-performance direct-drive, active matrix EPD controller. It is specifically designed to drive E Ink EPD panels, supporting a wide variety of TFT backplanes).

• Realtek RTL8189FTV – Wifi only, no Bluetooth

• TI TPS65185 – Single Chip Power-Management Solution for E Ink® Vizplex™ Electronic Paper (E-Paper)

• Elan eKTF – Touchscreen Controller

• Ricoh RC5T619PMU – Power Management

• Samsung KLM8G1GEME – 8 GB eNAND

• Nanya NT6TL xxx – 512 MB RAM

The device will be used as internet-connected display device with no user interaction through the touch-screen.

What I need / what I don't need:

• mandatory: access to a console via USB
• very desireable: Wifi support
• not mandatory: touchscreen support
• mandatory: support for those Chinese, Qualcomm MDM9200/9600-based 3-in-1 LTE 4G USB Modems with Wi-Fi Hotspot (attached via USB OTG cable, used as direct modem, not as Hotspot)

Possible? If so, how?

e.g. How to create an image supporting the listed components? And: How and where to flash it? (There is no SD card slot, I must flash the any Armbian image to the internal 8 GB. Using fastboot? Stick to the existing bootloader or replace it? (Worried about bricking the device).

Sorry for the barrage of questions.

In the dtsi, after udoo_ard: udoo_ard_manager it had:

onewire@0 { /* example for pin 08 */
    compatible = "w1-gpio";
    pinctrl-names = "default";
    pinctrl-0 = <&w1_gpio_pins>;
    status = "disabled"; /* "okay" to enable */
    gpios = <&gpio1 21 0>; 
};

and in iomuxc, there was a section (in external_hog: hoggrp-2, MX6QDL_PAD_SD1_DAT3__GPIO1_IO21                 0x80000000  // pin 08):

w1_gpio_pins: w1-gpio@0 {
    fsl,pins = <
        MX6QDL_PAD_SD1_DAT3__GPIO1_IO21 0x80000000 /* example for pin 08 */
    >;
};

I tried adding the following to /boot/armbianEnv.txt

overlays=w1-gpio
param_w1_pin=21
param_w1_pin_int_pullup=0

with no luck.  Do I need to modify the dtsi and rebuild, or is there an overlay that will add one wire? (the current dtsi has no entries for one wire)

uname -a reports: 

Linux udoo 5.6.18-imx6 #20.05.4 SMP Mon Jun 15 00:30:23 CEST 2020 armv7l armv7l armv7l GNU/Linux

However in https://docs.armbian.com/Hardware_Freescale-imx6/ I read: "Udoo Quad Kernel 3.14.x and 4.4.x with some hardware support, headers and some firmware included", which suggests that the image should have a 3.14 or 4.4 kernel.

In /var/log/Xorg.0.log I read:

[    21.345] (II) AIGLX: Screen 0 is not DRI2 capable
[    23.279] (II) IGLX: Loaded and initialized swrast
[    23.279] (II) GLX: Initialized DRISWRAST GL provider for screen 0

LIBGL_DEBUG=verbose glxgears  -info says:

libGL: screen 0 does not appear to be DRI2 capable
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/pi/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/pi/.drirc: No such file or directory.
GL_RENDERER   = llvmpipe (LLVM 9.0.1, 128 bits)
GL_VERSION    = 3.1 Mesa 20.0.4
GL_VENDOR     = VMware, Inc.

suggesting that there is no hardware acceleration.

Is there any way to get hardware acceleration on a Udoo Quad with Armbian

Edit: updated using armbian-config, everything seems to be ok.

Hello. Armbian bionic desktop mainline based kernel 5.4, USB ports do not work, wifi module is not visible. Everything works correctly on Stretch. Do not tell me where to look for the reason?

I am making Asterisk PBX over Orange Pi - 2g IoT, I have tried Armbian as well as Ubuntu. Everything is working fine, but I am stuck on two issues,

a. How to add built-in GSM module of Orange Pi 2g IoT board in asterisk, so that A GSM trunk call/text can be transferred on SIP extension. I know chan-dongle, but asterisk is not detecting GSM module. I ahve tried different versions of asterisk.

b. How to change IMEI of Orange Pi 2g IoT

Looking for solutions

Regards

Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.)

Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <warn>  [1585663445.9567] dhcp4 (eth0): request timed out
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9569] dhcp4 (eth0): state changed unknown -> timeout
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9738] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 4459
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9739] dhcp4 (eth0): state changed timeout -> done
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9761] device (eth0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <warn>  [1585663445.9800] device (eth0): Activation: failed for connection 'Wired connection 1'
Mar 31 14:04:05 nanopifire3 NetworkManager[3061]: <info>  [1585663445.9845] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0045] policy: auto-activating connection 'Wired connection 1'
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0147] device (eth0): Activation: starting connection 'Wired connection 1' (cf44b283-2a76-371d-9d8a-84fccecce8ea)
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0166] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0202] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0241] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 31 14:04:06 nanopifire3 NetworkManager[3061]: <info>  [1585663446.0268] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)

After reboot, it's connected via eth, but if I try to ping something is also fails

root@nanopifire3:~# ping 8.8.8.8
PING 8.8.88 (8.8.0.88) 56(84) bytes of data.
From 10.42.0.72 icmp_seq=1 Destination Host Unreachable
From 10.42.0.72 icmp_seq=2 Destination Host Unreachable
From 10.42.0.72 icmp_seq=3 Destination Host Unreachable
From 10.42.0.72 icmp_seq=4 Destination Host Unreachable
From 10.42.0.72 icmp_seq=5 Destination Host Unreachable
From 10.42.0.72 icmp_seq=6 Destination Host Unreachable
From 10.42.0.72 icmp_seq=7 Destination Host Unreachable
From 10.42.0.72 icmp_seq=8 Destination Host Unreachable
From 10.42.0.72 icmp_seq=9 Destination Host Unreachable
From 10.42.0.72 icmp_seq=10 Destination Host Unreachable
From 10.42.0.72 icmp_seq=11 Destination Host Unreachable
From 10.42.0.72 icmp_seq=12 Destination Host Unreachable
From 10.42.0.72 icmp_seq=13 Destination Host Unreachable
From 10.42.0.72 icmp_seq=14 Destination Host Unreachable
From 10.42.0.72 icmp_seq=15 Destination Host Unreachable
From 10.42.0.72 icmp_seq=16 Destination Host Unreachable
From 10.42.0.72 icmp_seq=17 Destination Host Unreachable
From 10.42.0.72 icmp_seq=18 Destination Host Unreachable
From 10.42.0.72 icmp_seq=19 Destination Host Unreachable
From 10.42.0.72 icmp_seq=20 Destination Host Unreachable
From 10.42.0.72 icmp_seq=21 Destination Host Unreachable
From 10.42.0.72 icmp_seq=22 Destination Host Unreachable
From 10.42.0.72 icmp_seq=23 Destination Host Unreachable
From 10.42.0.72 icmp_seq=24 Destination Host Unreachable
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

--

I connected my HD702 screen to board and if I install xubuntu-core/desktop... it works, but It's running via fb, thus it's slow and FriendlyArm OneWire touchscreen isn't working. I wasn't able to find information if is OneWire touchscreen supported in your kernel, or how to get it working.
I wasn't able to find any information if is GPU in S5P6818 supported or if it's possible to have accelerated desktop environment on it.
--
My last question is if SPI on this board works.

Thanks in advance.

Mar 15 03:07:13 matrix iscsid[2207]: iSCSI logger with pid=2208 started!
Mar 15 03:07:13 matrix systemd[1]: iscsid.service: Failed to parse PID from file /run/iscsid.pid: Invalid argument
Mar 15 03:07:13 matrix iscsid[2208]: iSCSI daemon with pid=2209 started!
Mar 15 03:07:13 matrix iscsid[2208]: can not create NETLINK_ISCSI socket
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Start operation timed out. Terminating.
Mar 15 03:08:43 matrix systemd[1]: iscsid.service: Failed with result 'timeout'.

with a timeout of around 90 seconds.  I'm running the kernel

Linux matrix 4.14.171-s5p6818 #24 SMP Mon Feb 17 06:09:30 CET 2020 aarch64 GNU/Linux

in the Buster image.  It would appear from /boot/config-4.14.171-s5p6818 that

# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
CONFIG_SCSI_LOWLEVEL=y
# CONFIG_ISCSI_TCP is not set
# CONFIG_ISCSI_BOOT_SYSFS is not set

That ISCSI_TCP is not set for ISCSI_ATTRS.  On a Raspberry Pi (also based on Buster) with the default Raspbian kernel the modules

iscsi_tcp              20480  2
libiscsi_tcp           28672  1 iscsi_tcp
libiscsi               57344  2 libiscsi_tcp,iscsi_tcp

automatically load and all is well.  However, I can't get Armbian to work.  I think I might need to recompile the kernel, but am not very excited to do so.  A web search also indicated that incorrectly configured selinux could cause the same problem, but I don't think selinux is running.  Does anyone know what's wrong and how to fix it?

I want to run omv and i just found out what is happening with omv5 and armbian the past year.

So ill go stretch and omv4.

Kind regards Oliver

The only thing that fixed it was to rever "back" to 5.3.11-imx6.

Note the change both up to the 5.4.12 and then back to 5.3.11 were performed via the armbian-config tool.

(the system is running headless, and the log file does include a boot of "Linux version 5.3.11-imx6" as well as the working 5.3.11

Is anyone else seeing this?

JB.

I am developing on an imx6 board that is no longer in production. It has a full Yacto-based build system that works, based on an old 3.17?) kernel, but its a pain to develop for.

It's not worth spending too much time on refactoring the image, but I'm wondering how big of a job it might be to build an Armbian image for it, given that I already have a working uboot and kernel.

The hardware just uses a couple of usbs and uarts, and a pcie wifi card. One wersion also has an hdmi encoder, another has hdmi display. Those might be the hardest to support, but driver support is in the kernel.

Thoughts?

Sent from my LM-G710 using Tapatalk

Here's what I get when trying to boot (data is from my serial adapter):

I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
I2C_WriteByte nack returned
I2C Device Address Write Abitration Error
Wakeup Sub CPU 1234567
CPU Wakeup done! WFI is expected.
CPU0 is Master!

U-Boot 2016.01-armbian (Sep 02 2019 - 08:57:37 +0200)

DRAM:  1 GiB
MMC:   NEXELL DWMMC: 0, NEXELL DWMMC: 1
loaded from SD, getting env from MMC 1
*** Warning - bad CRC, using default environment

MIPI: display.0
HDMI: display.0, preset 0 (1280 *  720)
HDMI: phy ready...
LCD: [HDMI] dp.0.1 1220x680 16bpp FB:0x46000000
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
** File not found /boot.scr **
## Executing script at 40000000
Wrong image format for "source" command
1277 bytes read in 31 ms (40 KiB/s)
## Executing script at 40000000
Wrong image format for "source" command
Card did not respond to voltage select!
** Bad device mmc 0 **
## Executing script at 40000000
Wrong image format for "source" command
** Bad device mmc 0 **
## Executing script at 40000000
Wrong image format for "source" command
nanoPi#

Here's what gpg and sha256sum output:

% gpg --verify Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.asc
gpg: assuming signed data in 'Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img'
gpg: Signature made Mon Jan 20 00:04:11 2020 EST
gpg:                using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5
gpg: Good signature from "Igor Pecovnik <igor@armbian.com>" [unknown]
gpg:                 aka "Igor Pecovnik (Ljubljana, Slovenia) <igor.pecovnik@gmail.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: DF00 FAF1 C577 104B 50BF  1D00 93D6 889F 9F0E 78D5
%  sha256sum -c Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img.sha
Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: OK

Output of mount:

# mount --ro Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img /mnt/usb
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

dmesg doesn't mention anything about the mounting problems.

Gdisk outputs:

# gdisk -l Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img 
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. 
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk Armbian_20.02.0-rc0_Nanopifire3_buster_legacy_4.14.166.img: 2957312 sectors, 1.4 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9FF78C6C-5C9B-4B4D-A4F3-B0B52827C119
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2957278
Partitions will be aligned on 2048-sector boundaries
Total free space is 8158 sectors (4.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            8192         2957311   1.4 GiB     8300  Linux filesystem

The board I'm using is the Nano PI Fire3 LTS. It has worked before, although with a different Micro SD card. I accidentally erased it's SD card and I'm trying to reinstall.

My current Micro SD card is a SanDisk Ultra 32GB rated USH-I, (10), U with a 1 inside, and A1.

I used dd if=IMG of=DEV BS=8192 status=progress to place the image onto the Micro SD card.

I also tried with my original SP Micro SD card without success.

If you need anything else, just yell.

Thanks!

coming from "ARMBIAN 5.73 stable Ubuntu 18.04.2 LTS 4.19.20-cubox" after performing

apt udate
apt upgrade

my cubox won't boot anymore. I've no idea how to recover from this. The output from boot is in the attached picture.

What can I do?

df -aTh
Filesystem     Type         Size  Used Avail Use% Mounted on
sysfs          sysfs           0     0     0    - /sys
proc           proc            0     0     0    - /proc
udev           devtmpfs     869M     0  869M   0% /dev
devpts         devpts          0     0     0    - /dev/pts
tmpfs          tmpfs        202M  8.1M  194M   5% /run
/dev/mmcblk1p1 ext4          15G  1.2G   14G   8% /
securityfs     securityfs      0     0     0    - /sys/kernel/security
selinuxfs      selinuxfs       0     0     0    - /sys/fs/selinux
tmpfs          tmpfs       1007M     0 1007M   0% /dev/shm
tmpfs          tmpfs        5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs       1007M     0 1007M   0% /sys/fs/cgroup
cgroup2        cgroup2         0     0     0    - /sys/fs/cgroup/unified
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/systemd
pstore         pstore          0     0     0    - /sys/fs/pstore
bpf            bpf             0     0     0    - /sys/fs/bpf
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/pids
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/perf_event
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/net_cls,net_prio
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/cpu,cpuacct
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/freezer
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/memory
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/cpuset
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/devices
cgroup         cgroup          0     0     0    - /sys/fs/cgroup/blkio
systemd-1      -               -     -     -    - /proc/sys/fs/binfmt_misc
debugfs        debugfs         0     0     0    - /sys/kernel/debug
mqueue         mqueue          0     0     0    - /dev/mqueue
configfs       configfs        0     0     0    - /sys/kernel/config
tmpfs          tmpfs       1007M   12K 1007M   1% /tmp
/dev/mmcblk1p1 ext4          15G  1.2G   14G   8% /var/log.hdd
/dev/zram0     ext4          49M   12M   34M  26% /var/log
tracefs        -               -     -     -    - /sys/kernel/debug/tracing
tmpfs          tmpfs        202M     0  202M   0% /run/user/1000
binfmt_misc    binfmt_misc     0     0     0    - /proc/sys/fs/binfmt_misc

...and I get the following error in dmesg error:

   43.261482] ata1: hard resetting link
[   43.728472] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   43.728946] ata1.00: supports DRM functions and may not be fully accessible
[   43.729942] ata1.00: Trusted Computing capability qword not valid!
[   43.730657] ata1.00: supports DRM functions and may not be fully accessible
[   43.731534] ata1.00: Trusted Computing capability qword not valid!
[   43.731571] ata1.00: configured for UDMA/133
[   43.731696] sd 0:0:0:0: [sda] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[   43.731724] sd 0:0:0:0: [sda] tag#22 Sense Key : Illegal Request [current] 
[   43.731754] sd 0:0:0:0: [sda] tag#22 Add. Sense: Unaligned write command
[   43.731781] sd 0:0:0:0: [sda] tag#22 CDB: Read(10) 28 00 6f c8 17 20 00 00 08 00
[   43.731808] blk_update_request: I/O error, dev sda, sector 1875384096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   43.731972] ata1: EH complete
[   74.226892] ata1.00: exception Emask 0x0 SAct 0x80000010 SErr 0x0 action 0x6 frozen
[   74.226918] ata1.00: failed command: READ FPDMA QUEUED
[   74.226956] ata1.00: cmd 60/08:20:80:17:4b/00:00:6f:00:00/40 tag 4 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   74.226970] ata1.00: status: { DRDY }
[   74.226991] ata1.00: failed command: READ FPDMA QUEUED
[   74.227025] ata1.00: cmd 60/08:f8:80:17:c8/00:00:6f:00:00/40 tag 31 ncq dma 4096 in
                        res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   74.227037] ata1.00: status: { DRDY }
[   74.227058] ata1: hard resetting link
[   84.261316] ata1: softreset failed (device not ready)
[   84.261336] ata1: hard resetting link
[   84.729328] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

The SSD mounts with no problem on my Ubuntu laptop. The disk is formatted with GParted to ext4.

Futhermore I got the following error when running smartctl:
 

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            0  Command failed due to ICRC error
0x000a  4           10  Device-to-host register FISes sent due to a COMRESET

smartctl_log

After a power shutdown, my Cubox-i 4 Pro does not boot anymore.

I am running on it Debian Stretch since years. My system is on a hard drive (/dev/sda1).

It seems that the boot process is blocked in a loop, as each time, just after:

Starting kernel ...
 Uncompressing Linux... done, booting the kernel.

...U-boot is restarting as after a fresh reboot.

My boot.txt:

$ more armbianEnv.txt
verbosity=7
rootdev=/dev/sda1
console=serial
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

Here is the bootlog:

U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...
 
 
U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
 
CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment
 
In:    serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0
mmc0 is current device
** File not found /boot.scr **
** File not found /uEnv.txt **
** File not found /zImage **
** File not found /uImage **
1816 bytes read in 122 ms (13.7 KiB/s)
Running bootscript from mmc ...
## Executing script at 10800000
** File not found .next **
94 bytes read in 113 ms (0 Bytes/s)
37237 bytes read in 855 ms (42 KiB/s)
4820085 bytes read in 378 ms (12.2 MiB/s)
5961616 bytes read in 568 ms (10 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x5af790 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4820021 Bytes = 4.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c174
 
Starting kernel ...
 
Uncompressing Linux... done, booting the kernel.
 
U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...
 
 
U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
 
CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment
 
In:    serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0
mmc0 is current device
** File not found /boot.scr **
** File not found /uEnv.txt **
** File not found /zImage **
** File not found /uImage **
1816 bytes read in 122 ms (13.7 KiB/s)
Running bootscript from mmc ...
## Executing script at 10800000
** File not found .next **
94 bytes read in 113 ms (0 Bytes/s)
37237 bytes read in 855 ms (42 KiB/s)
4820085 bytes read in 378 ms (12.2 MiB/s)
5961616 bytes read in 568 ms (10 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x5af790 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4820021 Bytes = 4.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c174
 
Starting kernel ...
 
Uncompressing Linux... done, booting the kernel.
 
U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...
 
 
U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
 
CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment
 
In:    serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0
mmc0 is current device
** File not found /boot.scr **
** File not found /uEnv.txt **
** File not found /zImage **
** File not found /uImage **
1816 bytes read in 122 ms (13.7 KiB/s)
Running bootscript from mmc ...
## Executing script at 10800000
** File not found .next **
94 bytes read in 113 ms (0 Bytes/s)
37237 bytes read in 855 ms (42 KiB/s)
4820085 bytes read in 378 ms (12.2 MiB/s)
5961616 bytes read in 568 ms (10 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x5af790 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4820021 Bytes = 4.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c174
 
Starting kernel ...
 
Uncompressing Linux... done, booting the kernel.
 
U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...
 
 
U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
 
CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

etc, etc...

I suspect a hard drive power issue, as I already had few weeks ago (see the thread below). On the current setup, the hard drive is powered directly thanks to a usb hub, not from the cubox.

Please note that the hard drive, plugged on my desktop, is running fine.

What could I investigate?

Thank you a lot for any support.

Armbian works well for me on a NanoPi Neo, and installing it on my Cubox i4 was straightforward... but I'd like to try a kernel newer than linux-image-cubox (version 4.14), to get improved video support, and both linux-image-dev-cubox (version 5.2.11) and linux-image-next-cubox (version 5.1.16) do not provide any video output at all.

I've uploaded the armbianmonitor report from booting the linux-image-dev-cubox kernel.

Help on this would be appreciated!

I wanted to test wireguard with my cubox i4, but I'm not able to load the module.

I tried to search the net for this error, but fond nothing useful.

Maybe someone has an idea.

Thank you

Michael

uname -a
Linux loki 4.19.41-cubox #5.85 SMP Wed May 8 15:52:55 CEST 2019 armv7l GNU/Linux

dpkg -l | grep linux
ii  console-setup-linux              1.164                              all          Linux specific part of console-setup
ii  libselinux1:armhf                2.6-3+b3                           armhf        SELinux runtime shared libraries
ii  linux-base                       4.5                                all          Linux image base package
ii  linux-dtb-next-cubox             5.85                               armhf        Linux DTB, version 4.19.41-cubox
ii  linux-headers-next-cubox         5.85                               armhf        Linux kernel headers for 4.19.41-cubox on armhf
ii  linux-image-next-cubox           5.85                               armhf        Linux kernel, version 4.19.41-cubox
ii  linux-libc-dev                   5.70                               armhf        Linux support headers for userspace development
ii  linux-stretch-root-next-cubox-i  5.85                               armhf        Armbian tweaks for stretch on cubox-i (next branch)
ii  linux-u-boot-cubox-i-next        5.85                               armhf        Uboot loader 2013.10-rc4
ii  util-linux                       2.29.2-1+deb9u1                    armhf        miscellaneous system utilities

modprobe wireguard
modprobe: ERROR: could not insert 'wireguard': Exec format error

dmesg | grep wireguard
[320752.917616] wireguard: unknown relocation: 102

modinfo wireguard
filename:       /lib/modules/4.19.41-cubox/kernel/net/wireguard/wireguard.ko
alias:          net-pf-16-proto-16-family-wireguard
alias:          rtnl-link-wireguard
version:        0.0.20190406
author:         Jason A. Donenfeld <Jason@zx2c4.com>
description:    WireGuard secure network tunnel
license:        GPL v2
srcversion:     9996946C3FF07EF91C1E1DA
depends:
intree:         Y
name:           wireguard
vermagic:       4.19.41-cubox SMP mod_unload modversions ARMv7 thumb2 p2v8

Bit not understand why new 5.44 for nanoPC T3 plus not run.

I see only first boot screen and then black always ???

Recently I bought a nanopi fire 3 and installed armbian without any issue (Armbian_5.91_Nanopifire3_Debian_buster_next_4.14.133).  The first thing I did was to connect the nanopi to my ADSL router in order to complete the basic configuration. Everything worked fine.

Then I connected the nanopi to an Edimax gigabit ethernet switch and here is where the network problems appeared. The ethernet connection was too slow, with ping times of more than 1000ms, and an unstable behavior that made it almost impossible to connect via ssh.

64 bytes from 192.168.22.12: icmp_seq=1 ttl=64 time=1004 ms
64 bytes from 192.168.22.12: icmp_seq=2 ttl=64 time=1025 ms
64 bytes from 192.168.22.12: icmp_seq=3 ttl=64 time=1001 ms
64 bytes from 192.168.22.12: icmp_seq=4 ttl=64 time=1002 ms

After many reconfigurations and reinstalls, I tried forcing the ethernet interface to work at 100Mbps, and it solved the network slugginess and unstability.

ethtool -s eth0 speed 100 autoneg off

Other devices connected to the same switch work fine at 1Gbps. 
 

Although with this workaround I can work for now, I still want to use my nanopi at full speed if possible. Anybody has any idea of how can I solve it?

I run a Cubox-i.

I upgraded to kernel 5.1.16 yesterday.

Then I rebooted and everything was running fine.

But today my server looked dead: none of my services was answering, no way to ssh to the cubox...

I tryied a hard reboot with no success.

Here is the log on a putty console:

U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...


U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0
mmc0 is current device
** File not found /boot.scr **
** File not found /uEnv.txt **
** File not found /zImage **
** File not found /uImage **
1816 bytes read in 122 ms (13.7 KiB/s)
Running bootscript from mmc ...
## Executing script at 10800000
** File not found .next **
94 bytes read in 114 ms (0 Bytes/s)
37237 bytes read in 854 ms (42 KiB/s)
4820085 bytes read in 375 ms (12.3 MiB/s)
5961616 bytes read in 564 ms (10.1 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x5af790 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4820021 Bytes = 4.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c174

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 5.1.16-cubox (root@nightly) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.90 SMP Sun Jul 7 11:37:47 CEST 2019
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=50c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: SolidRun Cubox-i Dual/Quad
Memory policy: Data cache writealloc
cma: Reserved 256 MiB at 0x70000000
random: get_random_bytes called from start_kernel+0x85/0x376 with crng_init=0
percpu: Embedded 17 pages/cpu s37196 r8192 d24244 u69632
Built 1 zonelists, mobility grouping on.  Total pages: 520256
Kernel command line: root=/dev/sda1 rootfstype=ext4 rootwait console=ttymxc0,115200 consoleblank=0 video=mxcfb0:dev=hdmi,1920x1080m60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi vt.global_cursor_default=0 loglevel=7 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u
Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
Memory: 1796204K/2097152K available (8192K kernel code, 391K rwdata, 2472K rodata, 1024K init, 461K bss, 38804K reserved, 262144K cma-reserved, 262144K highmem)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
rcu: Hierarchical RCU implementation.
rcu:    RCU event tracing is enabled.
rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
L2C: DT/platform modifies aux control register: 0x72070000 -> 0x72470000
L2C-310 errata 752271 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 16 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 16 ways, 1024 kB
L2C-310: CACHE_ID 0x410000c7, AUX_CTRL 0x76470001
Switching to timer-based delay loop, resolution 333ns
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns
clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=12000)
pid_max: default: 32768 minimum: 301
LSM: Security Framework initializing
Mount-cache hash table entries: 4096 (order: 2, 16384 bytes)
Mountpoint-cache hash table entries: 4096 (order: 2, 16384 bytes)
*** VALIDATE proc ***
*** VALIDATE cgroup1 ***
*** VALIDATE cgroup2 ***
CPU: Testing write buffer coherency: ok
CPU0: Spectre v2: using BPIALL workaround
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x10100000 - 0x10100054
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
CPU1: Spectre v2: using BPIALL workaround
CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
CPU2: Spectre v2: using BPIALL workaround
CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
CPU3: Spectre v2: using BPIALL workaround
smp: Brought up 1 node, 4 CPUs
SMP: Total of 4 processors activated (24.00 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
futex hash table entries: 1024 (order: 4, 65536 bytes)
xor: measuring software checksum speed
   arm4regs  :  1233.000 MB/sec
   8regs     :   916.000 MB/sec
   32regs    :   882.000 MB/sec
   neon      :   899.000 MB/sec
xor: using function: arm4regs (1233.000 MB/sec)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 2048 KiB pool for atomic coherent allocations
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(0.192:1): state=initialized audit_enabled=0 res=1
cpuidle: using governor ladder
cpuidle: using governor menu
CPU identified as i.MX6Q, silicon rev 1.2
vdd1p1: supplied by regulator-dummy
vdd3p0: supplied by regulator-dummy
vdd2p5: supplied by regulator-dummy
vddarm: supplied by regulator-dummy
vddpu: supplied by regulator-dummy
vddsoc: supplied by regulator-dummy
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
raid6: neonx8   gen()   529 MB/s
raid6: neonx8   xor()   496 MB/s
raid6: neonx4   gen()   685 MB/s
raid6: neonx4   xor()   652 MB/s
raid6: neonx2   gen()   661 MB/s
raid6: neonx2   xor()   669 MB/s
raid6: neonx1   gen()   615 MB/s
raid6: neonx1   xor()   571 MB/s
raid6: int32x8  gen()   217 MB/s
raid6: int32x8  xor()   157 MB/s
raid6: int32x4  gen()   192 MB/s
raid6: int32x4  xor()   157 MB/s
raid6: int32x2  gen()   174 MB/s
raid6: int32x2  xor()   159 MB/s
raid6: int32x1  gen()   134 MB/s
raid6: int32x1  xor()   129 MB/s
raid6: using algorithm neonx4 gen() 685 MB/s
raid6: .... xor() 652 MB/s, rmw enabled
raid6: using neon recovery algorithm
mxs-dma 110000.dma-apbh: initialized
v_usb2: supplied by v_5v0
vcc_3v3: supplied by v_5v0
v_usb1: supplied by v_5v0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c i2c-1: IMX I2C adapter registered
i2c i2c-2: IMX I2C adapter registered
videodev: Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource mxc_timer1
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 1024 (order: 1, 12288 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
UDP hash table entries: 1024 (order: 3, 32768 bytes)
UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 4708K
hw perfevents: no interrupt-affinity property for /pmu, guessing.
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
Initialise system trusted keyrings
workingset: timestamp_bits=14 max_order=19 bucket_order=5
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFS: nTxBlock = 8192, nTxLock = 65536
SGI XFS with ACLs, security attributes, realtime, no debug enabled
Key type asymmetric registered
Asymmetric key parser 'x509' registered
bounce: pool size: 64 pages
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
imx-pgc-pd imx-pgc-power-domain.0: DMA mask not set
imx-pgc-pd imx-pgc-power-domain.1: DMA mask not set
2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 26, base_baud = 5000000) is a IMX
printk: console [ttymxc0] enabled
21f0000.serial: ttymxc3 at MMIO 0x21f0000 (irq = 66, base_baud = 5000000) is a IMX
etnaviv etnaviv: bound 130000.gpu (ops 0x809686a4)
etnaviv etnaviv: bound 134000.gpu (ops 0x809686a4)
etnaviv etnaviv: bound 2204000.gpu (ops 0x809686a4)
etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
etnaviv-gpu 130000.gpu: command buffer outside valid memory window
etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
etnaviv-gpu 134000.gpu: command buffer outside valid memory window
etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
[drm] Initialized etnaviv 1.2.0 20151214 for etnaviv on minor 0
brd: module loaded
loop: module loaded
ahci-imx 2200000.sata: fsl,transmit-level-mV value 1104, using 00000044
ahci-imx 2200000.sata: fsl,transmit-boost-mdB value 0, using 00000000
ahci-imx 2200000.sata: fsl,transmit-atten-16ths value 9, using 00002000
ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000
ahci-imx 2200000.sata: SSS flag set, parallel bus scan disabled
ahci-imx 2200000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci-imx 2200000.sata: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst
scsi host0: ahci-imx
ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 69
libphy: Fixed MDIO Bus: probed
pps pps0: new PPS source ptp0
libphy: fec_enet_mii_bus: probed
fec 2188000.ethernet eth0: registered PHC device 0
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
imx_usb 2184000.usb: No over current polarity defined
ci_hdrc ci_hdrc.0: EHCI Host Controller
ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 5.1.16-cubox ehci_hcd
usb usb1: SerialNumber: ci_hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
imx_usb 2184200.usb: No over current polarity defined
ci_hdrc ci_hdrc.1: EHCI Host Controller
ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2
ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: EHCI Host Controller
usb usb2: Manufacturer: Linux 5.1.16-cubox ehci_hcd
usb usb2: SerialNumber: ci_hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mousedev: PS/2 mouse device common for all mice
rtc-pcf8523 2-0068: registered as rtc0
snvs_rtc 20cc000.snvs:snvs-rtc-lp: registered as rtc1
i2c /dev entries driver
Registered IR keymap rc-empty
rc rc0: gpio_ir_recv as /devices/soc0/ir-receiver/rc/rc0
input: gpio_ir_recv as /devices/soc0/ir-receiver/rc/rc0/input0
imx2-wdt 20bc000.wdog: timeout 60 sec (nowayout=0)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-esdhc-imx 2194000.usdhc: Got CD GPIO
mmc0: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver r8712u
ata1: SATA link down (SStatus 0 SControl 300)
ahci-imx 2200000.sata: no device found, disabling link.
ahci-imx 2200000.sata: pass ahci_imx..hotplug=1 to enable hotplug
mmc0: host does not support reading read-only switch, assuming write-enable
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 USD   7.47 GiB
 mmcblk0: p1
imx-spdif sound-spdif: ASoC: failed to init link S/PDIF PCM
NET: Registered protocol family 10
Segment Routing with IPv6
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
registered taskstats version 1
Loading compiled-in X.509 certificates
zswap: default zpool zbud not available
zswap: pool creation failed
Btrfs loaded, crc32c=crc32c-generic
Key type encrypted registered
usb usb2-port1: over-current condition
imx_thermal tempmon: Extended Commercial CPU temperature grade - max:105C critical:100C passive:95C
imx-spdif sound-spdif: ASoC: failed to init link S/PDIF PCM
imx-spdif sound-spdif: ASoC: failed to init link S/PDIF PCM
input: gpio-keys as /devices/soc0/gpio-keys/input/input1
rtc-pcf8523 2-0068: setting system clock to 2019-07-21T14:06:11 UTC (1563717971)
Duplicate name in testcase-data, renamed to "duplicate-name#1"
### dt-test ### start of unittest - you will see error messages
OF: /testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
OF: /testcase-data/phandle-tests/consumer-a: could not get #phandle-cells-missing for /testcase-data/phandle-tests/provider1
OF: /testcase-data/phandle-tests/consumer-a: could not find phandle
OF: /testcase-data/phandle-tests/consumer-a: could not find phandle
OF: /testcase-data/phandle-tests/consumer-a: arguments longer than property
OF: /testcase-data/phandle-tests/consumer-a: arguments longer than property
OF: /testcase-data/phandle-tests/consumer-b: could not get #phandle-missing-cells for /testcase-data/phandle-tests/provider1
imx-spdif sound-spdif: ASoC: failed to init link S/PDIF PCM
OF: /testcase-data/phandle-tests/consumer-b: could not find phandle
OF: /testcase-data/phandle-tests/consumer-b: arguments longer than property
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest0/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest1/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest2/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest3/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest5/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest6/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest7/status
imx-spdif sound-spdif: ASoC: failed to init link S/PDIF PCM
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest8/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/test-unittest8/property-foo
OF: overlay: node_overlaps_later_cs: #6 overlaps with #7 @/testcase-data/overlay-node/test-bus/test-unittest8
OF: overlay: overlay #6 is not topmost
i2c i2c-3: Added multiplexed i2c bus 4
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/i2c-test-bus/test-unittest12/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data/overlay-node/test-bus/i2c-test-bus/test-unittest13/status
i2c i2c-3: Added multiplexed i2c bus 5
imx-spdif sound-spdif: ASoC: failed to init link S/PDIF PCM
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/substation@100/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/fairway-1/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/fairway-1/ride@100/track@30/incline-up
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/fairway-1/ride@100/track@40/incline-up
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/lights@40000/status
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/lights@40000/color
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/lights@40000/rate
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /__symbols__/hvac_2
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /__symbols__/ride_200
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /__symbols__/ride_200_left
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /__symbols__/ride_200_right
OF: overlay: ERROR: multiple fragments add and/or delete node /testcase-data-2/substation@100/motor-1/controller
OF: overlay: ERROR: multiple fragments add, update, and/or delete property /testcase-data-2/substation@100/motor-1/controller/name
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/substation@100/motor-1/rpm_avail
OF: overlay: WARNING: memory leak will occur if overlay removed, property: /testcase-data-2/substation@100/motor-1/rpm_avail
OF: overlay: ERROR: multiple fragments add, update, and/or delete property /testcase-data-2/substation@100/motor-1/rpm_avail
### dt-test ### end of unittest - 224 passed, 0 failed
brcm_reg: disabling
ALSA device list:
  No soundcards found.
Freeing unused kernel memory: 1024K
Run /init as init process
Loading, please wait...
starting version 232
random: systemd-udevd: uninitialized urandom read (16 bytes read)
random: systemd-udevd: uninitialized urandom read (16 bytes read)
random: udevadm: uninitialized urandom read (16 bytes read)
pwrseq_simple: section 3 reloc 2 sym 'memset': relocation 10 out of range (0x7f800034 -> 0x80886321)
random: fast init done
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/sda1 does not exist.  Dropping to a shell!

If I check the boot args, as suggested:

cat /proc/cmdline
root=/dev/sda1 rootfstype=ext4 rootwait console=ttymxc0,115200 consoleblank=0 video=mxcfb0:dev=hdmi,1920x1080m60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi vt.global_cursor_default=0 loglevel=7 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u

And the modules:

(initramfs) cat /proc/modules; ls /dev
drwxr-xr-x 10 0 0    3380 .
drwxr-xr-x 15 0 0       0 ..
drwxr-xr-x  7 0 0     140 disk
drwxr-xr-x  2 0 0     320 block
lrwxrwxrwx  1 0 0       4 rtc -> rtc0
drwxr-xr-x  2 0 0    3000 char
lrwxrwxrwx  1 0 0      15 stderr -> /proc/self/fd/2
lrwxrwxrwx  1 0 0      15 stdout -> /proc/self/fd/1
lrwxrwxrwx  1 0 0      15 stdin -> /proc/self/fd/0
lrwxrwxrwx  1 0 0      13 fd -> /proc/self/fd
drwxr-xr-x  2 0 0       0 pts
crw-------  1 0 0  10, 58 ubi_ctrl
crw-------  1 0 0  10,234 btrfs-control
crw-------  1 0 0  10, 59 memory_bandwidth
crw-------  1 0 0  10, 60 network_throughput
crw-------  1 0 0  10, 61 network_latency
crw-------  1 0 0  10, 62 cpu_dma_latency
brw-------  1 0 0 179,  1 mmcblk0p1
brw-------  1 0 0 179,  0 mmcblk0
drwxr-xr-x  2 0 0      60 snd
crw-------  1 0 0 250,  0 watchdog0
crw-------  1 0 0  10,130 watchdog
crw-------  1 0 0  89,  2 i2c-2
crw-------  1 0 0  89,  1 i2c-1
crw-------  1 0 0 253,  1 rtc1
crw-------  1 0 0 253,  0 rtc0
drwxr-xr-x  2 0 0     100 input
drwxr-xr-x  3 0 0      60 bus
crw-------  1 0 0 252,  0 pps0
crw-------  1 0 0 251,  0 ptp0
brw-------  1 0 0   7,  7 loop7
brw-------  1 0 0   7,  6 loop6
brw-------  1 0 0   7,  5 loop5
brw-------  1 0 0   7,  4 loop4
brw-------  1 0 0   7,  3 loop3
brw-------  1 0 0   7,  2 loop2
brw-------  1 0 0   7,  1 loop1
brw-------  1 0 0   7,  0 loop0
crw-------  1 0 0  10,237 loop-control
brw-------  1 0 0   1,  3 ram3
brw-------  1 0 0   1,  2 ram2
brw-------  1 0 0   1,  1 ram1
brw-------  1 0 0   1,  0 ram0
drwxr-xr-x  2 0 0      80 dri
crw-------  1 0 0  10,183 hwrng
crw-------  1 0 0 207, 19 ttymxc3
crw-------  1 0 0 207, 16 ttymxc0
crw-rw-rw-  1 0 0   5,  2 ptmx
crw-------  1 0 0   3, 15 ttypf
crw-------  1 0 0   3, 14 ttype
crw-------  1 0 0   3, 13 ttypd
crw-------  1 0 0   3, 12 ttypc
crw-------  1 0 0   3, 11 ttypb
crw-------  1 0 0   3, 10 ttypa
crw-------  1 0 0   3,  9 ttyp9
crw-------  1 0 0   3,  8 ttyp8
crw-------  1 0 0   3,  7 ttyp7
crw-------  1 0 0   3,  6 ttyp6
crw-------  1 0 0   3,  5 ttyp5
crw-------  1 0 0   3,  4 ttyp4
crw-------  1 0 0   3,  3 ttyp3
crw-------  1 0 0   3,  2 ttyp2
crw-------  1 0 0   3,  1 ttyp1
crw-------  1 0 0   3,  0 ttyp0
crw-------  1 0 0   2, 15 ptypf
crw-------  1 0 0   2, 14 ptype
crw-------  1 0 0   2, 13 ptypd
crw-------  1 0 0   2, 12 ptypc
crw-------  1 0 0   2, 11 ptypb
crw-------  1 0 0   2, 10 ptypa
crw-------  1 0 0   2,  9 ptyp9
crw-------  1 0 0   2,  8 ptyp8
crw-------  1 0 0   2,  7 ptyp7
crw-------  1 0 0   2,  6 ptyp6
crw-------  1 0 0   2,  5 ptyp5
crw-------  1 0 0   2,  4 ptyp4
crw-------  1 0 0   2,  3 ptyp3
crw-------  1 0 0   2,  2 ptyp2
crw-------  1 0 0   2,  1 ptyp1
crw-------  1 0 0   2,  0 ptyp0
crw-r--r--  1 0 0  10,235 autofs
crw--w----  1 0 0   4, 63 tty63
crw--w----  1 0 0   4, 62 tty62
crw--w----  1 0 0   4, 61 tty61
crw--w----  1 0 0   4, 60 tty60
crw--w----  1 0 0   4, 59 tty59
crw--w----  1 0 0   4, 58 tty58
crw--w----  1 0 0   4, 57 tty57
crw--w----  1 0 0   4, 56 tty56
crw--w----  1 0 0   4, 55 tty55
crw--w----  1 0 0   4, 54 tty54
crw--w----  1 0 0   4, 53 tty53
crw--w----  1 0 0   4, 52 tty52
crw--w----  1 0 0   4, 51 tty51
crw--w----  1 0 0   4, 50 tty50
crw--w----  1 0 0   4, 49 tty49
crw--w----  1 0 0   4, 48 tty48
crw--w----  1 0 0   4, 47 tty47
crw--w----  1 0 0   4, 46 tty46
crw--w----  1 0 0   4, 45 tty45
crw--w----  1 0 0   4, 44 tty44
crw--w----  1 0 0   4, 43 tty43
crw--w----  1 0 0   4, 42 tty42
crw--w----  1 0 0   4, 41 tty41
crw--w----  1 0 0   4, 40 tty40
crw--w----  1 0 0   4, 39 tty39
crw--w----  1 0 0   4, 38 tty38
crw--w----  1 0 0   4, 37 tty37
crw--w----  1 0 0   4, 36 tty36
crw--w----  1 0 0   4, 35 tty35
crw--w----  1 0 0   4, 34 tty34
crw--w----  1 0 0   4, 33 tty33
crw--w----  1 0 0   4, 32 tty32
crw--w----  1 0 0   4, 31 tty31
crw--w----  1 0 0   4, 30 tty30
crw--w----  1 0 0   4, 29 tty29
crw--w----  1 0 0   4, 28 tty28
crw--w----  1 0 0   4, 27 tty27
crw--w----  1 0 0   4, 26 tty26
crw--w----  1 0 0   4, 25 tty25
crw--w----  1 0 0   4, 24 tty24
crw--w----  1 0 0   4, 23 tty23
crw--w----  1 0 0   4, 22 tty22
crw--w----  1 0 0   4, 21 tty21
crw--w----  1 0 0   4, 20 tty20
crw--w----  1 0 0   4, 19 tty19
crw--w----  1 0 0   4, 18 tty18
crw--w----  1 0 0   4, 17 tty17
crw--w----  1 0 0   4, 16 tty16
crw--w----  1 0 0   4, 15 tty15
crw--w----  1 0 0   4, 14 tty14
crw--w----  1 0 0   4, 13 tty13
crw--w----  1 0 0   4, 12 tty12
crw--w----  1 0 0   4, 11 tty11
crw--w----  1 0 0   4, 10 tty10
crw--w----  1 0 0   4,  9 tty9
crw--w----  1 0 0   4,  8 tty8
crw--w----  1 0 0   4,  7 tty7
crw--w----  1 0 0   4,  6 tty6
crw--w----  1 0 0   4,  5 tty5
crw--w----  1 0 0   4,  4 tty4
crw--w----  1 0 0   4,  3 tty3
crw--w----  1 0 0   4,  2 tty2
crw--w----  1 0 0   4,  1 tty1
crw-------  1 0 0   7,129 vcsa1
crw-------  1 0 0   7, 65 vcsu1
crw-------  1 0 0   7,  1 vcs1
crw-------  1 0 0   7,128 vcsa
crw-------  1 0 0   7, 64 vcsu
crw-------  1 0 0   7,  0 vcs
crw--w----  1 0 0   4,  0 tty0
crw-------  1 0 0   5,  1 console
crw-rw-rw-  1 0 0   5,  0 tty
crw-r--r--  1 0 0   1, 11 kmsg
crw-rw-rw-  1 0 0   1,  9 urandom
crw-rw-rw-  1 0 0   1,  8 random
crw-rw-rw-  1 0 0   1,  7 full
crw-rw-rw-  1 0 0   1,  5 zero
crw-r-----  1 0 0   1,  4 port
crw-rw-rw-  1 0 0   1,  3 null
crw-r-----  1 0 0   1,  1 mem
crw-------  1 0 0  10, 63 vga_arbiter
crw-------  1 0 0 254,  6 gpiochip6
crw-------  1 0 0 254,  5 gpiochip5
crw-------  1 0 0 254,  4 gpiochip4
crw-------  1 0 0 254,  3 gpiochip3
crw-------  1 0 0 254,  2 gpiochip2
crw-------  1 0 0 254,  1 gpiochip1
crw-------  1 0 0 254,  0 gpiochip0

On another computer, I fsck the hard drive and it is clean. I can even mount the file system and see all the files.

What could be investigated?

Thanks for any help.

After a reboot I get this kind of status for the service

systemctl status nftables
● nftables.service - nftables
   Loaded: loaded (/lib/systemd/system/nftables.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-07-12 16:04:59 CEST; 4min 28s ago
     Docs: man:nft(8)
           http://wiki.nftables.org
  Process: 287 ExecStart=/usr/sbin/nft -f /etc/nftables.conf (code=exited, status=3)
 Main PID: 287 (code=exited, status=3)

Jul 12 16:04:59 cubox nft[287]: netlink.c:62: Unable to initialize Netlink socket: Protocol not supported
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.


+++++++++++++++++++++++++++++++++++++
nftables installed ?
+++++++++++++++++++++++++++++++++++++
p  libnftables-dev - Development files for libnftables
i A libnftables0 - Netfilter nftables high level userspace API library
i  nftables - Program to control packet filtering rules by Netfilter project
+++++++++++++++++++++++++++++++++++++
update alternatives setup 
+++++++++++++++++++++++++++++++++++++
ip6tables                      auto     /usr/sbin/ip6tables-nft
iptables                       auto     /usr/sbin/iptables-nft

Anyway, a manual restart of the service works and the rules in /etc/nftables.conf are load properly.

I suppose there is a problem with a kernel module?

Doing the same upgrade on raspberries worked :

Linux bowerick 4.19.50-v7+ #896 SMP Thu Jun 20 16:11:44 BST 2019 armv7l GNU/Linux
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

Anything I can do?

board photo:

Because I do not have access to the programmer, I want to replace NAND and program it in the NAS.
However, I can not run U-Boot via UART.
I tried the adapters on PL2303HX and FTDI FT232RL.
I'm using a kwboot on this topic:

and the u-boot file from this: https://forum.doozan.com/read.php?2,27108,31893#msg-31893

Every time this error pops up:

root@gutek3:/gutek/nas326# ./kwboot-x86_64 -f -t -B 115200 /dev/ttyUSB0 -b uboot.bin -s 0 -q 1
Sending boot message. Please reboot the target...|
Sending boot image...
  0 % [+++++++++++++++++xmodem: Bad message

Sometimes it seems to start uploading, but there is also a error:

root@gutek3:/gutek/nas326# ./kwboot-x86_64 -f -t -B 115200 /dev/ttyUSB0 -b uboot.bin -s 0 -q 1
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
  0 % [..................................+++++++++++++++++xmodem: Bad message

I put static ip to eth0 and when i try to ping the output in not stable:

64 bytes from 104.27.115.15 (104.27.115.15): icmp_seq=1 ttl=58 time=580 ms

64 bytes from 104.27.115.15 (104.27.115.15): icmp_seq=2 ttl=58 time=120 ms

64 bytes from 104.27.115.15 (104.27.115.15): icmp_seq=3 ttl=58 time=350 ms

and then the output:

Destination host unreachable.

Destination host unreachable.

Destination host unreachable.

and i think there are some issues in kernel drivers related on Ethernet or ipv4 so could you please help me to fix Ethernet issue ?? 

Since I upgraded my kernel to version 4.19 (`linux-image-next-cubox=5.73` when I tried I think) on my cubox-i4 pro, I lost HDMI :

root@cubox:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SPDIF [Integrated SPDIF], device 0: S/PDIF PCM snd-soc-dummy-dai-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Anyone experiencing this too ? Downgrading to `linux-image-next-cubox=5.60` solved it.

apt install linux-image-next-cubox=5.60
reboot
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SPDIF [Integrated SPDIF], device 0: S/PDIF PCM snd-soc-dummy-dai-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: DWHDMI [DW-HDMI], device 0: DW HDMI [dw-hdmi-ahb-audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Thanks

I recently installed Armbian (Stretch: Armbian_5.83_Nanopifire3_Debian_stretch_next_4.14.115) on my new NanoPi Fire3.

I was able to boot, but it responds so slow, that it is unusable!

For example, when I SSH into it, it takes a log time to show me the login prompt. 

When I enter the username and press enter, it takes about 5 seconds to ask me for password.

When I enter password, it takes about 10 seconds to show me the Armbian banner.

I wasn't even able to go past the changing of unix password on first login, because it just "froze".

I have installed the image twice on my SD card, just to make sure it isn't a corrupted install.

I'm using a good PSU, and a good quality Samsung EVO 32GB sd card.

I have tried installing DietPi, and FriendlyElec's 64 bit xenial image, without problems!

This behavior happens only with Armbian. I want to use Armbian because I understood that it supports Docker on the Fire3 (is this true?)

I haven't tried the Ubuntu version of Armbian, since it has Desktop, and I'm looking for a headless OS.

BTW, is the Armbian Stretch image for the NanoPi 64 bit?

Thank you guys for the excellent work!

In the review of the Fire3

at least one person mentions powering this board via something other than the MicroUSB. This would allow me to use the serial console that's supposedly exposed over that port instead of wiring up yet another USB to serial converter.

What I can't work out is a) which pin/s are used to power it, and b) what kind of power supply is used. I'd rather not fry the board (it'll do that itself under load) so can someone point me in the right direction?

Thanks in advance.

But following the documentation, i did not manage to implement DMA data transfer.

Is it possible to get an example of the implementation of data transfer over DMA?

I've just created a SD-card with Armbian Bionic (mainline kernel 4.19.y) for a Hummingboard Gate. I noticed during boot that it says it uses U-boot version 2013.10-rc4. This seems quite old compared to the 2018 version that was on the Debian Stretch image from SolidRun. I've tried to search the internet to see what the impact of something like this is and wasn't able to find something that made sense to me (could be entirely my fault). I therefore have the question:

Is the U-boot version intentional? (maybe it has some features that newer versions have dropped.)

I searched and I found a related topic that has the same problem but there is no answer.

I believe the problem is because of different mem chip but the same revision (1709)

Can boot armbian whit compiled friendlyArm Uboot?

topic URL

my memory chip picture and logs (from the topic)

\

I am running Debian Strech on a headless server with armbian (since 2014 on wheezy), on a Cubox-i 4 Pro.

My system is on /dev/sda1

After an upgrade, few minutes ago, my device is no more reachable by ssh neither answering to ping.

It seems to boot the kernel but I am not even sure of that (as nothing appears in the console after "booting the kernel").

Here is the full console log:

U-Boot SPL 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)
Boot Device: SD1
spl: error reading image u-boot.img, err - -1
Load image from RAW...


U-Boot 2013.10-rc4-ge4bc4c3 (Dec 18 2014 - 14:55:42)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   vga
Err:   vga
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0
mmc0 is current device
** File not found /boot.scr **
** File not found /uEnv.txt **
** File not found /zImage **
** File not found /uImage **
1816 bytes read in 127 ms (13.7 KiB/s)
Running bootscript from mmc ...
## Executing script at 10800000
** File not found .next **
48 bytes read in 114 ms (0 Bytes/s)
36853 bytes read in 826 ms (43 KiB/s)
4636514 bytes read in 411 ms (10.8 MiB/s)
5839840 bytes read in 482 ms (11.6 MiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x591be0 ]
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4636450 Bytes = 4.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800bff4

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Files located in /boot on the SDCard (same files list in sda/boot):

-rw-r--r-- 1 root root   48 janv. 30 18:28 armbianEnv.txt
-rw-r--r-- 1 root root   79 janv. 30 18:28 armbianEnv.txte
-rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.cmd
-rw-r--r-- 1 root root 1,8K sept. 20 22:33 boot.scr
-rw-r--r-- 1 root root  360 déc.  27  2015 boot.txt
-rw-r--r-- 1 root root 160K févr.  8 09:33 config-4.14.98-cubox
-rw-r--r-- 1 root root 162K févr.  8 09:38 config-4.19.20-cubox
lrwxrwxrwx 1 root root   17 févr. 16 17:47 dtb -> dtb-4.19.20-cubox
drwxr-xr-x 2 root root  12K févr. 16 17:42 dtb-4.14.98-cubox
drwxr-xr-x 2 root root  12K févr. 16 17:31 dtb-4.19.20-cubox
-rw-r--r-- 1 root root 4,2M févr. 16 17:09 initrd.img-4.14.98-cubox
-rw-r--r-- 1 root root 4,5M févr. 16 17:09 initrd.img-4.19.20-cubox
-rw-r--r-- 1 root root 2,5M févr.  8 09:33 System.map-4.14.98-cubox
-rw-r--r-- 1 root root 2,6M févr.  8 09:38 System.map-4.19.20-cubox
lrwxrwxrwx 1 root root   21 févr. 16 17:47 uInitrd -> uInitrd-4.19.20-cubox
-rw-r--r-- 1 root root 4,2M févr. 16 17:09 uInitrd-4.14.98-cubox
-rw-r--r-- 1 root root 4,5M févr. 16 17:09 uInitrd-4.19.20-cubox
-rwxr-xr-x 1 root root 5,4M févr.  8 09:33 vmlinuz-4.14.98-cubox
-rwxr-xr-x 1 root root 5,6M févr.  8 09:38 vmlinuz-4.19.20-cubox
lrwxrwxrwx 1 root root   21 févr. 16 17:48 zImage -> vmlinuz-4.19.20-cubox

$ more boot.txt  
setenv bootargs root=/dev/sda1 rootfstype=ext4 rootwait console=tty1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 rd.dm=0 rd.luks=0 rd.lvm=0 raid=noautodetect pci=nomsi ahci_imx.hotplug=1 consoleblank=0 vt
.global_cursor_default=0 quiet
ext2load mmc 0 0x18000000 /boot/dtb/${fdt_file}
ext2load mmc 0 0x12000000 /boot/zImage
bootz 0x12000000 - 0x18000000

$ more armbianEnv.txt
verbosity=1
rootdev=/dev/sda1
usbstoragequirks=

What else could I provide as information to get help?

Thanks a lot to anybody that could give me some support...