Bug 437943

Summary: Xserver fails to configure itself correctly for Tiger4 systems
Product: Red Hat Enterprise Linux 5 Reporter: Adam Stokes <astokes>
Component: xorg-x11-serverAssignee: Dave Airlie <airlied>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.2CC: ktokunag, tao, tyamamot, xgl-maint
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2008-0446 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 16:56:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
xorg errors
none
xorg log
none
xorg logs from backed-out test
none
fix the rom reading code to fallback to the older methods. none

Description Adam Stokes 2008-03-18 11:12:30 UTC
Description of problem:
Unable to do graphic installations during 5.2 beta -- uses ATI Rage XL

Version-Release number of selected component (if applicable):
Problem in 20080313.1 tree.

How reproducible:
100%

Steps to Reproduce:
1. Attempt to install system
2.
3.
  
Actual results:
What happens in the 5.2 betas is that the video image is small and dim on the
screen and rolls so fast you can't make out any of the text. It looks like it's
using the wrong resolution for this monitor (really old Tatung CM15UHE 15" tube
monitor).

Expected results:
Able to see installer

Additional info:
Does not occur on 5.1

Comment 1 Adam Stokes 2008-03-18 11:12:30 UTC
Created attachment 298371 [details]
xorg errors

Comment 2 Matěj Cepl 2008-03-18 17:29:24 UTC
Could you please attach /var/log/anaconda.xlog please as an uncompressed
attachment to this bug?

Thank you.

Comment 3 Issue Tracker 2008-03-19 00:06:43 UTC
I don't have an anaconda.xlog on this system. I had to do the install in
text mode for it to work.

Internal Status set to 'Waiting on SEG'

This event sent from IssueTracker by gcase 
 issue 168997

Comment 4 Matěj Cepl 2008-03-19 15:42:19 UTC
Could you try to do login in graphical and let if fails before any actual
installation (and repartitioning and wiping up the drivers) actually happens?

Comment 6 Issue Tracker 2008-03-19 16:05:30 UTC
I can start a graphical installation or start X with 'init 5' or
'startx', but it doesn't display correctly. It's too garbled for me to
do anything. I'm attaching the Xorg.0.log file from a running X session,
in case that's helpful.


This event sent from IssueTracker by gcase 
 issue 168997
it_file 124481

Comment 7 Adam Stokes 2008-03-19 17:07:15 UTC
Created attachment 298541 [details]
xorg log

Comment 9 Dave Airlie 2008-04-01 01:55:13 UTC
dev_ack+, this could be an X server or kernel bug but needs investigation, lets
start with assuming the server broke.

Comment 10 Dave Airlie 2008-04-01 02:34:53 UTC
can we get an X.org log from 5.1 with this working if possible?

I'm trying to track down where it might have gone wrong.


Comment 13 Issue Tracker 2008-04-01 21:23:40 UTC
Here's the 5.1 working logs (in a sosreport).


This event sent from IssueTracker by gcase 
 issue 168997
it_file 126580

Comment 14 Issue Tracker 2008-04-01 21:29:32 UTC
Just to be safe, I've confirmed that 5.1 allows me to boot up in runlevel
5 as well as run 'startx'. I don't know why this wouldn't have worked,
I just wanted to test that too.


This event sent from IssueTracker by gcase 
 issue 168997

Comment 16 Gary Case 2008-04-01 22:49:56 UTC
Created attachment 299985 [details]
xorg logs from backed-out test

Comment 18 Dave Airlie 2008-04-02 01:40:12 UTC
*** Bug 439180 has been marked as a duplicate of this bug. ***

Comment 19 Dave Airlie 2008-04-02 01:51:05 UTC
Created attachment 300001 [details]
fix the rom reading code to fallback to the older methods.

Comment 20 Dave Airlie 2008-04-02 02:00:17 UTC
the latest scratch build from me in brew should have the fix, hopefully the
blocker person turns up so I can actually check this in.

Comment 27 Cameron Meadors 2008-04-16 18:25:09 UTC
Verified per comment #26

Comment 28 Keve Gabbert 2008-04-16 19:52:20 UTC
Dom0 startx still fails. 

info from Issue Tracker:
 Issue #168997 ([REGRESSION] RHEL5.2 installation and Dom0 can not startX in 
Tiger4 system.)[Intel]
https://enterprise.redhat.com/issue-tracker/168997

Previous Events:
----------------
Posted 04-16-2008 09:26am by yongkang.you
Hi,

How is this bug?
We test snapshot4 88.el5 in Tiger4. The install has graphic. But Dom0
startx still fail. 

I uploaded the Xorg log. 

Posted 04-16-2008 09:26am by yongkang.you
File uploaded: Xorg.0.log
    
https://enterprise.redhat.com/issue-tracker/?module=download&fid=128996

Comment 29 Issue Tracker 2008-04-17 00:29:51 UTC
I just installed RHEL5.2 beta -88.el5 kernel and updated to snapshot 5
(-89.el5 kernel). Snapshot 5 isn't available due to an anaconda problem
that prevents installation, but snapshot 6 will be available soon. The
system did boot into runlevel 5 with the xen kernel on my tiger4 box, BUT
there was one modification I had to make:

When I installed, I did so in text mode. When the installation was
complete, I dropped to the console (ctrl-alt-F2), went into
/mnt/sysimage/boot/efi/efi/redhat and edited the elilo.conf file. I needed
to add "console=tty" to the "append" line for the xen kernel, otherwise
I got no console access at all when the system booted post-install. That
bug's being tracked here:

https://bugzilla.redhat.com/show_bug.cgi?id=252347

I'm going to install the same snapshot you used (I won't update this
time) and see what happens.


This event sent from IssueTracker by gcase 
 issue 168997

Comment 30 Issue Tracker 2008-04-17 00:57:13 UTC
I was able to do an installation of the -88.el5 kernel snapshot on my
tiger4 with only the "console=tty" change I mentioned earlier. Graphical
installation worked and so did booting into runlevel5 with the Xen kernel.


This event sent from IssueTracker by gcase 
 issue 168997

Comment 33 errata-xmlrpc 2008-05-21 16:56:45 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0446.html