Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 162306 - starting X11 on i830M takes a long time
Summary: starting X11 on i830M takes a long time
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-02 08:14 UTC by David Monniaux
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-08-30 08:03:39 UTC

Attachments (Terms of Use)

Description David Monniaux 2005-07-02 08:14:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114

Description of problem:
When starting X, the X server takes a long time. Apparently, it tries one video mode, isn't happy, tries another video mode, isn't happy, then tries a third and is happy.

If booting with rhgb, the same happens when the system starts the graphic mode, which is annoying (and sometimes it even seems to fail and I have to VT-switch to text mode then back to graphics). I thus disabled rhgb.

System: Dell Latitude X200, i830M graphics, 1024x768 internal TFT LCD display

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

How reproducible:

Steps to Reproduce:
1. use a Dell Latitude X200
2. start X (or use telinit 5)

Actual Results:  It takes a while (screen flashes etc.) before X11 comes up.

Expected Results:  It should come up quickly as it used to do in FC1 etc.

Additional info:

Dell Latitude X200
TFT display

Comment 1 Mike A. Harris 2005-07-05 10:22:05 UTC
Upgrade to Fedora Core 4, apply all updates, and review bug #161242 which
might affect you in FC4.  If so, try the workaround in that bug, and an
update will be out for FC4 in the next month or so to resolve bug #161242.

Comment 2 Mike A. Harris 2005-08-30 08:03:39 UTC
This bug contains insufficient information to be able to diagnose the
cause of the problem, and there hasn't been any response to my inquiry
to obtain additional information over a month ago.

As such, we are unable to troubleshoot this problem further.

If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at in the "xorg"

Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.

Closing NOTABUG.

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