Red Hat Bugzilla – Bug 138489
FC1->FC3 Graphical Install Currupts Screen with i815 chip set
Last modified: 2007-11-30 17:10:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914
Description of problem:
Upgrading from FC1 to FC3 could not use the graphical install.
The screen gets corrupted (all colors) and it hangs.
Text mode seems to work fine.
Graphics chipset is i810/i815
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Insert CD
2. Press enter to use graphical install
3. Skip CD check
Actual Results: Screen turns all kinds of colors and hangs.
Expected Results: Installer goes into graphics mode
Tried it three times. Happened every time.
I added this bug as I was doing the upgrade.
It looks like the problem is deeper that I thought though.
That same corrupt screen greets me every time I boot up.
I can only see the dialog box that says; "probing for new harware" and
the progress bar moving.
After that it jumps back to text mode, stays a long time there.
Then jumps back to graphical (with corrupted backgound).
Starting some services I can see up in the top right corner.
Jumps back into text mode.
Stays there twice as long (about 5mins).
Back into graphical mode again to finish desktop start up.
Once in, the desktop never recovers.
It is not refreshing at all. Menus opened stay opened. That sort of
thing. Barely anything works.
I wonder if now is not just a video problem but something else...
Known problem. See bugs: #133010 and #132267
Thank you. I find hard to believe FC3 made the release in this state.
Maybe there aren't enough i815 users out there anymore.
For me, it broke my system badly. I can't get in. It hangs every time.
The few times it made it through the hang, it was just to freeze the
screen and corrupt the desktop.
I was happy with FC1 but I had to upgrade. Oh,well. Live and learn.
FC3 is still usable with Option "No Accel" and/or without graphics boot.
I think it should be mentioned in the Release Notes somewhere.
*** This bug has been marked as a duplicate of 132267 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.