Bug 338531

Created attachment 231361 [details]
Intel G33 log, F8T3-i686-KDE LiveCD

The first attempt was made with a BIOS setting of using 8MB for video RAM, plus
"1~2 GTT".  rhgb came up okay from the livecd, but not the X server.

I have now tried it with a 1MB setting for video RAM -- rhgb came up in much
lower resolution/depth, and X started -- but not useably.  Approximately 2 lines
of a Konsole on the display were viewable -- everything else was a nightmare of
misdrawn rectangles, video artifacts, and dancing vertical stripes.

"it" is the F8T3 i686-KDE LiveCD again.

Those are the only 2 settings in this particular BIOS.

I'll attach the X Log from this attempt in case the contrast is at all useful.

Created attachment 232361 [details]
Log when started with BIOS 1MB-VideoRAM setting

hmm if rhgb comes up okay I can't see why X wouldn't .. maybe you could disable
rhgb and see if X starts.. 

the 1MB is a known issue so please try with the 8MB..

I'll give that a try.

The hardware is a Gigabyte GA-G33M-DS2R motherboard with BIOS rev F4.  There are
2 subsequent BIOS revisions, neither of which claims to address any graphics
issues (but which take away at least one feature found in F4).  I won't be
messing with the BIOS unless/until I find a way to restore this revision, which
for some reason isn't on the manufacturer's site any more -- just in case other
revisions don't work as well.

Setting to NEEDINFO just so that we don't forget there is something to expect
from you.

Re comment 5 and 6 -- I've tried removing the "rhgb quiet" from the boot lines
of the i386 KDE-Live CD.  No change, still fails the same way in the log.

Also tried with the regular x86_64 LiveCD (burned to a DVD), with and without
rhgb in the boot command.  Still fails the same way.

Not sure what to try next.

Er, I meant the F8T3 i686 KDE LiveCD in comment 7, the same one I started out with.

I have a similar problem on my computer although I was able to install fedora 
8. When I need to reboot to complete the installation, that's when X fails 
with the same error as the original poster. My hardware is:
Intel Quad Core Q6600
Gigabyte GA-G33M-S2H

Judging from some searches, it looks like this is a pretty common situation 
for this video chipset. The driver looks for a /dev/agpgart device which 
appears to not exist for motherboards that don't have apg ports (makes sense)

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.