Bug 159496 - can't read display with GXT3000P graphics
Summary: can't read display with GXT3000P graphics
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: powerpc
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: David Howells
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-02 23:22 UTC by Andrew Elmore
Modified: 2012-06-20 15:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 15:58:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Elmore 2005-06-02 23:22:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050131

Description of problem:
The installation console is divided into two, each part in the upper corners of the screen, overlaying the white OpenFirmware background.  The pixels appear to be interlaced between each half of the console.

My configuration is a IBM RS/6000 7044-270 with 4x375MHz Power3+ cpus, 4GB memory, and a GXT3000P graphics card, and IBM P260 monitor at 1280x1024 resolution.  Looks like the linux kernel doesn't support the graphics card, and I'm betting the Xorg xserver doesn't either.

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


How reproducible:
Always

Steps to Reproduce:
1. install RHEL AS4 on this hardware.
2.
3.
  

Expected Results:  I would expect the console to present a legible display.

Additional info:

I am using a serial console for installation, which seems to be working.

Comment 4 Jiri Pallich 2012-06-20 15:58:02 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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