Bug 74137 - Video display skews on entry into graphics mode
Summary: Video display skews on entry into graphics mode
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-16 19:48 UTC by dshirsh
Modified: 2008-01-17 17:49 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:49:38 UTC
Embargoed:


Attachments (Terms of Use)

Description dshirsh 2002-09-16 19:48:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809

Description of problem:
After Anaconda detects my video card and display correctly the display skews
when it goes into graphics mode. Only a display power reset corrects it.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Begin beta installation, verify all CDs
2.Detect my Radeon VE video card
3.Detect my Sony SDM-M81 LCD monitor
4.When system goes into graphics mode the video is totally skewed and unreadable.
5. After resetting power on my LCD the display is just fine.
	

Actual Results:  Display returned to normal

Expected Results:  Should have a normal video display without having to reset
the LCD power.

Additional info:

I'm using a DVI-DVI connection from the Radeon to the Sony LCD.

Comment 1 Michael Fulbright 2002-09-16 21:19:26 UTC
I would try adding this to the boot command line:

  resolution=<res>

where <res> is something like '1024x768' (without the quotes) and should match
the native resolution of the LCD.

Comment 2 Michael Fulbright 2002-10-24 18:21:07 UTC
Closing due to inactivity. Please reopen if you have any new information to add
to this report.

Comment 3 Red Hat Bugzilla 2006-02-21 18:49:38 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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