Hide Forgot
Description of problem: Install hangs with blank screen Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Boot FC6T3 CDROM 2. proceed with install till hang when X/anaconda starts 3. Actual results: Blank screen Expected results: Initial Anaconda GUI screen Additional info:
Created attachment 139195 [details] config and log files from install system at hang
CD images from: I created new CD images for FC6 Test3 IPF. Pls. download them from' https://fedoraipf.108.redhat.com/servlets/ProjectDocumentList?folderID=44&expandFolder=44&folderID=43.
System is Quad Dell 7250 1.6GHz/9MB processors, 8GB Ram, IDE CDROM, USB Keyboard/Mouse
Created attachment 139198 [details] System log files from SR870BH2 gui install failure Install fails same way on Dual Intel SR870BH2 system with 1.4GHz/4MB cpus Both an NEC LCD1850X and a Gateway XVGA monitor report scan out of range.
John, I'll try to see if we have a similar box in house. We've hit a recent snag in trying to get ISO images out. I'll try to connect with Yanmin about figuring out a way to get new ISOs out for you to try an install with... P.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Even after almost three months there has been no activity on these bugs, so we consider them obsolete and they are being closed as INSUFFICIENT_DATA. Please, if you are able to reproduce this bug on currently supported (FC6 and F7) non-test distribution, or if there is any other reason why this bug should be kept alive, please, reopen, change the product to something more recent and add an additional information to the comment of such bug. Thank you very much.