Bug 127475
Summary: | monitor selection in kickstart | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas Gordon <memeyou> | ||||||
Component: | anaconda | Assignee: | Paul Nasrat <nobody+pnasrat> | ||||||
Status: | CLOSED WORKSFORME | QA Contact: | Mike McLean <mikem> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | rawhide | CC: | zoo | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2005-07-08 22:02:50 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 133260, 136451 | ||||||||
Attachments: |
|
Description
Thomas Gordon
2004-07-08 19:14:27 UTC
Does this still not work? I have encountered this same problem, using FC3rc1. My kickstart file contains the following line: xconfig --card "NVIDIA GeForce FX (generic)" --videoram 65536 --hsync 31.5-37.9 --vsync 50-70 --resolution 1280x960 --depth 24 --startxonboot --defaultdesktop gnome but when I run the installer, I end up with a configuration that matches what's put into /root/anaconda-ks.cfg xconfig --card "NVIDIA GeForce FX (generic)" --videoram 65536 --hsync 31.5-37.9 --vsync 50-70 --resolution 800x600 --depth 24 --startxonboot --defaultdesktop gnome Created attachment 105740 [details]
kickstart file with video specification
Created attachment 105741 [details]
the xorg.conf file generated by the kickstart file
Note the modes line which doesn't match the resolution specified in the
kickstart file. There was no firstboot run to offer a chance to fix this.
Is this better in FC4 test3? Remove from FC3 tracker - were you able to test with FC4test3? Closing due to inactivity. Please reopen if you have further information to add to this report. |