Bug 78827 - Xserver can't start
Xserver can't start
Status: CLOSED DUPLICATE of bug 73733
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-12-01 13:12 EST by aaron
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:50:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
The log file from the failed XServer start (14.68 KB, text/plain)
2002-12-01 13:13 EST, aaron
no flags Details

  None (edit)
Description aaron 2002-12-01 13:12:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126

Description of problem:
While doing the upgrade from 7.3 to 8.0 when it failed while "Probing for
monitors".  Later after the install which went allright it tried to start the
Xserver and gave and NVidia driver error saying there weren't any usable screens
and when i tried the X configuring tool it said bogus values returned.  My
monitol is a Hansol 710D and my video card is a GeForce 2 (32?) MB.  The system
worked properly with redhat 7.1, 7.2 and 7.3.

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

How reproducible:

Steps to Reproduce:
1.Upgrade from 7.3 to 8.0
2.try to start XServer
4.goto 2

Actual Results:  Xserver wouldn't start configuration tool wouldn't work

Expected Results:  XServer would start of the configureation tool would work

Additional info:
Comment 1 aaron 2002-12-01 13:13:25 EST
Created attachment 86984 [details]
The log file from the failed XServer start
Comment 2 Mike A. Harris 2002-12-18 15:31:04 EST

*** This bug has been marked as a duplicate of 73733 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:50:14 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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