Description of problem: On an Altix IA64 system with FireMV 2200 graphics, while attempting to install RHEL5.2-Snapshot1 from DVD and booting with option 'linux console=tty0', anaconda starts up and identifies the graphics card, but when it tries to run the X server, there's only a blank screen. How reproducible: Always. Steps to Reproduce: Boot RHEL5.2-Snapshot1 installation with option 'linux console=tty0'. Actual results: Blank screen. Expected results: Anaconda starts up in graphical mode. Additional info: Booting with option 'linux text console=tty0' > Does the X server come up normally after the system has been installed? This is not a regression because we've never supported the FireMV 2200 on Altix before. I've had to start the X server manually because the runlevel is not set to 5. To prevent the system from hanging as described in IT#170845, I've disabled nautilus. Thereafter, X and gnome run without any problems. > Does the X server come up normally after the system has been installed? I upgraded a Prism system (AGP graphics) from RHEL5.2-Snapshot1 to Snapshot4 and now Xorg fails to even come up. The process is hung with the following stack trace: #0 0x4000000000119fb0 in xf86FixPciResource () #1 0x400000000010a870 in xf86BusProbe () #2 0x40000000000b7f20 in InitOutput () #3 0x400000000003b570 in main () Also attached is the corresponding Xorg.0.log. > can you try snapshot 5? There is no change in the outcome as compared to the results posted on 04-11-2008. Xorg still doesn't work, as tested on Prism with AGP graphics and the 2.6.18-89.el5 kernel.
Created attachment 303216 [details] x.org log from snapshot 4
When the anaconda crashes, please, switch to the console (Ctrl+Alt+F2) and cp /tmp/X* to some other place -- USB stick, some other computer via network, some on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
There is a more serious problem in BZ 211530 that needs to be resolved first.
Built xorg-x11-server 1.1.1-48.43.el5 MODIFIED Please test is on as much other ia64 hw as we have time for. Not just the ALTIX. Don't want any nasty regressions showing up. Should be the same as 448139 really.
From IT 170840: The following problem is still observed on RHEL5.3-Snapshot3: Non-functional keyboard, escape sequences instead of arrow keys; unresponsive to tab and return. This is when installing directly from DVD, running bootia64 with 'linux console=ttyS0'. The dialog shows up, but the keyboard is unusable at the CD test page. Reproduced at Red Hat and SGI.
Jonathan, Do you still see the same behavior if you boot with no console line, or console=tty0 ? Thanks, David This event sent from IssueTracker by dwa issue 170840
If I boot with no console argument, I don't see the installation dialog at all. If I boot with console=tty0, I can use the keyboard and get past the CD test page, but once anaconda probes for the graphics card, the machine resets (I'm guessing it's the same problem as when system-config-display is run). This event sent from IssueTracker by dwa issue 170840
FAILS_QA due to Comment #16.
can we try and get the log from Comment #2 if X crashes or hangs. does VT switching work at all or does the machine reboot?
(In reply to comment #18) > can we try and get the log from Comment #2 if X crashes or hangs. does VT > switching work at all or does the machine reboot? This is during installation from CD, so I'm not sure how to get in and where to grab any logs from. The machine resets once anaconda probes for the graphics card, presumably because Xorg is loading the "r500" driver instead of "radeon" (see Comment #25 in BZ 448139).
So this machine appears to have an r500 of some sort in it as well as the FireMV card. Can someone confirm this?
(In reply to comment #21) > So this machine appears to have an r500 of some sort in it as well as the > FireMV card. It had a blade with two non-FireMV cards; I've now removed it. The machine still hangs while trying to run Xorg, but does not reset. See BZ 448139 for the updated results.
and why this isn't duplicate of bug 448139?
mcepl, server vs -ati driver, not sure where the fixes need to be yet. so don't duplicate this.
(In reply to comment #22) > (In reply to comment #21) > > So this machine appears to have an r500 of some sort in it as well as the > > FireMV card. > > It had a blade with two non-FireMV cards; I've now removed it. The machine > still hangs while trying to run Xorg, but does not reset. See BZ 448139 > for the updated results. I tried this again just now, booting the machine off the RHEL5.3-Snapshot4 installation DVD; bootia64 with 'linux console=tty0'. I was able to use the keyboard and skipped past the CD test page. It was able to start anaconda and probe the graphics card, and brought up the graphical install menus, though I didn't proceed with a complete install. George: can you check also? Thanks.
MODIFIED xorg-x11-server-1.1.1-48.52 and xorg-x11-drv-ati-6.6.3-21 built
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: * the graphical installer would fail to start when attempting to install Red Hat Enterprise Linux on certain platforms, for example, an Altex IA64 system with a FireMV 2200 graphics card. Attempting to continue with the installation would make the system reset. This update for X includes a patch that improves support for the IA64 platform. With this patch in place, graphical installation can proceed normally.
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -* the graphical installer would fail to start when attempting to install Red Hat Enterprise Linux on certain platforms, for example, an Altex IA64 system with a FireMV 2200 graphics card. Attempting to continue with the installation would make the system reset. This update for X includes a patch that improves support for the IA64 platform. With this patch in place, graphical installation can proceed normally.+* the graphical installer would fail to start when attempting to install Red Hat Enterprise Linux on certain platforms, for example, an Altex IA64 system with a FireMV 2200 graphics card. Attempting to continue with the installation would make the system reset. This update for X includes a patch that improves support for the IA64 platform. With this patch in place, graphical installation can proceed normally. A similar but unrelated problem that prevented graphical installation on a Lenovo T61 was related to the driver for the Synaptics input driver and is resolved by a separate patch also provided in this update.
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 therefore 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-2009-0162.html
Tested on the affected rx2660 with RHEL5.3 installed cd-rom, and confirmed the GUI installer was started on the system. And I have been using RHEL 5.2 with vesa driver on the rx2660. I have updated xorg related RPMs to RHEL 5.3 and confirmed the NEW xorg works with radeon driver. Thanks for the fix. You may close this call.