|Summary:||keyboard kickstart directive is ignored|
|Product:||[Fedora] Fedora||Reporter:||david d zuhn <zoo>|
|Component:||anaconda||Assignee:||Paul Nasrat <pnasrat>|
|Status:||CLOSED RAWHIDE||QA Contact:||Mike McLean <mikem>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2005-02-02 02:59:23 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description david d zuhn 2004-10-19 14:44:20 UTC
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040808 Firefox/0.9.3 Description of problem: I have a kickstart file for FC3test3, and this file contains a keyboard directive. Yet when I perform an installation using this config file, I am still being prompted for a keyboard choice. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. use the kickstart config file attached to this bug 2. see the prompt for keyboard type 3. enter a keyboard type Expected Results: The keyboard directive should be honored. Additional info:
Comment 1 david d zuhn 2004-10-19 14:46:10 UTC
Created attachment 105449 [details] kickstart file for bug This kickstart file is loaded via http: Kernel command line: initrd=/install/fedora/3t3/initrd.img ksdevice=eth0 ks=http://lab/ks/machine/trabant3/fc3t3.ks console=ttyS0,9600 BOOT_IMAGE=/install/fedora/3t3/vmlinuz vnc vncconnect=homestake
Comment 2 Paul Nasrat 2004-10-20 10:46:44 UTC
Created attachment 105503 [details] My ks file Unable to reproduce here. Tested with a FC3T3 tree and above kickstart using uk initially then changing to us for keyboard directive. The kickstart boots up into graphical and goes straight to reading package information, before formatting and installing. No additional input required. Can you confirm with above config just changing the url/nfs line as appropriate for your setup?
Comment 3 david d zuhn 2004-10-20 15:19:57 UTC
Yes, I can confirm the bug. I also had to change the disk partitioning from hda to sda, but using your attached kickstart file I was again prompted for a keyboard type. This was the only prompt for user input. Some more information about my configuration: this is a Dell 2650 machine, pxebooting the installation, using a serial console for the installation. There is no keyboard actually attached to this system.
Comment 4 Paul Nasrat 2004-10-20 17:05:58 UTC
Can you retest with a keyboard attached?
Comment 5 david d zuhn 2004-10-20 17:53:56 UTC
Tested again, with full keyboard/mouse/video setup attached. No change in behavior -- I'm still prompted for a keyboard type. I then tried it without the serial console (no console= argument on the kernel command line), and it proceeded to do a complete installation, without prompting for the keyboard type.
Comment 6 david d zuhn 2004-10-20 18:08:51 UTC
Just for comparison, running the same sort of setup (serial console, no keyboard, pxebooted kernel) works fine on RHEL 4b1 (Nahant).
Comment 7 Jeremy Katz 2005-02-02 02:59:23 UTC
Add 'serial' to your command line options and it'll work. It's fixed post-FC3