SD card and PSU issues Latest Topics

Freshly downloaded OS for Orange pi Zero 2 are not getting booted

Sun, 02 Aug 2026 11:05:49 +0000

Armbian_24.2.1_Orangepizero2_bookworm_current_6.6.16_minimal

This is working.

Armbian_25.5.1_Orangepizero2_bookworm_current_6.12.23_minimal

Armbian_community_26.8.0-trunk.7_Orangepizero2_trixie_current_6.18.41_minimal

These two are not taking me to login screen even after waiting for 10 minutes after bootup.

It gets stuck at line called starting kernel.

I tried to boot multiple times hoping that new versions should be smooth.

But it wasn't the case.

OrangePi Zero 2 wont resize after reboot

Sun, 11 Feb 2024 18:18:37 +0000

I've been looking for ways to fix this all afternoon but I'm giving up.

I flash the latest version of the image with BalenaEtcher, it takes about 10 min approximately to boot. I log in I do the setup, and the partition / is only 2GB, I reboot the red light stops flashing and the board stays with a steady green light does not respond to ping. I pull the cable and start in armbian the partition is still the same at 2GB, I check the resize2fs service and it does not start.

I don't know what I'm doing wrong, the PSU is working properly, I did a health test to the SD is also OK.

I don't know what else to check.

Help me recover corrupted OS

Thu, 19 Dec 2024 17:34:42 +0000

I have a Rock64 I'm using for about 3-4 years.
last month November, '24, due to a power failure issue, the Memory card got corrupted and won't boot anymore.

I backed up the memory card using win32disk imager to rock64_corrupted.img

now if I insert the memory card in a debian 12 machine, then I can see all files.

root@debian:~# lsblk
sdb           8:16   1  29.8G  0 disk
└─sdb1        8:17   1  29.5G  0 part /media/user/ddc95179-99af-4380-b45b-fa41999ac3d0

root@debian:~# fdisk -l /dev/sdb
Disk /dev/sdb: 29.81 GiB, 32010928128 bytes, 62521344 sectors
Disk model: Mass-Storage
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: dos
Disk identifier: 0xce7a88b0

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdb1       32768 61896127 61863360 29.5G 83 Linux


root@debian:~# cat /media/user/ddc95179-99af-4380-b45b-fa41999ac3d0/etc/os-release
PRETTY_NAME="Armbian 24.2.1 bookworm"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.armbian.com"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
ARMBIAN_PRETTY_NAME="Armbian 24.2.1 bookworm"

root@debian:~# umount /media/user/ddc95179-99af-4380-b45b-fa41999ac3d0
root@debian:~# fsck.ext4 /dev/sdb1
e2fsck 1.47.0 (5-Feb-2023)
/dev/sdb1: clean, 448797/1914432 files, 5384081/7732920 blocks

Is it possible to fix this?

Please let me know if I should provide any more info.
Any help is greatly appreciated.

I have a backup img file from February, '24 which works fine when written into the memory card. But that one is very old.

Burn ISO Image to Micro SD Card

Fri, 01 Jun 2018 01:43:51 +0000

Would you please recommend a proper tool to burn ISO and XZ image to Micro SD card? I tried ImgBurn but it doesn't work at all.

latest bananapi-m5 vs wireless keyboard/mouse combo, stops working after gui starts

Sat, 20 Apr 2024 15:26:49 +0000

latest armbian jammy, bananapi-m5, not recognizing wirelless keyboard mouse kit after x startup. This same elcheapo mini keyboard/mouse worked great with previous jammy/xfce4 versions.

Any fixes available?. Both keyboard and mouse have sleep functions to save battery's.

Also the security check expires long before I could type 20% of the about sentence. Like 20 seconds. Also would not accept w/o tag, only tag is solved, but is not

SDCard from backup doesnt start

Mon, 07 Feb 2022 20:55:12 +0000

Hello!

Shortform:

SDCard recreated from .iso image does not boot.

####

Detailed:

I use an Odroid as my Minecraft server. I have a fast 32GB card in it, and a usb hdd for swap and media files.

After the setup was working, and after each update, I pulled the card from the machine (after shutting down) and plugged it into my PC to make a backup:

dd if=/dev/sdc bs=4M | gzip -c >/media/backup/odroid.img.gz

In case I ever needed to recreate the card, I have this line to run:

gunzip -c /media/backup/odroid.img.gz | dd of=/dev/sdc bs=4M

/dev/sdc is a placeholder for whichever drive my USB Cardreader is appearign as.

I do have a https enabled Apache webserver with some static content, a Mumble voicechat server for gaming voicechat, Dokuwiki for my occasional bouts of hobby writing and a lot of other little tidbits on the machine, such as a VPN and one of these mediaserver thingies for my TV.

That is a LOT of hand crafting that went into it over the years, and I am effectively unable to recreate all the little things I added over the years, which is why a new setup is something I am scared shitless imagining.

Also, I named every backup separately, so I do have a LOT of backups - my backup drive is 4TB in size and my systems run on average on a space budged of 32 to 64 GB, my home partition being rsynced to a NAS via 1GB ethernet on each shutdown.

When my SDCard died after years of trusty service and I replaced it with a newer, faster card, writing the isoimage went smoothly, the ext4 partition was flawless un doing fsck on it before doing sync and then pulling the card.

However, the machine doesn't start. Power LED goes on, but nothing else happens.

####

The error I see - Power LED on, no Keepalive LED blinking - makes me guess the bootloader isn't - or wasn't - backed up with the method I used.

However, the way I use DD I am very sure it should copy the whole drive inclusive the bootloader, grub, lilo, uboot or whatever else there might be on it.

Even cloning Amiga HDDs works flawlessly with DD this way.

So, assuming I am correct and the way the backup was made was correct:

1) is there a known way to get an image written to SDCard that wil lhave the odroid bootloader workable?

2) is there a trick, like creating a new SDCard from an Armbian image and then copying the /dev/sd*1 partition from the image file to the newly made sdcard, that might get the image working?

3) Which other recommendations or suggestions ( I don't know, like mounting a rewritten image and a newly made SDCard and then doing cp -a /mnt/source/* /mnt/target/ ?) that might help me get my system back to working do you people have?

With kind regards,

a frustrated SDCard-user

(with HDDs doing DD in the manner described above works nicely since almost 20 years for me, cloning systems between machines, replacing deceased drives and so on )

orange pi 5 boost up issue

Wed, 29 Mar 2023 02:10:34 +0000

hi, I am a newbie using the orange pi 5 board, or any kind like this.

I have a boost-up issue, I connect to the power supply and only red light is on (on the board) but when connect the display by HDMI-HDMI or HDMI-typeC, nothing I can see.

I am not sure my new board is functioning or not, the problem is, the requirement says this needs 5V4A, but for some reason, my new power supply shipping will come later, so I use 5V2A for test currently, and I am not sure 2A will be able to boost up the board, or at least I can see the startup screen.

I will get my 5V4A power next week, but the reason why I want to try with 2A now is because I want to know if my board is functioning or not, otherwise, I need to return to the retail store and replace a new one.

so can anyone tell if 5V2A can boost the board, or if my board is just not functioning?

any other way to work around, maybe, can I connect this with an iPad power adapter? the iPad adaper spec says it outputs 5V3A or 9V2.22A, isn't it about the PD standard? And I did read the orange pi 5 user manual, and it say that the board has no PD support, so can I still use the iPad adaptor to power it, or it will damage the board?

Thank for help when you answer it.

failing first boot when using sd -> eMMC adapter

Wed, 18 Nov 2020 13:37:32 +0000

Hi All,

I bought a nice SD to eMMC adapter with a 32GB eMMC module for the orange PI PC.

Unfortunately it does not go through first boot.

Formatting goes okay, flashing goes okay, booting does not.

With Armbian_20.08.1_Orangepipc_focal_current_5.8.5.img.xz image there is no more terminal output after "Uncompressing Linux... done, booting the kernel.".

With the Armbian_20.05.4_Orangepipc_focal_current_5.4.45.img.xz image I had laying around (and have successfully used on this OpiPC on a normal SD card before), this is the terminal output:

U-Boot SPL 2020.04-armbian (Jun 15 2020 - 06:08:51 +0200)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2020.04-armbian (Jun 15 2020 - 06:08:51 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
Bus usb@1c1d000: USB EHCI 1.00
Bus usb@1c1d400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
scanning bus usb@1c1d000 for devices... 1 USB Device(s) found
scanning bus usb@1c1d400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3789 bytes read in 1 ms (3.6 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 1 ms (148.4 KiB/s)
11634345 bytes read in 551 ms (20.1 MiB/s)
7163872 bytes read in 341 ms (20 MiB/s)
Found mainline kernel configuration
29475 bytes read in 4 ms (7 MiB/s)
4185 bytes read in 4 ms (1021.5 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11634281 Bytes = 11.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 494e7000, end 49fff669 ... OK
   Loading Device Tree to 49477000, end 494e6fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    5.496839] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[    5.503254] sunxi-mmc 1c0f000.mmc: send stop command failed
[    5.509577] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[    5.515900] sunxi-mmc 1c0f000.mmc: send stop command failed
[    6.874824] sun4i-codec 1c22c00.codec: Failed to register our card
[    6.908187] sun4i-codec 1c22c00.codec: Failed to register our card
[    6.936994] debugfs: Directory '1c22c00.codec' with parent 'H3 Audio Codec' already present!
[   12.084564] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[   12.090920] sunxi-mmc 1c0f000.mmc: send stop command failed
[   12.151934] sunxi-mmc 1c0f000.mmc: data error, sending stop command
[   13.155270] sunxi-mmc 1c0f000.mmc: send stop command failed

Any help greatly appreciated.

[Odroid-C4] Alert! Root UUID does not exist. Dropping to a shell!

Wed, 16 Mar 2022 20:18:00 +0000

Hey, I'm trying to boot Armbian 27 Feb bullseye for Odroid C4 from microSD card and I get dropped to initramfs console because root UUID is not found. I fsck'd the card and it seems okay. Read that I should say to the kernel to wait for root to be found with rootdelay, added a line to armbianEnv.txt to no avail (didn't run any update command, though). What are your thoughts? Any other ideas? Thanks!

Duo automated build not expanding

Sat, 03 Dec 2022 15:24:15 +0000

Tried a few builds such as https://github.com/armbian/community/releases/download/202248/Armbian_22.11.0-trunk_Nanopiduo_kinetic_edge_6.0.10.img.xz#nanopiduo and the image doesn't even expand. No heartbeat flaching. Not sure how to troubleshoot this.

Restoring Orange PI 3 LTS 2GB/8GB EMMC boot partition

Mon, 07 Mar 2022 11:34:10 +0000

Hi there, firstly I selected "Orangepi PC" from the Board dropdown since Orange PI 3 wasn't present (although you have Orange PI 3 images so I assume it's supported ... )

I have wound up with an unbootable board, even though it was initially bootable.

I am connecting with an ethernet cable/eth0 and powered via USB using a power brick/charging cable for a Google Pixel. I don't think this is a power issue, because everything was going well, and was stable for quite some time (hours).

I was connected initially "headlessly" and later connected an HDMI cable when it failed to reboot (details below).

I have tried each of the images listed below with 2 different SanDisk Extreme Pro SD Cards, and have tested both cards booting Armbian_22.02.1_Orangepione_bullseye_current_5.15.25.img successfully in an OPI One board.

All images burned using Etcher.

Here's what happened:

1) I installed this Debian image for Orange PI 3 from the Orange PI website:

Orangepi3-lts_2.1.6_debian_buster_server_linux5.10.75.img

2) I went through the setup steps for my application. The most "controversial" of these steps are to disable predictable device names by adding this to /boot/orangepiEnv.txt:

extraargs=net.ifnames=0, and to add a reverse port forward using autossh into systemctl, everything else is just installing various software packages using apt

3) Nothing was behaving funnily, it was all stable at this point. Total elapsed time was 2 - 3 hours with no issues, crashes, random reboots or network problems.

4) During my setup steps, I need to reboot, I did so and the network did not come back up. I connected a monitor and saw it was starting the boot process but failing when adding the console on tty0

5) I thought maybe something to do with the extraargs was causing a problem so I disconnected the ethernet cable from eth0

6) The system failed to boot a couple of more times, and then successfully booted. I tested this multiple times. The system would never boot with ethernet connected, but would boot after a few failed tries with ethernet disconnected, it definitely wasn't a coincidence.

7) I logged in and then connected the ethernet cable. The system didn't crash or anything. I figured maybe updating would sort something out, so I started the upgrade to bullseye

8) At some point during the upgrade process, the system crashed and rebooted.

9) After this point, the system wouldn't successfully boot with or without ethernet disconnected. It would always restart at the same point of connecting the console on tty0

10) At this point I removed the SD card, and powered on the device, it successfully booted into whatever Android is shipped with the EMMC.

11) I also inserted the SD card into a linux VM and noticed that there was no boot partition. I thought that maybe the boot partition for Orange PI 3 is located on the EMMC

12) So I went looking for some instructions to push an install to EMMC, which is when I found the Armbian forums

13) I flashed this Armbian image:

Armbian_22.02.1_Orangepi3_bullseye_current_5.15.25.img

14) When I inserted the SD card and attempted to boot, I now saw the message "Running /scripts/local-block... done" over and over until it eventually gave up trying to find the root file system

15) I searched this error and found instructions for mounting the SD card partition and ensuring that the UUID is correct in armbianEnv.txt:

It was already correct

16) I then discovered that the Android version shipped in the EMMC no longer boots, it just hangs at the Orange PI logo

17) I then tried this Orange PI debian image which has an older kernel:

Orangepi3-lts_2.1.6_debian_buster_server_linux4.9.118

When I boot using this image on an SD card, I see an Orange PI logo with "Initialising boot loader" but it never gets past that

So the current situation is:

Orangepi3-lts_2.1.6_debian_buster_server_linux4.9.118: boots to a pi logo with "Initializing boot loader"

Orangepi3-lts_2.1.6_debian_buster_server_linux5.10.75: starts booting but then gives up waiting for root file system after "Running /scripts/local-block" repeatedly

Armbian_22.02.1_Orangepi3_bullseye_current_5.15.25.img: starts booting but then gives up waiting for root file system after "Running /scripts/local-block" repeatedly

Booting with no SD card inserted shows an Orange PI logo on the screen with no writing forever

So it seems that the SD card reader definitely works since the behaviour changes depending on which image I insert, and it seems that somehow something I did "broke" the EMMC boot partition, and that even when I'm booting from the SD card, it's still using the EMMC somehow.

NOW ... I dug around for some way to "reset" the EMMC and found out there is a thing called "PhoenixCard" that lets you burn Android images in "Product" mode that allegedly copy themselves automatically to EMMC when you turn the machine on, which I found in the OPI 3 User Manual.

I am downloading a Windows 10 iso for use with VirtualBox so I can run PhoenixCard from my Mac to do so, but since it's a 5.5GB download and that's going to take a couple of hours I thought I'd write out the situation here to see if whether or not anyone has a better idea and/or I'm barking up entirely the wrong tree or something else.

Thanks!

Unable to boot NanoPi NEO3 after system upgrade

Sat, 02 Apr 2022 20:25:16 +0000

Hi,

I have 4 FriendlyElec NanoPi Neo 3 boards.

Till now they were working fine, but after today 'apt upgrade' none of them boot anymore.

I got one connected in debug mode and got this log:

=> DDR version 1.16 20190528
ID:0x805 N
In
DDR4
333MHz
Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=16 CS=1 Die Bus-Width=16 Size=2048MB
ddrconfig:14
OUT
Boot1 Release Time: May 13 2019 17:34:36, version: 2.50
ChipType = 0x11, 248
mmc2:cmd1,20
emmc reinit
mmc2:cmd1,20
emmc reinit
mmc2:cmd1,20
SdmmcInit=2 1
mmc0:cmd5,20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 33580
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x337a9f0 signature is wrong
recovery gpt...
GPT 0x337a9f0 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
hdr 000000000337a3b0 + 0x0:0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,

Load OK, addr=0x200000, size=0xab950
RunBL31 0x40000
INFO:    Preloader serial: 2
NOTICE:  BL31: v1.3(debug):403e0b816
NOTICE:  BL31: Built : 14:13:08, Aug 11 2020
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

U-Boot 2020.10-armbian (May 06 2021 - 17:55:54 +0000)

Model: FriendlyElec NanoPi R2S
DRAM:  2 GiB
PMIC:  RK8050 (on=0x40, off=0x00)
MMC:   mmc@ff500000: 1
Loading Environment from MMC... MMC Device 0 not found
*** Warning - No MMC card found, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: FriendlyElec NanoPi R2S
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 8 ms (388.7 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
261 bytes read in 4 ms (63.5 KiB/s)
14236833 bytes read in 623 ms (21.8 MiB/s)
30083584 bytes read in 1307 ms (22 MiB/s)
Failed to load '/boot/dtb/rockchip/rk3328-nanopi-neo3-rev02.dtb'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr " command.
Aborting!
1314 bytes read in 9 ms (142.6 KiB/s)
Applying kernel provided DT overlay rockchip-spi-jedec-nor.dtbo
No FDT memory address configured. Please configure
the FDT address via "fdt addr " command.
Aborting!
1266 bytes read in 9 ms (136.7 KiB/s)
Applying kernel provided DT overlay rockchip-spi-spidev.dtbo
No FDT memory address configured. Please configure
the FDT address via "fdt addr " command.
Aborting!
Error applying DT overlays, restoring original DT
Failed to load '/boot/dtb/rockchip/rk3328-nanopi-neo3-rev02.dtb'
Moving Image from 0x2080000 to 0x2200000, end=3f50000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    14236769 Bytes = 13.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
MMC Device 0 not found
no mmc device at slot 0
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...

No working controllers found
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-b6-20-d4-48-8b-b5
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
ethernet@ff540000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Could not initialize PHY ethernet@ff540000
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
(...)

SD card is good and I can read it in PC in normal SD-to-USB reader.

Is there a way to boot from this state ?

Is NEO3 still supported ?

Can't not boot after abnormal power off

Fri, 04 Feb 2022 08:04:28 +0000

Hello, we contact you with Odroid booting issues.

I've confirmed that the problem occurs from the next boot when the board is powered off while the armbian logo is displayed. (It happens with a high probability.)
When booting, the following log is displayed and it does not boot.

Loading, please wait...
starting version 237
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 ... Scanning for Btrfs filesystems
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block … done
done.
Gave up waiting for root 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/mmcblk1p1 does not exits. Dropping to a shell!

BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3.2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)_

After that, if you try to reboot about 5-6 times, one boot is possible. (This phenomenon does not disappear and continues.)

The sd card is not physically damaged.
This is because cloning the OS will reboot normally.

Another feature is that the Armbian logo does not appear normally after booting problems.
When there were no problems booting, the Armbian logo was always displayed.

It appears that some file related to booting are crashed on an abnormal shutdown.
This is because we found a file that is believed to be the cause.

After a few tries I successfully booted from the sd card with this boot problem and checked the /boot/armbianEnv.txt file.

And found that the file contents are broken. (The contents are different from normal files.)
I got the armbianEnv.txt file from a general sd card that did not have the problem raised in this article, overwritten it, and then booted it, and it was confirmed that it boots normally without any problem.
I think this happens if the file writes don't complete properly while boot.cmd is running. Is my guess correct?

I've heard that armbianEnv.txt is giving incorrect kernel parameters for the root filesystem root=/dev/mmcblk1p1 if it is corrupted.

On the other hand, the kernel recognizes the SD card as /dev/mmcblk0p1, so there is a problem when booting.

Has this phenomenon ever been reported?
I would like to know the exact cause of this phenomenon and how to fix it or prevent this problem?

We are looking for a way to recover if this happens during boot up.

For example running script that pass hard coded boot parameter to kernel each boot...

Because the product must be used in an environment where it is difficult to restrict users, unexpected power off (whether booting or not) may occur.

(However, the system must be restored and operational.)

We are considering mass production, so I think this is a very important issue.
Thanks in advance for the reply.
-------------------------------------------------
Environment of use
- board : odroid c4
- power : DC 9V, 0.5A
- os : ubuntu 18.04
- sdcard : SanDisk Ultra micro 32GB

no properly formatted SHA checksum lines found

Sat, 27 Nov 2021 17:32:34 +0000

Hello,

I have downloaded two times Armbian_21.08.1_Orangepipcplus_buster_current_5.10.60.img.xz and two times i have this result :

shasum -a 256 -c Armbian_21.08.1_Orangepipcplus_buster_current_5.10.60.img.xz.sha Armbian_21.08.1_Orangepipcplus_buster_current_5.10.60.img.xz
Armbian_21.08.1_Orangepipcplus_buster_current_5.10.60.img.xz: OK
shasum: Armbian_21.08.1_Orangepipcplus_buster_current_5.10.60.img.xz: no properly formatted SHA checksum lines found

I don't know if it's ok... There is a "OK" but after it seems there is problem "no properly formatted SHA checksum lines found".

Someone know if I can use it without problem ?

Thanks,

Best regards

error booting after microSD clone

Mon, 15 Nov 2021 22:00:46 +0000

HiAll, i am new here, and i have a big problem with clone my SD card with armbian image for nanopi neo plus2 H5

image: Armbian Focal mainline based kernel 5.10.y

I insert master SD to USB adapter and make sudo dd if=/dev/sdb of=XXXX.img bs=4096 for creating image

After complete, i change master SD to backup SD and make sudo dd of=/dev/sdb if=XXXX.img bs=4096 for creating backup SD.

I got thisdmesg.txt

in master SD i have

armbianEnv.txt boot.cmd fstab

Where i make mistakes?

RockPro64 only booting legacy kernel

Fri, 27 Aug 2021 19:01:33 +0000

Hello everyone,

First of all, thank you all for making ARM accessible!

I have a RockPro64 that only boot legacy kernels... I couldn't find anything specific about it online.

Is this something to do with the SPI chip? Do I have to update it with the procedure listed here? https://github.com/ayufan-rock64/linux-build/blob/master/recipes/flash-spi.md

Any tip would be really welcome, I tried most of the ROCKPRO64 images and nothing... only kernel 4.x boot, SD or emmc, no difference.

Bellow is one of the error messages I get... the screen flashes different colors and the system halts.

Different images, different behaviors... usually it just flash colors.

(Warning... Bad CRC) is this CRC about the SPI firmware? It's not the emmc or SD. I tried different ones and it just doesn't work for mainline kernels.

No HDMI output and I won't see an new IP on my network.

I tried it without the HDMI cable too.. nothing.

Thank you for any assistance!

PROVE your power

Wed, 25 Mar 2020 04:10:03 +0000

As in this Armbian forum I am regularly diagnosing power issues. I've answered with this info on a few different posts over the years but I wanted this in one place so my students and the Armbian forum could discuss it.

You will read over and over the importance of good power, both in the supply, the cables, and the connection. Anything that causes the voltage to drop below each boards threshold will cause problems that seem to have no explanation. The board may run and appear to be 'working' but operations that draw more power may fail and let the processor continue running. You might think a fully functional board has software failures. It's hair pulling, especially for those uneducated in power issues.

Without attempting to teach a power class I've come up with some tools that can 'prove' weather the power supply and cables can deliver the power you expect. There's deep math and science to all of it, but what we really need is to be able to 'trust' our power. These tools can help us 'prove' our power is at least staying above the levels we expect.

When there are so many variables in a situation we have to eliminate things to narrow down the problem. Since power is frequently the problem and fairly easy to prove, it's smart to start there. But how? We use our tools to test what we need to eliminate.

We used to use banks of resistors and separate power and current meters to measure power draw and voltage drop, but these days there are inexpensive tools called DC Electronic Loads that do this for us. I've purchased numerous versions and models, and they've all been good at what they are designed for yet lacking in some other things. A trade off of quality for expense, but good enough really is good enough.

Basically they have a transistor and a very low value resistor across the output and your power supply is pulsed with a PWM across that transistor. The width of the pulse determines the current draw on your power supply, effectively 'simulating' power draw from your device while displaying the voltage at the point of the load and the draw current. You simply attach your power supply and increase the load until the voltage drops below the supply's rating. If the voltage stays above its voltage rating at its rated current, it passes. If not, it fails. Almost as simple as that.

I usually let the thing run for a while and check for heating, voltage drop over time and shutdown. Sometimes failure comes with heat.

If you have a 5v power supply that's rated at 4 amps, and your load reports 4.9v at 4A draw, your supply has failed.

The image below shows a successful test of a popular power supply, the Meanwell RD65A., a dual voltage supply rated for 3A at 12v, and 6A at 5v. As you can see in the photos the voltage stays above its rating at the rated current. This particular photo was taken after approximately 40 minutes running at full load, which is highly inadvisable for this kind of power supply. Usually one would never run over 80% load continuously, but hey, this was a burn test. The only thing that failed here was the load, as the fan sensors on these particular models are somewhat flawed and overheat at less than their rating and shut down. Both the load and supply were run to their limits and we 'proved' this is a viable supply for our purposes.

Here is an ebay search in the US that has similar inexpensive loads -

https://www.ebay.com/sch/sis.html?_id=172461371107&_nkw=Constant+Current+Electronic+Load+9.99A+60W+1-30V+Battery+Capacity+Tester%23S

and Amazon -

https://www.amazon.com/s?k=DC+Electronic+Load+Tester&ref=nb_sb_noss

They can be inexpensive and the fancy high power ones can be quite expensive ... find one that suits your needs.

With another voltmeter you can check the drop in your cables. Set up the load to draw what you think is appropriate, note the voltage at the load. Then using the voltmeter measure the voltage at the power supply. Note the difference between the voltage at the supply and the voltage at the load. Viola, there's your drop. Is it good enough to run your board?

Most 5v boards complain at 5v. They want above 5v, like 5.1.

This is only a basic test, you can go a lot further but this will definitely prove your supply or fail it. If you really get into testing get some inline current measuring tools so you can see what your board is actually drawing. Most voltmeters have inline current meters and many are quite accurate and detailed. Watching the current draw on your board as you perform various operations can tell you if you have a hardware problem; if it draws more than the manufacturer specifies then there may well be a hardware issue.

I hope this motivates someone to go farther with testing and proving their power.

Orange Pi One OTG port

Thu, 21 Oct 2021 02:34:12 +0000

I wanted to setup wifi using the on my Orange PI one. I have a rtlsdr in the regular port and want to mount the Orange Pi in a different room without a wired connection. Is it possible to use the usb otg port for that? I can plug in usb storage drives and they are picked up but not the wifi or rtlsdr are picked up when I plug them in.

Unable to boot 'focal' or 'buster' images on SOPine Clusterboard

Mon, 22 Mar 2021 10:28:05 +0000

I am trying to boot armbian on the Pine64 clusterboard but I cannot get past a 'Starting kernel...' message on the serial console.

I am not able to boot either of the images from https://www.armbian.com/sopine-a64/#kernels-archive-all

I'm not sure if the serial is just turning off or the system is freezing. It does not connect to my router.

Here is the serial output for for 'focal' image.

Spoiler


U-Boot SPL 2020.10-armbian (Mar 08 2021 - 19:07:13 +0100)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.4(debug):2c62b00-dirty
NOTICE:  BL31: Built : 19:07:11, Mar  8 2021
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x4094bd8, model: SoPine with baseboard
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP803 on RSB
INFO:    PMIC: dcdc1 voltage: 3.300V
INFO:    PMIC: dcdc5 voltage: 1.200V
INFO:    PMIC: dcdc6 voltage: 1.100V
INFO:    PMIC: dldo1 voltage: 3.300V
INFO:    PMIC: dldo2 voltage: 3.300V
INFO:    PMIC: dldo4 voltage: 3.300V
INFO:    PMIC: fldo1 voltage: 1.200V
INFO:    PMIC: Enabling DC SW
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Mar 08 2021 - 19:07:13 +0100) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
230454 bytes read in 13 ms (16.9 MiB/s)
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
=>                      
=> 
=> 
=> 
=> 
=> 
=> 
=> 
=> 
U-Boot SPL 2020.10-armbian (Mar 08 2021 - 19:07:13 +0100)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.4(debug):2c62b00-dirty
NOTICE:  BL31: Built : 19:07:11, Mar  8 2021
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x4094bd8, model: SoPine with baseboard
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP803 on RSB
INFO:    PMIC: dcdc1 voltage: 3.300V
INFO:    PMIC: dcdc5 voltage: 1.200V
INFO:    PMIC: dcdc6 voltage: 1.100V
INFO:    PMIC: dldo1 voltage: 3.300V
INFO:    PMIC: dldo2 voltage: 3.300V
INFO:    PMIC: dldo4 voltage: 3.300V
INFO:    PMIC: fldo1 voltage: 1.200V
INFO:    PMIC: Enabling DC SW
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Mar 08 2021 - 19:07:13 +0100) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In:    serial
Out:   serial
Err:   serial
Net:   phy interface7
eth0: ethernet@1c30000
230454 bytes read in 13 ms (16.9 MiB/s)
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3202 bytes read in 3 ms (1 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
155 bytes read in 2 ms (75.2 KiB/s)
41034 bytes read in 5 ms (7.8 MiB/s)
3821 bytes read in 4 ms (932.6 KiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 45000000
11754630 bytes read in 564 ms (19.9 MiB/s)
21792776 bytes read in 1041 ms (20 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41730000
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    11754566 Bytes = 11.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
EHCI failed to shut down host controller.
   Loading Ramdisk to 494ca000, end 49fffc46 ... OK
   Loading Device Tree to 0000000049457000, end 00000000494c9fff ... OK

Starting kernel ...

Can anyone provide any advice for diagnosing/fixing this?

Tinker Board, latest updates result in kernel backtrace

Sat, 19 Jun 2021 17:56:05 +0000

I just ran apt update && apt upgrade on my Tinkerboard S, now it boots to a backtrace and I can't connect to it either.

Might a recent update have problems?

I have attached a screenshot of the backtrace.

NanoPi Air Bluetooth dont work

Wed, 16 Jun 2021 09:17:36 +0000

Armbianmonitor

http://ix.io/3q6H

Hello!

I Have this board, y want to use hcitool

If i use

hcitool dev

it response

Devices:

If i try to use scan

hcitool scan

Device is not available: No such device

Any idea?

Thanks!

orange pi mini 2 unable to get past uboot

Thu, 20 May 2021 22:14:11 +0000

i have orange pi mini 2 board that fails to go past uboot. i used buster and focal images from here. here is the uboot snippet:

U-Boot SPL 2021.04-armbian (May 06 2021 - 18:16:10 +0000)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2021.04-armbian (May 06 2021 - 18:16:10 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi 2
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... Card did not respond to voltage select! : -110
In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1b000:

nothing happens after this. i have tried with different sd cards with same results. so i have a few quesions: is the board damaged? or i have used the wrong image or is there some wrong configurations as the image and boards aren't exactly identical.

Orange Pi3: booting stucks on "login" step

Fri, 30 Apr 2021 22:16:05 +0000

Hello, problem is next: my Orange Pi 3 now can't get IP address from my router. To solve it, I've connected via USB-TTL and on step "login:" it totally stucks and doesn't response for keyboard.

What variants do I have, except reinstall OS? :)

U-Boot SPL 2020.10-armbian (Feb 04 2021 - 00:24:13 +0100)
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.2(debug):a04808c-dirty
NOTICE:  BL31: Built : 00:24:06, Feb  4 2021
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc07e188, model: OrangePi 3
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
NOTICE:  PMIC: AXP805 detected
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 04 2021 - 00:24:13 +0100) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from FAT... Unable to use mmc 1:1... In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   No ethernet found.
starting USB...
No working controllers found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3173 bytes read in 2 ms (1.5 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
203 bytes read in 1 ms (198.2 KiB/s)
MMC: no card present
35737 bytes read in 6 ms (5.7 MiB/s)
4191 bytes read in 3 ms (1.3 MiB/s)
Applying kernel provided DT fixup script (sun50i-h6-fixup.scr)
## Executing script at 45000000
10050849 bytes read in 1007 ms (9.5 MiB/s)
21792776 bytes read in 2181 ms (9.5 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41730000
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10050785 Bytes = 9.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 4966a000, end 49fffce1 ... OK
   Loading Device Tree to 00000000495f8000, end 0000000049669fff ... OK

Starting kernel ...


Armbian 21.02.3 Buster ttyS0

orangepi3 login:

OrangePi PC not booting up

Mon, 05 Apr 2021 00:07:31 +0000

Hello everyone

Just bought a bunch of Orange Pi PC and I'm having issues making them boot properly.
The behaviour of the board changes everytime I power it on, sometimes it just shows a black screen, others it stays frozen in the "Starting version 245" (I've waited more than 10 minutes in that screen to see if something happens but nothing) if i get lucky sometimes I get a kernel panic (first image attached), and also one time I got an "unable to handle kernel paging request" (second image attached). So, in short, after working on this for at least 4h I did not get one succesful boot and I don't know what else to try.
Also don't know if it's relevant but I never saw the red led of the board on, just the green one.

- I'm powering the board using a USB to DC cable (the barrel plug), connected to an Anker PowerPort 10, rated to 5V 2.4A per port (have a friend using the same setup with the same boards and no issue on his side) but also tried different smartphone chargers that I had laying arround, one of them rated for 5V 4A, to no avail.
- Loaded also multiple images downloaded from this website for the Orange Pi PC, the two current versions of Armbian Buster and Focal and also a old version on Buster, burned them using Etcher.
- I'm using a 16Gb MicroSD SanDisk Ultra C10 A1, tried different ones since I have a bunch, also executed H2testw with no issues
- And as a last resort I did try Win32DiskImager and another card reader in a totally different computer just out of desesperation and to rule out anything that came to mind.

I'm starting to think that maybe it's a power issue, I had a look at the powering via MicroUSB post but I don't know how to diagnose the voltage that I'm getting since I only have a multimeter and this is my first time working on boards.

Any help would be much appreciated since I don't know what else to try.

Thanks

NanoPi NEO2 Black fresh install fails to boot properly

Sat, 27 Feb 2021 10:02:22 +0000

I had a NanoPi NEO2 Black lying around with an old (but working) Armbian image on which I decided to wipe and re-flash. As per usual I check my DHCP server to see which IP it is assigned, but it never showed up. At this point I hooked up one of my UART adapters to it after re-flashing the image (Armbian_21.02.1_Nanopineo2black_buster_current_5.10.12.img):

INFO:    Configuring SPC Controller
NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 03 2021 - 23:47:50 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO Core 2
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
230454 bytes read in 26 ms (8.5 MiB/s)
starting USB...
Bus usb@1c1b000: USB EHCI 1.00
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3173 bytes read in 4 ms (774.4 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
183 bytes read in 3 ms (59.6 KiB/s)
31278 bytes read in 10 ms (3 MiB/s)
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
4191 bytes read in 7 ms (584 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 45000000
10046824 bytes read in 488 ms (19.6 MiB/s)
21700616 bytes read in 1038 ms (19.9 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41710000
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10046760 Bytes = 9.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 4966b000, end 49fffd28 ... OK
   Loading Device Tree to 00000000495fb000, end 000000004966afff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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 ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 43321/105664 files, 361761/421888 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 21.02.1 Buster!

[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on Journal Audit Socket.
         Starting Load Kernel Modules...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Reached target Swap.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Starting Nameserver information manager...
         Mounting Huge Pages File System...
         Starting Create list of re&odes for the current kernel...
         Starting Restore / save the current clock...
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
         Mounting POSIX Message Queue File System...
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Set up automount Arbitrary&s File System Automount Point.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on udev Control Socket.
         Mounting Kernel Debug File System...
[  OK  ] Started Forward Password R&uests to Wall Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
         Starting Set the console keyboard layout...
[  OK  ] Reached target Remote File Systems.
         Starting udev Coldplug all Devices...
[  OK  ] Started Load Kernel Modules.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Create list of req& nodes for the current kernel.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Started Nameserver information manager.
         Starting Create System Users...
         Starting Load/Save Random Seed...
         Starting Apply Kernel Variables...
         Mounting Kernel Configuration File System...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started udev Coldplug all Devices.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Started Helper to synchronize boot up for ifupdown.
[  OK  ] Started Create System Users.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Mounted /tmp.
[  OK  ] Reached target Local File Systems.
         Starting Armbian ZRAM config...
         Starting Set console font and keymap...
         Starting Mark the need to relabel after reboot...
         Starting Raise network interfaces...
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Mark the need to relabel after reboot.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Found device /dev/ttyGS0.
[  OK  ] Found device /dev/ttyS1.

And then it just freezes. I reflashed it onto a new SD Card (SanDisk Ultra 16GB A1) and booted with the same behaviour as above:

NOTICE:  PMIC: Assuming H5 reference regulator design
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
NOTICE:  PSCI: System suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2020.10-armbian (Feb 03 2021 - 23:47:50 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: FriendlyARM NanoPi NEO Core 2
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Card did not respond to voltage select!
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
230454 bytes read in 13 ms (16.9 MiB/s)
starting USB...
Bus usb@1c1b000: USB EHCI 1.00
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3173 bytes read in 3 ms (1 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
183 bytes read in 1 ms (178.7 KiB/s)
31278 bytes read in 6 ms (5 MiB/s)
504 bytes read in 4 ms (123 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo
504 bytes read in 4 ms (123 KiB/s)
Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo
4191 bytes read in 4 ms (1022.5 KiB/s)
Applying kernel provided DT fixup script (sun50i-h5-fixup.scr)
## Executing script at 45000000
10046824 bytes read in 483 ms (19.8 MiB/s)
21700616 bytes read in 1035 ms (20 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41710000
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10046760 Bytes = 9.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 4966b000, end 49fffd28 ... OK
   Loading Device Tree to 00000000495fb000, end 000000004966afff ... OK

Starting kernel ...

Loading, please wait...
Starting version 241
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 ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
/dev/mmcblk0p1: clean, 43327/105664 files, 361765/421888 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 21.02.1 Buster!

[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Set up automount Arbitrary&s File System Automount Point.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket.
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Starting Restore / save the current clock...
[  OK  ] Reached target Remote File Systems.
         Starting Set the console keyboard layout...
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Listening on udev Kernel Socket.
         Starting udev Coldplug all Devices...
         Starting Nameserver information manager...
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
[  OK  ] Reached target Swap.
         Mounting Huge Pages File System...
[  OK  ] Started Forward Password R&uests to Wall Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
         Starting Create list of re&odes for the current kernel...
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Create list of req& nodes for the current kernel.
[  OK  ] Started Set the console keyboard layout.
[  OK  ] Started Nameserver information manager.
         Starting Create System Users...
         Starting Load/Save Random Seed...
         Mounting Kernel Configuration File System...
         Starting Apply Kernel Variables...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Apply Kernel Variables.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Started Create System Users.
[  OK  ] Started Helper to synchronize boot up for ifupdown.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Create Static Device Nodes in /dev.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Mounted /tmp.
[  OK  ] Reached target Local File Systems.
         Starting Set console font and keymap...
         Starting Mark the need to relabel after reboot...
         Starting Armbian ZRAM config...
         Starting Raise network interfaces...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Mark the need to relabel after reboot.
[  OK  ] Found device /dev/ttyGS0.
[  OK  ] Found device /dev/ttyS1.

I'd be grateful for any help.

Powering SBC from in-wall charger?

Thu, 21 Jan 2021 01:59:31 +0000

I bought a set of Leviton T5632 in-wall USB chargers before I even thought of tinkering with SBCs. The spec sheet says it delivers 3.6A@5V, so I thought it should be enough to power a board and a couple of USB disks.

Has anyone used a similar device to power an SBC?

I still don't have my device and I don't have a USB power meter at hand, when I have them I'll update this.

I bought a set of 3 for about $25 off eBay, so price is decent.

Here are some pics of the insides in case anyone is interested.

Armbian Buster doesn't boot on Cubox-!

Sat, 02 Jan 2021 09:51:48 +0000

Just tried to load Armbian Buster on a Cubox-i.

Couldn't see it in the network, so tried HDMI. I saw an Armbian logo and a line: uboot 2018-1...

Booting the Solid-Run Debian image, works fine.

What should I do to get Armbian working?

[Nanopi R4S]: Checksum failed while flashing with Etcher (Armbian_20.11.5_Nanopi-r4s_buster_current_5.9.16)

Sat, 02 Jan 2021 10:37:03 +0000

I tried to flash the above image with Etcher, but the verification failed with error :

"Source and Destination checksums do not match:
defc7b3b82291e03!==7c2644f965e6fc1f"

RockPi4b on focal 20.11 stuck on boot at bluetooth

Mon, 28 Dec 2020 20:34:29 +0000

I tested this on multiple v1.3 and 1.4 Boards

In the boot sequence the message appears.

`A start job is running for Bluetooth Rockpi (3min 1s / no limit)`

The boot process continue for other tasks but never completes, even after waiting for hours.
All boards boot fine with 20.08

Orange Pi 3 (H6) ethernet not working on 5.9 and above

Fri, 11 Dec 2020 17:04:11 +0000

Red light on boot and Can't detect via putty serial. But, OPi3 works ok on ubuntu 16.8(green light).

Any sollution????

Problem burning 256GB SD

Sat, 19 Dec 2020 15:24:03 +0000

I can't burn a 256GB SD, neither with Etcher nor with dd. With an 8Gb Sd everything works. Thanks

20.11 - Orange Pi Zero not booting

Wed, 25 Nov 2020 22:12:22 +0000

Hi,

Hopefully I have posted appropriately, I am completely new to Armbian and orange PI so hopefully this fault is because of my lack of experience.

My problem I cannot get my orange pi to boot.. I have tried both supported Armbian Focal and Armbian Buster. They both appear to stop at the same place of boot (wondering if its actually a hardware fault?). Hardware is a Orange Pi Zero H2 (H2 Printed on top of CPU yet CPU reports itself as H3 when booting) the outputs captured via the serial port, the SD is a SANDisk A1 32GB card, the board is powered by a 2A USB wall supply and I also connected an ethernet cable directly to the router. Below is the captured output from focal build (Armbian_20.11_Orangepizero_focal_current_5.8.16.img) , The first boot results in a kernel panic and the second one stalls at the t "Update UTMP about System Runlevel Changes" I am note sure how to debug this as I have no opportunity to intervene etc, and not having an Orange PI that does boot, I have nothing to compare it too... Can anybody help? am I using the wrong build?- can anybody help? Have I bought a duff Orange? what am I doing wrong?

thanks all.

Spoiler


U-Boot SPL 2020.10-armbian (Nov 23 2020 - 18:53:11 +0100)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2020.10-armbian (Nov 23 2020 - 18:53:11 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Zero
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 4 ms (967.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
182 bytes read in 3 ms (58.6 KiB/s)
11503995 bytes read in 871 ms (12.6 MiB/s)
7793968 bytes read in 591 ms (12.6 MiB/s)
Found mainline kernel configuration
32515 bytes read in 11 ms (2.8 MiB/s)
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo
4185 bytes read in 7 ms (583 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11503931 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49507000, end 49fff93b ... OK
   Loading Device Tree to 49496000, end 49506fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Loading, please wait...
Starting version 245.4-4ubuntu3.3
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 ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.34
[/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: clean, 39833/69408 files, 243502/277504 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 20.11 Focal!

[  OK  ] Created slice system-modprobe.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[  OK  ] Set up automount Arbitrary…s File System Automount Point.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Slices.
[  OK  ] Reached target Swap.
[  OK  ] Reached target System Time Set.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Mounting Kernel Trace File System...
         Starting Restore / save the current clock...
         Starting Set the console keyboard layout...
         Starting Create list of st…odes for the current kernel...
[  OK  ] Started Nameserver information manager.
[  OK  ] Reached target Network (Pre).
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
         Starting udev Coldplug all Devices...
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Trace File System.
[  OK  ] Finished Restore / save the current clock.
[  OK  ] Finished Create list of st… nodes for the current kernel.
[  OK  ] Finished Remount Root and Kernel File Systems.
[  OK  ] Finished Load Kernel Modules.
         Mounting FUSE Control File System...
         Mounting Kernel Configuration File System...
         Starting Load/Save Random Seed...
         Starting Apply Kernel Variables...
         Starting Create System Users...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Finished Create System Users.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Finished Set the console keyboard layout.
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /tmp.
[  OK  ] Reached target Local File Systems.
         Starting Armbian ZRAM config...
         Starting Set console font and keymap...
         Starting Mark the need to relabel after reboot...
[  OK  ] Finished Set console font and keymap.
[  OK  ] Finished udev Coldplug all Devices.
[  OK  ] Finished Mark the need to relabel after reboot.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Finished Helper to synchronize boot up for ifupdown.
         Starting Raise network interfaces...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Found device /dev/ttyGS0.
[   10.982337] thermal thermal_zone0: binding zone cpu_thermal with cdev thermal                                                            -cpufreq-0 failed:-22
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Finished Raise network interfaces.
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Finished Armbian ZRAM config.
         Starting Armbian memory supported logging...
[  OK  ] Finished Armbian memory supported logging.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Finished Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Create Volatile Files and Directories.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
         Starting Network Name Resolution...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Finished Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Started resolvconf-pull-resolved.path.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Paths.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
         Starting Armbian hardware monitoring...
         Starting Armbian hardware optimization...
         Starting Armbian filesystem resize...
[  OK  ] Finished Armbian hardware monitoring.
[  OK  ] Finished Armbian hardware optimization.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Finished Armbian filesystem resize.
[  OK  ] Reached target Basic System.
[  OK  ] Started Armbian first run tasks.
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started Save initial kernel messages after boot.
         Starting Remove Stale Onli…t4 Metadata Check Snapshots...
         Starting LSB: Load kernel …d to enable cpufreq scaling...
         Starting Dispatcher daemon for systemd-networkd...
         Starting resolvconf-pull-resolved.service...
         Starting System Logging Service...
         Starting Resets System Activity Data Collector...
         Starting Login Service...
         Starting WPA supplicant...
[  OK  ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
[  OK  ] Finished Resets System Activity Data Collector.
[  OK  ] Finished resolvconf-pull-resolved.service.
[  OK  ] Started WPA supplicant.
[  OK  ] Started System Logging Service.
[  OK  ] Started Login Service.
[  OK  ] Started LSB: Load kernel m…ded to enable cpufreq scaling.
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
         Starting chrony, an NTP client/server...
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting /etc/rc.local Compatibility...
         Starting OpenBSD Secure Shell server...
         Starting Permit User Sessions...
[  OK  ] Started Unattended Upgrades Shutdown.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Serial Getty on ttyGS0.
[  OK  ] Started Serial Getty on ttyS0.
         Starting Set console scheme...
         Starting Hostname Service...
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started chrony, an NTP client/server.
[  OK  ] Finished Set console scheme.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Started Periodic ext4 Onli…ata Check for All Filesystems.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Started Message of the Day.
[  OK  ] Reached target Timers.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Hostname Service.
[  OK  ] Started Dispatcher daemon for systemd-networkd.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Finished Update UTMP about System Runlevel Changes.
[   44.853428] 8<--- cut here ---
[   44.856532] Unable to handle kernel paging request at virtual address 347dec0                                                            1
[   44.863800] pgd = 4354a836
[   44.866505] [347dec01] *pgd=00000000
[   44.870144] Internal error: Oops: 5 [#1] SMP THUMB2
[   44.875019] Modules linked in: xradio_wlan mac80211 sun4i_gpadc_iio industria                                                            lio cfg80211 sun8i_thermal rfkill libarc4 sunxi_cedrus(C) sun8i_ce crypto_engine                                                             sun8i_di cpufreq_dt uio_pdrv_genirq uio zram sch_fq_codel usb_f_acm u_serial g_                                                            serial libcomposite ip_tables x_tables autofs4 pwrseq_simple sunxi phy_generic
[   44.902829] CPU: 1 PID: 1148 Comm: iozone Tainted: G         C        5.8.16-                                                            sunxi #20.08.14
[   44.911251] Hardware name: Allwinner sun8i Family
[   44.915964] PC is at kmem_cache_alloc+0x84/0x1e4
[   44.920576] LR is at 0xcc0
[   44.923279] pc : []    lr : [<00000cc0>]    psr: a0070033
[   44.929536] sp : d2ab3eb8  ip : 000131d1  fp : 347dec01
[   44.934753] r10: 00000142  r9 : c0f056c4  r8 : c0277a1b
[   44.939969] r7 : d70c5700  r6 : 00000cc0  r5 : d6804000  r4 : d70c5700
[   44.946487] r3 : 5dfdac01  r2 : eff2f8df  r1 : 1f0d7000  r0 : d2ab3eb8
[   44.953006] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment no                                                            ne
[   44.960304] Control: 50c5387d  Table: 5203806a  DAC: 00000051
[   44.966044] Process iozone (pid: 1148, stack limit = 0xbafee82d)
[   44.972043] Stack: (0xd2ab3eb8 to 0xd2ab4000)
[   44.976395] 3ea0:                                                       00000                                                            000 00000000
[   44.984563] 3ec0: d1710220 c026c4f9 c0bd4e68 00000000 006ca404 00000000 00000                                                            000 d2ab3f50
[   44.992731] 3ee0: c0f056c4 00000142 00596438 c0277a1b 00000000 00000000 00000                                                            000 00000000
[   45.000899] 3f00: d2ab3f50 ffffff9c 00000142 c0268083 d54f9f70 d2ab2000 00030                                                            000 ffff0000
[   45.009067] 3f20: 00000004 00000100 00000001 c0f04fc8 c0f04fcc d2ab3f60 d2ab3                                                            f78 00030000
[   45.017235] 3f40: 00000000 00000000 00000000 c026903f 00030000 00000000 00000                                                            000 00000000
[   45.025402] 3f60: 00000000 00000000 00030000 00000000 00000000 00000000 00000                                                            000 00000000
[   45.033571] 3f80: 00000006 c0f04fc8 d450ba80 00001000 b6fae5f0 00860a60 00000                                                            142 c0100284
[   45.041739] 3fa0: d2ab2000 c0100061 00001000 b6fae5f0 ffffff9c 006ca404 00030                                                            000 00000000
[   45.049907] 3fc0: 00001000 b6fae5f0 00860a60 00000142 be97f0b0 00597bf0 004dc                                                            9f8 00596438
[   45.058076] 3fe0: 00000142 be97ef70 b6f6fa5d b6f71416 20070030 ffffff9c 00000                                                            000 00000000
[   45.066263] [] (kmem_cache_alloc) from [] (getname_flags+                                                            0x3b/0x130)
[   45.074354] [] (getname_flags) from [] (do_sys_openat2+0x                                                            13b/0x220)
[   45.082355] [] (do_sys_openat2) from [] (do_sys_open+0x6b                                                            /0x9c)
[   45.090008] [] (do_sys_open) from [] (ret_fast_syscall+0x                                                            1/0x62)
[   45.097738] Exception stack(0xd2ab3fa8 to 0xd2ab3ff0)
[   45.102785] 3fa0:                   00001000 b6fae5f0 ffffff9c 006ca404 00030                                                            000 00000000
[   45.110953] 3fc0: 00001000 b6fae5f0 00860a60 00000142 be97f0b0 00597bf0 004dc                                                            9f8 00596438
[   45.119119] 3fe0: 00000142 be97ef70 b6f6fa5d b6f71416
[   45.124169] Code: f8d4 20d0 eb05 0b03 (f855) a003
[   45.129017] ---[ end trace 3d01fddb7caaea25 ]---
[   45.129707] 8<--- cut here ---
[   45.136797] Unable to handle kernel paging request at virtual address 27df6c0                                                            1
[   45.136888] 8<--- cut here ---
[   45.144035] pgd = 77b9d853
[   45.144039] [27df6c01] *pgd=00000000
[   45.147104] Unable to handle kernel paging request at virtual address 84021ac                                                            6
[   45.147109] pgd = 88933591
[   45.149814] Internal error: Oops: 5 [#2] SMP THUMB2
[   45.153387] [84021ac6] *pgd=00000000
[   45.160580] Modules linked in: xradio_wlan mac80211 sun4i_gpadc_iio industria                                                            lio cfg80211 sun8i_thermal rfkill libarc4 sunxi_cedrus(C) sun8i_ce crypto_engine                                                             sun8i_di cpufreq_dt uio_pdrv_genirq uio zram sch_fq_codel usb_f_acm u_serial g_                                                            serial libcomposite ip_tables x_tables autofs4 pwrseq_simple sunxi phy_generic
[   45.199478] CPU: 0 PID: 1133 Comm: rs:main Q:Reg Tainted: G      D  C                                                                    5.8.16-sunxi #20.08.14
[   45.208506] Hardware name: Allwinner sun8i Family
[   45.213214] PC is at kmem_cache_alloc+0x84/0x1e4
[   45.217826] LR is at 0xcc0
[   45.220529] pc : []    lr : [<00000cc0>]    psr: a0010033
[   45.226785] sp : d2177ef8  ip : 000116fd  fp : 27df6c01
[   45.232000] r10: fffff000  r9 : c0f056c4  r8 : c0277a1b
[   45.237217] r7 : d70c5700  r6 : 00000cc0  r5 : c9e1c000  r4 : d70c5700
[   45.243735] r3 : 5dfdac01  r2 : eff2f8df  r1 : 1f0c3000  r0 : d2177ef8
[   45.250252] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment no                                                            ne
[   45.257550] Control: 50c5387d  Table: 5200006a  DAC: 00000051
[   45.263287] Process rs:main Q:Reg (pid: 1133, stack limit = 0x237a0996)
[   45.269892] Stack: (0xd2177ef8 to 0xd2178000)
[   45.274243] 7ee0:                                                       00000                                                            000 c025457b
[   45.282411] 7f00: 04042000 00000cc0 ce6f2bf5 00000001 b6e088dc 00000001 00000                                                            000 00000000
[   45.290580] 7f20: c0f056c4 fffff000 00502f44 c0277a1b 00000001 ffffff9c d2177                                                            f74 b6e088dc
[   45.298748] 7f40: 00000000 d2176000 fffff000 c0278239 00000001 00000000 fffff                                                            f9c c0268697
[   45.306916] 7f60: 00000000 00000000 00000000 d28c7880 d206ef03 c026ba17 00009                                                            855 c0f04fc8
[   45.315084] 7f80: d2177fb0 b6e088dc b6e1dc00 00044d92 00000021 c0100284 d2176                                                            000 00000021
[   45.323252] 7fa0: 00502f44 c0100061 b6e088dc b6e1dc00 b6e088dc 00000000 00000                                                            000 7261762f
[   45.331421] 7fc0: b6e088dc b6e1dc00 00044d92 00000021 00073570 00ee3d18 b61fe                                                            6fc 00502f44
[   45.339589] 7fe0: 00000021 b61fe1fc b6db76df b6d3dbe6 60010030 b6e088dc 00000                                                            000 00000000
[   45.347768] [] (kmem_cache_alloc) from [] (getname_flags+                                                            0x3b/0x130)
[   45.355853] [] (getname_flags) from [] (user_path_at_empt                                                            y+0x19/0x2c)
[   45.364026] [] (user_path_at_empty) from [] (do_faccessat                                                            +0x6f/0x1d8)
[   45.372188] [] (do_faccessat) from [] (ret_fast_syscall+0                                                            x1/0x62)
[   45.380005] Exception stack(0xd2177fa8 to 0xd2177ff0)
[   45.385052] 7fa0:                   b6e088dc b6e1dc00 b6e088dc 00000000 00000                                                            000 7261762f
[   45.393221] 7fc0: b6e088dc b6e1dc00 00044d92 00000021 00073570 00ee3d18 b61fe                                                            6fc 00502f44
[   45.401386] 7fe0: 00000021 b61fe1fc b6db76df b6d3dbe6
[   45.406434] Code: f8d4 20d0 eb05 0b03 (f855) a003
[   45.411222] Internal error: Oops: 5 [#3] SMP THUMB2
[   45.411284] ---[ end trace 3d01fddb7caaea26 ]---
[   45.416092] Modules linked in: xradio_wlan mac80211 sun4i_gpadc_iio industria                                                            lio cfg80211 sun8i_thermal rfkill libarc4 sunxi_cedrus(C) sun8i_ce crypto_engine                                                             sun8i_di cpufreq_dt uio_pdrv_genirq uio zram sch_fq_codel usb_f_acm u_serial g_                                                            serial libcomposite ip_tables x_tables autofs4 pwrseq_simple sunxi phy_generic
[   45.448465] CPU: 1 PID: 1148 Comm: iozone Tainted: G      D  C        5.8.16-                                                            sunxi #20.08.14
[   45.456888] Hardware name: Allwinner sun8i Family
[   45.461594] PC is at lock_page_memcg+0x1c/0x60
[   45.466034] LR is at page_remove_rmap+0x11/0x178
[   45.470644] pc : []    lr : []    psr: 40070133
[   45.476899] sp : d2ab3c18  ip : 00000000  fp : d2ab3d38
[   45.482115] r10: b6f89000  r9 : d2ab2000  r8 : 5775d59f
[   45.487332] r7 : 00000000  r6 : d7acc914  r5 : 00000000  r4 : 84021806
[   45.493848] r3 : 75ad3038  r2 : 00000000  r1 : 00000000  r0 : d7acc914
[   45.500365] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment no                                                            ne
[   45.507662] Control: 50c5387d  Table: 5203806a  DAC: 00000051
[   45.513402] Process iozone (pid: 1148, stack limit = 0xbafee82d)
[   45.519400] Stack: (0xd2ab3c18 to 0xd2ab4000)
[   45.523752] 3c00:                                                       d7acc                                                            914 00000000
[   45.531920] 3c20: d2a0d628 c023a7a9 fffffffc d7acc914 b6f8a000 c023110d b6f9f                                                            000 d7a1e9d4
[   45.540088] 3c40: 00000000 d5fe2c00 c1031700 c0f08e04 d298ec00 d2a0d618 b6f86                                                            000 00000000
[   45.548257] 3c60: c100247c d203adc0 b6f9f000 b6f9efff c0e9663c c0212c4b c0f04                                                            fc8 d794c3f8
[   45.556424] 3c80: 00000006 dff6d008 d2ab3cbc c0212d8d c0fd71c0 00000006 dff6d                                                            008 c0212c4b
[   45.564592] 3ca0: c0a16aac 00000001 d794c3f8 d23c9e00 d794c3fc 00000000 00000                                                            001 d2ab3cbc
[   45.572760] 3cc0: d2ab3cbc c0f04fc8 00000000 fffffffc 00000000 00000000 00000                                                            000 c0f04fc8
[   45.580928] 3ce0: 00000000 d298ec00 ffffffff b6f86000 d2ab3d38 00000000 00000                                                            000 d54f9b00
[   45.589096] 3d00: ffffe000 c023157d 00000000 d54f9b00 ffffe000 d298e4e0 00000                                                            000 d5fe2c00
[   45.597264] 3d20: 00000000 ffffe000 d5fe2c40 c02368f1 1f0d7000 1f0d7000 d5fe2                                                            c00 00487000
[   45.605432] 3d40: ffffffff 00000009 00000005 cd09d000 cd0a2000 00000008 00000                                                            008 d79d2798
[   45.613600] 3d60: d79d2774 d79d2750 d79d272c d79d4dfc d79d4e20 d79d4e44 d79d4                                                            e68 c0f04fc8
[   45.621768] 3d80: d5fe2c00 d5fe2c00 ffffe000 c0118773 00000000 d54f9b00 d5fe2                                                            c00 c011fc71
[   45.629936] 3da0: 0000000b c10023e0 d2ab2000 c0f04fc8 bf000000 c0f0a894 ffffe                                                            000 c0109ce7
[   45.638104] 3dc0: d2ab2210 0000000b d5fe2c40 347dec01 d2ab3e68 00000005 d5fe2                                                            c00 d5fe2c00
[   45.646272] 3de0: d5fe2c40 00000000 00000234 c01108ed d54f9b00 c0110b27 00000                                                            000 c02ce581
[   45.654441] 3e00: d2ab2000 c04f7e4d d53bc988 00010000 00000000 c0151de5 d5631                                                            a80 00000005
[   45.662609] 3e20: c0f0b0d8 347dec01 d2ab3e68 c0f0b128 d2ab2000 00000142 347de                                                            c01 c0110c3d
[   45.670777] 3e40: 00001000 c0282a6f 00000010 c0a1e220 c0254a04 a0070033 fffff                                                            fff d2ab3e9c
[   45.678946] 3e60: c0277a1b c0100ad3 d2ab3eb8 1f0d7000 eff2f8df 5dfdac01 d70c5                                                            700 d6804000
[   45.687114] 3e80: 00000cc0 d70c5700 c0277a1b c0f056c4 00000142 347dec01 00013                                                            1d1 d2ab3eb8
[   45.695282] 3ea0: 00000cc0 c0254a04 a0070033 ffffffff 00000051 bf000000 00000                                                            000 00000000
[   45.703450] 3ec0: d1710220 c026c4f9 c0bd4e68 00000000 006ca404 00000000 00000                                                            000 d2ab3f50
[   45.711618] 3ee0: c0f056c4 00000142 00596438 c0277a1b 00000000 00000000 00000                                                            000 00000000
[   45.719786] 3f00: d2ab3f50 ffffff9c 00000142 c0268083 d54f9f70 d2ab2000 00030                                                            000 ffff0000
[   45.727954] 3f20: 00000004 00000100 00000001 c0f04fc8 c0f04fcc d2ab3f60 d2ab3                                                            f78 00030000
[   45.736122] 3f40: 00000000 00000000 00000000 c026903f 00030000 00000000 00000                                                            000 00000000
[   45.744289] 3f60: 00000000 00000000 00030000 00000000 00000000 00000000 00000                                                            000 00000000
[   45.752458] 3f80: 00000006 c0f04fc8 d450ba80 00001000 b6fae5f0 00860a60 00000                                                            142 c0100284
[   45.760626] 3fa0: d2ab2000 c0100061 00001000 b6fae5f0 ffffff9c 006ca404 00030                                                            000 00000000
[   45.768794] 3fc0: 00001000 b6fae5f0 00860a60 00000142 be97f0b0 00597bf0 004dc                                                            9f8 00596438
[   45.776962] 3fe0: 00000142 be97ef70 b6f6fa5d b6f71416 20070030 ffffff9c 00000                                                            000 00000000
[   45.785136] [] (lock_page_memcg) from [] (page_remove_rma                                                            p+0x11/0x178)
[   45.793395] [] (page_remove_rmap) from [] (unmap_page_ran                                                            ge+0x291/0x5f4)
[   45.801827] [] (unmap_page_range) from [] (unmap_vmas+0x2                                                            5/0x3c)
[   45.809564] [] (unmap_vmas) from [] (exit_mmap+0x89/0x104                                                            )
[   45.816784] [] (exit_mmap) from [] (mmput+0x43/0xd8)
[   45.823482] [] (mmput) from [] (do_exit+0x2c5/0x870)
[   45.830179] [] (do_exit) from [] (die+0x267/0x27c)
[   45.836704] [] (die) from [] (__do_kernel_fault.part.0+0x                                                            69/0x74)
[   45.844527] [] (__do_kernel_fault.part.0) from [] (do_pag                                                            e_fault+0x22f/0x230)
[   45.853390] [] (do_page_fault) from [] (do_DataAbort+0x35                                                            /0x9c)
[   45.861039] [] (do_DataAbort) from [] (__dabt_svc+0x53/0x                                                            80)
[   45.868422] Exception stack(0xd2ab3e68 to 0xd2ab3eb0)
[   45.873469] 3e60:                   d2ab3eb8 1f0d7000 eff2f8df 5dfdac01 d70c5                                                            700 d6804000
[   45.881638] 3e80: 00000cc0 d70c5700 c0277a1b c0f056c4 00000142 347dec01 00013                                                            1d1 d2ab3eb8
[   45.889803] 3ea0: 00000cc0 c0254a04 a0070033 ffffffff
[   45.894857] [] (__dabt_svc) from [] (kmem_cache_alloc+0x8                                                            4/0x1e4)
[   45.902682] [] (kmem_cache_alloc) from [] (getname_flags+                                                            0x3b/0x130)
[   45.910769] [] (getname_flags) from [] (do_sys_openat2+0x                                                            13b/0x220)
[   45.918768] [] (do_sys_openat2) from [] (do_sys_open+0x6b                                                            /0x9c)
[   45.926419] [] (do_sys_open) from [] (ret_fast_syscall+0x                                                            1/0x62)
[   45.934149] Exception stack(0xd2ab3fa8 to 0xd2ab3ff0)
[   45.939196] 3fa0:                   00001000 b6fae5f0 ffffff9c 006ca404 00030                                                            000 00000000
[   45.947364] 3fc0: 00001000 b6fae5f0 00860a60 00000142 be97f0b0 00597bf0 004dc                                                            9f8 00596438
[   45.955530] 3fe0: 00000142 be97ef70 b6f6fa5d b6f71416
[   45.960577] Code: f3af 8000 6a34 b194 (f8d4) 32c0
[   45.965463] ---[ end trace 3d01fddb7caaea27 ]---
[   45.970097] Fixing recursive fault but reboot is needed!
[   54.187662] 8<--- cut here ---
[   54.190724] Unable to handle kernel paging request at virtual address f7defeb                                                            b
[   54.197939] pgd = 79774b7a
[   54.200641] [f7defebb] *pgd=00000000
[   54.204218] Internal error: Oops: 5 [#4] SMP THUMB2
[   54.209088] Modules linked in: xradio_wlan mac80211 sun4i_gpadc_iio industria                                                            lio cfg80211 sun8i_thermal rfkill libarc4 sunxi_cedrus(C) sun8i_ce crypto_engine                                                             sun8i_di cpufreq_dt uio_pdrv_genirq uio zram sch_fq_codel usb_f_acm u_serial g_                                                            serial libcomposite ip_tables x_tables autofs4 pwrseq_simple sunxi phy_generic
[   54.236892] CPU: 1 PID: 1189 Comm: sleep Tainted: G      D  C        5.8.16-s                                                            unxi #20.08.14
[   54.245227] Hardware name: Allwinner sun8i Family
[   54.249931] PC is at page_remove_rmap+0x128/0x178
[   54.254629] LR is at page_remove_rmap+0x11/0x178
[   54.259238] pc : []    lr : []    psr: 400f0033
[   54.265494] sp : d2a59df0  ip : cd0af000  fp : d2a59f00
[   54.270710] r10: b6e5a000  r9 : d2a58000  r8 : 576d759f
[   54.275927] r7 : 00000000  r6 : d29c816c  r5 : 00000000  r4 : d7acb63c
[   54.282444] r3 : c0fd71c0  r2 : c7025800  r1 : 00000000  r0 : f7defe7f
[   54.288963] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment no                                                            ne
[   54.296260] Control: 50c5387d  Table: 5296c06a  DAC: 00000051
[   54.301997] Process sleep (pid: 1189, stack limit = 0x9990dc95)
[   54.307907] Stack: (0xd2a59df0 to 0xd2a5a000)
[   54.312260] 9de0:                                     ffffffd6 d7acb63c b6e5b                                                            000 c023110d
[   54.320428] 9e00: b6f19000 d7a1e020 00000000 cdc2ce00 c1031700 c0f08e04 cdc28                                                            240 d29c80c0
[   54.328596] 9e20: b6e30000 00000000 c100247c d296edc0 b6f19000 b6f18fff d2a59                                                            e50 00000000
[   54.336764] 9e40: d71964a0 c015148d 00000000 d2a59e50 00000000 00000000 00000                                                            000 d2a59e5c
[   54.344932] 9e60: d2a59e5c c0f04fc8 00000000 cdc74c00 d7196464 00000001 d7196                                                            4a0 d2a59ea4
[   54.353100] 9e80: 00000003 c07fede1 00000000 c028e7f9 d7196400 ffffffd6 00000                                                            000 00000000
[   54.361268] 9ea0: 00000000 c0f04fc8 d1776c88 cdc28240 ffffffff b6e30000 d2a59                                                            f00 00000000
[   54.369436] 9ec0: 00000000 000000f8 b6f2a000 c023157d 00000000 c0564e7f fffff                                                            fff cdc28d20
[   54.377604] 9ee0: 00000000 cdc2ce00 00000000 ffffe000 cdc2ce40 c02368f1 fffff                                                            fff c010933b
[   54.385772] 9f00: cdc2ce00 004f3000 ffffffff c0f04f89 00000001 cd0ae000 cd0ae                                                            000 00000008
[   54.393940] 9f20: 00000008 d79e5248 d7a049b8 d79e5098 d7a31b20 d79e4ccc d7998                                                            190 d799b9d0
[   54.402108] 9f40: d7993438 c0f04fc8 cdc2ce00 cdc2ce00 ffffe000 c0118773 00000                                                            000 d2a91440
[   54.410277] 9f60: cdc2ce00 c011fc71 b6e7b64c c0f04fc8 c0f0b2d8 c0f04fc8 00000                                                            000 000000f8
[   54.418445] 9f80: b6f2a000 c0120277 97080500 b6f2b438 b6f2b438 00000000 00000                                                            0f8 c01202df
[   54.426613] 9fa0: 97080500 c0100061 b6f2b438 b6f2b438 00000000 00000000 00000                                                            000 97080500
[   54.434781] 9fc0: b6f2b438 b6f2b438 00000000 000000f8 00000002 00000000 b6f2d                                                            628 b6f2a000
[   54.442948] 9fe0: 000000f8 bec1dc9c b6eaad19 b6e4abe6 600f0030 00000000 00000                                                            000 00000000
[   54.451126] [] (page_remove_rmap) from [] (unmap_page_ran                                                            ge+0x291/0x5f4)
[   54.459557] [] (unmap_page_range) from [] (unmap_vmas+0x2                                                            5/0x3c)
[   54.467295] [] (unmap_vmas) from [] (exit_mmap+0x89/0x104                                                            )
[   54.474514] [] (exit_mmap) from [] (mmput+0x43/0xd8)
[   54.481212] [] (mmput) from [] (do_exit+0x2c5/0x870)
[   54.487906] [] (do_exit) from [] (do_group_exit+0x2f/0x84                                                            )
[   54.495122] [] (do_group_exit) from [] (sys_exit_group+0x                                                            13/0x14)
[   54.502945] [] (sys_exit_group) from [] (ret_fast_syscall                                                            +0x1/0x62)
[   54.510935] Exception stack(0xd2a59fa8 to 0xd2a59ff0)
[   54.515982] 9fa0:                   b6f2b438 b6f2b438 00000000 00000000 00000                                                            000 97080500
[   54.524150] 9fc0: b6f2b438 b6f2b438 00000000 000000f8 00000002 00000000 b6f2d                                                            628 b6f2a000
[   54.532315] 9fe0: 000000f8 bec1dc9c b6eaad19 b6e4abe6
[   54.537364] Code: eb02 0281 f8d2 05cc (6bc2) 210f
[   54.542149] ---[ end trace 3d01fddb7caaea28 ]---
[   54.546758] Fixing recursive fault but reboot is needed!
▒
U-Boot SPL 2020.10-armbian (Nov 23 2020 - 18:53:11 +0100)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2020.10-armbian (Nov 23 2020 - 18:53:11 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Zero
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0, mmc@1c10000: 1
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
Bus usb@1c1c000: USB EHCI 1.00
Bus usb@1c1c400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3967 bytes read in 4 ms (967.8 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
231 bytes read in 2 ms (112.3 KiB/s)
11503995 bytes read in 876 ms (12.5 MiB/s)
7793968 bytes read in 594 ms (12.5 MiB/s)
Found mainline kernel configuration
32515 bytes read in 10 ms (3.1 MiB/s)
504 bytes read in 6 ms (82 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo
504 bytes read in 7 ms (70.3 KiB/s)
Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo
4185 bytes read in 7 ms (583 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 45000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    11503931 Bytes = 11 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49507000, end 49fff93b ... OK
   Loading Device Tree to 49496000, end 49506fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Loading, please wait...
Starting version 245.4-4ubuntu3.3
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 ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.34
[/usr/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
/dev/mmcblk0p1: clean, 39867/1820032 files, 354066/7712800 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Armbian 20.11 Focal!

[  OK  ] Created slice system-modprobe.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[  OK  ] Set up automount Arbitrary…s File System Automount Point.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Slices.
[  OK  ] Reached target Swap.
[  OK  ] Reached target System Time Set.
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Mounting Kernel Trace File System...
         Starting Restore / save the current clock...
         Starting Set the console keyboard layout...
         Starting Create list of st…odes for the current kernel...
[  OK  ] Started Nameserver information manager.
[  OK  ] Reached target Network (Pre).
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
         Starting udev Coldplug all Devices...
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Trace File System.
[  OK  ] Finished Restore / save the current clock.
[  OK  ] Finished Create list of st… nodes for the current kernel.
[  OK  ] Finished Load Kernel Modules.
[  OK  ] Finished Remount Root and Kernel File Systems.
         Mounting FUSE Control File System...
         Mounting Kernel Configuration File System...
         Starting Load/Save Random Seed...
         Starting Apply Kernel Variables...
         Starting Create System Users...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Finished Create System Users.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Finished Set the console keyboard layout.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /tmp.
[  OK  ] Reached target Local File Systems.
         Starting Armbian ZRAM config...
         Starting Set console font and keymap...
[  OK  ] Finished udev Coldplug all Devices.
         Starting Helper to synchronize boot up for ifupdown...
[  OK  ] Finished Set console font and keymap.
[  OK  ] Finished Helper to synchronize boot up for ifupdown.
         Starting Raise network interfaces...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Found device /dev/ttyGS0.
[   10.793027] thermal thermal_zone0: binding zone cpu_thermal with cdev thermal                                                            -cpufreq-0 failed:-22
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Raise network interfaces.
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Finished Armbian ZRAM config.
         Starting Armbian memory supported logging...
[  OK  ] Finished Armbian memory supported logging.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Finished Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Create Volatile Files and Directories.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
         Starting Network Name Resolution...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Finished Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Started resolvconf-pull-resolved.path.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Paths.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
         Starting Armbian hardware monitoring...
         Starting Armbian hardware optimization...
[  OK  ] Finished Armbian hardware monitoring.
[  OK  ] Finished Armbian hardware optimization.
[  OK  ] Reached target Basic System.
[  OK  ] Started Armbian first run tasks.
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started Save initial kernel messages after boot.
         Starting Remove Stale Onli…t4 Metadata Check Snapshots...
         Starting LSB: Load kernel …d to enable cpufreq scaling...
         Starting Dispatcher daemon for systemd-networkd...
         Starting System Logging Service...
         Starting Resets System Activity Data Collector...
         Starting Login Service...
         Starting WPA supplicant...
[  OK  ] Started Network Name Resolution.
[  OK  ] Finished Resets System Activity Data Collector.
[  OK  ] Reached target Host and Network Name Lookups.
         Starting resolvconf-pull-resolved.service...
[  OK  ] Started WPA supplicant.
[  OK  ] Started System Logging Service.
[  OK  ] Started Login Service.
[  OK  ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
[  OK  ] Started LSB: Load kernel m…ded to enable cpufreq scaling.
         Starting LSB: set CPUFreq kernel parameters...
[  OK  ] Finished resolvconf-pull-resolved.service.
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
         Starting chrony, an NTP client/server...
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting /etc/rc.local Compatibility...
         Starting OpenBSD Secure Shell server...
         Starting Permit User Sessions...
[  OK  ] Started Unattended Upgrades Shutdown.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Serial Getty on ttyGS0.
[  OK  ] Started Serial Getty on ttyS0.
         Starting Set console scheme...
         Starting Hostname Service...
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Finished Set console scheme.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started chrony, an NTP client/server.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Started Periodic ext4 Onli…ata Check for All Filesystems.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Daily man-db regeneration.
[  OK  ] Started Message of the Day.
[  OK  ] Reached target Timers.
[  OK  ] Started Hostname Service.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Dispatcher daemon for systemd-networkd.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Finished Update UTMP about System Runlevel Changes.

How to boot from SD card but leave rest of the system on NVMe drive?

Wed, 25 Nov 2020 14:51:19 +0000

Hi,

I have RockPro64 board and NVMe drive. This board doesn't support booting from NVMe so I need to have spearate boot partition. Here's my /etc/fstab file (on NVMe filesystem):

UUID=645f4a77-3e04-48da-ab41-0de8a81c1c13	/boot	ext4	defaults,noatime,nodiratime,commit=600,errors=remount-ro	0 1
UUID=c94a693a-74df-4e63-a466-2107a287f26a	/	ext4	defaults,noatime,nodiratime,commit=600,errors=remount-ro	0 1
tmpfs						/tmp	tmpfs	defaults,nosuid							0 0

In my opinion, it shouldn't work because if /etc/fstab is on a different partition, how can it be mounted? But I heard that initramfs stored on /boot will contain drivers and information necessary to mount the root filesystem. Once the root filesystem is mounted, /etc on it is accessible and fstab is processed.

So here is my SD card (UUID=645f4a77-3e04-48da-ab41-0de8a81c1c13) content (this what was previously in the /boot directory):

armbianEnv.txt                  boot.bmp  boot.scr                  dtb                    Image                         System.map-5.8.17-rockchip64  uInitrd-5.8.17-rockchip64
armbian_first_run.txt.template  boot.cmd  config-5.8.17-rockchip64  dtb-5.8.17-rockchip64  initrd.img-5.8.17-rockchip64  uInitrd                       vmlinuz-5.8.17-rockchip64

Here is my NVMe drive (UUID=c94a693a-74df-4e63-a466-2107a287f26a) content (this what was previously in / except /boot, in /boot /dev/mmcblk1p1 is mounted):

bin  boot  dev  etc  home  lib  media  mnt  opt  proc  root  run  sbin  selinux  srv  sys  tmp  usr  var

I was able to gather this information by booting from USB, then mounting /dev/nvm0n1 in /mnt and /dev/mmcblk1p1 in /mnt/boot, and finally running systemd-nspawn -b -D /mnt. USB is 4th in boot order (after SPI, eMMC and SD card) and when I plugged it into my board it booted successfully, so u-boot flashed to my SPI don't know that my SD card (that is before USB in boot order) contains bootable data. It was able to boot my system when this data was in /boot directory on this same card but can't do it now. Why?

Or maybe it's booting and I deduced it wrong...

EDIT:

It's booting but then freezes. Even fan isn't working.

n

Sat, 29 Jun 2019 12:43:20 +0000

Powering through micro USB

Sun, 23 Jul 2017 14:39:38 +0000

Since there are a lot of issiues with underpowered boards, this ‘White Paper’ should explain why it’s recommendet to think about the powering situation of your board (especially if it’s powered throught micro USB).

Basics:

It’s all about Ohm’s Law (eq. 1), your SBC needs a defined voltage (U) and current (I). So the only variable that we can influence is the resistance (R)!

The micro USB cable which powers our board acts as resistor between the output of the power source and the input of our board. For the moment, let’s assume our power source delivers a stable Voltage (what isn’t true, depends on current needed) and our cable has fixed resistance (what’s more or less correct). It’s clear that the more current is needed, the more drops the voltage (fig. 1).

Figure 1: Voltage droping (cable ressistance was assumed to 0.5 Ohm)

Depending on your SBC, it’s more or less tolerant to such a voltage drop. But the result is mostly the same à software instability.

How can we influence the resistance of our cable, this is simple à Use the thickest and shortest cable that you can find. The resistance of a round coper wire is defined by eq. 2.

Cause ρ is a material constant, only length and thickness could be changed. The length can easily be checked. Whereas for the thickness you have to cut the cable and check it, or trust the vendor that he doesn't cheat you (the more copper inside a cable, the higher the production cost). The American wire gauge (AWG) classifys the thickness of your copper wires inside your cable. Its often written on your cable. Micro USB cables have mostly a AWG number between 30 (d=0.255mm) to 20 (d=0.812mm) for realy good ones (Illustration 1).

Illustration 1: AWG print on cable

Example:

If we assume that there’s no voltage drop from the connector (which is not true) and the power source has an output of 5.1 V @ 2.0 A and our SBC needs >4.8 V to run properly*. How long can a copper-cable with a defined diameter be before the SBC crashes?

*this numbers are chosen randomly, since I don’t have any validatet numbers when a specific board runs into instability.

Using eq. 2 for cables between EWG 20 and EWG 30 gives us the following results (fig. 2).

Figure 2: Voltage drop of a copper cable at various thiknesses

If we only had a voltage drop due to the cable length (no resistance from the USB connectors nor inside the SBC) we could have cable lenghts between 40cm (AWG30) up to 4.8m (AWG 20). But that’s not the reallity! To illustrate this, some measurements on a real issue were done.

Case Study:

Three different USB-Chargers and four different micro USB cables were used to charge a ‘xtorm’ powerbank (from the powerbank spec, it should be possible to charge it with 2.0A @5V). This powerbank has to possibilities for charging. With the ‘onboard’ USB-cable or with a micro-USB input. With a ‘Keweisi’ USB-Powermeter on one side and a multimeter on the other side current, and voltage drop during charging was measured (Illustration 2).

Illustration 2: Setup vor measurement

FYI: These measurements weren't made under laboratory conditions nor with high precision equipment. All chargers are listed in Table 1.

Table 1: Specification of the tested chargers

Table 2 displays the tested micro-USB cables, they came mostly from buyed usb devices and were not especially buyed to power a SBC!

Table 2: Tested micro USB cables

Results:

After all this theory, lets have a look how much the voltage drops at delivered current. All resulsts are sumarized in Fig. 3.

Figure 3: Voltage drop at delivered current of all chargers

Firstly, we see that the noname USB charger from aliexpress couldn’t deliver the claimed 2A, it seems like that it is more or less a 1A charger sold as 2A charger. The short USB-cable and the one deliverd to power a tablet (cable 1&2) performe well, with only a small voltage drop and the highest current. Even at arround 1A the thin cables (cable 3&4) have a realy hight voltage drop of around 0.5-0.7V! This is similar on the iPhone charger. If we go to high current, the situation becomes interesting. Even if the charger can deliver such a high current (cable 1&2), thin long cables (cable 3&4) can't deliver it and the voltage drops more than 0.8V! That’s definitely not a recommended setting for a SBC.

All these chargers are a little bit above the 5.0V at its output so no problem, right? ‘If I use a short cable this small voltage-drop of around 0.3-0.5V wouldn’t be a problem. That’s not true! As soon as the charger must deliver higher current the voltage drops at its output (Fig 4)

Figure 4: Voltage without load, with load and on output and @powerbank

Worst in class here to is also the noname cell phone charger. It delivers around 4.1V on the powerbank side. The iPhone charger doesn’t perfome much better. Even the Trekstore charger, which is able to deliver 2.0A couldn’t do this at 5V. With a short cable, it’s around 4.6V. I wouldn’t recommend one of these chargers to power a SBC with some peripherals attached to it.

Conclusion:

What's next? Should we never buy again a micro USB powered SBC? IMO no! A micro USB powered board is not a no go. But we should keep the powering situation in mind when we have such a device. Long thin cables are definitely not recommended for powering such a device. Even short cables with a bad power source will end in touble. It stands and falls with your setup (e. g. powerconsumption of your SBC, perepherials attachted to it) and the choosing of the right charger. For example, I use a charger (2A @5V) with a fix attached AWG 22 cable (Ill. 2). Doing the same test with it (current and voltage under load at its output could not been mesured since there is no USB for the powermeter) showed 4.84V on the output of the powerbank and 5.20V without load. Which is about 0.2V more than the Trekstore charger with the best cable attached to it. Spend a little bit more money on your powersource and you eliminate one of the possibilities to frustrate you!

Illustration 3: Recommended powersource

Armbian 20.05.2 Tinkerboard buster not working

Sat, 18 Jul 2020 14:10:56 +0000

I just d/l and installed the above image, does not boot at all!

is this for the "Tinker S" otherwise is a kind of joke...

Orange PI 4 not boot

Sat, 18 Jul 2020 10:30:28 +0000

No boot from sd card Armbian_20.05.7_Orangepi4_focal_current_5.4.49.img.xz

The Image OrangePi_4_ubuntu_bionic_desktop_linux4.4.179_v1.3.tar.gz is boot normaly.

SD card SanDisk Ultra 64G 10class.

gdisk p table

Number Start (sector)    End (sector) Size       Code Name
   1           24576           32767   4.0 MiB     8300 uboot
   2           32768           40959   4.0 MiB     8300 trust
   3           49152          114687   32.0 MiB    8300 boot
   4          376832       124735454   59.3 GiB    8300 rootfs

console debug no viewer, but my usb-ttl not support 1500000!

Where SD card is new, armbian boot normaly!!!!

After OrangePi image no...

Bananapi M1 with Armbian 20.02.1 not booting

Mon, 13 Jul 2020 18:45:15 +0000

Hello Community,

I'm trying to get Armbian running on my Banana PI M1 with the following image:

https://dl.armbian.com/bananapi/archive/Armbian_20.05.2_Bananapi_buster_current_5.4.43_minimal.img.xz

I flashed the image with Etcher on my SD Card which is a Sandisk Ultra 16GB SDHC Card.
After flashing I have inserted the Card into my Banana PI but I only get a red light, I already tried different images like the bionic image but without positive result and tried

different power supply cables. In my DHCP Server I see no request.

I have also flashed for testing reasons current image of Bananian which was directly working but I don't want to use that because
their project is not under active development anymore and they recommend to use Armbian.

Can you help me?

Best Regards

Orange Pi Zero does not start

Mon, 06 Jul 2020 16:51:00 +0000

Hello there,

I am trying to (first) boot an Orange Pi Zero (H2+, 512MB ram, v1.5) that I received a long time ago but can't get it to start.
There are no LEDs turned on, not on the ethernet port nor on the other side (but afaik the latter is software controlled so this does not worry me).

Here is what I tried: multiple attempts with Armbian Buster (Armbian_20.05.3_Orangepizero_buster_current_5.4.45.img) burnt with BalenaEtcher, multiple microSD cards, different power supplies (via microUSB and GPIO).

Unfortunately, nothing shows up on the serial connection, and 0 amps are drained when 5V is sent to the board.

I have little experience with Orange Pis and I have usually found my way around, the microSD cards and PSUs were also tested working on an Orange Pi PC and another Orange Pi Zero (H2+, 256MB ram, v1.4)...

Can someone help me? Is my board dead?

Thank you for your help!

Orange Pi Zero +2 H3 don't start

Tue, 09 Jun 2020 18:24:14 +0000

Hello,

I'm getting strange erros from my board.. i dunno what else i can do.. i tried many images (focal, buster, bionic..), few different SDs and PSUs..

Always getting error like that:

Someone can help pleae?

Thanks

armbian in orange pi zero plus dont start

Sun, 31 May 2020 08:03:30 +0000

Hi,

I tried many time with different version of armbian o.s. for orange pi zero plus, but operative system dont want to start....

Work only old version DietPi ...

With armbian o.s. , at start, I see orange e green ethernet led ON fixed and nothing other....

Why ?

Bad signature on Focal img, nanopiM4-V2

Tue, 02 Jun 2020 15:42:57 +0000

I cannot verify a gpg signature for your Focal image. It could be my error, of course. But for Buster, all works perfectly by the same methods.

Something about the Focal download is different and undocumented, or something is just plain wrong. (Buster and Focal are zipped with different programs. What's up with that?)

Yesterday, attempting to verify the Focal image from the main download by similar steps led to a runaway output (symbols, code) in terminal. That scared me. I shut down the virtual machine, then deleted it.

Tried again today (below). All done in a fresh virtual machine. Files for checking (.asc, .img) downloaded by wget from links at base of Downloads page.

Public key downloaded according to your webpage https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity.

1. Download from Denmark mirror:

[user@d-nanopi-m4-v2 focal]$ wget http://mirrors.dotsrc.org/armbian-dl/nanopim4v2/archive/Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.xz
--2020-06-02 15:30:38--  http://mirrors.dotsrc.org/armbian-dl/nanopim4v2/archive/Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.xz
Resolving mirrors.dotsrc.org (mirrors.dotsrc.org)... 130.225.254.116, 2001:878:346::116
Connecting to mirrors.dotsrc.org (mirrors.dotsrc.org)|130.225.254.116|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 771774000 (736M) [application/octet-stream]
Saving to: ‘Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.xz’

Armbian_20.05.1_Nan 100%[===================>] 736.02M  3.94MB/s    in 3m 14s  

2020-06-02 15:33:53 (3.80 MB/s) - ‘Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.xz’ saved [771774000/771774000]

2. Unzip (as per instructions) and list folder contents

[user@d-nanopi-m4-v2 focal]$ xz -d Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.xz

[user@d-nanopi-m4-v2 focal]$ ls
Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img
Focal_current_desktop.asc
Focal_current_desktop.sha

3. Fail gpg verify

[user@d-nanopi-m4-v2 focal]$ gpg --verify Focal_current_desktop.asc Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img
gpg: Signature made Sun May 31 06:59:23 2020 AEST
gpg:                using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5
gpg: BAD signature from "Igor Pecovnik @armbian.com>" [unknown]

4. Trying to test .asc file - fail

[user@d-nanopi-m4-v2 focal]$ gpg --keyid-format long --list-options show-keyring Focal_current_desktop.asc
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
Detached signature.
Please enter name of data file: Focal_current_desktop.asc
gpg: Signature made Sun May 31 06:59:23 2020 AEST
gpg:                using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5
gpg: BAD signature from "Igor Pecovnik @armbian.com>" [unknown]

5. Change name and try to verify again - fail. x2

[user@d-nanopi-m4-v2 focal]$ cp Focal_current_desktop.asc Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.asc

[user@d-nanopi-m4-v2 focal]$ gpg --verify Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.asc Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img
gpg: Signature made Sun May 31 06:59:23 2020 AEST
gpg:                using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5
gpg: BAD signature from "Igor Pecovnik @armbian.com>" [unknown]

[user@d-nanopi-m4-v2 focal]$ gpg --verify Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img.asc
gpg: assuming signed data in 'Armbian_20.05.1_Nanopim4v2_focal_current_5.4.43_desktop.img'
gpg: Signature made Sun May 31 06:59:23 2020 AEST
gpg:                using RSA key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5
gpg: BAD signature from "Igor Pecovnik @armbian.com>" [unknown]

Have images for Rock Pi 4 been tested lately?

Thu, 07 May 2020 00:54:16 +0000

Neither versions (Bionic or Buster) imgs available on this site boot up on my Rock Pi 4 board. I've had it for a week.

It does with Debian which reports excellent power and it also boots Android 9.

Yes I've tried many thoroughly tested SDs.

If you haven't personally tried booting these images as they are on your newer Rock Pi 4 board please don't respond to this message.

Official/Supported Nanopi M4 images are not booting

Mon, 18 May 2020 06:43:33 +0000

Hi -

My brand new nanopi M4 (2gb) will boot the friendly elec nanopi images just fine, it'll boot to a usable text console with the armbian rockpi minimal image, but none of the supported images (or any unsupported ones) from the armbian nanopi m4 download page will boot or generate video. Same sd card, sufficient power, flashed with etcher just to make sure.

What's the best way to root cause/fix this?

Cubietruck USB issue with HDD hub

Thu, 07 May 2020 18:56:22 +0000

Hi guys,

maybe you can give an advice. I have setup a NAS with my cubietruck, works like a charm with a single HDD3.5 sata connected.

I have an usb hub for two HDD 3., this one:

https://www.amazon.it/SALCAR-Docking-ottimizzato-compreso-Aluminum/dp/B01LZFH7NO/ref=sr_1_6?__mk_it_IT=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=salcar&qid=1588877559&sr=8-6

it's a 3.0 usb with external power, it works perfectly on my desktop pc: I can see both the disk, but nothing if connected to cubietruck USB port. It is externally powered up.

This is my cubitruk lsusb:

root@cubietruck:~# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And dmesg | grep usb:

root@cubietruck:~# dmesg | grep usb
[    0.000000] Kernel command line: root=UUID=09c47a69-3f67-4fa2-afcf-7c3abb0c17aa rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=e988e4f0-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1
[    1.321384] usbcore: registered new interface driver usbfs
[    1.321436] usbcore: registered new interface driver hub
[    1.321513] usbcore: registered new device driver usb
[    3.711349] usbcore: registered new interface driver usb-storage
[    3.777804] usbcore: registered new interface driver usbhid
[    3.777808] usbhid: USB HID core driver
[    5.031900] axp20x-usb-power-supply axp20x-usb-power-supply: DMA mask not set
[   16.041899] ehci-platform 1c14000.usb: EHCI Host Controller
[   16.041944] ehci-platform 1c14000.usb: new USB bus registered, assigned bus number 1
[   16.048877] ehci-platform 1c14000.usb: irq 33, io mem 0x01c14000
[   16.064658] ehci-platform 1c14000.usb: USB 2.0 started, EHCI 1.00
[   16.065028] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[   16.065040] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.065047] usb usb1: Product: EHCI Host Controller
[   16.065054] usb usb1: Manufacturer: Linux 5.4.35-sunxi ehci_hcd
[   16.065060] usb usb1: SerialNumber: 1c14000.usb
[   16.067326] ehci-platform 1c1c000.usb: EHCI Host Controller
[   16.067371] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2
[   16.067864] ehci-platform 1c1c000.usb: irq 38, io mem 0x01c1c000
[   16.080568] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[   16.085059] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[   16.085087] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.085100] usb usb2: Product: EHCI Host Controller
[   16.085113] usb usb2: Manufacturer: Linux 5.4.35-sunxi ehci_hcd
[   16.085121] usb usb2: SerialNumber: 1c1c000.usb
[   16.087695] ohci-platform 1c14400.usb: Generic Platform OHCI controller
[   16.087742] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3
[   16.088243] ohci-platform 1c14400.usb: irq 34, io mem 0x01c14400
[   16.153009] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[   16.153027] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.153035] usb usb3: Product: Generic Platform OHCI controller
[   16.153042] usb usb3: Manufacturer: Linux 5.4.35-sunxi ohci_hcd
[   16.153048] usb usb3: SerialNumber: 1c14400.usb
[   16.155112] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[   16.155152] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4
[   16.155575] ohci-platform 1c1c400.usb: irq 39, io mem 0x01c1c400
[   16.216894] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[   16.216910] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.216918] usb usb4: Product: Generic Platform OHCI controller
[   16.216924] usb usb4: Manufacturer: Linux 5.4.35-sunxi ohci_hcd
[   16.216931] usb usb4: SerialNumber: 1c1c400.usb
[   16.219264] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[   16.220098] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[   16.220135] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5
[   16.222034] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[   16.222051] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.222058] usb usb5: Product: MUSB HDRC host driver
[   16.222065] usb usb5: Manufacturer: Linux 5.4.35-sunxi musb-hcd
[   16.222072] usb usb5: SerialNumber: musb-hdrc.1.auto
[   35.963846] usb0-vbus: disabling

Any advice??

Thanks!

Lino

Mon, 23 Mar 2020 19:51:20 +0000

Hello,

I have a Pi Plus 2e.

I want install Armabian. I try write with etcher the image into microsd.

But, when I insert microsd, I have only led green on board.

Without the microsd, there is Android on the eMMC.

Do you have any idea for installarion?

Excuse for my English, but I'm Italian.....

I try the fel mode. The fel-sdboot write correctly. But I not have any way for install Armbian (Pi Plus 2e not have any led).

Thanks for any help.

OrangePI Prime continuiusly rebooting

Wed, 30 Jan 2019 16:33:36 +0000

Hello Folks,

Seems like it is very strange behaviour with last Armbian at the OrangePi Prime board.
It is continuiusly rebooting after power is on. Green led near the HDMI output is on, then after few seconds board is rebooting (led is off), and again.

Board:
OrangePi Prime
SD Cards (the same results on both):

  SanDisk Extreme Pro microSDXC Class 10 UHS Class 3 V30 A1 64GB
Kingston microSDHC Class 10 8GB
Compilation environment:
VMware Workstation 14.1.3 with Ubuntu Bionic installed
Linux ubuntu-bionic 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:   Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
All steps are applied: https://docs.armbian.com/Developer-Guide_Build-Preparation/
For SD formatting tool is used:
  SD Card Formatter 5.0.1

For build image flashing tools are used (the same results on both):

Win32 DiskImager 1.0
balenaEtcher 1.4.9

Tested builds of the Armbian where problem is observed:

Official server release for OrangePi Prime (yesterday was "Armbian_5.69_Orangepiprime_Debian_stretch_next_4.19.13.img"):
https://www.armbian.com/orange-pi-prime/
https://dl.armbian.com/orangepiprime/Debian_stretch_next.7z
Manually compiled builds using compilation env described before (all builds are compiled with default build options):
Armbian_5.73_Orangepiprime_Ubuntu_bionic_next_4.19.17.img
Armbian_5.73_Orangepiprime_Ubuntu_xenial_next_4.19.17.img
Armbian_5.74_Orangepiprime_Debian_stretch_next_4.19.17.img
Armbian_5.74_Orangepiprime_Ubuntu_bionic_next_4.19.17.img
Armbian_5.74_Orangepiprime_Ubuntu_xenial_next_4.19.17.img

This build was able to start successfully: "Armbian_5.72_Orangepiprime_Ubuntu_bionic_next_4.19.13.img"
But when I've started cpu load test it is freeze immedialetely.

Script on python that was used for cpu load testing:

# Produces load on all available CPU cores
from multiprocessing import Pool
from multiprocessing import cpu_count

def f(x):
while True:
x*x

if __name__ == '__main__':
processes = cpu_count()
print 'utilizing %d cores\n' % processes
pool = Pool(processes)
pool.map(f, range(processes))

Board is fully functional and working. Was tested with official "OranagePi Prime Ubuntu Desktop V2.1" build:
http://www.orangepi.org/downloadresources/orangepiprime/orangepiprime_90a173615c3d08cc1efb22.html
ubuntu_desktop_xfce_prime_V0_1.img
With this build board is successfully start and running cpu loading script without any problems.

Can you please lake a look into this problem?

Thanks,
Grigory.

[PINE-A64] External hard disk not recognized

Mon, 24 Feb 2020 10:48:03 +0000

Hi to all,

I've a problem with my installation of Armbian.

Currently i'm using Armbian Bionic on my pine A64 kernel version:

Linux pine64 5.4.20-sunxi64 #20.02.1 SMP Mon Feb 17 02:37:37 CET 2020 aarch64 aarch64 aarch64 GNU/Linux

When i attach my external hdd it doesn't show in /dev neither i can find it in the logs;

daniele@pine64:~$ lsusb 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
daniele@pine64:~$ dmesg | grep usb
[    1.254270] usbcore: registered new interface driver usbfs
[    1.254306] usbcore: registered new interface driver hub
[    1.254366] usbcore: registered new device driver usb
[    2.035099] sun4i-usb-phy 1c19400.phy: failed to get clock usb0_phy
[    2.057968] ehci-platform 1c1a000.usb: EHCI Host Controller
[    2.057989] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1
[    2.058095] ehci-platform 1c1a000.usb: irq 19, io mem 0x01c1a000
[    2.071979] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00
[    2.072211] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    2.072219] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.072225] usb usb1: Product: EHCI Host Controller
[    2.072231] usb usb1: Manufacturer: Linux 5.4.20-sunxi64 ehci_hcd
[    2.072237] usb usb1: SerialNumber: 1c1a000.usb
[    2.073450] ohci-platform 1c1a400.usb: Generic Platform OHCI controller
[    2.073468] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2
[    2.073558] ohci-platform 1c1a400.usb: irq 20, io mem 0x01c1a400
[    2.136249] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[    2.136257] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.136263] usb usb2: Product: Generic Platform OHCI controller
[    2.136269] usb usb2: Manufacturer: Linux 5.4.20-sunxi64 ohci_hcd
[    2.136275] usb usb2: SerialNumber: 1c1a400.usb
[    2.137581] usbcore: registered new interface driver usb-storage
[    2.142711] usbcore: registered new interface driver usbhid
[    2.142713] usbhid: USB HID core driver
[    2.280060] ehci-platform 1c1b000.usb: EHCI Host Controller
[    2.280082] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 3
[    2.280183] ehci-platform 1c1b000.usb: irq 21, io mem 0x01c1b000
[    2.295979] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00
[    2.296153] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    2.296161] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.296167] usb usb3: Product: EHCI Host Controller
[    2.296173] usb usb3: Manufacturer: Linux 5.4.20-sunxi64 ehci_hcd
[    2.296178] usb usb3: SerialNumber: 1c1b000.usb
[    2.297275] ohci-platform 1c1b400.usb: Generic Platform OHCI controller
[    2.297293] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 4
[    2.297386] ohci-platform 1c1b400.usb: irq 22, io mem 0x01c1b400
[    2.360140] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.04
[    2.360147] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.360154] usb usb4: Product: Generic Platform OHCI controller
[    2.360160] usb usb4: Manufacturer: Linux 5.4.20-sunxi64 ohci_hcd
[    2.360165] usb usb4: SerialNumber: 1c1b400.usb
[    2.361268] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[    2.361648] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    2.361665] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5
[    2.361876] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[    2.361884] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.361890] usb usb5: Product: MUSB HDRC host driver
[    2.361896] usb usb5: Manufacturer: Linux 5.4.20-sunxi64 musb-hcd
[    2.361901] usb usb5: SerialNumber: musb-hdrc.1.auto
[    5.366107] axp20x-usb-power-supply axp20x-usb-power-supply: DMA mask not set
daniele@pine64:~$ ls -l /dev/sd*
ls: cannot access '/dev/sd*': No such file or directory

The same hdd is recognized correctly in my laptop:

Bus 001 Device 013: ID 1bcf:0c31 Sunplus Innovation Technology Inc. SPIF30x Serial-ATA bridge

I've installed the full firmware package from the armbian-config tools, other usb dongles are recognized correctly.

What can i do now?

Thanks, Daniele.

Sd card Copy = no boot

Thu, 07 Nov 2019 14:02:42 +0000

Dear all,

My problem:

I've tried to Copy my current micro sd card(8go) to another one (32go)

Copy with a virtualbox (Ubuntu with the dd command to Copy the first card to the other one) , or with gparted (Copy and past)

But with all these methods the problem stay the same = no boot

Error message:
Gave up waiting for root file system device.
Common problems
- Boot args (cat proc/cnd.no)
- Check rootdelay (did the system wait long enough?)
- Missing modules (cat proc/modules: Is /dev)
ALERT UUID-16bb1d19-3ee3-119r-Be32-9920fr7d190a does not exist.
Dropping to a shell!
(initramfs)

I'm not an expert with Linux so I don't know how can I resolve this problem.

Can you help me ?
Thx in advance

Sdcard not formatting..

Wed, 05 Feb 2020 20:39:37 +0000

Hi again... Im posting this issue to get some reply about a original sdcard i've used to install armbian to an orange pi device,.. as told before i flashed armbian on it an it just worked fine.. but i need to erase/format now and in any partition type it'snt working.. i've tried this o a windows machine and on a linux machine.. thats it.

i couldnt format this 8gb sdcard in any partition type.. (on a windows machine i've got a warning concerning its protected, but on a linux machine no warnings just doesnt work)..

Can someone tell me how to format this sdcard?.. (there is armbiaN for orangepi win plus on it)..

Thx a lot..

booting Pine H64 with directly attached USB3 SSD fails

Tue, 04 Feb 2020 21:45:22 +0000

On 12/25/2019 at 9:48 AM, Igor said:

I added support and images for model B, but I don't own this hardware ... https://dl.armbian.com/pineh64-b/

@TonyMac32 You got this board? You have gears and time to make a hires photo?

This is AWESOME. I was using the regular pineh64 images, and most things were working except my NIC kept shutting off about 33-34s after boot every time.

Turns out, if I use the pineh64-b image, my gigabit link stays active and everything seems to be pretty great!

My only issue now is that booting with a USB3 SSD attached directly to the device seems not to work very well. Maybe the SSD is trying to pull too much power at boot? It worked fine when I plugged it in directly after the system was booted from microSD, but cold boots always fail with direct attachment. It's booting 100% reliably for me with my rootfs on SSD if I attach the SSD to a powered USB3 hub, but I'd like it if it didn't need any extra hardware to boot.

Random Reboot on my orange pi zero

Thu, 30 Jan 2020 22:02:32 +0000

im working on an embedded system, but i have a problem with random reboot, my orange pi zero, works well but sometimes it restarts for no apparent reason,

it's not a problem with my script because it happens even without the script working, problem can it be my sd card or power suply, or something?

[SOLVED] Odroid XU4 does not boot from eMMC Card

Wed, 22 Jan 2020 15:46:53 +0000

Hi,

I'm proud owner of an ODROID XU4 REV 0.1 20180912 and would like to use your latest Image.

Here are the steps I have done on my Win 10 - 1803 PC:

Downloading your image file from your site
Unpacking with 7zip to .img
Starting Etcher Portable 1.5.63
Select the .img file
Connect my eMMC card (16GB) to my CardReader
This card is auto-selected by Etcher as Target device
Click on Flash
Etcher tranfers the image to the eMMC card and then validates it.
When ready i close Etcher, remove the card safely from my PC and put it onto my ODROID-XU4
I connect only a LAN cable and a power cable to the ODROID XU 4.
The on-board boot select switch selects eMMC as boot device
The ventilator starts to run, the ethernet leds starts blinking, that’s all
When I connect a Monitor via HDMI and/or a mouse, keyboard and/or external SSD -> same result
No desktop ist displayed, no IP address is assigned (I have checked this on my router)

To check if I do anything wrong I exactly repeated the above steps but this time I used the standard Ubuntu image that I had downloded from the ODROID website.

With this image my ODROID-XU4 starts Ubuntu and runs without any problems.

I hope this helps to find the problem.

Thanks a lot for your support.

garysn

orange pi one broken?

Sun, 29 Sep 2019 16:22:34 +0000

orange pi one

I was installing armbian buster. Then decided to abort the installation and turned off power.

If I install armbian on a sd card and then put the sd card into the orange pi one,

the orange pi one keeps rebooting and display message boot. env

file invalid elf header rebooting. Is the orange pi garbage? Can I reset the orange pi one?

Thank you.

Unreliable HW watchdog?

Fri, 06 Dec 2019 16:58:19 +0000

Hi,

I'm having issues with an unreliable HW watchdog on the Orange Pi Zero. I am using the standard Armbian kernels (tried 4.19.62, 5.3.x, 5.4.x - all the same) and have nowayout=1:

[ 4.328286] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=1)

I'm feeding /dev/watchdog every 2 seconds. Superficially it works, for example, if I do the following the WD triggers after 16 sec and the board reboots:

echo c > /proc/sysrq-trigger

However I am finding that in other crash scenarios, the WD reboot sometimes happens and sometimes does not. For example, with a forkbomb :(){ :|:& };: about 70% of the time the WD reboots the board, but 30% of the time the board stays crashed and the WD never reboots it. (I've confirmed that the forkbomb does stop the watchdog feeder, so the WD should trigger a reset.) I have to do a hard power cycle to get it to boot again.

Has anyone else had experience with an unreliable watchdog on these boards? Any more insight or fixes?

-Adrian

Latest update put my device in read-only mode. How do I fix that?

Fri, 17 May 2019 20:01:04 +0000

I just update my device and rebooted. It now is in "read only" mode. How do I fix that?

root@renegade:/home/nifd# touch test.txt
touch: cannot touch 'test.txt': Read-only file system

Linux renegade 4.4.178-rockchip64 #4 SMP Wed May 8 19:34:01 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux

buster not working cubox-i

Sun, 17 Nov 2019 22:00:52 +0000

Hi I have been able to use armbian (Stretch) on the Cubox-i well. But I tried to use the Buster images, and I get the same problem for all of them. The initial display starts up, I get about 10 lines of output, and then the screen goes blank.

On the router, I don't see the board, so I don't think that I can ssh in. (It's being used as a headless server, but I need to a display or SSH to fix it). Any ideas why buster wouldn't work but stretch is OK ? I could just go back to stretch, if necessary. By the way, is there a link to download the armbian stretch images ?

Orange Pi One and Orange Pi PC: stalls at boot with Armbian_5.91_Orangepipc_Debian_buster_next_4.19.59

Sun, 10 Nov 2019 15:35:05 +0000

I have several Orange Pi One and Orange Pi PC boards (the original ones, H3-based). I have downloaded the latest Armbian release for them Armbian_5.91_Orangepipc_Debian_buster_next_4.19.59 and imaged several SD cards in Linux with dd. The cards are all class 10, some are Sandisk and some are Samsung. I am using a 2.5A power supply for the boards.

For all the boards and all the SD cards I get the same result. U-boot starts, gets to the point of loading the kernel, clears the screen then displays "Loading, please wait" then "Starting version 241" and stalls there. Nothing else happens no matter how long I wait. If I power the board off and then back on, the same thing happens.

This happens with 3 different boards (one Orange Pi One and 2 Orange Pi PCs), and 5 different SD cards. The SD cards are all 16GB, class 10, 3 are Sandisk and 2 are Samsung. Any combination of board+card gives me the same result.

The way the cards are written is with:

dd if=Armbian_5.91_Orangepipc_Debian_buster_next_4.19.59.img of=/dev/mmcblk0 bs=4M

I have used the same approach with Armbian for the Odroid-C2 with the corresponding version of Armbian, and that worked well.

If I connect any of the boards to the Linux PC via USB-TTL adapter and use a serial console, the boards freeze before loading the kernel. Here is the serial console output.

U-Boot SPL 2019.04-armbian (Jul 15 2019 - 17:15:48 +0200)
DRAM: 1024 MiB
Trying to boot from MMC1


U-Boot 2019.04-armbian (Jul 15 2019 - 17:15:48 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   phy interface0
eth0: ethernet@1c30000
230454 bytes read in 12 ms (18.3 MiB/s)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
USB2:   USB EHCI 1.00
USB3:   USB OHCI 1.0
USB4:   USB EHCI 1.00
USB5:   USB OHCI 1.0
USB6:   USB EHCI 1.00
USB7:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 2 USB Device(s) found
scanning bus 4 for devices... 2 USB Device(s) found
scanning bus 5 for devices... 1 USB Device(s) found
scanning bus 6 for devices... 1 USB Device(s) found
scanning bus 7 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3798 bytes read in 2 ms (1.8 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 1 ms (148.4 KiB/s)
6746780 bytes read in 326 ms (19.7 MiB/s)
7494376 bytes read in 361 ms (19.8 MiB/s)
Found mainline kernel configuration
29890 bytes read in 6 ms (4.8 MiB/s)
4155 bytes read in 4 ms (1013.7 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6746716 Bytes = 6.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
   Loading Ramdisk to 49990000, end 49fff25c ... OK
   Loading Device Tree to 49920000, end 4998ffff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

my board don't start te system

Thu, 07 Nov 2019 17:20:48 +0000

I have a nanopc t4 and I make armbian buster booteble and it takes a few second and then the screen goes on and I wait a 1 hour and noting is going happening he does nothing

IMG_0222.MOV

RESOLVED: Bananapi M1 Bionic mainline 4.19.y: no HDMI video

Tue, 24 Sep 2019 05:21:41 +0000

My BPi M1 board is working fine, but the old bananalinux is no longer updating. So I downloaded Armbian Bionic mainline image as it is supported.

However, after I boot it up, I get no HDMI video signal. I know that the BPi is working as I can see its IP address on my router and ping it.

Any suggestions? Try a different image? Build my own?

Thank you in advance for helping.

Orange PI R1 Segfaults no matter what pls hlp

Tue, 08 Oct 2019 13:09:51 +0000

[13677.938894] Unable to handle kernel paging request at virtual address fff00010
[13678.025402] pgd = 4cb4f804
[13678.057789] [fff00010] *pgd=4fffd861, *pte=00000000, *ppte=00000000
[13678.132839] Internal error: Oops: 37 [#1] SMP THUMB2
[13678.192234] Modules linked in: tun nft_chain_nat_ipv4 ipt_MASQUERADE nf_nat_ipv4 nf_nat xt_multiport xt_state nft_limit xt_limit xt_tcpudp xt_conntrack ip_tables nft_compat x_tables nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink usb_f_acm u_serial g_serial libcomposite 8189es sun8i_codec_analog cfg80211 sun4i_i2s snd_soc_simple_card sun8i_adda_pr_regmap snd_soc_simple_card_utils cdc_ether lima snd_soc_core usbnet snd_pcm_dmaengine r8152 gpu_sched snd_pcm sun4i_gpadc_iio ttm snd_timer snd industrialio soundcore sun8i_ths cpufreq_dt thermal_sys uio_pdrv_genirq uio pwrseq_simple
[13678.849823] CPU: 1 PID: 2156 Comm: htop Not tainted 4.19.62-sunxi #5.92
[13678.928975] Hardware name: Allwinner sun8i Family
[13678.985258] PC is at path_init+0xe/0x1fc
[13679.032172] LR is at path_openat+0x65/0xe0c
[13679.082201] pc : []    lr : []    psr: 00030033
[13679.157191] sp : ce8d7e28  ip : cd5f0770  fp : c0e04d48
[13679.219701] r10: cd5f06c0  r9 : ffffe000  r8 : fffff000
[13679.282213] r7 : ce8d7f70  r6 : 09200000  r5 : c0bb033c  r4 : ce8d7ec0
[13679.360324] r3 : fff00010  r2 : 04900000  r1 : 00000043  r0 : ce8d7ec0
[13679.438435] Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment none
[13679.525911] Control: 50c5387d  Table: 4f2b406a  DAC: 00000051
[13679.594664] Process htop (pid: 2156, stack limit = 0x7dd56812)
[13679.664458] Stack: (0xce8d7e28 to 0xce8d8000)
[13679.716572] 7e20:                   ce8d7ec0 c0bb033c 09200000 ce8d7f70 fffff000 c0249659
[13679.814450] 7e40: 00000000 00000000 00000000 00000000 cf9802c0 00000000 00000000 00000043
[13679.912333] 7e60: ffffe000 00000000 00000000 00000000 00000000 00000000 ffffffff ffffffff
[13680.010217] 7e80: c012e8fb 00000000 00000000 00000000 00000003 308cbb93 00006278 c0e04d48
[13680.108100] 7ea0: 00000000 ce8d7f70 00000003 fffff000 ce8d6000 00000142 016004c8 c024b123
[13680.205984] 7ec0: cfa64710 00000001 c0296ced cd6a2370 cf9802c0 c0512f89 cd6a2388 c0512f77
[13680.303868] 7ee0: ce8d7f78 c0296cff 00000001 c023c0fd 00000000 c0e04d48 00000000 ce8d7f00
[13680.401751] 7f00: 00000000 c023fc29 00000000 c0255f83 c025a75b c022bfc1 cd6a23a0 c0e04d48
[13680.499635] 7f20: 00472b7e 308cbb93 00000004 00000100 fff00010 00000000 00000000 00000400
[13680.597519] 7f40: ffffff9c c0255f83 000a4800 308cbb93 ffffff9c 00000004 c0e04d48 ffffff9c
[13680.695401] 7f60: fff00010 c023ccf3 ce8d6000 00000000 00024800 308c0000 00000004 00000100
[13680.793286] 7f80: 00000003 308cbb93 b6f6e968 00404000 01564a88 00000142 c0101224 ce8d6000
[13680.891169] 7fa0: 00000142 c0101001 b6f6e968 00404000 ffffff9c beccff48 000a4800 00000000
[13680.989053] 7fc0: b6f6e968 00404000 01564a88 00000142 00000000 beccffcc 015f2f53 016004c8
[13681.086936] 7fe0: 00000142 beccf270 b6df3207 b6d76746 00030030 ffffff9c 00000000 00000000
[13681.184827] [] (path_init) from [] (path_openat+0x65/0xe0c)
[13681.272314] [] (path_openat) from [] (do_filp_open+0x4f/0x94)
[13681.361877] [] (do_filp_open) from [] (do_sys_open+0x13f/0x1a8)
[13681.453522] [] (do_sys_open) from [] (ret_fast_syscall+0x1/0x62)
[13681.546195] Exception stack(0xce8d7fa8 to 0xce8d7ff0)
[13681.606629] 7fa0:                   b6f6e968 00404000 ffffff9c beccff48 000a4800 00000000
[13681.704507] 7fc0: b6f6e968 00404000 01564a88 00000142 00000000 beccffcc 015f2f53 016004c8
[13681.802388] 7fe0: 00000142 beccf270 b6df3207 b6d76746
[13681.862823] Code: f85d eb04 6f03 4604 (681d) 782e
[13681.920196] ---[ end trace 37fedba6a1c14f6f ]---

Hello,

With the given board, latest armbian:

No LSB modules are available.
Distributor ID:   Debian
Description:   Debian GNU/Linux 10 (buster)
Release:   10
Codename:   buster

Latest kernel:

Linux linux 4.19.62-sunxi #5.92 SMP Wed Jul 31 22:07:23 CEST 2019 armv7l GNU/Linux

The board just segfaults and dies, it doesnt run anything complex, a small nameserver, firewall thats all.

Any ideas?

Helios4 requires USB serial console cable connected to function

Fri, 20 Sep 2019 13:09:05 +0000

Board ran fine when I did initial setup outside the case with no disks or fans connected, was able to SSH in fine.

After assembling the case and plugging in all the disks and OLED display the board will only boot whilst the serial console is connected. Without it dumps to the initramfs prompt.

Once booted the board runs fine, until I disconnect the serial console cable then anything running from memory is fine, but any access to the linux system on the SD card throws IO errors.

On replugging the serial console cable I see more SD read/write errors.

Regards,

Martin

Orange Pi One stuck on boot at "Loading Ramdisk"

Thu, 29 Aug 2019 13:52:04 +0000

Hi,

I have flashed the latest version 4.19.y of Armbian Buster to my SD card using Etcher.

After putting it into my OrangePi One, the system boots until the message "Loading Ramdisk to 49a3b000, end 49fffdba ...

Sometimes the system is stuck even before.

I have tried different SD cards and different card readers as well - also a new one.

2A power supply.

bios issue

Sat, 24 Aug 2019 21:41:04 +0000

Hello,

Can you explain me why this screen appears when the board shutdown and how to reset the default configuration ? It is new and i don't understand chinese

Expressobin Update Uboot

Fri, 16 Aug 2019 20:23:11 +0000

Espressobin V7 1G 800MHz DDR4 RAM 1GHz cpu purchased last week.

The board starts up reliably and gets to the boot prompt ok (using minicom).

I downloaded and unpacked Armbian_5.91_Espressobin_Debian_buster_next_4.19.59.img.
Ran shasum and got "Ok". I dd'd it to a new Samsung SD card, dd'd it back, and ran
shasum again, getting "Ok".

I put the card in the board and powered it up. It finds the card and tries to boot
but fails, saying:

    Hit any key to stop autoboot: 0
    switch to partitions #0, OK
    mmc0 is current device
    Failed to mount ext2 filesystem...
    ** Unrecognized filesystem type **
    Failed to mount ext2 filesystem...
    ** Unrecognized filesystem type **
    Bad Linux ARM64 Image magic!

I'm guessing that the problem is that I did not update uboot. I copied
flash-image-ddr4-1g-1cs-1000_800.bin to a FAT formatted USB key, but this:

    Updated u-boot needs new default boot environment and new boot script
    (overwrite the one on your /boot media – needed only if you upgrade from < v5.59).
    This is what you need to copy/paste into u-boot prompt:

is unclear. This:

    Copy this flash-image-ddr4-1g-1cs-1000_800.bin to your FAT formatted
    USB key, plug it into USB3.0 port and execute from u-boot prompt:
    bubt flash-image-ddr4-1g-1cs-1000_800.bin spi usb

Seems clear enough. I assume that I am then to paste the list of commands that follows
in at the boot prompt but the part about the "new boot script" is unclear.

[Edit]

I updated uboot and inserted the setenv commands (but ignored the unclear part about the "new boot script").

I'm getting

U-Boot 2018.03-devel-18.12.3-gc9aa92c-armbian (Feb 20 2019 - 09:45:04 +0100)

so that evidently worked. However, when it tries to boot from the SD card I get

Marvell>> run bootcmd_mmc0
/
** Unrecognized filesystem type **
## Executing script at 06d00000
Wrong image format for "source" command
/boot/
** Unrecognized filesystem type **
## Executing script at 06d00000
Wrong image format for "source" command
Marvell>>

[Edit]

The SD card is the same one that I used to flash the Uboot update. Is it necessary to prepare the card

in any way other than to dd the image to it?

[Edit] I loop mounted the image and found that it has an ext4 filesystem with an 8192 block offset.

Used dd to make a copy with no offset. That copy boots.

--
John Hasler

Kernel not boot with u-boot

Fri, 05 Apr 2019 10:43:07 +0000

On my cubietruck I have tried the Armbian_5.75_Cubietruck_Debian_stretch_next_4.19.20. For me it looks that u-boot loads the files, but the kernel will/can not start. Attached the output from the console.

Rarly I get some additional output on the console like "Uncompressing Linux... done, booting the kernel." but nothing happens, or some wild output from wrong instructions which leads to a reset.

I have also tried "Armbian_5.59_Cubietruck_Ubuntu_xenial_default_3.4.113_desktop" to exclude some mainline / legacy kernel issues. But no luck.

With some older versions (e.g. 5.20) I have no luck also.

From my feeling there is a basic thing, may be:

timing (RAM, SD-card)
RTC / empty batterie
problem with the NAND in the background / or the bootloader from there interferes
missing some requirements

After reading dozens of topics from the forum and spending a lot of hours for a search in the web, a have no idea how to go further to solve this issue.

Any hints what I can check / do?

What works:

I am able to boot an old armbian (legacy kernel) from NAND. There , I can mount the SD-card and read and write.

I am able to boot an linaro (older) from SD-card without problems. I have seen that the clock is not up to date. The time started an bootup.

How I have tested:

To the cubietruck I have only connected SD-card, HDMI, network, power supply and UART0 console with putty.

I have burned image with win32imager (version 1.0) and verified.

I have used different SD-cards (brands, sizes, classes).

I have used different power supplies on the power connector => same result.

Regards,

Joerg

printenv.txt

u-boot_log.txt

Armbian sadly died, re-imaging, but partition 1GB?

Thu, 13 Jun 2019 09:55:37 +0000

Hi all,

Downloaded it from here:

https://www.armbian.com/orange-pi-zero/

https://dl.armbian.com/orangepizero/archive/Armbian_5.83_Orangepizero_Debian_stretch_next_4.19.38.7z

Wrote it to a 16GB MicroSD using rufus.

I'm going to be supporting this remotely (long story!!) but before mailing the SDCard to my tech at the other end, I noticed the partition is only 1GB in size.

Is this normal? Will Armbian 'extract' or re-size the partition as part of the first install / boot process?

Banana Pie with SD and USB HDD wont boot from SD

Tue, 25 Jun 2019 06:04:13 +0000

Hello,

my Banana Pie wont start after i plugged in an USB HDD with external power supply.

Can you give me a hint please?

usb 3.0 gigabit as eth1 not recognized - opi pc

Sat, 08 Jun 2019 11:25:50 +0000

hi guys,

literally i'm new to orange pi and as well as here on armbian. like days old. I managed to run and use the usb device in rpi3b+ but was unable to on orange pi. now i know that this is a driver issue.

can someone show me how to download and install the driver on my opi pc?

TIA

Cam

Orange Pi Win Plus supplied with 1.42Amps PSU.

Sun, 12 May 2019 16:07:08 +0000

Ordered Orange Pi Win Plus from official Orange Pi store, it came with bundled PSU.

I always get different errors when latest (by post date) linux Armbian starts and sometimes it starts correctly.

I read this forum carefully and found out this is shitty PSU symptoms, so I took 20 Amps ampermeter and short-circuit PSU through it for 2 seconds, display stopped counting at 1.42 Amps. It is below specs where literally 2 Amps is required!

Besides this I measured voltage and current near board PSU outlet, I got max current it eats through boot process is 0.54 Amps and voltage falls max to 5.32 Volts. Seems like PSU must fit this board but I still get that low power issues. Physics laws are wrong or what?)

Someone maybe can tell me voltage should not be lower than X so board will work good. X = ?

My multimeter looks like this:

https://i.ibb.co/h8JJ5j6/Digital-Multimeter-VC9808-with-Frequency-Capacitance-Temperature.jpg

Strange behaviour and boot log parameter on Nanopi NEO

Fri, 17 May 2019 02:23:07 +0000

I noticed that with Nanopi NEO v1.2 the fixup.src is not loaded at startup, but after some googling i noticed that other boards with h3 chip succesfully load the correct fixup.

My boot log:

U-Boot SPL 2018.11-armbian (Feb 08 2019 - 11:04:44 +0100)

DRAM: 512 MiB

Trying to boot from MMC1





U-Boot 2018.11-armbian (Feb 08 2019 - 11:04:44 +0100) Allwinner Technology



CPU:   Allwinner H3 (SUN8I 1680)

Model: FriendlyARM NanoPi NEO

DRAM:  512 MiB

MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1

Loading Environment from EXT4... ** File not found /boot/boot.env **



** Unable to read "/boot/boot.env" from mmc0:1 **

In:    serial

Out:   serial

Err:   serial

Net:   phy interface0



Error: ethernet@1c30000 address not set.

eth-1: ethernet@1c30000

230454 bytes read in 35 ms (6.3 MiB/s)

Unknown command 'bmp' - try 'help'

starting USB...

USB0:   USB EHCI 1.00

USB1:   USB OHCI 1.0

USB2:   USB EHCI 1.00

USB3:   USB OHCI 1.0

scanning bus 0 for devices... 1 USB Device(s) found

scanning bus 2 for devices... 1 USB Device(s) found

       scanning usb for storage devices... 0 Storage Device(s) found

Autoboot in 1 seconds, press  to stop

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0:1...

Found U-Boot script /boot/boot.scr

3798 bytes read in 20 ms (184.6 KiB/s)

## Executing script at 43100000

U-boot loaded from SD

Boot script loaded from mmc

278 bytes read in 16 ms (16.6 KiB/s)

8002310 bytes read in 637 ms (12 MiB/s)

7489584 bytes read in 602 ms (11.9 MiB/s)

Found mainline kernel configuration

29427 bytes read in 90 ms (318.4 KiB/s)

** File not found /boot/dtb/overlay/-fixup.scr **

## Loading init Ramdisk from Legacy Image at 43300000 ...

   Image Name:   uInitrd

   Image Type:   ARM Linux RAMDisk Image (gzip compressed)

   Data Size:    8002246 Bytes = 7.6 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 43000000

   Booting using the fdt blob at 0x43000000

EHCI failed to shut down host controller.

EHCI failed to shut down host controller.

   Loading Ramdisk to 4985e000, end 49fffac6 ... OK

   reserving fdt memory region: addr=43000000 size=6d000

   Loading Device Tree to 497ee000, end 4985dfff ... OK



Starting kernel ...



Uncompressing Linux... done, booting the kernel.

it's a normal behaviour?

and...

This can be the cause of a random boot/reboot stuck (after some status led startup blinks)?

Thanks in advance for your help and work on this awesome project.

Rock64 V3 will not boot Armbian

Mon, 13 May 2019 16:06:22 +0000

Hello all!

I bought a Rock64 V3 and it wouldn't boot Armbian, not any other GNU/Linux based OS that I tried, I got in touch with Pine64 and they said:

>The issue on the SD boot on the ROCK64 SBC is the GPIO0_D6 (SDMMC0_PWREN) default needs to set high instead of lets this pin floating at Linux DT (Device Tree). The ROCK64 V3 has the high speed SD access design which can double boost up with proper software driver. We will advise developer to update the OS build (stock Android already implemented) accordingly.

>Please refer to ROCK64 SBC v3.0 Change Notice, http://files.pine64.org/doc/rock64/Rock64%20Ver%203%20change%20notice.pdf

>Now the developer is work on it. When the OS ready, the developer will update at Pine64 Forum. Please check on Pine64 Forum (https://forum.pine64.org/forumdisplay.php?fid=85)

When is they estimate for when Armbian will support this new driver?

Thank you,

Joe.

Armbian does not boot on orange pi pc

Sun, 12 May 2019 18:40:06 +0000

What i have so far:

1 sd card, with Armbian Bionic image, flashed with Etcher

2 Orange Pi PC connected to PC through usb to serial converter

And my problem is:

Orange pi pc tries to boot for few times and stuck

log from putty:

Spoiler

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2019.05.12 12:00:43 =~=~=~=~=~=~=~=~=~=~=~=

U-Boot SPL 2019.04-armbian (May 04 2019 - 02:06:03 +0200)
DRAM: 1024 MiB
Trying to boot from MMC1

U-Boot 2019.04-armbian (May 04 2019 - 02:06:03 +0200) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
DRAM: 1 GiB
MMC: mmc@1c0f000: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In: serial
Out: serial
Err: serial
Net: phy interface0
eth0: ethernet@1c30000
230454 bytes read in 12 ms (18.3 MiB/s)
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
USB4: USB EHCI 1.00
USB5: USB OHCI 1.0
USB6: USB EHCI 1.00
USB7: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning bus 4 for devices... 1 USB Device(s) found
scanning bus 5 for devices... 1 USB Device(s) found
scanning bus 6 for devices... 1 USB Device(s) found
scanning bus 7 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3585 bytes read in 1 ms (3.4 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 1 ms (148.4 KiB/s)
7989481 bytes read in 385 ms (19.8 MiB/s)
7489576 bytes read in 361 ms (19.8 MiB/s)
Found mainline kernel configuration
29890 bytes read in 9 ms (3.2 MiB/s)
4155 bytes read in 6 ms (675.8 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7989417 Bytes = 7.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
Loading Ramdisk to 49861000, end 49fff8a9 ... OK
Loading Device Tree to 497f1000, end 49860fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.19.38-sunxi (root@nightly) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.83 SMP Fri May 3 23:33:25 CEST 2019
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Xunlong Orange Pi PC
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 128 MiB at 0x75c00000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] random: get_random_bytes called from start_kernel+0x8d/0x3c6 with crng_init=0
[ 0.000000] percpu: Embedded 18 pages/cpu s41548 r8192 d23988 u73728
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260416
[ 0.000000] Kernel command line: root=UUID=792dc3df-48f8-4101-9640-3a9c73ec438b rootwait rootfstype=ext4 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=7 ubootpart=dfcbd449-01 ubootsource=mmc usb-storage.quirks= sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] allocated 1048576 bytes of page_ext
[ 0.000000] Memory: 883148K/1048576K available (9216K kernel code, 1004K rwdata, 2576K rodata, 1024K init, 331K bss, 34356K reserved, 131072K cma-reserved, 131060K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB)
[ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (10208 kB)
[ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB)
[ 0.000000] .data : 0x(ptrval) - 0x(ptrval) (1005 kB)
[ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 332 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 39959 entries in 79 pages
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 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: Using split EOI/Deactivate mode
[ 0.000000] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000006] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000017] Switching to timer-based delay loop, resolution 41ns
[ 0.000176] Console: colour dummy device 80x30
[ 0.000651] console [tty0] enabled
[ 0.000705] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[ 0.000733] pid_max: default: 32768 minimum: 301
[ 0.000935] Security Framework initialized
[ 0.000957] AppArmor: AppArmor disabled by boot time parameter
[ 0.001039] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001062] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001898] CPU: Testing write buffer coherency: ok
[ 0.002330] CPU0: update cpu_capacity 1024
[ 0.002352] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002831] Setting up static identity map for 0x40100000 - 0x40100054
[ 0.002992] rcu: Hierarchical SRCU implementation.
[ 0.003718] smp: Bringing up secondary CPUs ...
[ 0.014480] CPU1: update cpu_capacity 1024
[ 0.014486] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.025271] CPU2: update cpu_capacity 1024
[ 0.025276] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.035990] CPU3: update cpu_capacity 1024
[ 0.035995] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.036088] smp: Brought up 1 node, 4 CPUs
[ 0.036173] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[ 0.036188] CPU: All CPU(s) started in HYP mode.
[ 0.036200] CPU: Virtualization extensions available.
[ 0.037374] devtmpfs: initialized
[ 0.043851] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[ 0.044080] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.044116] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.048803] xor: measuring software checksum speed
[ 0.087949] arm4regs : 1255.000 MB/sec
[ 0.128010] 8regs : 748.000 MB/sec
[ 0.168072] 32regs : 766.000 MB/sec
[ 0.208133] neon : 1270.000 MB/sec
[ 0.208147] xor: using function: neon (1270.000 MB/sec)
[ 0.208221] pinctrl core: initialized pinctrl subsystem
[ 0.209139] NET: Registered protocol family 16
[ 0.211505] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[ 0.211990] audit: initializing netlink subsys (disabled)
[ 0.212185] audit: type=2000 audit(0.192:1): state=initialized audit_enabled=0 res=1
[ 0.212688] cpuidle: using governor ladder
[ 0.212732] cpuidle: using governor menu
[ 0.213225] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.213248] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.296639] raid6: int32x1 gen() 189 MB/s
[ 0.364561] raid6: int32x1 xor() 160 MB/s
[ 0.432591] raid6: int32x2 gen() 255 MB/s
[ 0.500658] raid6: int32x2 xor() 194 MB/s
[ 0.568805] raid6: int32x4 gen() 258 MB/s
[ 0.636935] raid6: int32x4 xor() 193 MB/s
[ 0.704932] raid6: int32x8 gen() 247 MB/s
[ 0.773158] raid6: int32x8 xor() 172 MB/s
[ 0.841186] raid6: neonx1 gen() 495 MB/s
[ 0.909233] raid6: neonx1 xor() 460 MB/s
[ 0.977380] raid6: neonx2 gen() 664 MB/s
[ 1.045464] raid6: neonx2 xor() 594 MB/s
[ 1.113587] raid6: neonx4 gen() 798 MB/s
[ 1.181645] raid6: neonx4 xor() 669 MB/s
[ 1.249731] raid6: neonx8 gen() 716 MB/s
[ 1.317833] raid6: neonx8 xor() 606 MB/s
[ 1.317848] raid6: using algorithm neonx4 gen() 798 MB/s
[ 1.317861] raid6: .... xor() 669 MB/s, rmw enabled
[ 1.317875] raid6: using neon recovery algorithm
[ 1.319243] SCSI subsystem initialized
[ 1.319663] usbcore: registered new interface driver usbfs
[ 1.319718] usbcore: registered new interface driver hub
[ 1.319800] usbcore: registered new device driver usb
[ 1.319984] media: Linux media interface: v0.10
[ 1.320028] videodev: Linux video capture interface: v2.00
[ 1.320204] pps_core: LinuxPPS API ver. 1 registered
[ 1.320221] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[ 1.320255] PTP clock support registered
[ 1.321790] clocksource: Switched to clocksource arch_sys_counter
[ 1.424912] VFS: Disk quotas dquot_6.6.0
[ 1.425014] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.432567] NET: Registered protocol family 2
[ 1.433287] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[ 1.433337] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 1.433438] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 1.433562] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.433684] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 1.433756] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 1.434054] NET: Registered protocol family 1
[ 1.434541] RPC: Registered named UNIX socket transport module.
[ 1.434563] RPC: Registered udp transport module.
[ 1.434576] RPC: Registered tcp transport module.
[ 1.434589] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.434842] Trying to unpack rootfs image as initramfs...
[ 1.887420] Freeing initrd memory: 7804K
[ 1.889166] Initialise system trusted keyrings
[ 1.889417] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 1.895121] zbud: loaded
[ 1.897191] NFS: Registering the id_resolver key type
[ 1.897234] Key type id_resolver registered
[ 1.897247] Key type id_legacy registered
[ 1.897269] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.897285] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 1.898452] JFS: nTxBlock = 7984, nTxLock = 63876
[ 1.907241] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 1.914828] Key type asymmetric registered
[ 1.914862] Asymmetric key parser 'x509' registered
[ 1.914937] bounce: pool size: 64 pages
[ 1.915002] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 1.915185] io scheduler noop registered
[ 1.915204] io scheduler deadline registered
[ 1.915421] io scheduler cfq registered (default)
[ 1.915441] io scheduler mq-deadline registered
[ 1.915455] io scheduler kyber registered
[ 1.915597] io scheduler bfq registered
[ 1.916711] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO
[ 1.920600] sun8i-h3-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[ 1.922206] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[ 1.970597] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[ 1.992940] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 42, base_baud = 1500000) is a U6_16550A
[ 2.881215] console [ttyS0] enabled
[ 2.908035] sun4i-drm display-engine: bound 1100000.mixer (ops 0xc0a85d08)
[ 2.915201] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0a83454)
[ 2.922936] sun8i-dw-hdmi 1ee0000.hdmi: 1ee0000.hdmi supply hvcc not found, using dummy regulator
[ 2.931878] sun8i-dw-hdmi 1ee0000.hdmi: Linked as a consumer to regulator.0
[ 2.939600] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy)
[ 2.949462] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver
[ 2.957217] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0a8578c)
[ 2.964029] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.970655] [drm] No driver support for vblank timestamp query.
[ 2.976637] [drm] Cannot find any crtc or sizes
[ 2.981616] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0
[ 2.992265] brd: module loaded
[ 3.000758] loop: module loaded
[ 3.006254] libphy: Fixed MDIO Bus: probed
[ 3.010930] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[ 3.016735] dwmac-sun8i 1c30000.ethernet: No regulator found
[ 3.022737] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000)
[ 3.032174] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
[ 3.039414] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
[ 3.046652] dwmac-sun8i 1c30000.ethernet: COE Type 2
[ 3.051631] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
[ 3.058431] dwmac-sun8i 1c30000.ethernet: Normal descriptors
[ 3.064102] dwmac-sun8i 1c30000.ethernet: Chain mode enabled
[ 3.069898] libphy: stmmac: probed
[ 3.073738] dwmac-sun8i 1c30000.ethernet: Found internal PHY node
[ 3.079946] libphy: mdio_mux: probed
[ 3.083555] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY
[ 3.089926] dwmac-sun8i 1c30000.ethernet: Powering internal PHY
[ 3.101286] libphy: mdio_mux: probed
[ 3.105817] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.112361] ehci-platform: EHCI generic platform driver
[ 3.117800] ehci-platform 1c1a000.usb: EHCI Host Controller
[ 3.123411] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1
[ 3.131854] ehci-platform 1c1a000.usb: irq 26, io mem 0x01c1a000
[ 3.153807] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00
[ 3.160188] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.168486] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.175724] usb usb1: Product: EHCI Host Controller
[ 3.180613] usb usb1: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.186632] usb usb1: SerialNumber: 1c1a000.usb
[ 3.191743] hub 1-0:1.0: USB hub found
[ 3.195567] hub 1-0:1.0: 1 port detected
[ 3.200358] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.206585] ohci-platform: OHCI generic platform driver
[ 3.211988] ohci-platform 1c1a400.usb: Generic Platform OHCI controller
[ 3.218633] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2
[ 3.226550] ohci-platform 1c1a400.usb: irq 27, io mem 0x01c1a400
[ 3.294035] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.302328] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.309567] usb usb2: Product: Generic Platform OHCI controller
[ 3.315499] usb usb2: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 3.321517] usb usb2: SerialNumber: 1c1a400.usb
[ 3.326499] hub 2-0:1.0: USB hub found
[ 3.330314] hub 2-0:1.0: 1 port detected
[ 3.335405] usbcore: registered new interface driver usb-storage
[ 3.342181] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
[ 3.348998] sun6i-rtc 1f00000.rtc: RTC enabled
[ 3.353651] i2c /dev entries driver
[ 3.359111] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
[ 3.367714] sunxi-mmc 1c0f000.mmc: Linked as a consumer to regulator.2
[ 3.374740] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[ 3.379476] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.385570] hidraw: raw HID events driver (C) Jiri Kosina
[ 3.391096] usbcore: registered new interface driver usbhid
[ 3.396686] usbhid: USB HID core driver
[ 3.404505] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB
[ 3.406827] Initializing XFRM netlink socket
[ 3.416419] NET: Registered protocol family 10
[ 3.438421] Segment Routing with IPv6
[ 3.442235] NET: Registered protocol family 17
[ 3.446719] NET: Registered protocol family 15
[ 3.451242] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 3.464269] 8021q: 802.1Q VLAN Support v1.8
[ 3.468761] Key type dns_resolver registered
[ 3.473473] Registering SWP/SWPB emulation handler
[ 3.478835] registered taskstats version 1
[ 3.482969] Loading compiled-in X.509 certificates
[ 3.487874] zswap: loaded using pool lzo/zbud
[ 3.494034] Btrfs loaded, crc32c=crc32c-generic
[ 3.502557] mmc0: host does not support reading read-only switch, assuming write-enable
[ 3.506892] Key type encrypted registered
[ 3.514467] mmc0: new high speed SDHC card at address aaaa
[ 3.521536] mmcblk0: mmc0:aaaa SU16G 14.8 GiB
[ 3.523739] sun4i-usb-phy 1c19400.phy: Linked as a consumer to regulator.4
[ 3.534018] ehci-platform 1c1b000.usb: EHCI Host Controller
[ 3.534684] mmcblk0: p1
[ 3.539645] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 3
[ 3.550387] ehci-platform 1c1b000.usb: irq 28, io mem 0x01c1b000
[ 3.569793] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00
[ 3.576107] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.584393] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.591628] usb usb3: Product: EHCI Host Controller
[ 3.596520] usb usb3: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.602538] usb usb3: SerialNumber: 1c1b000.usb
[ 3.607596] hub 3-0:1.0: USB hub found
[ 3.611414] hub 3-0:1.0: 1 port detected
[ 3.616147] ehci-platform 1c1c000.usb: EHCI Host Controller
[ 3.621785] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 4
[ 3.629756] ehci-platform 1c1c000.usb: irq 30, io mem 0x01c1c000
[ 3.649807] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[ 3.656106] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.664394] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.671632] usb usb4: Product: EHCI Host Controller
[ 3.676523] usb usb4: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.682541] usb usb4: SerialNumber: 1c1c000.usb
[ 3.687516] hub 4-0:1.0: USB hub found
[ 3.691316] hub 4-0:1.0: 1 port detected
[ 3.695960] ehci-platform 1c1d000.usb: EHCI Host Controller
[ 3.701575] ehci-platform 1c1d000.usb: new USB bus registered, assigned bus number 5
[ 3.709518] ehci-platform 1c1d000.usb: irq 32, io mem 0x01c1d000
[ 3.729805] ehci-platform 1c1d000.usb: USB 2.0 started, EHCI 1.00
[ 3.736082] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.744368] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.751605] usb usb5: Product: EHCI Host Controller
[ 3.756496] usb usb5: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.762514] usb usb5: SerialNumber: 1c1d000.usb
[ 3.767509] hub 5-0:1.0: USB hub found
[ 3.771324] hub 5-0:1.0: 1 port detected
[ 3.775955] ohci-platform 1c1b400.usb: Generic Platform OHCI controller
[ 3.782608] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 6
[ 3.790540] ohci-platform 1c1b400.usb: irq 29, io mem 0x01c1b400
[ 3.858004] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.866292] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.873527] usb usb6: Product: Generic Platform OHCI controller
[ 3.879460] usb usb6: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 3.885478] usb usb6: SerialNumber: 1c1b400.usb
[ 3.890763] hub 6-0:1.0: USB hub found
[ 3.894573] hub 6-0:1.0: 1 port detected
[ 3.899212] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[ 3.905870] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 7
[ 3.913809] ohci-platform 1c1c400.usb: irq 31, io mem 0x01c1c400
[ 3.981981] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.990269] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.997508] usb usb7: Product: Generic Platform OHCI controller
[ 4.003442] usb usb7: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 4.009461] usb usb7: SerialNumber: 1c1c400.usb
[ 4.014229] [drm] Cannot find any crtc or sizes
[ 4.018986] hub 7-0:1.0: USB hub found
[ 4.022795] hub 7-0:1.0: 1 port detected
[ 4.027418] ohci-platform 1c1d400.usb: Generic Platform OHCI controller
[ 4.034084] ohci-platform 1c1d400.usb: new USB bus registered, assigned bus number 8
[ 4.042004] ohci-platform 1c1d400.usb: irq 33, io mem 0x01c1d400
[ 4.109981] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 4.118268] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.125504] usb usb8: Product: Generic Platform OHCI controller
[ 4.131437] usb usb8: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 4.137455] usb usb8: SerialNumber: 1c1d400.usb
[ 4.142432] hub 8-0:1.0: USB hub found
[ 4.146238] hub 8-0:1.0: 1 port detected
[ 4.150914] usb_phy_generic usb_phy_generic.2.auto: usb_phy_generic.2.auto supply vcc not found, using dummy regulator
[ 4.161715] usb_phy_generic usb_phy_generic.2.auto: Linked as a consumer to regulator.0
[ 4.170047] musb-hdrc musb-hdrc.3.auto: MUSB HDRC host driver
[ 4.175823] musb-hdrc musb-hdrc.3.auto: new USB bus registered, assigned bus number 9
[ 4.183878] usb usb9: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 4.192172] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.199410] usb usb9: Product: MUSB HDRC host driver
[ 4.204388] usb usb9: Manufacturer: Linux 4.19.38-sunxi musb-hcd
[ 4.210406] usb usb9: SerialNumber: musb-hdrc.3.auto
[ 4.215783] hub 9-0:1.0: USB hub found
[ 4.219597] hub 9-0:1.0: 1 port detected
[ 4.224515] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01 00:00:18 UTC (18)
[ 4.232729] of_cfs_init
[ 4.235278] of_cfs_init: OK
[ 4.238238] vcc3v0: disabling
[ 4.241212] vcc5v0: disabling
[ 4.244194] usb0-vbus: disabling
[ 4.251124] Freeing unused kernel memory: 1024K
[ 4.265981] Run /init as init process
Loading, please wait...
starting version 237
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 ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.31.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
[ 5.453145] random: fast init done
/dev/mmcblk0p1: clean, 35989/56896 files, 192523/227328 blocks
done.
[ 5.503611] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 6.069742] systemd[1]: System time before build time, advancing clock.
[ 6.117366] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 6.139147] systemd[1]: Detected architecture arm.

Welcome to [1mUbuntu 18.04.2 LTS[0m!

[ 6.166696] systemd[1]: Set hostname to .
[ 6.721752] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.729130] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[[0;32m OK [0m] Set up automount Arbitrary Executab…rmats File System Automount Point.
[ 6.757965] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.764681] systemd[1]: Reached target Swap.
[[0;32m OK [0m] Reached target Swap.
[ 6.781904] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.789475] systemd[1]: Created slice User and Session Slice.
[[0;32m OK [0m] Created slice User and Session Slice.
[ 6.806177] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[[0;32m OK [0m] Started Dispatch Password Requests to Console Directory Watch.
[ 6.830048] systemd[1]: Started ntp-systemd-netif.path.
[[0;32m OK [0m] Started ntp-systemd-netif.path.
[ 6.845972] systemd[1]: Reached target Remote File Systems.
[[0;32m OK [0m] Reached target Remote File Systems.
[ 6.862693] systemd[1]: Created slice System Slice.
[[0;32m OK [0m] Created slice System Slice.
[[0;32m OK [0m] Listening on Journal Socket (/dev/log).
[[0;32m OK [0m] Listening on fsck to fsckd communication Socket.
[[0;32m OK [0m] Listening on Journal Audit Socket.
[[0;32m OK [0m] Created slice system-serial\x2dgetty.slice.
[[0;32m OK [0m] Reached target Slices.
[[0;32m OK [0m] Listening on Syslog Socket.
[[0;32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe.
[[0;32m OK [0m] Reached target System Time Synchronized.
[[0;32m OK [0m] Listening on Journal Socket.
Starting Journal Service...
Mounting POSIX Message Queue File System...
Starting Nameserver information manager...
Starting Create list of required st…ce nodes for the current kernel...
Starting Load Kernel Modules...
Starting Set the console keyboard layout...
Mounting Kernel Debug File System...
[[0;32m OK [0m] Started Forward Password Requests to Wall Directory Watch.
[[0;32m OK [0m] Reached target Local Encrypted Volumes.
Starting Remount Root and Kernel File Systems...
Starting Restore / save the current clock...
[[0;32m OK [0m] Listening on udev Kernel Socket.
[ 7.196592] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[[0;32m OK [0m] Listening on udev Control Socket.
Starting udev Coldplug all Devices...
[[0;32m OK [0m] Started Journal Service.
[[0;32m OK [0m] Mounted POSIX Message Queue File System.
[[0;32m OK [0m] Started Create list of required sta…vice nodes for the current kernel.
[[0;32m OK [0m] Started Load Kernel Modules.
[[0;32m OK [0m] Mounted Kernel Debug File System.
[[0;32m OK [0m] Started Remount Root and Kernel File Systems.
[[0;32m OK [0m] Started Restore / save the current clock.
[[0;32m OK [0m] Started Nameserver information manager.
[[0;32m OK [0m] Reached target Network (Pre).
Starting Load/Save Random Seed...
Starting Apply Kernel Variables...
Mounting Kernel Configuration File System...
Starting Create Static Device Nodes in /dev...
Starting Flush Journal to Persistent Storage...
[[0;32m OK [0m] Started Set the console keyboard layout.
[[0;32m OK [0m] Started Load/Save Random Seed.
[[0;32m OK [0m] Started Apply Kernel Variables.
[[0;32m OK [0m] Mounted Kernel Configuration File System.
[[0;32m OK [0m] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...
[[0;32m OK [0m] Reached target Local File Systems (Pre).
Mounting /tmp...
[[0;32m OK [0m] Mounted /tmp.
[[0;32m OK [0m] Reached target Local File Systems.
Starting Set console font and keymap...
Starting Raise network interfaces...
Starting Armbian ZRAM config...
[[0;32m OK [0m] Started udev Kernel Device Manager.
[[0;32m OK [0m] Started Flush Journal to Persistent Storage.
[[0;32m OK [0m] Started Set console font and keymap.
Starting Create Volatile Files and Directories...
[[0;32m OK [0m] Started udev Coldplug all Devices.
[[0;32m OK [0m] Started Create Volatile Files and Directories.

U-Boot SPL 2019.04-armbian (May 04 2019 - 02:06:03 +0200)
DRAM: 1024 MiB
Trying to boot from MMC1

U-Boot 2019.04-armbian (May 04 2019 - 02:06:03 +0200) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
DRAM: 1 GiB
MMC: mmc@1c0f000: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In: serial
Out: serial
Err: serial
Net: phy interface0
eth0: ethernet@1c30000
230454 bytes read in 12 ms (18.3 MiB/s)
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
USB4: USB EHCI 1.00
USB5: USB OHCI 1.0
USB6: USB EHCI 1.00
USB7: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning bus 4 for devices... 1 USB Device(s) found
scanning bus 5 for devices... 1 USB Device(s) found
scanning bus 6 for devices... 1 USB Device(s) found
scanning bus 7 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3585 bytes read in 1 ms (3.4 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 1 ms (148.4 KiB/s)
7989481 bytes read in 385 ms (19.8 MiB/s)
7489576 bytes read in 361 ms (19.8 MiB/s)
Found mainline kernel configuration
29890 bytes read in 8 ms (3.6 MiB/s)
4155 bytes read in 6 ms (675.8 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7989417 Bytes = 7.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
Loading Ramdisk to 49861000, end 49fff8a9 ... OK
Loading Device Tree to 497f1000, end 49860fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.19.38-sunxi (root@nightly) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.83 SMP Fri May 3 23:33:25 CEST 2019
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Xunlong Orange Pi PC
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 128 MiB at 0x75c00000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] random: get_random_bytes called from start_kernel+0x8d/0x3c6 with crng_init=0
[ 0.000000] percpu: Embedded 18 pages/cpu s41548 r8192 d23988 u73728
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260416
[ 0.000000] Kernel command line: root=UUID=792dc3df-48f8-4101-9640-3a9c73ec438b rootwait rootfstype=ext4 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=7 ubootpart=dfcbd449-01 ubootsource=mmc usb-storage.quirks= sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] allocated 1048576 bytes of page_ext
[ 0.000000] Memory: 883148K/1048576K available (9216K kernel code, 1004K rwdata, 2576K rodata, 1024K init, 331K bss, 34356K reserved, 131072K cma-reserved, 131060K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB)
[ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (10208 kB)
[ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB)
[ 0.000000] .data : 0x(ptrval) - 0x(ptrval) (1005 kB)
[ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 332 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 39959 entries in 79 pages
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 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: Using split EOI/Deactivate mode
[ 0.000000] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000005] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000017] Switching to timer-based delay loop, resolution 41ns
[ 0.000175] Console: colour dummy device 80x30
[ 0.000638] console [tty0] enabled
[ 0.000692] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[ 0.000719] pid_max: default: 32768 minimum: 301
[ 0.000922] Security Framework initialized
[ 0.000946] AppArmor: AppArmor disabled by boot time parameter
[ 0.001029] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001052] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001883] CPU: Testing write buffer coherency: ok
[ 0.002307] CPU0: update cpu_capacity 1024
[ 0.002329] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002807] Setting up static identity map for 0x40100000 - 0x40100054
[ 0.002975] rcu: Hierarchical SRCU implementation.
[ 0.003713] smp: Bringing up secondary CPUs ...
[ 0.014481] CPU1: update cpu_capacity 1024
[ 0.014487] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.025268] CPU2: update cpu_capacity 1024
[ 0.025273] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.035987] CPU3: update cpu_capacity 1024
[ 0.035993] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.036086] smp: Brought up 1 node, 4 CPUs
[ 0.036171] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[ 0.036186] CPU: All CPU(s) started in HYP mode.
[ 0.036197] CPU: Virtualization extensions available.
[ 0.037377] devtmpfs: initialized
[ 0.043854] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[ 0.044084] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.044118] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.048784] xor: measuring software checksum speed
[ 0.087947] arm4regs : 1255.000 MB/sec
[ 0.128007] 8regs : 748.000 MB/sec
[ 0.168068] 32regs : 766.000 MB/sec
[ 0.208130] neon : 1270.000 MB/sec
[ 0.208144] xor: using function: neon (1270.000 MB/sec)
[ 0.208217] pinctrl core: initialized pinctrl subsystem
[ 0.209140] NET: Registered protocol family 16
[ 0.211934] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[ 0.212450] audit: initializing netlink subsys (disabled)
[ 0.212619] audit: type=2000 audit(0.192:1): state=initialized audit_enabled=0 res=1
[ 0.213121] cpuidle: using governor ladder
[ 0.213168] cpuidle: using governor menu
[ 0.213660] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.213685] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.296639] raid6: int32x1 gen() 189 MB/s
[ 0.364543] raid6: int32x1 xor() 160 MB/s
[ 0.432593] raid6: int32x2 gen() 255 MB/s
[ 0.500646] raid6: int32x2 xor() 194 MB/s
[ 0.568795] raid6: int32x4 gen() 258 MB/s
[ 0.636923] raid6: int32x4 xor() 193 MB/s
[ 0.704936] raid6: int32x8 gen() 247 MB/s
[ 0.773152] raid6: int32x8 xor() 172 MB/s
[ 0.841195] raid6: neonx1 gen() 495 MB/s
[ 0.909213] raid6: neonx1 xor() 460 MB/s
[ 0.977382] raid6: neonx2 gen() 664 MB/s
[ 1.045429] raid6: neonx2 xor() 594 MB/s
[ 1.113582] raid6: neonx4 gen() 798 MB/s
[ 1.181647] raid6: neonx4 xor() 669 MB/s
[ 1.249723] raid6: neonx8 gen() 716 MB/s
[ 1.317829] raid6: neonx8 xor() 606 MB/s
[ 1.317844] raid6: using algorithm neonx4 gen() 798 MB/s
[ 1.317857] raid6: .... xor() 669 MB/s, rmw enabled
[ 1.317870] raid6: using neon recovery algorithm
[ 1.319241] SCSI subsystem initialized
[ 1.319665] usbcore: registered new interface driver usbfs
[ 1.319721] usbcore: registered new interface driver hub
[ 1.319799] usbcore: registered new device driver usb
[ 1.319981] media: Linux media interface: v0.10
[ 1.320025] videodev: Linux video capture interface: v2.00
[ 1.320201] pps_core: LinuxPPS API ver. 1 registered
[ 1.320218] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[ 1.320253] PTP clock support registered
[ 1.321781] clocksource: Switched to clocksource arch_sys_counter
[ 1.424870] VFS: Disk quotas dquot_6.6.0
[ 1.424968] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.432555] NET: Registered protocol family 2
[ 1.433270] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[ 1.433319] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 1.433419] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 1.433542] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.433665] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 1.433737] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 1.434029] NET: Registered protocol family 1
[ 1.434518] RPC: Registered named UNIX socket transport module.
[ 1.434541] RPC: Registered udp transport module.
[ 1.434554] RPC: Registered tcp transport module.
[ 1.434567] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.434819] Trying to unpack rootfs image as initramfs...
[ 1.887537] Freeing initrd memory: 7804K
[ 1.889282] Initialise system trusted keyrings
[ 1.889527] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 1.895237] zbud: loaded
[ 1.897312] NFS: Registering the id_resolver key type
[ 1.897358] Key type id_resolver registered
[ 1.897372] Key type id_legacy registered
[ 1.897393] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.897409] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 1.898578] JFS: nTxBlock = 7984, nTxLock = 63876
[ 1.907371] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 1.914695] Key type asymmetric registered
[ 1.914730] Asymmetric key parser 'x509' registered
[ 1.914796] bounce: pool size: 64 pages
[ 1.914861] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 1.915028] io scheduler noop registered
[ 1.915046] io scheduler deadline registered
[ 1.915252] io scheduler cfq registered (default)
[ 1.915272] io scheduler mq-deadline registered
[ 1.915285] io scheduler kyber registered
[ 1.915413] io scheduler bfq registered
[ 1.916541] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO
[ 1.920508] sun8i-h3-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[ 1.922060] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[ 1.969933] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[ 1.992284] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 42, base_baud = 1500000) is a U6_16550A
[ 2.880540] console [ttyS0] enabled
[ 2.907374] sun4i-drm display-engine: bound 1100000.mixer (ops 0xc0a85d08)
[ 2.914534] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0a83454)
[ 2.922269] sun8i-dw-hdmi 1ee0000.hdmi: 1ee0000.hdmi supply hvcc not found, using dummy regulator
[ 2.931216] sun8i-dw-hdmi 1ee0000.hdmi: Linked as a consumer to regulator.0
[ 2.938959] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy)
[ 2.948820] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver
[ 2.956576] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0a8578c)
[ 2.963389] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.970015] [drm] No driver support for vblank timestamp query.
[ 2.975991] [drm] Cannot find any crtc or sizes
[ 2.980964] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0
[ 2.991599] brd: module loaded
[ 3.000049] loop: module loaded
[ 3.005505] libphy: Fixed MDIO Bus: probed
[ 3.010222] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[ 3.016026] dwmac-sun8i 1c30000.ethernet: No regulator found
[ 3.022019] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000)
[ 3.031449] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
[ 3.038686] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
[ 3.045919] dwmac-sun8i 1c30000.ethernet: COE Type 2
[ 3.050897] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
[ 3.057693] dwmac-sun8i 1c30000.ethernet: Normal descriptors
[ 3.063361] dwmac-sun8i 1c30000.ethernet: Chain mode enabled
[ 3.069150] libphy: stmmac: probed
[ 3.073030] dwmac-sun8i 1c30000.ethernet: Found internal PHY node
[ 3.079233] libphy: mdio_mux: probed
[ 3.082844] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY
[ 3.089210] dwmac-sun8i 1c30000.ethernet: Powering internal PHY
[ 3.100588] libphy: mdio_mux: probed
[ 3.105098] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.111647] ehci-platform: EHCI generic platform driver
[ 3.117059] ehci-platform 1c1a000.usb: EHCI Host Controller
[ 3.122671] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1
[ 3.131155] ehci-platform 1c1a000.usb: irq 26, io mem 0x01c1a000
[ 3.149796] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00
[ 3.156158] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.164459] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.171697] usb usb1: Product: EHCI Host Controller
[ 3.176589] usb usb1: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.182608] usb usb1: SerialNumber: 1c1a000.usb
[ 3.187740] hub 1-0:1.0: USB hub found
[ 3.191568] hub 1-0:1.0: 1 port detected
[ 3.196335] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.202576] ohci-platform: OHCI generic platform driver
[ 3.207971] ohci-platform 1c1a400.usb: Generic Platform OHCI controller
[ 3.214617] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2
[ 3.222537] ohci-platform 1c1a400.usb: irq 27, io mem 0x01c1a400
[ 3.290051] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.298345] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.305584] usb usb2: Product: Generic Platform OHCI controller
[ 3.311516] usb usb2: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 3.317533] usb usb2: SerialNumber: 1c1a400.usb
[ 3.322546] hub 2-0:1.0: USB hub found
[ 3.326378] hub 2-0:1.0: 1 port detected
[ 3.331512] usbcore: registered new interface driver usb-storage
[ 3.338314] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
[ 3.345135] sun6i-rtc 1f00000.rtc: RTC enabled
[ 3.349811] i2c /dev entries driver
[ 3.355265] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
[ 3.363878] sunxi-mmc 1c0f000.mmc: Linked as a consumer to regulator.2
[ 3.370915] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[ 3.375643] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.381739] hidraw: raw HID events driver (C) Jiri Kosina
[ 3.387281] usbcore: registered new interface driver usbhid
[ 3.392874] usbhid: USB HID core driver
[ 3.400677] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB
[ 3.402990] Initializing XFRM netlink socket
[ 3.412641] NET: Registered protocol family 10
[ 3.434207] Segment Routing with IPv6
[ 3.438024] NET: Registered protocol family 17
[ 3.442513] NET: Registered protocol family 15
[ 3.447026] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 3.460037] 8021q: 802.1Q VLAN Support v1.8
[ 3.464514] Key type dns_resolver registered
[ 3.469205] Registering SWP/SWPB emulation handler
[ 3.474592] registered taskstats version 1
[ 3.478729] Loading compiled-in X.509 certificates
[ 3.483638] zswap: loaded using pool lzo/zbud
[ 3.489881] Btrfs loaded, crc32c=crc32c-generic
[ 3.502728] Key type encrypted registered
[ 3.514748] mmc0: host does not support reading read-only switch, assuming write-enable
[ 3.523795] sun4i-usb-phy 1c19400.phy: Linked as a consumer to regulator.4
[ 3.531662] ehci-platform 1c1b000.usb: EHCI Host Controller
[ 3.537287] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 3
[ 3.545320] mmc0: new high speed SDHC card at address aaaa
[ 3.551999] mmcblk0: mmc0:aaaa SU16G 14.8 GiB
[ 3.557034] ehci-platform 1c1b000.usb: irq 28, io mem 0x01c1b000
[ 3.564497] mmcblk0: p1
[ 3.577790] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00
[ 3.584117] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.592415] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.599653] usb usb3: Product: EHCI Host Controller
[ 3.604546] usb usb3: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.610565] usb usb3: SerialNumber: 1c1b000.usb
[ 3.615569] hub 3-0:1.0: USB hub found
[ 3.619375] hub 3-0:1.0: 1 port detected
[ 3.624159] ehci-platform 1c1c000.usb: EHCI Host Controller
[ 3.629794] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 4
[ 3.637908] ehci-platform 1c1c000.usb: irq 30, io mem 0x01c1c000
[ 3.657793] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[ 3.664094] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.672381] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.679618] usb usb4: Product: EHCI Host Controller
[ 3.684510] usb usb4: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.690529] usb usb4: SerialNumber: 1c1c000.usb
[ 3.695516] hub 4-0:1.0: USB hub found
[ 3.699321] hub 4-0:1.0: 1 port detected
[ 3.703967] ehci-platform 1c1d000.usb: EHCI Host Controller
[ 3.709592] ehci-platform 1c1d000.usb: new USB bus registered, assigned bus number 5
[ 3.717543] ehci-platform 1c1d000.usb: irq 32, io mem 0x01c1d000
[ 3.737791] ehci-platform 1c1d000.usb: USB 2.0 started, EHCI 1.00
[ 3.744074] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.752361] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.759596] usb usb5: Product: EHCI Host Controller
[ 3.764488] usb usb5: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.770507] usb usb5: SerialNumber: 1c1d000.usb
[ 3.775500] hub 5-0:1.0: USB hub found
[ 3.779311] hub 5-0:1.0: 1 port detected
[ 3.783933] ohci-platform 1c1b400.usb: Generic Platform OHCI controller
[ 3.790587] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 6
[ 3.798502] ohci-platform 1c1b400.usb: irq 29, io mem 0x01c1b400
[ 3.865991] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.874280] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.881515] usb usb6: Product: Generic Platform OHCI controller
[ 3.887448] usb usb6: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 3.893466] usb usb6: SerialNumber: 1c1b400.usb
[ 3.898759] hub 6-0:1.0: USB hub found
[ 3.902562] hub 6-0:1.0: 1 port detected
[ 3.907196] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[ 3.913857] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 7
[ 3.921784] ohci-platform 1c1c400.usb: irq 31, io mem 0x01c1c400
[ 3.989964] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.993839] [drm] Cannot find any crtc or sizes
[ 3.998244] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.010013] usb usb7: Product: Generic Platform OHCI controller
[ 4.015945] usb usb7: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 4.021963] usb usb7: SerialNumber: 1c1c400.usb
[ 4.026955] hub 7-0:1.0: USB hub found
[ 4.030762] hub 7-0:1.0: 1 port detected
[ 4.035389] ohci-platform 1c1d400.usb: Generic Platform OHCI controller
[ 4.042045] ohci-platform 1c1d400.usb: new USB bus registered, assigned bus number 8
[ 4.050009] ohci-platform 1c1d400.usb: irq 33, io mem 0x01c1d400
[ 4.117975] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 4.126266] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.133502] usb usb8: Product: Generic Platform OHCI controller
[ 4.139436] usb usb8: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 4.145454] usb usb8: SerialNumber: 1c1d400.usb
[ 4.150437] hub 8-0:1.0: USB hub found
[ 4.154242] hub 8-0:1.0: 1 port detected
[ 4.158927] usb_phy_generic usb_phy_generic.2.auto: usb_phy_generic.2.auto supply vcc not found, using dummy regulator
[ 4.169705] usb_phy_generic usb_phy_generic.2.auto: Linked as a consumer to regulator.0
[ 4.178022] musb-hdrc musb-hdrc.3.auto: MUSB HDRC host driver
[ 4.183801] musb-hdrc musb-hdrc.3.auto: new USB bus registered, assigned bus number 9
[ 4.191857] usb usb9: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 4.200151] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.207390] usb usb9: Product: MUSB HDRC host driver
[ 4.212367] usb usb9: Manufacturer: Linux 4.19.38-sunxi musb-hcd
[ 4.218386] usb usb9: SerialNumber: musb-hdrc.3.auto
[ 4.223772] hub 9-0:1.0: USB hub found
[ 4.227589] hub 9-0:1.0: 1 port detected
[ 4.232361] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01 00:00:40 UTC (40)
[ 4.240582] of_cfs_init
[ 4.243136] of_cfs_init: OK
[ 4.246092] vcc3v0: disabling
[ 4.249066] vcc5v0: disabling
[ 4.252049] usb0-vbus: disabling
[ 4.258974] Freeing unused kernel memory: 1024K
[ 4.269970] Run /init as init process
Loading, please wait...
starting version 237
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 ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.31.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
[ 5.439227] random: fast init done
/dev/mmcblk0p1: clean, 35989/56896 files, 192523/227328 blocks
done.
[ 5.529948] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 6.096140] systemd[1]: System time before build time, advancing clock.
[ 6.143815] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 6.165724] systemd[1]: Detected architecture arm.

Welcome to [1mUbuntu 18.04.2 LTS[0m!

[ 6.194674] systemd[1]: Set hostname to .
[ 6.749138] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.756288] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[[0;32m OK [0m] Started Forward Password Requests to Wall Directory Watch.
[ 6.777990] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.785615] systemd[1]: Created slice System Slice.
[[0;32m OK [0m] Created slice System Slice.
[ 6.801963] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.808665] systemd[1]: Reached target Swap.
[[0;32m OK [0m] Reached target Swap.
[ 6.826654] systemd[1]: Created slice User and Session Slice.
[[0;32m OK [0m] Created slice User and Session Slice.
[ 6.845916] systemd[1]: Reached target Slices.
[[0;32m OK [0m] Reached target Slices.
[ 6.862035] systemd[1]: Started ntp-systemd-netif.path.
[[0;32m OK [0m] Started ntp-systemd-netif.path.
[ 6.878296] systemd[1]: Listening on Journal Socket (/dev/log).
[[0;32m OK [0m] Listening on Journal Socket (/dev/log).
[[0;32m OK [0m] Listening on Syslog Socket.
[[0;32m OK [0m] Listening on udev Kernel Socket.
[[0;32m OK [0m] Set up automount Arbitrary Executab…rmats File System Automount Point.
[[0;32m OK [0m] Listening on Journal Audit Socket.
[[0;32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe.
[[0;32m OK [0m] Created slice system-serial\x2dgetty.slice.
[[0;32m OK [0m] Listening on fsck to fsckd communication Socket.
[[0;32m OK [0m] Reached target Remote File Systems.
[[0;32m OK [0m] Started Dispatch Password Requests to Console Directory Watch.
[[0;32m OK [0m] Reached target Local Encrypted Volumes.
[[0;32m OK [0m] Listening on udev Control Socket.
[[0;32m OK [0m] Reached target System Time Synchronized.
[[0;32m OK [0m] Listening on Journal Socket.
Starting udev Coldplug all Devices...
Starting Set the console keyboard layout...
Starting Nameserver information manager...
Mounting POSIX Message Queue File System...
Mounting Kernel Debug File System...
Starting Journal Service...
Starting Restore / save the current clock...
Starting Create list of required st…ce nodes for the current kernel...
Starting Remount Root and Kernel File Systems...
Starting Load Kernel Modules...
[ 7.268552] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
[[0;32m OK [0m] Mounted POSIX Message Queue File System.
[[0;32m OK [0m] Mounted Kernel Debug File System.
[[0;32m OK [0m] Started Restore / save the current clock.
[[0;32m OK [0m] Started Create list of required sta…vice nodes for the current kernel.
[[0;32m OK [0m] Started Remount Root and Kernel File Systems.
[[0;32m OK [0m] Started Load Kernel Modules.
[[0;32m OK [0m] Started Journal Service.
[[0;32m OK [0m] Started Nameserver information manager.
[[0;32m OK [0m] Reached target Network (Pre).
Starting Apply Kernel Variables...
Mounting Kernel Configuration File System...
Starting Load/Save Random Seed...
Starting Flush Journal to Persistent Storage...
Starting Create Static Device Nodes in /dev...
[[0;32m OK [0m] Mounted Kernel Configuration File System.
[[0;32m OK [0m] Started Set the console keyboard layout.
[[0;32m OK [0m] Started Apply Kernel Variables.
[[0;32m OK [0m] Started Load/Save Random Seed.
[[0;32m OK [0m] Started Create Static Device Nodes in /dev.
Starting udev Kernel Device Manager...
[[0;32m OK [0m] Reached target Local File Systems (Pre).
Mounting /tmp...
[[0;32m OK [0m] Mounted /tmp.
[[0;32m OK [0m] Reached target Local File Systems.
Starting Armbian ZRAM config...
Starting Set console font and keymap...
Starting Raise network interfaces...
[[0;32m OK [0m] Started udev Kernel Device Manager.
[[0;32m OK [0m] Started Flush Journal to Persistent Storage.
[[0;32m OK [0m] Started Set console font and keymap.
[[0;32m OK [0m] Started udev Coldplug all Devices.
Starting Create Volatile Files and Directories...
[[0;32m OK [0m] Started Create Volatile Files and Directories.
Starting Network Name Resolution...
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...

U-Boot SPL 2019.04-armbian (May 04 2019 - 02:06:03 +0200)
DRAM: 1024 MiB
Trying to boot from MMC1

U-Boot 2019.04-armbian (May 04 2019 - 02:06:03 +0200) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC
DRAM: 1 GiB
MMC: mmc@1c0f000: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In: serial
Out: serial
Err: serial
Net: phy interface0
eth0: ethernet@1c30000
230454 bytes read in 12 ms (18.3 MiB/s)
starting USB...
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
USB2: USB EHCI 1.00
USB3: USB OHCI 1.0
USB4: USB EHCI 1.00
USB5: USB OHCI 1.0
USB6: USB EHCI 1.00
USB7: USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning bus 2 for devices... 1 USB Device(s) found
scanning bus 3 for devices... 1 USB Device(s) found
scanning bus 4 for devices... 1 USB Device(s) found
scanning bus 5 for devices... 1 USB Device(s) found
scanning bus 6 for devices... 1 USB Device(s) found
scanning bus 7 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3585 bytes read in 1 ms (3.4 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 1 ms (148.4 KiB/s)
7989481 bytes read in 385 ms (19.8 MiB/s)
7489576 bytes read in 361 ms (19.8 MiB/s)
Found mainline kernel configuration
29890 bytes read in 8 ms (3.6 MiB/s)
4155 bytes read in 6 ms (675.8 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7989417 Bytes = 7.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
Loading Ramdisk to 49861000, end 49fff8a9 ... OK
Loading Device Tree to 497f1000, end 49860fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.19.38-sunxi (root@nightly) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.83 SMP Fri May 3 23:33:25 CEST 2019
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=50c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Xunlong Orange Pi PC
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 128 MiB at 0x75c00000
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] random: get_random_bytes called from start_kernel+0x8d/0x3c6 with crng_init=0
[ 0.000000] percpu: Embedded 18 pages/cpu s41548 r8192 d23988 u73728
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260416
[ 0.000000] Kernel command line: root=UUID=792dc3df-48f8-4101-9640-3a9c73ec438b rootwait rootfstype=ext4 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=7 ubootpart=dfcbd449-01 ubootsource=mmc usb-storage.quirks= sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] allocated 1048576 bytes of page_ext
[ 0.000000] Memory: 883148K/1048576K available (9216K kernel code, 1004K rwdata, 2576K rodata, 1024K init, 331K bss, 34356K reserved, 131072K cma-reserved, 131060K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB)
[ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (10208 kB)
[ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB)
[ 0.000000] .data : 0x(ptrval) - 0x(ptrval) (1005 kB)
[ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) ( 332 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 39959 entries in 79 pages
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 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: Using split EOI/Deactivate mode
[ 0.000000] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000005] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000017] Switching to timer-based delay loop, resolution 41ns
[ 0.000175] Console: colour dummy device 80x30
[ 0.000641] console [tty0] enabled
[ 0.000694] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[ 0.000722] pid_max: default: 32768 minimum: 301
[ 0.000927] Security Framework initialized
[ 0.000950] AppArmor: AppArmor disabled by boot time parameter
[ 0.001032] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001056] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001891] CPU: Testing write buffer coherency: ok
[ 0.002327] CPU0: update cpu_capacity 1024
[ 0.002347] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002835] Setting up static identity map for 0x40100000 - 0x40100054
[ 0.003003] rcu: Hierarchical SRCU implementation.
[ 0.003739] smp: Bringing up secondary CPUs ...
[ 0.014503] CPU1: update cpu_capacity 1024
[ 0.014508] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.025291] CPU2: update cpu_capacity 1024
[ 0.025296] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.036006] CPU3: update cpu_capacity 1024
[ 0.036011] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.036104] smp: Brought up 1 node, 4 CPUs
[ 0.036188] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[ 0.036202] CPU: All CPU(s) started in HYP mode.
[ 0.036214] CPU: Virtualization extensions available.
[ 0.037388] devtmpfs: initialized
[ 0.043870] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[ 0.044095] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.044130] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.048810] xor: measuring software checksum speed
[ 0.087966] arm4regs : 1255.000 MB/sec
[ 0.128027] 8regs : 748.000 MB/sec
[ 0.168089] 32regs : 766.000 MB/sec
[ 0.208150] neon : 1270.000 MB/sec
[ 0.208165] xor: using function: neon (1270.000 MB/sec)
[ 0.208238] pinctrl core: initialized pinctrl subsystem
[ 0.209160] NET: Registered protocol family 16
[ 0.211525] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[ 0.212018] audit: initializing netlink subsys (disabled)
[ 0.212214] audit: type=2000 audit(0.192:1): state=initialized audit_enabled=0 res=1
[ 0.212721] cpuidle: using governor ladder
[ 0.212767] cpuidle: using governor menu
[ 0.213261] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.213284] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.296664] raid6: int32x1 gen() 189 MB/s
[ 0.364577] raid6: int32x1 xor() 160 MB/s
[ 0.432611] raid6: int32x2 gen() 255 MB/s
[ 0.500683] raid6: int32x2 xor() 194 MB/s
[ 0.568830] raid6: int32x4 gen() 258 MB/s
[ 0.636961] raid6: int32x4 xor() 193 MB/s
[ 0.704958] raid6: int32x8 gen() 247 MB/s
[ 0.773175] raid6: int32x8 xor() 172 MB/s
[ 0.841214] raid6: neonx1 gen() 495 MB/s
[ 0.909264] raid6: neonx1 xor() 460 MB/s
[ 0.977399] raid6: neonx2 gen() 664 MB/s
[ 1.045463] raid6: neonx2 xor() 594 MB/s
[ 1.113606] raid6: neonx4 gen() 798 MB/s
[ 1.181655] raid6: neonx4 xor() 669 MB/s
[ 1.249751] raid6: neonx8 gen() 716 MB/s
[ 1.317853] raid6: neonx8 xor() 606 MB/s
[ 1.317868] raid6: using algorithm neonx4 gen() 798 MB/s
[ 1.317881] raid6: .... xor() 669 MB/s, rmw enabled
[ 1.317895] raid6: using neon recovery algorithm
[ 1.319256] SCSI subsystem initialized
[ 1.319653] usbcore: registered new interface driver usbfs
[ 1.319710] usbcore: registered new interface driver hub
[ 1.319783] usbcore: registered new device driver usb
[ 1.319965] media: Linux media interface: v0.10
[ 1.320007] videodev: Linux video capture interface: v2.00
[ 1.320136] pps_core: LinuxPPS API ver. 1 registered
[ 1.320151] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[ 1.320228] PTP clock support registered
[ 1.321746] clocksource: Switched to clocksource arch_sys_counter
[ 1.424785] VFS: Disk quotas dquot_6.6.0
[ 1.424889] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.432453] NET: Registered protocol family 2
[ 1.433157] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[ 1.433205] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 1.433302] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 1.433426] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.433545] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 1.433621] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 1.433912] NET: Registered protocol family 1
[ 1.434396] RPC: Registered named UNIX socket transport module.
[ 1.434417] RPC: Registered udp transport module.
[ 1.434430] RPC: Registered tcp transport module.
[ 1.434443] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.434703] Trying to unpack rootfs image as initramfs...
[ 1.887093] Freeing initrd memory: 7804K
[ 1.888837] Initialise system trusted keyrings
[ 1.889074] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[ 1.894777] zbud: loaded
[ 1.896887] NFS: Registering the id_resolver key type
[ 1.896927] Key type id_resolver registered
[ 1.896941] Key type id_legacy registered
[ 1.896962] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.896978] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 1.898132] JFS: nTxBlock = 7984, nTxLock = 63876
[ 1.906901] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 1.914561] Key type asymmetric registered
[ 1.914596] Asymmetric key parser 'x509' registered
[ 1.914679] bounce: pool size: 64 pages
[ 1.914767] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 1.914926] io scheduler noop registered
[ 1.914943] io scheduler deadline registered
[ 1.915148] io scheduler cfq registered (default)
[ 1.915168] io scheduler mq-deadline registered
[ 1.915182] io scheduler kyber registered
[ 1.915319] io scheduler bfq registered
[ 1.916425] sun4i-usb-phy 1c19400.phy: Couldn't request ID GPIO
[ 1.920398] sun8i-h3-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[ 1.921967] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[ 1.970332] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[ 1.992678] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 42, base_baud = 1500000) is a U6_16550A
[ 2.880952] console [ttyS0] enabled
[ 2.907805] sun4i-drm display-engine: bound 1100000.mixer (ops 0xc0a85d08)
[ 2.914949] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0a83454)
[ 2.922681] sun8i-dw-hdmi 1ee0000.hdmi: 1ee0000.hdmi supply hvcc not found, using dummy regulator
[ 2.931620] sun8i-dw-hdmi 1ee0000.hdmi: Linked as a consumer to regulator.0
[ 2.939383] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy)
[ 2.949235] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver
[ 2.956974] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0a8578c)
[ 2.963785] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.970410] [drm] No driver support for vblank timestamp query.
[ 2.976386] [drm] Cannot find any crtc or sizes
[ 2.981338] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0
[ 2.991968] brd: module loaded
[ 3.000451] loop: module loaded
[ 3.005977] libphy: Fixed MDIO Bus: probed
[ 3.010653] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[ 3.016458] dwmac-sun8i 1c30000.ethernet: No regulator found
[ 3.022437] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000)
[ 3.031870] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
[ 3.039113] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
[ 3.046351] dwmac-sun8i 1c30000.ethernet: COE Type 2
[ 3.051329] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
[ 3.058128] dwmac-sun8i 1c30000.ethernet: Normal descriptors
[ 3.063799] dwmac-sun8i 1c30000.ethernet: Chain mode enabled
[ 3.069584] libphy: stmmac: probed
[ 3.073472] dwmac-sun8i 1c30000.ethernet: Found internal PHY node
[ 3.079682] libphy: mdio_mux: probed
[ 3.083290] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY
[ 3.089660] dwmac-sun8i 1c30000.ethernet: Powering internal PHY
[ 3.100987] libphy: mdio_mux: probed
[ 3.105500] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.112046] ehci-platform: EHCI generic platform driver
[ 3.117472] ehci-platform 1c1a000.usb: EHCI Host Controller
[ 3.123092] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1
[ 3.131612] ehci-platform 1c1a000.usb: irq 26, io mem 0x01c1a000
[ 3.149755] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00
[ 3.156114] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.164408] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.171661] usb usb1: Product: EHCI Host Controller
[ 3.176550] usb usb1: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.182568] usb usb1: SerialNumber: 1c1a000.usb
[ 3.187661] hub 1-0:1.0: USB hub found
[ 3.191482] hub 1-0:1.0: 1 port detected
[ 3.196258] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.202495] ohci-platform: OHCI generic platform driver
[ 3.207893] ohci-platform 1c1a400.usb: Generic Platform OHCI controller
[ 3.214540] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2
[ 3.222476] ohci-platform 1c1a400.usb: irq 27, io mem 0x01c1a400
[ 3.290011] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.298302] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.305541] usb usb2: Product: Generic Platform OHCI controller
[ 3.311473] usb usb2: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 3.317492] usb usb2: SerialNumber: 1c1a400.usb
[ 3.322521] hub 2-0:1.0: USB hub found
[ 3.326376] hub 2-0:1.0: 1 port detected
[ 3.331493] usbcore: registered new interface driver usb-storage
[ 3.338310] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
[ 3.345131] sun6i-rtc 1f00000.rtc: RTC enabled
[ 3.349805] i2c /dev entries driver
[ 3.355272] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
[ 3.363906] sunxi-mmc 1c0f000.mmc: Linked as a consumer to regulator.2
[ 3.370941] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[ 3.375668] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.381775] hidraw: raw HID events driver (C) Jiri Kosina
[ 3.387301] usbcore: registered new interface driver usbhid
[ 3.392892] usbhid: USB HID core driver
[ 3.400696] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB
[ 3.403052] Initializing XFRM netlink socket
[ 3.412633] NET: Registered protocol family 10
[ 3.434361] Segment Routing with IPv6
[ 3.438167] NET: Registered protocol family 17
[ 3.442656] NET: Registered protocol family 15
[ 3.447168] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 3.460172] 8021q: 802.1Q VLAN Support v1.8
[ 3.464638] Key type dns_resolver registered
[ 3.469328] Registering SWP/SWPB emulation handler
[ 3.474705] registered taskstats version 1
[ 3.478839] Loading compiled-in X.509 certificates
[ 3.483764] zswap: loaded using pool lzo/zbud
[ 3.490038] Btrfs loaded, crc32c=crc32c-generic
[ 3.502759] mmc0: host does not support reading read-only switch, assuming write-enable
[ 3.502961] Key type encrypted registered
[ 3.514993] mmc0: new high speed SDHC card at address aaaa
[ 3.521985] mmcblk0: mmc0:aaaa SU16G 14.8 GiB
[ 3.523914] sun4i-usb-phy 1c19400.phy: Linked as a consumer to regulator.4
[ 3.534443] ehci-platform 1c1b000.usb: EHCI Host Controller
[ 3.535133] mmcblk0: p1
[ 3.540066] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 3
[ 3.550771] ehci-platform 1c1b000.usb: irq 28, io mem 0x01c1b000
[ 3.569765] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00
[ 3.576095] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.584383] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.591617] usb usb3: Product: EHCI Host Controller
[ 3.596509] usb usb3: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.602528] usb usb3: SerialNumber: 1c1b000.usb
[ 3.607560] hub 3-0:1.0: USB hub found
[ 3.611374] hub 3-0:1.0: 1 port detected
[ 3.616096] ehci-platform 1c1c000.usb: EHCI Host Controller
[ 3.621719] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 4
[ 3.629679] ehci-platform 1c1c000.usb: irq 30, io mem 0x01c1c000
[ 3.649762] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[ 3.656042] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.664329] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.671566] usb usb4: Product: EHCI Host Controller
[ 3.676458] usb usb4: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.682476] usb usb4: SerialNumber: 1c1c000.usb
[ 3.687467] hub 4-0:1.0: USB hub found
[ 3.691269] hub 4-0:1.0: 1 port detected
[ 3.695896] ehci-platform 1c1d000.usb: EHCI Host Controller
[ 3.701509] ehci-platform 1c1d000.usb: new USB bus registered, assigned bus number 5
[ 3.709460] ehci-platform 1c1d000.usb: irq 32, io mem 0x01c1d000
[ 3.729759] ehci-platform 1c1d000.usb: USB 2.0 started, EHCI 1.00
[ 3.736035] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 3.744321] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.751557] usb usb5: Product: EHCI Host Controller
[ 3.756449] usb usb5: Manufacturer: Linux 4.19.38-sunxi ehci_hcd
[ 3.762467] usb usb5: SerialNumber: 1c1d000.usb
[ 3.767438] hub 5-0:1.0: USB hub found
[ 3.771241] hub 5-0:1.0: 1 port detected
[ 3.775860] ohci-platform 1c1b400.usb: Generic Platform OHCI controller
[ 3.782523] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 6
[ 3.790441] ohci-platform 1c1b400.usb: irq 29, io mem 0x01c1b400
[ 3.857964] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.866252] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.873488] usb usb6: Product: Generic Platform OHCI controller
[ 3.879421] usb usb6: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 3.885439] usb usb6: SerialNumber: 1c1b400.usb
[ 3.890684] hub 6-0:1.0: USB hub found
[ 3.894487] hub 6-0:1.0: 1 port detected
[ 3.899100] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[ 3.905758] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 7
[ 3.913671] ohci-platform 1c1c400.usb: irq 31, io mem 0x01c1c400
[ 3.981931] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 3.990220] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.993810] [drm] Cannot find any crtc or sizes
[ 3.997454] usb usb7: Product: Generic Platform OHCI controller
[ 4.007916] usb usb7: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 4.013934] usb usb7: SerialNumber: 1c1c400.usb
[ 4.018928] hub 7-0:1.0: USB hub found
[ 4.022735] hub 7-0:1.0: 1 port detected
[ 4.027366] ohci-platform 1c1d400.usb: Generic Platform OHCI controller
[ 4.034022] ohci-platform 1c1d400.usb: new USB bus registered, assigned bus number 8
[ 4.041951] ohci-platform 1c1d400.usb: irq 33, io mem 0x01c1d400
[ 4.109935] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
[ 4.118223] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.125459] usb usb8: Product: Generic Platform OHCI controller
[ 4.131393] usb usb8: Manufacturer: Linux 4.19.38-sunxi ohci_hcd
[ 4.137412] usb usb8: SerialNumber: 1c1d400.usb
[ 4.142401] hub 8-0:1.0: USB hub found
[ 4.146205] hub 8-0:1.0: 1 port detected
[ 4.150881] usb_phy_generic usb_phy_generic.2.auto: usb_phy_generic.2.auto supply vcc not found, using dummy regulator
[ 4.161657] usb_phy_generic usb_phy_generic.2.auto: Linked as a consumer to regulator.0
[ 4.169985] musb-hdrc musb-hdrc.3.auto: MUSB HDRC host driver
[ 4.175761] musb-hdrc musb-hdrc.3.auto: new USB bus registered, assigned bus number 9
[ 4.183816] usb usb9: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 4.192109] usb usb9: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.199347] usb usb9: Product: MUSB HDRC host driver
[ 4.204325] usb usb9: Manufacturer: Linux 4.19.38-sunxi musb-hcd
[ 4.210343] usb usb9: SerialNumber: musb-hdrc.3.auto
[ 4.215737] hub 9-0:1.0: USB hub found
[ 4.219546] hub 9-0:1.0: 1 port detected
[ 4.224499] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01 00:01:02 UTC (62)
[ 4.232720] of_cfs_init
[ 4.235275] of_cfs_init: OK
[ 4.238229] vcc3v0: disabling
[ 4.241204] vcc5v0: disabling
[ 4.244185] usb0-vbus: disabling
[ 4.251114] Freeing unused kernel memory: 1024K
[ 4.265941] Run /init as init process
Loading, please wait...
starting version 237
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 ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.31.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1: recovering journal
[ 5.443556] random: fast init done
/dev/mmcblk0p1: clean, 35989/56896 files, 192523/227328 blocks
done.
[ 5.485417] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 6.052403] systemd[1]: System time before build time, advancing clock.
[ 6.100005] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 6.121989] systemd[1]: Detected architecture arm.

Welcome to [1mUbuntu 18.04.2 LTS[0m!

[ 6.150648] systemd[1]: Set hostname to .
[ 6.705934] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.713289] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[[0;32m OK [0m] Set up automount Arbitrary Executab…rmats File System Automount Point.
[ 6.741978] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.748696] systemd[1]: Reached target Remote File Systems.
[[0;32m OK [0m] Reached target Remote File Systems.
[ 6.765856] random: systemd: uninitialized urandom read (16 bytes read)
[ 6.772761] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[[0;32m OK [0m] Started Forward Password Requests to Wall Directory Watch.
[ 6.793903] systemd[1]: Reached target System Time Synchronized.
[[0;32m OK [0m] Reached target System Time Synchronized.
[ 6.810815] systemd[1]: Created slice System Slice.
[[0;32m OK [0m] Created slice System Slice.
[ 6.830263] systemd[1]: Listening on fsck to fsckd communication Socket.
[[0;32m OK [0m] Listening on fsck to fsckd communication Socket.
[ 6.850286] systemd[1]: Listening on Journal Socket.
[[0;32m OK [0m] Listening on Journal Socket.
[[0;32m OK [0m] Listening on Journal Socket (/dev/log).
[[0;32m OK [0m] Listening on /dev/initctl Compatibility Named Pipe.
[[0;32m OK [0m] Listening on Journal Audit Socket.
Starting Set the console keyboard layout...
[[0;32m OK [0m] Listening on Syslog Socket.
Starting Journal Service...
Starting Nameserver information manager...
Mounting Kernel Debug File System...
Starting Restore / save the current clock...
[[0;32m OK [0m] Started Dispatch Password Requests to Console Directory Watch.
[[0;32m OK [0m] Reached target Local Encrypted Volumes.
Mounting POSIX Message Queue File System...
Starting Load Kernel Modules...
[[0;32m OK [0m] Listening on udev Kernel Socket.
[[0;32m OK [0m] Created slice User and Session Slice.
[[0;32m OK [0m] Reached target Slices.
[[0;32m OK [0m] Reached target Swap.
[[0;32m OK [0m] Listening on udev Control Socket.
Starting udev Coldplug all Devices...
[[0;32m OK [0m] Created slice system-serial\x2dgetty.slice.
Starting Remount Root and Kernel File Systems...
[[0;32m OK [0m] Started ntp-systemd-netif.path.
[ 7.213453] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro
Starting Create list of required st…ce nodes for the current kernel...
[[0;32m OK [0m] Started Journal Service.
[[0;32m OK [0m] Mounted Kernel Debug File System.
[[0;32m OK [0m] Started Restore / save the current clock.
[[0;32m OK [0m] Mounted POSIX Message Queue File System.
[[0;32m OK [0m] Started Load Kernel Modules.
[[0;32m OK [0m] Started Remount Root and Kernel File Systems.
[[0;32m OK [0m] Started Create list of required sta…vice nodes for the current kernel.
[[0;32m OK [0m] Started Set the console keyboard layout.
[[0;32m OK [0m] Started Nameserver information manager.
[[0;32m OK [0m] Reached target Network (Pre).
Starting Create Static Device Nodes in /dev...
Starting Load/Save Random Seed...
Starting Apply Kernel Variables...
Mounting Kernel Configuration File System...
Starting Flush Journal to Persistent Storage...
[[0;32m OK [0m] Started Load/Save Random Seed.
[[0;32m OK [0m] Mounted Kernel Configuration File System.
[[0;32m OK [0m] Started Create Static Device Nodes in /dev.
[[0;32m OK [0m] Started Apply Kernel Variables.
[[0;32m OK [0m] Reached target Local File Systems (Pre).
Mounting /tmp...
Starting udev Kernel Device Manager...
[[0;32m OK [0m] Mounted /tmp.
[[0;32m OK [0m] Reached target Local File Systems.
Starting Raise network interfaces...
Starting Armbian ZRAM config...
Starting Set console font and keymap...
[[0;32m OK [0m] Started Flush Journal to Persistent Storage.
[[0;32m OK [0m] Started Set console font and keymap.
[[0;32m OK [0m] Started udev Kernel Device Manager.
Starting Create Volatile Files and Directories...
[[0;32m OK [0m] Started udev Coldplug all Devices.
[[0;32m OK [0m] Started Create Volatile Files and Directories.
Starting Network Name Resolution...
Starting Network Time Synchronization...
Starting Update UTMP about System Boot/Shutdown...
[[0;32m OK [0m] Started Entropy daemon using the HAVEGE algorithm.

filesystem error on one time

Sun, 21 Apr 2019 13:57:53 +0000

Hello, there

I have got three device`s in one room;

Image`s for this three device`s was burned to ssd card`s on this week (at 17.04.2019)

Today, in the same time (Apr 21 06:47:03) they all fall down with same error (form syslog):

Apr 21 06:20:52 localhost systemd[1]: Starting Daily apt upgrade and clean activities...
Apr 21 06:20:52 localhost systemd[1]: Started Daily apt upgrade and clean activities.
Apr 21 06:25:01 localhost CRON[8132]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 21 06:25:01 localhost CRON[8131]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Apr 21 06:30:01 localhost CRON[8283]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Apr 21 06:35:01 localhost CRON[8347]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 21 06:45:01 localhost CRON[8454]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
Apr 21 06:45:01 localhost CRON[8455]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Apr 21 06:47:01 localhost CRON[8484]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))
Apr 21 06:47:03 localhost kernel: [192981.845014] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530053: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=28672, inode=4294967295, rec_len=65535, name_len=255, size=4096
Apr 21 06:47:03 localhost kernel: [192981.941193] Aborting journal on device mmcblk0p1-8.
Apr 21 06:47:03 localhost kernel: [192981.953977] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
Apr 21 06:47:03 localhost kernel: [192981.964478] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530052: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=24576, inode=4294967295, rec_len=65535, name_len=255, size=4096

in kern log i see same error:

Apr 21 06:47:03 localhost kernel: [192981.845014] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530053: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=28672, inode=4294967295, rec_len=65535, name_len=255, size=4096
Apr 21 06:47:03 localhost kernel: [192981.941193] Aborting journal on device mmcblk0p1-8.
Apr 21 06:47:03 localhost kernel: [192981.953977] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
Apr 21 06:47:03 localhost kernel: [192981.964478] EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1006: inode #172314: block 530052: comm mandb: bad entry in directory: rec_len % 4 != 0 - offset=24576, inode=4294967295, rec_len=65535, name_len=255, size=4096

Environment:

BOARD=orangepipc2
BOARD_NAME="Orange Pi PC2"
BOARDFAMILY=sun50iw2
VERSION=5.67
LINUXFAMILY=sunxi64
BRANCH=next
ARCH=arm64
IMAGE_TYPE=custom
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image

In syslog I gote line bofore error =

Apr 21 06:47:01 localhost CRON[8484]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))

can it be that cron.weekly was do something wrong?

How you think, what was going wrong?

Card full using Octoprint

Sat, 30 Mar 2019 20:41:40 +0000

Usage of /: 100% of 15G

Last login: Sat Mar 30 13:41:33 2019 from 192.168.1.238

root@Ender3:~# df
Filesystem     1K-blocks     Used Available Use% Mounted on
udev              184064        0    184064   0% /dev
tmpfs              50508     2812     47696   6% /run
/dev/mmcblk0p1 14696736 14483996     37088 100% /
tmpfs             252532        0    252532   0% /dev/shm
tmpfs               5120        4      5116   1% /run/lock
tmpfs             252532        0    252532   0% /sys/fs/cgroup
tmpfs             252532        4    252528   1% /tmp
/dev/zram0         49584    31828     14172 70% /var/log
tmpfs              50504        0     50504   0% /run/user/0

Every time I use Octoprint it seems to fill the disk by a lot more than the size of the file I upload.

How do I reduce the size of mmcblk0p1 or do a clean up?

5v 2a phone charger dude

Sat, 16 Mar 2019 18:24:39 +0000

I am use a phone charger to power my Orange pi lite and u-boot show freeze in "dram".

Is phone charger the problem?

Or other thing

Edit:

Now I am using a opi lite 5v 3a for powering and the same

OrangePi R1 - Overheating

Fri, 08 Jun 2018 22:48:51 +0000

Good afternoon, I am seeking advice on cooling my Orange Pi R1, it seems to overheat after about 6 hours of idel even with a heatsink on it.

Currently i have a desk fan moving air around it and it holding around 31c with ambient room temperature around 25c.

The device is just running a network bridge, pihole, and vnstat (hourly).

CPU is on average 1-3% and memory use is 53%.

Touching the device it is hard as it is physically hot. The USB hat is not installed. Any ideas?

Orange Pi One Bionic image issues

Wed, 23 Jan 2019 16:16:37 +0000

HI there .I am facing issues regarding installing the latest image (Ubuntu Bionic ) for Orange Pi One . The normal boot procedure involving u-boot fails as the board attempts to boot from the network . The u-boot console says no fdt found . This is the console log of the boot process .

U-Boot SPL 2018.05-armbian (Jan 09 2019 - 19:39:57 +0100)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2018.05-armbian (Jan 09 2019 - 19:39:57 +0100) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi One
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
Failed (-5)
In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
230454 bytes read in 23 ms (9.6 MiB/s)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3798 bytes read in 15 ms (247.1 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 12 ms (11.7 KiB/s)
8126319 bytes read in 414 ms (18.7 MiB/s)
6906920 bytes read in 352 ms (18.7 MiB/s)
Found mainline kernel configuration
28858 bytes read in 52 ms (541 KiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr " command.
Aborting!
4155 bytes read in 54 ms (74.2 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
Wrong image format for "source" command
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8126255 Bytes = 7.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...

Device 0: device type unknown
... is now current device
** Bad device usb 0 **
** Bad device usb 0 **
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10

Abort
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-02-81-58-b5-28-97
_sun8i_emac_eth_init: Timeout
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
ethernet@1c30000 Waiting for PHY auto negotiation to complete.user interrupt!
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
ethernet@1c30000 Waiting for PHY auto negotiation to complete..user interrupt!
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
ethernet@1c30000 Waiting for PHY auto negotiation to complete..user interrupt!
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
ethernet@1c30000 Waiting for PHY auto negotiation to complete.user interrupt!
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set

Do I need to pass the address manually via uboot? I am stumped . Please help .

SD Card not booting with Armbian

Sat, 29 Dec 2018 18:33:52 +0000

I'm trying to boot a Banana Pi M2U that I know is not supported, but I cannot make it even start booting with a SD Card.

Let me explain.

If I use the MFR Debian, image I flash the card and can boot. Another thing is the botched job the image is, that even no init is well done and at the end, the official Debian build ends failing and locking the board or entering in an eternal reboot with some kernel panics in between.

Then I tried Armbian. I downloaded an unsupported image for my board flash it (with balenaEtcher, as recommended) but the board does not boot. A normal boot means a red led, blue and green on. In this case only red one.

What I think is happening is I'm generating a wrong image, but I follow the steps in the documentation, that is un-zip2 the file, run Balena, flash the card and ready to go. As said, with original Banana Pi Debian image and same SD Card, (SanDisk Ultra 32GB) it boots. I've even installed a virtual Ubuunty and generated an image from sources, as described in documentation. Same problem with the generated image.

Once the card has been flashed, my iMAC says "unrecognized disk" for Armbian image, but original Banana image shows a mounted FAT partition called "boot_sd". That is why I think I'm mistaking something when flashing the Armbian image.

I've tried a Centos image from an original PI and at least it starts booting. It does nothing but at least the blue and green led flashes for a time. But with a Armbian it is completely dead.

Any idea?

Thanks.

Adequate power supply for the Orange Pi Zero?

Tue, 13 Feb 2018 07:25:42 +0000

I've got an OPi Zero v1.1 for a home project, It was supposed to be something very simple, connect the board to wifi, make a web app for external control and switch a power relay, I did finished it and everything was working fine but I had sudden disconnections and one day just didn't wanted to reconnect, I've read before about how this board has an horrible wifi chip and trying to avoid further headaches I went and bought an USB WiFi dongle TP-LINK_TL-WN725N, I got it today and connected it to the board using its 13 pin header, then I powered it on via micro usb and worked right out the box, no need for extra config, to finish it off I rewired it to this little box where I have it tucked away aaaand didn't work...

After testing why I found that the wifi would work only on the microusb power with my laptop, inside the box where it was working before I have this AC/DC 5v 1A module which power the OPi through 5v pin of the expansion header and relay (1 channel model), whenever I tried using the converter in the box the wifi didn't work, looked like it didn't even power since there was no led activity of the dongle, but the board itself was powered and booted correctly, or at least that is what I believe because the board led would behave the same as when it would boot and connect to wifi.

In short, when I power it via microusb usb wifi works, when I use the 5v 1A converter mentioned above it doesn't, and for a last test I disconnected the relay from the circuit to feed just the OPi but wifi still wouldn't work, then I read this answer about usb power, if right it would mean that my laptop isn't supplying more than the ac/dc module, or is it wrong?, also I have video output and onboard wifi disabled, I really don't know what I'm missing here.

USB-C powered boards -- important information

Tue, 02 Oct 2018 12:09:38 +0000

Some SBCs for which Armbian images are available (supported, wip or csc) can be powered via USB-C. Depending on its implementation, some pitfalls must be considered. This short tutorial should give you an overview.

'Dumb mode':

The USB-C connector is used similar to the microUSB connectors in previous SBCs. Means that the pitfalls must be considered when you choose a charger and cable. See the following thread for some background:

Additionally, those boards may be problematic with PD compatible chargers. Without a proper PD implementation those PSUs will only deliver up to 900mA at 5V (4.5W). In case you have a board which isn't PD compliant you should go for a PSU without PD implementation aka 'dumb PSU'. Voltage drop from cable and voltage drop of the PSU at hight load itself must be kept in mind similar to microUSB powered boards!

SBCs which don't support PD (also boards not supported in any form by Armbian):

Vim
Vim2
NanoPi M4
NanoPi NEO4
Orange Pi 4

PD mode (power detection):

With a proper PD implementation, a PD capable PSU can deliver 'more juice' on demand. It's also possible to deliver power at higher voltage (between 5V and 20V). See graphic (12V is missing here):

(source: https://www.digikey.ch/en/articles/techzone/2017/mar/designing-in-usb-type-c-and-using-power-delivery-for-rapid-charging)

To ensure proper powering you should go for a PD compliant PSU. See documentation of your board to see which PD modes are supported within your SBC. Boards known to support PD-Mode:

ROC-RK3399-PC (Renegade Elite)

Authentication token manipulation error

Thu, 22 Jun 2017 14:18:11 +0000

Go figure, I haven't had much luck with my Orange Pi Zero after it appeared that attaching the expansion board fragged the motherboard somewhat (see my journey at).

The confounding factor was that multiple SD image burns, using WIN32DiskImager, prior to expansion board insertion on the Orange Pi Zero, were fine for about a week of experiments. Immediately expansion board was inserted it all went downhill - literally.

Thus, without any other evidence it appeared a hardware frag.

Problems like this not seen previously on my microPython, ODROID-W, ODROID-C1, RaspingBreathberry Doodle Pi, BeagleBone Black, BeagleBoard XM - all using WIN32DiskImager.

Indeed, parallella distro was burnt to one of the SD from the Orange Pi experiments, using WIN32DiskImager, and no problem there.

Orange Pi Zero SD card was finally re-burnt, as suggested on forum, using Etcher.

I note no warning on download page about why Etcher should be used (it is a "can" implying optional). There is some explanation in the docs but, as tech authoring standards are not being used, it wasn't wrapped as NOTE or WARNING so is lost on page buried in website.

If, like me, you go to the archive to get the debian server, and you haven't come across etcher (and the mention of it is at bottom of the parent Orange Pi Zero page so is easily missed), and you have gotten by with WIN32DiskImager for yonks, you will also be burnt.

I can't corroborate claims of FS corruption as I wasn't using 3-pin serial - thus missing out on early login messages.

Otherwise, seems to be running again, for now, with same distro as before/during problems (but using Etcher instead of WIN32DiskImager).

Thanks to all those that helped me understand the problem.

RETRACTION!

I ran the system for two days, checking in occasionally by browsing into see node-red and emqttd running. This morning I could not connect. I checked and IP address had disappeared which was a problem seen on the WIN32DiskImager burnt version of the distro. The problem cleared after 3 reboots (that is 2 reboots came up no IP set and then third with IP set). I had done nothing but reboot (so no fiddling of config in between). The piece de resistance was that I hung the device by opening up nmtui and going to the connection window. That was a problem I was plagued with on the WIN32DiskImager burn version of distro and can now confirm it occurs on Etcher burnt distro.

The quirk with the nmtui that noticed was that, with the fresh Etcher burnt SD card, I used nmtui and the window was blue colour. Now that the system has degraded the nmtui window opens white on black background with connection highlighted in yellow. Exactly the same behaviour on WIN32DI burnt SD card. So, the quirk seems that system is hanging in mid draw of nmtui connection window.

So, the behaviour seems characterised as a slow degrading of system over time that persists between reboots. The IP dropout likely will flit in and out now, and then become permanent, as it did with WIN32DI burnt SD card.

I am going back to my device fragged (somehow) by expansion board.

I have two more OPiZ coming so I will try same process to built SD card, using Etcher, to see if there is a difference with board that haven't had expansion board inserted (originally I have a working device that would not boot once expansion board was inserted).

[Solved] OPZero don't work then from first boot.

Sun, 07 Oct 2018 08:11:10 +0000

Hi all,

I beginner for OPZero, i followed steps and boot my device with Armbian 5.59 Ubuntu Bionic. It's running first boot no problem, i did login to ubuntu with serial, SSH, and some processes install armbianmonitor and connected port:8888 no problem but i did restart device, its no working. I plug TTL-usb and view serial monitor and this results:

https://www.copypaste.io/detail?id=1538899137

U-Boot SPL 2018.05-armbian (Aug 21 2018 - 21:44:47 +0200)
DRAM: 512 MiB
Trying to boot from MMC1

U-Boot 2018.05-armbian (Aug 21 2018 - 21:44:47 +0200) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi Zero
DRAM: 512 MiB
MMC: SUNXI SD/MMC: 0
Loading Environment from EXT4… fs_devread read outside partition 4294967288
Failed to mount ext2 filesystem…

** Unable to use mmc 0:auto for loading the env **
Failed (-5)
In: serial
Out: serial
Err: serial
Net: phy interface0
eth0: ethernet@1c30000
fs_devread read outside partition 4294967288
Failed to mount ext2 filesystem…
** Unrecognized filesystem type **
fs_devread read outside partition 4294967288
Failed to mount ext2 filesystem…
** Unrecognized filesystem type **
starting USB…
USB0: USB EHCI 1.00
USB1: USB OHCI 1.0
scanning bus 0 for devices… 1 USB Device(s) found
scanning usb for storage devices… 0 Storage Device(s) found
Autoboot in 1 seconds, press to stop
switch to partitions #0, OK
mmc0 is current device
fs_devread read outside partition 4294967288
Failed to mount ext2 filesystem…
** Unrecognized filesystem type **

Device 0: device type unknown
… is now current device
** Bad device usb 0 **
** Bad device usb 0 **
ethernet@1c30000 Waiting for PHY auto negotiation to complete. done
BOOTP broadcast 1
DHCP client bound to address 192.168.1.103 (22 ms)
*** Warning: no boot file name; using 'C0A80167.img'
Using ethernet@1c30000 device
TFTP from server 0.0.0.0; our IP address is 192.168.1.103; sending through gateway 192.168.1.1
Filename 'C0A80167.img'.
Load address: 0x42000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-02-42-43-d8-5d-93
*** ERROR: serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A80167 *** ERROR:serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A8016
*** ERROR: serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A801 *** ERROR:serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A80
*** ERROR: serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A8 *** ERROR:serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C0A
*** ERROR: serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0 *** ERROR:serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/C
*** ERROR: serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi *** ERROR:serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
*** ERROR: serverip' not set missing environment variable: bootfile Retrieving file: pxelinux.cfg/default *** ERROR:serverip' not set
Config file not found
BOOTP broadcast 1
DHCP client bound to address 192.168.1.103 (13 ms)
Using ethernet@1c30000 device
TFTP from server 0.0.0.0; our IP address is 192.168.1.103; sending through gateway 192.168.1.1
Filename 'boot.scr.uimg'.
Load address: 0x43100000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
=>

So how can I fix it issue?

Thank you for all.

OrangePI PC reboots during apt-upgrade

Tue, 25 Sep 2018 15:45:36 +0000

Hi,

some times ago I installed an Orange PI with armbian-5.31 (stable, kernel 3.4.113).

Now I needed to upgrade some installed packages, but when I run apt-get upgrade at some point the process interrupts and the system reboots.

Now I have an interrupted upgrade process, and each time I try to restart this process with sudo dpkg --configure -a

the system try to upgrade the policykit-1, it reboots.

Looking at messages or syslog I don't find any particular error.

Any suggestion where to look for this problem ?

Watchdog process could be responsible for such reboots ?

Thanks in advance for any suggestion

Testing ARMbian 5.59 en OPI+2

Sun, 30 Sep 2018 08:37:36 +0000

Tested new versions ARMbian Server 5.59 Kernel 4.14 in OPI + 2.

Armbian Bionic: It starts but hangs when opening kernel.

Armbian Stretch: It works but I have not been able to change locales or keyboard language. armbian-config does not perform its function.

UN saludo.

Orange Pi issues with PoE

Thu, 29 Jun 2017 15:27:57 +0000

I'm a little out of ideas what is rong ? My OPiPC is functioning well with all 12v 19v and 24v + converter to 5v but OPi+2E sometimes flickers red led, one time functioned but mostly dosen't.

Clearly I'm using methode 2

https://de.aliexpress.com/item/Hot-POE-Cable-Passive-Power-Over-Ethernet-Adapter-Cable-POE-Splitter-Injector-Power-Supply-Module-12/32695459204.html?

https://de.aliexpress.com/item/New-Banana-Pi-M2-USB-Switch-Cable-USB-Wire-To-DC-Port-Charging-Switch-Cable-For/32521915580.html?

https://de.aliexpress.com/item/Fine-6-24V-12V-24V-to-5V-3A-CAR-USB-Charger-Module-DC-Buck-step-down/32807024340.html?

https://de.aliexpress.com/item/Free-Shipping-New-Arrival-DC-6V-40V-To-5V-3A-Double-USB-Charge-DC-DC-Step/32728305031.html?

if im not over POE OPi+2E functions with both converters

Can't start network interface

Sun, 23 Sep 2018 14:01:09 +0000

Hello to you all!

I've been running Armbian on H3 board (Orang Pi One) for some time now, with occasional problems that have been resolved one way or another. When I say 'another', I mean by writing image again to sd card, when it gets corrupted somehow. I've been there 3 or 4 times in more than a year. I don't know if it happens because of power loss or whatever, never been able to troubleshoot it and get it back up.

I thought I had a similar situation a few days ago, but when I connected to serial, I noticed that it boots, but can't start network interface. I get the following message when ifup eth0:

/bin/ip: error while loading shared libraries: /usr/lib/arm-linux-gnueabihf/libelf.so.1: Unable to run arch-specific checks

I can't find anything reasonable with the help of favorite web search engine, do you have some idea?

Thanks!

SOLVED (POWER RELATED ISSUE) - Orange Pi Win Plus not booting with current stable Armbian Xenial

Tue, 10 Jul 2018 19:03:26 +0000

Hello everybody!

I have an Orange Pi Win Plus and I'm trying to boot the current stable release of the Armbian Xenial but I get no video output on the hdmi and sometimes the board turns itself off. I've tried both server and desktop versions but the issue remains.

My current setup:
5.01V@2.0A PSU;

Usb mouse and keyboard;

Used Etcher to burn the images on the sd card;
Tried to boot using 2 different sd cards, both 8gb, the result is the same;

Tested images are Armbian_5.41_Orangepiwin_Ubuntu_xenial_default_3.10.107_desktop.img and Armbian_5.41_Orangepiwin_Ubuntu_xenial_default_3.10.107.img

The console output on the ttl port shows this:

U-Boot 2014.07 (Feb 11 2018 - 19:21:28) Allwinner Technology

uboot commit : 6f37e5cf6a65b0b10455d12dbd631effabe765ec

rsb: secure monitor exist
[      0.404]pmbus:   ready
[      0.407][ARISC] :arisc initialize
[      0.736][ARISC] :arisc_dvfs_cfg_vf_table: support only one vf_table
[SCP] :sunxi-arisc driver begin startup 2
[SCP] :arisc_para size:1a8
[SCP] :arisc version: [v0.1.76]
[SCP] :sunxi-arisc driver v1.10 is starting
[      0.864][ARISC] :sunxi-arisc driver startup succeeded
[      0.898]PMU: AXP81X
[      0.900]PMU: AXP81X found
bat_vol=0, ratio=100
[      0.906]PMU: dcdc2 1100
[      0.909]PMU: cpux 1008 Mhz,AXI=336 Mhz
PLL6=600 Mhz,AHB1=200 Mhz, APB1=100Mhz AHB2=300Mhz MBus=400Mhz
device_type = 3253, onoff=1
dcdc1_vol = 3300, onoff=1
dcdc2_vol = 1100, onoff=1
dcdc6_vol = 1100, onoff=1
aldo1_vol = 2800, onoff=0
aldo2_vol = 1800, onoff=1
aldo3_vol = 3000, onoff=1
dldo1_vol = 3300, onoff=0
dldo2_vol = 3300, onoff=0
dldo3_vol = 2800, onoff=0
dldo4_vol = 3300, onoff=1
eldo1_vol = 1800, onoff=1
eldo2_vol = 1800, onoff=0
eldo3_vol = 1800, onoff=0
fldo1_vol = 1200, onoff=0
fldo2_vol = 1100, onoff=1
gpio0_vol = 3100, onoff=0
vbus not exist
no battery, limit to dc
run key detect
no key found
no uart input
DRAM:  2 GiB
fdt addr: 0xb6ebce80
Relocation Offset is: 75f0f000
In:    serial
Out:   serial
Err:   serial
gic: sec monitor mode
[      1.219]start
drv_disp_init
init_clocks: finish init_clocks.
enable power vcc-hdmi-33, ret=0
drv_disp_init finish
boot_disp.output_disp=0
boot_disp.output_type=3
boot_disp.output_mode=10
fetch script data boot_disp.auto_hpd fail
disp0 device type(4) enable
attched ok, mgr0<-->device1, type=4, mode=10
[      1.587]end
workmode = 0,storage type = 1
[      1.591]MMC:        0
[mmc]: mmc driver ver 2015-06-03 13:50:00
SUNXI SD/MMC: 0
[mmc]: start mmc_calibrate_delay_unit, don't access device...
[mmc]: delay chain cal done, sample: 185(ps)
[mmc]: media type 0x0
[mmc]: Wrong media type 0x0
[mmc]: ************Try SD card 0************
[mmc]: host caps: 0x27
[mmc]: MID 02 PSN 9c0001b2
[mmc]: PNM SA08G -- 0x53-41-30-38-47
[mmc]: PRV 0.4
[mmc]: MDT m-1 y-2010
[mmc]: speed mode     : HSSDR52/SDR25
[mmc]: clock          : 50000000 Hz
[mmc]: bus_width      : 4 bit
[mmc]: user capacity  : 7604 MB
[mmc]: ************SD/MMC 0 init OK!!!************
[mmc]: erase_grp_size      : 0x1WrBlk*0x200=0x200 Byte
[mmc]: secure_feature      : 0x0
[mmc]: secure_removal_type : 0x0
[      1.778]sunxi flash init ok

** Unable to use mmc 0:1 for loading the env **
Using default environment

--------fastboot partitions--------
mbr not exist
base bootcmd=run mmcbootcmd
bootcmd set setargs_mmc
key 0
recovery key high 12, low 10
fastboot key high 6, low 4
no misc partition is found
to be run cmd=run mmcbootcmd
update dtb dram start
update dtb dram  end
serial is: 64107884c8080c2e060f
check for ANX9807
get Pine64 model from DRAM size
DRAM >512M
Pine64 model: pine64-plus
no battery exist
sunxi bmp: unable to open file /boot/bootlogo.bmp
[      2.069]inter uboot shell
autoboot in 3 seconds, Press s or  to abort
4984 bytes read in 24 ms (202.1 KiB/s)
Booting with script ...
## Executing script at 41000000
166 bytes read in 19 ms (7.8 KiB/s)
69613 bytes read in 38 ms (1.7 MiB/s)
4353809 bytes read in 374 ms (11.1 MiB/s)
12636952 bytes read in 1002 ms (12 MiB/s)
Image lacks image_size field, assuming 16MiB
## Loading init Ramdisk from Legacy Image at 45300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4353745 Bytes = 4.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 45000000
   Booting using the fdt blob at 0x45000000
   reserving fdt memory region: addr=41010000 size=10000
   reserving fdt memory region: addr=41020000 size=800
   reserving fdt memory region: addr=40100000 size=4000
   reserving fdt memory region: addr=40104000 size=1000
   reserving fdt memory region: addr=40105000 size=1000
   reserving fdt memory region: addr=45000000 size=12000
   Loading Ramdisk to b6a8f000, end b6eb5ed1 ... OK
   Loading Device Tree to 44fea000, end 44ffefff ... OK

Starting kernel ...

[mmc]: MMC Device 2 not found
[mmc]: mmc 2 not find, so not exit
INFO:    BL3-1: Next image address = 0x41080000
INFO:    BL3-1: Next image spsr = 0x3c9

I've also tested the Armbian_5.51.180709_Orangepiwin_Ubuntu_bionic_dev_4.18.0-rc3.img, this image shows output through hdmi but the boot stops sometimes. I've managed to boot this image but sometimes when it boots it freezes soon after I do the login. Usually console output when it doesn't boots looks like this:

U-Boot 2018.07-rc1-armbian (Jul 10 2018 - 00:17:35 +0000) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: OrangePi Win/Win Plus
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0
Loading Environment from FAT... Unable to use mmc 0:1... Failed (-5)
In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
230454 bytes read in 31 ms (7.1 MiB/s)
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB OHCI 1.0
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press  to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3090 bytes read in 21 ms (143.6 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
153 bytes read in 17 ms (8.8 KiB/s)
13616 bytes read in 35 ms (379.9 KiB/s)
** File not found /boot/dtb/allwinner/overlay/sun50i-a64-fixup.scr **
 ** fs_devread read error **
** File not found /boot/uInitrd **
 ** fs_devread read error **
** File not found /boot/Image **
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    8056392 Bytes = 7.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...

Device 0: device type unknown
... is now current device
** Bad device usb 0 **
** Bad device usb 0 **
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
=>

Any hints on this? It's an issue or am I missing something?

Thank you!

Package list error due to filesystem corruption

Sat, 21 Jul 2018 14:12:39 +0000

I was faced with a very weird erroneous behavior. The distribution and board are the same. the board is 4GB.

the oddity is in that apt-get cannot do anything complaining that it is "unable to parse package list file" /var/lib/apt/armbian.com_dists_InRelease. sorry the name of the file could be written not 100% precise, but you probably get what the file is.

You know what I found inside the file where looked into it? In the middle of it there were some bullshit network configuration related and inserted by NetworkManager (there was a comment inside - "inserted/merged by network manager")! I very doubt it is normal. Removing that didn't help, because apparently it's not enough to recover the file. I barely could imagine what the thing could happen for that infamous networkmanager to corrupt this file, how? Anyway, any ideas on how I could recover the packaging system to make it "great again"? Has anyone encountered this before?

I almost didn't anything with the board before noticing that. what I did:

set up static IP

uninstalled unattended-upgrades

resized (offline) ext4 volume where the root resides and the appropriate partition. namely shrank them. But, everything worked after that just fine. hardly that bug could be from this?

Dpkg error - triggers ci file contains unknown directive syntax

Mon, 23 Jul 2018 14:59:03 +0000

Hi, if I want install any package (try mc, kodi) get this error:

root@cubieboard2:~# sudo apt-get install mc
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libssh2-1 mc-data
Suggested packages:
  arj catdvi | texlive-binaries dbview djvulibre-bin genisoimage gv links
  | w3m | lynx odt2txt python-boto python-tz xpdf | pdf-viewer zip
The following NEW packages will be installed:
  libssh2-1 mc mc-data
0 upgraded, 3 newly installed, 0 to remove and 34 not upgraded.
Need to get 0 B/1,676 kB of archives.
After this operation, 6,817 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: error: triggers ci file contains unknown directive syntax
E: Sub-process /usr/bin/dpkg returned an error code (2)

Any suggestions?

use image: Armbian_5.38_Cubieboard2_Ubuntu_xenial_default_3.4.113_desktop.7z and Armbian_5.38_Micro_Ubuntu_xenial_default_3.4.113_desktop.7z

4MB sectors - aka "Optimizing Linux with cheap flash drives"

Tue, 10 Jul 2018 04:47:05 +0000

Just came across this
Might be useful for developers
Improved Optimization/speed and wear leveling of software on SD Cards

https://lwn.net/Articles/428584/

It's an older report...but it might help since devices are getting bigger and the need to keep the cards alive longer is getting more and more important

My take on the document is that 4MB blocks or when writing the image
Write to SD card using Linux:
- Find the device (eg: /dev/sdb1) you need to write to by using blkid or mount.
- Double check that you have the correct dev path for your SD card (eg: /dev/sdb1).
- Unmount the SD card and all its partitions by using umount /dev/sdb?.
- Write the image using dd if=/path/to/DietPi_vXX.img of=/dev/sdb.

sudo dd if=/path/to/DietPi_vXX.img of=/dev/sdb bs=4096

sudo dd if=/path/to/DietPi_vXX.img of=/dev/sdb bs=4M

single user mode ?

Sun, 20 May 2018 01:05:45 +0000

Something happened to my armbian, I executed rather simple find --execute grep ... troughout the whole sd card, it froze and will not boot any more .. attached a hdmi display (orangepi one is the board in question) and I see it boots the kernel and then just "rebooting..." and reboots and does that in a loop...

on a normal linux running grub bootloader I'd stop the boot and add "single" to the kernel parameters, it will ignore all the boot scripts and after booting the kernel would drop me directly into shell as root so I can investigate wth is going on... anything similar I can do to armbian?

Opi PC Plus

Sun, 29 Apr 2018 21:02:51 +0000

Hello, I've try several version of armbian (stable, testing, debian, ubuntu) but I stopped at the same point :

U-boot 2017.09-armbian (Nov 22 2017 - 16:49:59 +0100) Allwinner Technology

CPU: Allwinner H3 (SUN8I 1680)

Model: Xunlong Orange Pi PC Plus

DRAM : 1GiB

MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1

*** Warning - bad CRC, using default environment

In : serial

Out: vidconsole

Err: vidconsole

Net : phy interface0

eth0: ethernet@1c30000

With ethernet or without : no change

With keybord, the five last lines aren't here

Doesn't understand what this mean.

Odroid HC1 SATA disk switches between sda and sdb

Sun, 14 Jan 2018 18:54:30 +0000

Hi, I have 3 Odroid HC1. All have a 2TB SATA disk attached. I am using Armbian_5.35_Odroidxu4_Ubuntu_xenial_next_4.9.61.img, and the armbian-config to copy the rootfs to the SATA disk. I have used ext4 and btrfs. Actually used btrfs from the start, but I got some weird error after running the HC1 for a couple of days, so that my open command, would return -bash: /sbin/blkid: Input/output error on any input. This is just an example. Didn't really know what was going on, I rebooted, and then could not login through ssh anymore. I assume rootfs gone, and reinstalled the HC1 again, copied over rootfs with armbian-config using btrfs.

Few days later I had the same issue again, so reinstalled again but changed to ext4 (to see if this makes a difference). Now I have that same issue also with ext4 as the rootfs. So it's unrelated to ext4/btrfs I assume. I noticed that the SATA disk from originally sda changed to sdb. Have a look at lsblk below. I restarted the node and it came back working, but now using sda again. You also find the dmesg outpout from when the node wasn't working properly anymore.

I think the trouble started at line: [ 7432.871964] usb 4-1: USB disconnect, device number 2 (maybe these disks go sleep)? I am not running any big computations on them. The power supplies are 5V/4A

I have 2 HC1 with a 2TB Seagate Barracuda and the 3rd HC1 with a 2TB Seagate Firecuda. Both HC1 with each the Barracuda had that issue so far. One with ext4, one with btrfs. The disks are new. The setup with the Firecuda didn't break yet.

I have tried to read SMART but didn't get that working: smartctl -a -d usbjmicron /dev/sda

Any help much appreciated.

root@hc1-node-1:~# lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT

zram7 253:7 0 124.6M 0 disk [SWAP]

zram5 253:5 0 124.6M 0 disk [SWAP]

sdb 8:16 0 1.8T 0 disk

└─sdb1 8:17 0 1.8T 0 part /

zram3 253:3 0 124.6M 0 disk [SWAP]

zram1 253:1 0 124.6M 0 disk [SWAP]

mmcblk1 179:0 0 14.9G 0 disk

└─mmcblk1p1 179:1 0 14.7G 0 part /media/mmcboot

zram6 253:6 0 124.6M 0 disk [SWAP]

zram4 253:4 0 124.6M 0 disk [SWAP]

zram2 253:2 0 124.6M 0 disk [SWAP]

zram0 253:0 0 124.6M 0 disk [SWAP]

root@hc1-node-1:~# blkid

-bash: /sbin/blkid: Input/output error

root@hc1-node-1:~#

dmesg.txt

Initial login (via SSH) can't set password

Sat, 30 Dec 2017 00:57:10 +0000

I have Armbian (headless/server edition, no GUI) booting nicely on an OrangePi.
I got the IP address from my router and SSH'd into the Pi with success.

When I log in, I am asked to change the password. After I do, I receive no error message or indication that the password changed, I am simply logged out.

When I reconnect, the password is back to the default of 1234 and it asks me to change the password. I'm stuck in this loop.

How do I change the password and get it to save?

Orange Pi One is not booting from SD Card....

Sat, 09 Dec 2017 00:38:13 +0000

Hi,

I am trying to boot up my OP1 with debian jessie and ubuntu images but both of them are not booting.

If I attach a USB drive and it has the same image written on it as on SD Card then it boots from USB drive. Am I missing something? Plz Help. I got JPEGs of the screen when it tries to boot but fails with error but I cannot manage to upload them.

Thanks

Orange Pi Prime: USB problem under heavy I/O (and CPU) load

Sat, 09 Dec 2017 17:37:45 +0000

Just for information (i know there is no support): under heavy load i have such error (for 3 times on different re-runs)

Spoiler

[76957.139777] monerod[1798]: undefined instruction: pc=000000000054a3e0

[76957.139788] Code: 00942f40 00000000 00000402 00001c60 (00000000)

[76988.126797] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: IN

[76988.126811] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 03 00 08 18 00 00 08 00

[76988.130108] scsi host0: uas_eh_device_reset_handler start

[76988.254794] usb 4-1: reset high-speed USB device number 2 using ehci-platform

[76988.411953] scsi host0: uas_eh_device_reset_handler success

[81988.438809] monerod[9811]: unhandled level 0 translation fault (11) at 0xfffffffffffffffe, esr 0x92000004, in libc-2.23.so[ffff9ac8c000+12e000]

[81988.438835] CPU: 0 PID: 9811 Comm: monerod Tainted: G C 4.14.4-sunxi64 #11

[81988.438837] Hardware name: Xunlong Orange Pi Prime (DT)

[81988.438841] task: ffff80007411c380 task.stack: ffff000010718000

[81988.438847] PC is at 0xffff9acfe9a8

[81988.438850] LR is at 0xffff9b325bc4

[81988.438853] pc : [<0000ffff9acfe9a8>] lr : [<0000ffff9b325bc4>] pstate: 80000000

[81988.438854] sp : 0000ffffe529ebc0

[81988.438857] x29: 0000ffffe529ebc0 x28: 0000000000000000

[81988.438862] x27: 00000000033b0fa0 x26: 00000000033b0fc0

[81988.438866] x25: 00000000033af000 x24: 0000000000000001

[81988.438871] x23: 0000ffffe529ee08 x22: 000000000054ba70

[81988.438875] x21: 0000000000000000 x20: 0000000000000000

[81988.438880] x19: 0000ffffe529ec58 x18: 0000000000000a03

[81988.438884] x17: 0000ffff9b33b110 x16: 0000ffff9acfe988

[81988.438889] x15: 0000ffff9b5dc000 x14: 0000000000000000

[81988.438894] x13: 6436336136666334 x12: 6135356266363861

[81988.438898] x11: 0000000000000030 x10: 0101010101010101

[81988.438903] x9 : 000000000054c180 x8 : 0000000000943538

[81988.438907] x7 : 0000000000000000 x6 : 000000000094354c

[81988.438912] x5 : 0000000000000000 x4 : 0000000000000001

[81988.438916] x3 : 0000000000000000 x2 : 0000000000000000

[81988.438920] x1 : fffffffffffffff6 x0 : 0000000000000006

Orange Pi PC2 doesn't boot

Fri, 01 Dec 2017 16:51:12 +0000

Hi! I have some troubles with my OPI.

I was install Armbian on the microSd (black SanDisk 16gb class 10) with Rufus. After insert card into OPI and connect HDMI and power cable on screen i have next:

U-Boot 2017.09-armbian (Now 20 2017 - 02:47:53 +0100) Allwinner Technology

CPU:   Allwinner H5 (SUN50I)
Model: OrangePi PC 2
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   phy interface7
eth0: ethernet@1c30000
230454 bytes read in 151 ms (1.5 MiB/s)
There is no valid bmp file at the given address
starting USB...
USB0:	USB EHCI 1.00
USB1:	USB OHCI 1.0
Autoboot in 1 seconds, press "Space" to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3100 bytes read in 197 ms (14.6 KiB/s)
#executing script at 4fc00000
Wring image format for "source" command
SCRIPT FAILED: continuint...
  
Device 0: device type unknown
... is now current device
** Bad device usb 0 **
** Bad device usb 0 **
Bootp broadcast 1
Bootp broadcast 2
Bootp broadcast 3
...

After another some "BooTP broadcast " around 10 - 15 they print:

Retry time exceeded: starting again
missing enviroment variable: pxeuuid
missing enviroment variable: bootfile

and some errors related to 'serverip' not set, print config not found and start again.

I try to install another OS (like Ubuntu, Debian desktop and server version) but they give me purple screen.

Can someone help me?

disgusting theme: emmc (hardkernel) and memory card

Mon, 20 Nov 2017 13:09:18 +0000

Allthough I know that this was discussed several times

I didn't get a satisfying answer.

I checked both with cfdisk with that result of emmc:

gpt:
Festplatte: /dev/sdc
Größe: 14,7 GiB, 15758000128 Bytes, 30777344 Sektoren
Bezeichner: gpt, Identifikator: 2953EEFC-99A8-443F-8AA2-F17BC4D94878

Gerät Anfang Ende Sektoren Größe Typ
>> Freier Bereich 2048 30777343 30775296 14,7G

dos:
Festplatte: /dev/sdc
Größe: 14,7 GiB, 15758000128 Bytes, 30777344 Sektoren
Bezeichner: dos, Identifikator: 0xc4d40d74

Gerät Boot Anfang Ende Sektoren Größe Kn Typ
>> Freier Bereich 2048 30777343 30775296 14,7G

sgi:
Festplatte: /dev/sdc
Größe: 14,7 GiB, 15758000128 Bytes, 30777344 Sektoren
Bezeichnung: sgi

Gerät Anfang Ende Sektoren Größe Kn Typ Attr.
>> /dev/sdc9 0 4095 4096 2M 0 SGI volhdr
/dev/sdc11 0 30777343 30777344 14,7G 6 SGI-Datenträger
Freier Bereich 4096 30777343 30773248 14,7G

sun:
Festplatte: /dev/sdc
Größe: 14,7 GiB, 15758000128 Bytes, 30777344 Sektoren
Bezeichnung: sun

Gerät Anfang Ende Sektoren Größe Kn Typ Markierungen
>> /dev/sdc1 0 30674943 30674944 14,6G 83 Linux native
/dev/sdc2 30674944 30777343 102400 50M 82 Linux Swap u
/dev/sdc3 0 30777343 30777344 14,7G 5 Gesamte Festplatte

But which filesystem do I really have? How many partitions? How to mount it?

Writing cannot be done nor copying. Formatting doesn't help. With sfdisk writing only can

happen one time. Just a single time. Then everything disappeared again.

The card was used successfully. Afterwards only microSD can be used until it crashed.

And now it shows the similar result. Where can I go to for further reading?

Bananapi suddenly powers off

Sun, 19 Nov 2017 10:50:05 +0000

I tried the Armbian_5.34.171119_Bananapi_Debian_stretch_next_4.13.13: it seems to have problems, when using an usb hub. Connected when booting after showing the login it seems to have a power loss. Connecting the hub after login it take some time and then the same: the BananaPi is complete off. I already checked the cables an power supply.