Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 577708
| Summary: | Black screen during graphical kickstart install | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Liam Li <lili> | ||||||||||||||
| Component: | anaconda | Assignee: | Ales Kozumplik <akozumpl> | ||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||
| Priority: | low | ||||||||||||||||
| Version: | 13 | CC: | alex, awilliam, dlehman, jlaska, jonathan, jzeleny, kparal, rhe, vanmeeuwen+fedora | ||||||||||||||
| Target Milestone: | --- | Keywords: | CommonBugs | ||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | All | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | https://fedoraproject.org/wiki/Common_F13_bugs#black-screen-on-kickstart-install | ||||||||||||||||
| Fixed In Version: | anaconda-13.38 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | |||||||||||||||||
| : | 579653 579654 (view as bug list) | Environment: | |||||||||||||||
| Last Closed: | 2010-05-03 19:16:08 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: | 507681, 579653, 579654 | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Liam Li
2010-03-29 02:52:21 UTC
Created attachment 403156 [details]
anaconda.log
Created attachment 403157 [details]
X.log
Created attachment 403158 [details]
other logs
I've reproduced this failure in both a known working virt guest, and on bare metal hardware. In both cases, I am booting the DVD and providing a link to a kickstart file (http://jlaska.fedoraproject.org/ks.cfg). If I boot without the kickstart file ... X starts without problems. If I boot with the kickstart file ... X fails to start as indicated in Liam's attached files. = anaconda.log = 02:26:45,341 WARNING anaconda.stdout: X startup failed, falling back to text mode = X.log = [ 64.383] (II) XINPUT: Adding extended input device ""Macintosh mouse button emulation"" (type: MOUSE) [ 64.383] (II) "Macintosh mouse button emulation": initialized for relative axes. [ 64.383] (II) config/udev: Adding input device "Macintosh mouse button emulation" (/dev/input/mouse0) [ 64.383] (EE) No input driver/identifier specified (ignoring) [ 2019.006] (II) AIGLX: Suspending AIGLX clients for VT switch I have a suspicion that there is some interaction with anaconda and X that isn't working problem when starting a kickstart graphical install. Created attachment 403290 [details]
X.log from virt DVD install (works)
Created attachment 403291 [details]
X.log from virt DVD kickstart install (fails)
I've compared the /tmp/X.log from a working graphical DVD install, and from an attempted graphical kickstart DVD install. Note, I've removed the leading timestamp from the logs to make comparing output easier. There is no difference in the /tmp/X.log between the working and failing cases.
This makes me believe there might be some interaction in the installer space?
NOTE: this isn't specific to DVD installs. I can recreate this problem doing PXEboot installs. Chris Lumens directed me to a recent thread on anaconda-devel that might account for this problem. See https://www.redhat.com/archives/anaconda-devel-list/2010-February/msg00364.html As such, I created an updates.img with the proposed patch from the mail above. This resolves the reported problem! If you'd like to test, use http://jlaska.fedorapeople.org/updates-577708.img Spoke with release engineering (jkeating) and development (dlehman), everyone agreed that we can document this issue in Common_F13_Bugs and address this post-beta. This issue appears to affect only graphical kickstart installs. The install progresses per the instructions in the kickstart file, however the user may not see if any problems have surfaced. Until this is resolved recommended workarounds are: 1. Perform graphical kickstart installs using the updates.img noted in comment#8 2. Perform graphical kickstart installs using VNC 3. Perform graphical kickstart installs using text-mode Adding keyword CommonBugs to note this on https://fedoraproject.org/wiki/Common_F13_bugs Just realized that this will also impact preupgrade users. Support for preupgrade is on the Beta release criteria (https://fedoraproject.org/wiki/Fedora_13_Beta_Release_Criteria). Reproduced in anaconda 13.37.1 of F13 Beta RC2 Adding for consideration as a F-13-Beta blocking issue as this will most likely impact preupgrade users. Fixed for Fedora 13 by c773081e75b049256c1377c1f9a702a1a6cc9f12. The bug will be moved to modified once the beta blocker decision is made so the fixed-in version can be determined. (In reply to comment #14) > The bug will be moved to modified once the beta blocker decision is made so the > fixed-in version can be determined. Ales, this issue can be fixed in F-13 after F13Beta. I don't know if you have a branch in anaconda for post f13beta changes. *** Bug 582590 has been marked as a duplicate of this bug. *** can someone please test and confirm that this is fixed in TC1? Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Confirmed during Preupgrade test day. (In reply to comment #18) > Confirmed during Preupgrade test day. Which used anaconda-13.38-1 (http://git.fedorahosted.org/git?p=anaconda.git;a=commit;h=c773081e75b049256c1377c1f9a702a1a6cc9f12). Closing, please feel free to reopen this issue if the reported problem is no longer addressed. tested on anaconda 13.39, fixed. |