Hi,
there is a problem with post install first boot process on some boards.
For example on board pcDuino3 Nano and based on [1] probably on
Cubieboard too.
After installing latest Fedora 25 nightly image(*.sda.raw.xz) on sd card
using fedora-arm-image-installer, system "hangs" during last boot phase
when it runs initial-setup service.
What really happens is that on attached monitor, there is nothing
indicating what is happening and no login prompt, because initial-setup
is actually running, but it is not attached to tty1. With serial-usb
cable from other computer, I've verified that it is in fact running on
ttyS0 console.
I'm not sure what is proper solution and what is the problem exactly.
I've file a bug [2] and discussed this with initial-setup
maintainer(CCed), yet did not come up with good solution. initial-setup
can be forced to run on tty1, but it's probably not the correct
solution, because I guess that boards with no GPU won't have tty1,
right? initial-setup.service uses tty which as systemd default is set to
/dev/console. Seems that /dev/console is set to ttyS0, which is probably
beneficial for debugging purposes, but causes this invisible initial-setup.
Cheers
Michal Hlavinka
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1344942
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1387742
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
