Bug 1249 - X crashes on startup with fglrx
Summary: X crashes on startup with fglrx
Status: RESOLVED DUPLICATE of bug 1085
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xorg (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
Depends on:
Blocks: 351
  Show dependency treegraph
Reported: 2004-08-31 05:23 UTC by Seppe Van Sande
Modified: 2004-08-31 03:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Xorg log (44.88 KB, text/plain)
2004-08-31 05:25 UTC, Seppe Van Sande
no flags Details
Xorg config file (8.04 KB, text/plain)
2004-08-31 05:27 UTC, Seppe Van Sande
no flags Details

Description Seppe Van Sande 2004-08-31 05:23:27 UTC
Xorg from CVS and xorg-x11- have problems with fgrlx, ATI's closed
source driver. GDM loads fine, but when I log in as a normal user and select a
session (XFCE, Gnome, ...) then the colors look weird and X crashes and reloads
GDM again. I can succesfully log in as root. See the attachments for more info.
Comment 1 Seppe Van Sande 2004-08-31 05:25:45 UTC
Created attachment 787 [details]
Xorg log

When you grep for GL in Xorg.0.log.old, then you see this:

No matching visual for __GLcontextMode with visual class = -1 (-1), nplanes = 0

I think this is the problem, and I've seen other people with the same problem
but I haven't seen a solution for it.
Comment 2 Seppe Van Sande 2004-08-31 05:27:37 UTC
Created attachment 788 [details]
Xorg config file

This is my xorg.conf
I know it's correct, because I have used it succesfully before with the stable
version of Xorg. I only have made minor changes to it which are not related to
fglrx (keyboard driver for example)
Comment 3 Dave Airlie 2004-08-31 05:30:28 UTC
One of the success criteria is:

ATI and NVIDIA binary modules work with the release

so I marked this as a blocker...
Comment 4 Kevin E. Martin 2004-08-31 20:46:05 UTC

*** This bug has been marked as a duplicate of 1085 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.