sinnykumari added a new comment to an issue you are following:
``
@dustymabe ppc64le uses console=tty1. Atomic cloudImage of ppc64le boots perfectly with
existing kernel boot parameter provided in [fedora-atomic
kickstart](https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_20).
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](https://pagure.io/fedora-kickstarts/blob/master/f/fedora-atomic.ks#_20)
```
-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](https://www.kernel.org/doc/html/v4.12/admin-guide/serial-c...,
"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?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/347