Description of problem: The display either is missing text until the mouse hovers over the display (Eric) or has random lines and corrupt displays in Firefox. Version-Release number of selected component (if applicable): Fedora 10 upgraded from Fedora 9. How reproducible: All the time Steps to Reproduce: 1. Start machine 2. Logon on 3. Open Firefox Actual results: Lines across the screen or compressed text in place of html. Expected results: Clear display with just text Additional info: The machine is a Dell with an Intel 82865F Integrated Graphics controller. Standard install with no customisation
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 325039 [details] The xorg.conf file This xorg.conf was system generated and has not been edited in any way.
Created attachment 325040 [details] The log file Firefox is the worst application so far. Sometime the buttons seem to be one line out .
Intel Corporation 82865G Integrated Graphics Controller rev 2
I'm facing the same trouble. The driver i810 was supposed to work fine with this video card, instead of only intel (general) driver, but I get just a black screen. I used the live cd to remove the xorg.conf (with i810) generated by sistem-config-display and the system detected my video card, selecting the intel driver. So, I get my screen back, but also the trouble.
I believe this is a duplicate of 485419. *** This bug has been marked as a duplicate of bug 485419 ***