Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 224493 - Graphical Corruption after first execution of Firstboot and durring subsequent executions.
Summary: Graphical Corruption after first execution of Firstboot and durring subsequen...
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-25 22:08 UTC by christopher.bridenstine
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-05-30 21:44:40 UTC

Attachments (Terms of Use)

Description christopher.bridenstine 2007-01-25 22:08:59 UTC
Description of problem:

The Fedora Core 6 version of first boot enables and runs (what I believe to be)
an implementation of X11 correctly.  Upon finishing the first execution of
firstboot, the operating system attempts to implement the next step in the setup
process, however at this point whatever the os does next causes the X11 graphics
to corrupt and system to freeze.  Upon restarting of the os, firstboot runs
again, however upon initiallization of the gui for firstboot the system hangs
witht he same graphics corruption as seen previously post-firstboot.

I'm knowlegable that this problem may not be confined to just firstboot. 
However, I am unable to determine why firstboot would have no graphical problems
undtill after its first execution

Version-Release number of selected component (if applicable):
Fedora Core 6 (Zod stable)  Firstboot v.*  (version included in DVD-iso as of

How reproducible:

System -

Pentium IV - 2.6C
Asus P800
Corsair 512mb PC3200 Ram
Radeon X800XT PE    (I know recent ATI cards have support problems.
2x WD1200JB  EIDE Hard-drives

Steps to Reproduce:
1.Install Fedora on hdb1 partition using DVD-iso boot disk (as of 1/24/07)
2.Install grub using hda1 Windows intall as primary boot and hdb1 Fedora as 2nd
3.Remove DVD-iso boot disk
4.Restart computer
5.Use grub to boot into hdb1 install of Fedora Core 6
6.Wait for initial setup
7.Wait for Firstboot to load
8.Configure Firstboot accordingly
9.Firstboot finishes and GUI begins loading.
10.System Freeze + Display grapics corruption.
11.Restart Machine  (Hard restart all controls ineffective)
12.Use grub to boot into hdb1 install of Fedora Core 6
13.Wait for initial setup
14.Upon start of Firstboot, system freezes with display corruption as before.

Actual results:
System freezes.. all controls are ineffective..  Background image for next
expected GUI implementation loads, however graphical corruption can be seen
across the top 10% of the display.

Expected results:
Firstboot runs and is configured appropriately.  Firstboot ends.  GUI
implementation begins and continues without freezing

Additional info:
It would be nice to know if Firstboot uses a display driver or X11
implementation other than what is used for the main GUI.  I could understand if
firstboot ran its own graphics display drivers to ensure maximum compatability
durring a initial install, however I am puzzled how a corruption which occurs
after firstboot can cause problems durring subsequent executions.

Comment 1 Chris Lumens 2007-01-30 20:29:15 UTC
If you are booting with rhgb, firstboot takes over the X server that was already
started.  If you are not, it starts its own server using a configuration that
was probed for.  This config should be very similar to the one that ran in
anaconda as it uses the same code.

Can you please test with Fedora 7 test 1 when released and see if it's working
better for you?  I know we did some work with firstboot, rhgb, and so forth
after FC6 to fix some sporadically appearing problems like this.

Note You need to log in before you can comment on or make changes to this bug.