If I add the ks= option to the kernel command line, anaconda does not get started. I wrote the F20 x86_64 netinst.iso to a USB drive. The laptop is UEFI, secure boot enabled. Booting it with the default command line activates the network device (external USB ethernet) and starts the installer. If I add a ks= option to the kernel command line, the boot up process stops and eventually drops me to the dracut shell. I have had this issue since F19 with several windows8 laptops. I don't have one at hand right now and I only have the journalctl output. I can get more info in a couple of weeks if necessary. I diffed both the log files and there is no difference up to the point that the one stops. I tried to reproduce this in a UEFI VM, but it worked there (although secure boot was disabled).
Created attachment 935506 [details] journalctl output without ks=
Created attachment 935507 [details] journalctl output with ks=
> ks=http://servername/ks-sl64.cfg Is servername reachable? Can you add rd.debug=1 to the kernel command line and attach the rdsosreport file from that?
The network device doesn't get started. It seems that it never actually loads the stage2 or whatever it's called. Look at the point the ks log ends. I will get more logs from the laptop when I have access to it again in two weeks.
Created attachment 940612 [details] rdosreport.txt from failed boot Here is the rdosreport.txt with rd.debug=1 and rd.retry=2 to limit the massive repeats. It appears that it won't go to the next step without the kickstart but it can't get the kickstart until the network is up and it can't bring the network up until it gets to the next step.
Ok, so the initrd is missing the drivers for your network device, presumably, and dracut is thus unable to start the network.
If I add the drivers to the initrd should it automatically work or is there some configuration involved as well?
I guess that depends on the device. I don't know what it actually is, but if the problem is missing drivers then adding the drivers is usually enough for wired ethernet.
That did it. I added the asix module and ran depmod (forgot that step the first time) and the network came up and the installer worked.
I had to use the F21 installer on a laptop that wouldn't work with the kernel from F20 and the driver was available there, so I would consider this closed. The subject is somewhat misleading given what the actual cause is. However, I think it should stay as that since it might help someone else that runs into the same problem.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.