Red Hat Bugzilla – Bug 155933
installer hangs/display corrupts post 'starting atd...'
Last modified: 2007-11-30 17:11:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Description of problem:
Text only install, monitor not recognised, successfull installation. Post-install reboot, installer hangs/display corrupts after 'configuring kernel parameters' boot section. Removed 'rhgb' from vmlinuz, bootup reaches 'starting atd....', display corrupts/installer hangs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Text only install (GUI crashes/hangs at post hardware probing)
Actual Results: Installer hangs/crashes after 'configuring kernel parameters' boot section.
Expected Results: Normal bootup to post-install config/Fedora start screen
Monitor was not recognised, added manufacturers specs for HS and VR, added "noaccel" option under device, added "1024x768" with default 24 color/depth. Able to access FC3 command shell via rescue disk. Ran 'system-config-display', result was black screen/system crash, occurred with system defaults and amended /xorg.conf as above.
Ran 'X -probeonly' and was given this:
(ww) * INVALID MEMORY ALLOCATION * b: 0xe4000004d0000000 e: 0xe4000004dfffffff
(ee) Sparse io range (base: 0x2a95c7d406 mask: 0xb1d790) doesnt satisfy (base+mask =mask)
Sparkle 6600 256mb PCIe
FC3 i386 version worked fine. MOBO BIOS beta ver F3j
Note: When filing bug reports, hit ENTER at the end of each line after
70 characters. This bug report is virtually unreadable.
>Description of problem:
>Text only install, monitor not recognised
Monitor autodetection is x86 specific and does not work on any other
architecture, so this is expected.
> Sparkle 6600 256mb PCIe
If that's a GeForce 6600, they're unsupported in FC3 out of the box.
Might work with latest updates for FC3. FC4's current xorg-x11 has
support for it, but it is buggy. Using "XaaNoScreenToScreenCopy" works
around the problem however, and might work on FC3+updates also.
Attach X server log and config file, and output of "rpm -q xorg-x11"
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "CURRENTRELEASE".