On 1 April 2018 at 03:58, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote: [..] Maybe it is not obvious but NanoPi Neo2 has *only* serial console and what I'v sent it is output fron serial console. kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

On 1 April 2018 at 04:20, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote: [..] Probably it was other NanoPi. This is how NanoPi Neo2 looks like: http://www.friendlyarm.com/index.php?route=product/product&product_id... So .. do you have any suggestions about what I can do to diagnose/debug this issue? This output which I've copied was after I found that ssk-keygen services has been frozen as well. I've generated necessary keys b mounting root fs on my laptop and generate those keys using ssh-keygen commands. Initially I've been thinking that just generate those keys takes to long. Now to be hones I think that freezing ssh-keygen services and initial-setup may have te same cause. However none of those services have been failing after some time by timeout which is strange. Why I think that it is strange? Because IMO default systemd settings should be failing if service cannot finish in some time defined globally or per service. It is only explanation why everything waits in infinite loop. Any suggestions about change systemd settings to fail service if it will not start within let's say 60s? kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

On 1 April 2018 at 12:02, Tomasz Kłoczko <kloczko.tomasz(a)gmail.com&gt; wrote: ]..] I've repeat test today with today Fedora-Minimal-Rawhide-20180401.n.0.aarch64.raw.xz image. Here is end part of the boot log on serial console: [ OK ] Started Rebuild Dynamic Linker Cache. Starting Update is Completed... [ OK ] Started Update is Completed. [ OK ] Reached target System Initialization. [ OK ] Listening on Open-iSCSI iscsid Socket. [ OK ] Listening on SSSD Secrets Service responder socket. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Started dnf makecache timer. [ OK ] Reached target Timers. [ OK ] Listening on Open-iSCSI iscsiuio Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting OpenSSH ecdsa Server Key Generation... Starting Login Service... [ OK ] Started D-Bus System Message Bus. Starting Initial Setup configuration program... [ OK ] Started Secure Boot DBX (blacklist) updater. Starting OpenSSH ed25519 Server Key Generation... [ OK ] Started Hardware RNG Entropy Gatherer Daemon. Starting firewalld - dynamic firewall daemon... Starting NTP client/server... Starting OpenSSH rsa Server Key Generation... [FAILED] Failed to start OpenSSH ecdsa Server Key Generation. See 'systemctl status sshd-keygen(a)ecdsa.service&#39; for details. [FAILED] Failed to start OpenSSH ed25519 Server Key Generation. See 'systemctl status sshd-keygen(a)ed25519.service&#39; for details. [FAILED] Failed to start OpenSSH rsa Server Key Generation. See 'systemctl status sshd-keygen(a)rsa.service&#39; for details. After those fails I've left NanoPi Neo2 running with connected eth cable. After about an hour next part of the console logs appeared: [ 3573.381667] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 3573.392157] RTL8211E Gigabit Ethernet 0.2:07: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=0.2:07, irq=POLL) [ 3573.419960] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 3573.427816] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 3573.439070] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 3576.559307] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 3576.568165] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 3753.881940] DMA-API: cacheline tracking ENOMEM, dma-debug disabled [ 3753.888624] DMA-API: cacheline tracking ENOMEM, dma-debug disabled [ 4242.259031] python3 (1410) used greatest stack depth: 9632 bytes left [ OK ] Started D-Bus System Message Bus. [FAILED] Failed to start Login Service. See 'systemctl status systemd-logind.service' for details. [FAILED] Failed to start Network Manager. See 'systemctl status NetworkManager.service' for details. [ OK ] Stopped Login Service. Starting Login Service... [ OK ] Started Initial Setup configuration program. [ OK ] Stopped Network Manager. Starting Network Manager... [ OK ] Reached target Login Prompts (Pre). [ OK ] Started Serial Getty on ttyS0. [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. Fedora 29 (Rawhide) Kernel 4.16.0-0.rc7.git1.1.fc29.aarch64 on an aarch64 (ttyS0) localhost login: root Password: Login incorrect Despite that I've wrote image on the sd card with --norootpass I was not able to login. I've left NanoPi running and started doing other things and after about another hour next batch of boot log messages on SC appeared: [ OK ] Started D-Bus System Message Bus. [ OK ] Stopped OpenSSH server daemon. [ OK ] Stopped target sshd-keygen.target. Stopping sshd-keygen.target. Starting OpenSSH ecdsa Server Key Generation... Starting OpenSSH rsa Server Key Generation... Starting OpenSSH ed25519 Server Key Generation... [FAILED] Failed to start Network Manager. See 'systemctl status NetworkManager.service' for details. [FAILED] Failed to start Login Service. See 'systemctl status systemd-logind.service' for details. [FAILED] Failed to start OpenSSH ecdsa Server Key Generation. See 'systemctl status sshd-keygen(a)ecdsa.service&#39; for details. [FAILED] Failed to start OpenSSH rsa Server Key Generation. See 'systemctl status sshd-keygen(a)rsa.service&#39; for details. [FAILED] Failed to start OpenSSH ed25519 Server Key Generation. See 'systemctl status sshd-keygen(a)ed25519.service&#39; for details. [ OK ] Stopped Network Manager. [ OK ] Started D-Bus System Message Bus. Starting Network Manager... [ OK ] Stopped Login Service. Starting Login Service... [ OK ] Stopped Serial Getty on ttyS0. [ OK ] Started Serial Getty on ttyS0. [ OK ] Reached target sshd-keygen.target. Starting OpenSSH server daemon... [ OK ] Started D-Bus System Message Bus. [FAILED] Failed to start OpenSSH server daemon. See 'systemctl status sshd.service' for details. [ OK ] Started D-Bus System Message Bus. Fedora 29 (Rawhide) Kernel 4.16.0-0.rc7.git1.1.fc29.aarch64 on an aarch64 (ttyS0) localhost login: root Password: Login incorrect So: 1) looks like first try to generate ssh keys fails for some still unknown reasons 2) --norootpass and --addkey options are not working (I was not able to login over ssh when ssh at least started). Here is full command line which I've used to write image: # fedora-arm-image-installer --image=Fedora-Minimal-Rawhide-20180401.n.0.aarch64.raw.xz --media=/dev/sdd --target=nanopi_neo2 --norootpass -y --addconsole --addkey=id_rsa.pub Will try latter to have look for some logs left on the image after initial boot. I'll try lated as well with today image and RPi3. Looking as well for any other suggestions about what can I do more to diagnose those issues. kloczek -- Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH

On Mon, Apr 2, 2018 at 6:01 PM, Tomasz Kłoczko <kloczko.tomasz(a)gmail.com&gt; wrote: Should be fixed in GA I only see one. Patches welcome. There are other use cases other than just that. I don't know what that provides, please link to documentation That won't ever happen, SELinux is a key security feature and if there's bugs we file them and get them fixed. In most cases when the host name is changed you need to reboot to make sure all things referencing the hostname are updated, there's nothing new or special here. Or the bugs are reported and fixed for the next image creation.