Description of problem: As of version 3.17 the kernel is able to decide which console to use based on the device tree or ACPI table content. Currently live media creator will always insert 'console=ttyS0,115200' into the kernel command line in the aarch64 template. Since some aarch64 devices don't use ttyS0, this limits compatibility. It is better to leave off any console, earlyprintk, or earlycon parameters entirely. Version-Release number of selected component (if applicable): The version of lorax used in the fc21_rc1 compose exhibits this behavior. How reproducible: Happens every time. Example configuration from fc21_rc1: http://arm.koji.fedoraproject.org/compose/f21_RC1/21/Server/aarch64/os/EFI/BOOT/grub.cfg
There's now RC5 which was composed with 21.30-1 vs 21.24-1 of RC1, not sure if that would make a difference but it would be good to double check http://arm.koji.fedoraproject.org/compose/21_RC5/
Created attachment 964778 [details] patch If someone could test this patch with the correct kernel that would be great.
lorax-21.32-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/lorax-21.32-1.fc21
Package lorax-21.32-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing lorax-21.32-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-16415/lorax-21.32-1.fc21 then log in and leave karma (feedback).
dmarlin asked about removing these lines from the config: -serial --speed=115200 -terminal_input serial console -terminal_output serial console Should those have been left in? Can someone with access to the various systems confirm that it is ok to remove them?
lorax-21.33-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/lorax-21.33-1.fc21
lorax-21.33-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.