Description of problem: Attempting to do a graphical install using RHEL5.3 snapshot2 fails with xServer crashing. Same problem on RHEL5.2GA. RHEL5.1GA works fine. How reproducible: Attempt to install 5.3beta using a CD. Initial screens indicating loading the SAS driver appear, then screen goes dark. CNTL+ALT+BackSpace returns to a command line prompt. Text install works. When the system boots after a text install, startx works fine with the nv driver configured. Changing this to the VESA driver in /etc/X11/xorg.conf also works fine. So it appears something in anaconda during install is not getting set up properly. Steps to Reproduce: 1. Boot RHEL5.3 snapshot 2 on a Lenovo ThinkStation D10 with NVS 290 video 2. Observe the dark screen after loading the SAS driver 3. CNTL+ALT+BackSpace gets you back to a command line prompt. Actual results: Graphical install fails. Expected results: Graphical install works as it did in RHEL5.1GA. Additional info: System in my Office. Brock also has a D10 in Raleigh. Scott Dodson has an S10 in GSS support (whioch should have the same problem)
Will try to get a dump of the xorg install log and a sysreport of the running machine after install completes.
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
Created attachment 323905 [details] sosreport from running system after successful text install
The X log in that sosreport is from a run with the vesa driver (which, unsurprisingly, appears to work). Can I get a log from a run with the nv driver? Alternatively, see if you have a file named /var/log/anaconda.xlog, which should be the X log from anaconda time. IWBNI sosreport attached that directly, but, here we are.
Created attachment 323956 [details] anaconda.log - text install
Created attachment 323957 [details] associated anaconda.syslog
Created attachment 323965 [details] sosreport after successful text install -- nv driver
Ajax, will try to capture the anaconda.log after a failed graphical install.
Can't establish a network connection via dhclient eth0. Installation sequence is as follows: Loading MPTSAS driver : Loading AHCI driver : Running Anaconda : Probing video : Waiting for xserver to start : "Input Not Supported" in box moving across screen : : CNTL+ALT+BS (kill X) : CNTL+ALT+F1 (switch to alternate xterm F1) 1...2...3...4...5... Xserver started successfully Starting graphical installation... Will post a screen photo of the anaconda.log later tonight.
Created attachment 323994 [details] anaconda log at graphical failure
Created attachment 324035 [details] Anaconda logs after failure (help from jlaska)
I only tried this on an x86_64 system but suspect it is all arches.
(II) Loading /usr/lib64/xorg/modules/drivers/nv_drv.so (II) Module nv: vendor="X.Org Foundation" compiled for 7.1.1, module version = 2.1.6 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.0 ... (**) NV(0): Default mode "800x600": 87.8 MHz (scaled from 0.0 MHz), 81.2 kHz, 65.0 Hz (D) (II) NV(0): Modeline "800x600" 87.75 800 832 928 1080 600 600 602 625 doublescan +hsync +vsync (**) NV(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz (II) NV(0): Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync The (D) means doublescan mode, which too many monitors don't support (or get confused by how G80 cards do it), so we turned it off. The 2.1.6 means you're running an old version of the nv driver. Both of these issues are fixed by xorg-x11-drv-nv-2.1.12-2.el5, which is included in snap3 and later. *** This bug has been marked as a duplicate of bug 466347 ***
VERIFIED that fix is in RHEL5.3 snapshot3 (20081113.1 ISO). Will post in bug 466347 as well.