@dustymabe ppc64le uses console=tty1. Atomic cloudImage of ppc64le boots perfectly with existing kernel boot parameter provided in fedora-atomic kickstart.

I have two solution to fix console issue, which works on all three enabled arches (x86_64, ppc64le and aarch64):
1. Add console=ttyAMA0 in kernel boot parameter in fedora-atomic.ks

-bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0"
+bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 console=ttyAMA0 net.ifnames=0"

2. As per serial console documentation, "If no console device is specified, the first device found capable of acting as a system console will be used". So, we don't need to explicitly pass console value to kernel boot parameter.

-bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0"
+bootloader --timeout=1 --append="no_timer_check net.ifnames=0"

Any thoughts?

@dustymabe ppc64le uses console=tty1. Atomic cloudImage of ppc64le boots perfectly with existing kernel boot parameter provided in fedora-atomic kickstart.

does ppc64le have a serial console option?

1. Add console=ttyAMA0 in kernel boot parameter in fedora-atomic.ks

So just adding them all works? i.e. it will just ignore entries that don't work?

1. As per serial console documentation, "If no console device is specified, the first device found capable of acting as a system console will be used". So, we don't need to explicitly pass console value to kernel boot parameter.

I'd like to satisfy these requirements:

1. kernel messages go to VGA console output on all platforms
2. kernel messages go to serial console output on all platforms

If we can do that with either of the solutions above then I'm happy.

@dustymabe ppc64le uses console=tty1. Atomic cloudImage of ppc64le boots perfectly with existing kernel boot parameter provided in fedora-atomic kickstart.

does ppc64le have a serial console option?

Yes, ppc64le uses console=hvc0 for serial console.

Add console=ttyAMA0 in kernel boot parameter in fedora-atomic.ks

So just adding them all works? i.e. it will just ignore entries that don't work?

Yes, it ignores unsupported consoles (will be good to know that same results is being seen by others too)

As per serial console documentation, "If no console device is specified, the first device found capable of acting as a system console will be used". So, we don't need to explicitly pass console value to kernel boot parameter.

I'd like to satisfy these requirements:

kernel messages go to VGA console output on all platforms
kernel messages go to serial console output on all platforms

If we can do that with either of the solutions above then I'm happy.

Considering kernel messages being appear on both VGA and serial console, passing explicitly console to kernel boot parameter is needed.

-bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0"
+bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 console=ttyAMA0 console=hvc0 net.ifnames=0"

-bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0"
+bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 console=ttyAMA0 console=hvc0 net.ifnames=0"

Can you open a pull request for that against rawhide? Also a comment with a nice explanation would be useful.

Pull request - https://pagure.io/fedora-kickstarts/pull-request/300

Related patch got merged to rawhide and f27 branch of fedora-kickstarts.

F27, nightly compose(20171015.n.0) Atomic cloudImage boots fine on both aarch64 and ppc64le along with kernel debug message output on consoles.

marking this as fixed