Red Hat Bugzilla – Bug 427635
T61P graphical install fails
Last modified: 2010-11-01 15:58:25 EDT
Description of problem: Trying to install on a Thinkpad T61P, with a Quadro FX 570M, the X server apparently starts, but the screen goes blank and that's it - nothing is displayed, and I can't switch to the other virtual consoles. Specifying resolution=640x400 or driver=vesa does not help. I don't know another way to provide further debugging info, as I can't get back to the text console. Version-Release number of selected component (if applicable): RHEL5.1 x86_64 How reproducible: Every time.
Created attachment 290896 [details] Post-install Xorg log on failure
Proprietary nvidia driver does work.
I found a bug on freedesktop that describes this (btw, VESA with 1280x1024 works too)
Hi, John (we know each other from LyX bugzilla, but there you were on the other side of the fence ;-)), could you try starting X without any /etc/X11/xorg.conf whatsoever? What happens? Could we get a log from that attempt, please? Also, what is the status of your RHEL subscription? Why you haven't filed the bug into the IssueTracker? Is this CentOS, or what? (not that we would have anything against CentOS, just that being in the IssueTracker would rise your priority, CentOS bug is for me as any other Fedora bug).
Hi Matej: starting X without an xorg.conf gives the same symptoms. Attaching the Xorg.0.log. This is CentOS 5.1, indeed, hence the filing location - if you'd prefer me to file this in CentOS's tracker instead, I certainly can do.
Created attachment 292391 [details] Xorg log
(In reply to comment #5) > This is CentOS 5.1, indeed, hence the filing location - if you'd prefer me > to file this in CentOS's tracker instead, I certainly can do. No, that's OK, I just need to be sure that no true RHEL bug is filed directly through bugzilla. Our business customers have different issue tracker which works with all entitlements, response time, and similar stuff. For me, CentOS is just another spin of Fedora ;-). Passing to the developers.
bug #428438 is probably duplicate of this entry.
Yup, you are right. Closing as duplicate. *** This bug has been marked as a duplicate of 428438 ***