Bug 185993 - random vertical lines after starting graphical interface
random vertical lines after starting graphical interface
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: XFree86 (Show other bugs)
5
i386 Linux
medium Severity high
: ---
: ---
Assigned To: X/OpenGL Maintenance List
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-20 15:17 EST by Miroslav Šimko
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-20 16:05:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Miroslav Šimko 2006-03-20 15:17:35 EST
Description of problem:
I downloaded new Fedora Core 5 and tryed to instal it. After several preinstal 
steps, instalation program recognized my system graphic ( intel 915 onboard) and 
monitor (AOC spectrum 7GLR) Then, it writes 'starting anaconda' and I can see 
just random vertical lines after while. 

So I though that problem may be in wrong horizSync & vertSync values. I reboot 
instalation program once again and put those values as command line arguments ( 
hsync=30-95 vsync=50-160) and start instal process with these params. But with 
same problem.

I have to mention, that winXP are running perfectly on this configuration. 


Version-Release number of selected component (if applicable):
release version of Fedora Core 5

HW:
  Intel 915gvwb chipset board with onboard graphic
  AOC Spectrum 7GlrA+ monitor
SW: 
  newest BIOS from intel according to this board
  winXP system (should not interfere)

Steps to reproduce:
  run instalation of Fedora Core 5 (release) with no options
Comment 1 Miroslav Šimko 2006-03-20 16:05:35 EST
I try one more thing - load optimal defaults in my BIOS. With these settings, 
there was no problem, luckyly. 

So sorry for bothering.

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