PR#303: Include console=ttyAMA0 and console=hvc0 in Atomic kickstart - fedora-kickstarts

fedora-kickstarts

#303 Include console=ttyAMA0 and console=hvc0 in Atomic kickstart

Merged 6 years ago by kevin. Opened 6 years ago by sinnykumari.

sinnykumari/fedora-kickstarts f27 into f27

Include console=ttyAMA0 and console=hvc0 in Atomic kickstart

Sinny Kumari • 6 years ago

2d46089

fedora-atomic.ks

file modified

+5 -1

		`@@ -17,7 +17,11 @@`

		`firewall --disabled`

		`- bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 net.ifnames=0"`
		`+ # console=ttyAMA0 and console=hvc0 as kernel boot parameter to see`
		`+ # kernel boot messages on serial console as well on aarch64 and`
		`+ # ppc64le respectively.`
		`+ # https://pagure.io/atomic-wg/issue/347`
		`+ bootloader --timeout=1 --append="no_timer_check console=tty1 console=ttyS0,115200n8 console=ttyAMA0 console=hvc0 net.ifnames=0"`

		`network --bootproto=dhcp --device=link --activate --onboot=on`
		`services --enabled=sshd,cloud-init,cloud-init-local,cloud-config,cloud-final`

sinnykumari commented 6 years ago

While booting Atomic cloudImage, we want to see kernel messages
on both VGA and serial console. It works fine with
tty1(vga console) and ttyS0(serial console) on x86_64 arch.
But, aarch64 and ppc64le doesn't use ttyS0 as serial console.
Instead, they use ttyAMA0(aarch64) and hvc0 (ppc64le).

Also, good point is that if a serial console specified in kernel
boot parameter is not supported on a given hardware platform, it
gets ignored. For example: console=ttyAMA0 and console=hvc0 will
get ignored on x86_64

Fixes: https://pagure.io/atomic-wg/issue/347

Signed-off-by: Sinny Kumari sinny@redhat.com

sinnykumari commented 6 years ago

This change is already available in master branch. @dustymabe (on x86_64) and I (on ppc64le) have tested Atomic CloudImage from today's rawhide nightly compose which contains fixes and it worked fine for us.

It will be nice to have this change available in F27.

Note: Atomic cloudImage build for aarch64 is failing in rawhide from past few days but it's totally unrelated with this change.