Bug 1287 - Repeatable segv starting X w/ ATI closed-source driver
Summary: Repeatable segv starting X w/ ATI closed-source driver
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/fglrx (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: atilinuxbugsunassigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-03 15:50 UTC by David Hagood
Modified: 2005-03-25 20:20 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Log file showing segv (45.59 KB, text/plain)
2004-09-03 15:58 UTC, David Hagood
no flags Details
x.org config file used for that run (14.61 KB, text/plain)
2004-09-03 15:58 UTC, David Hagood
no flags Details

Description David Hagood 2004-09-03 15:50:44 UTC
I have never been able to get the closed source (boo!) ATI drivers to play
nicely with the Xorg server - they always segv at startup.

This is with a 2.8.1 kernel with 8K stacks enabled.

Steps to reproduce:
1) Install the ATI driver RPM for 4.3.0
2) Build the ATI kernel module.
3) Select ATI driver.
4) run startx.

Expected results:
X should start.

Actual results:
X segv's at start in mPicture_Init.
Comment 1 David Hagood 2004-09-03 15:58:02 UTC
Created attachment 819 [details]
Log file showing segv

This is a log of attempting to start with the proprietary drivers.
Comment 2 David Hagood 2004-09-03 15:58:50 UTC
Created attachment 820 [details]
x.org config file used for that run

This is the config file for that run.
Comment 3 David Hagood 2004-09-03 16:00:50 UTC
Additional info - this build of X was from a CVS pull of a couple of hours ago
(ca. 15:00 CDT Sept 3 2004.)

Also, after this run, attempting to fall back to the Free driver locks the
machine up at startup.
Comment 4 Adam Jackson 2004-09-03 19:37:38 UTC
could you look at the workaround in #1282 and see if that's the same issue?  if
so, could you also figure out which of the options is at fault?  hopefully it's
just one option causing the problem.
Comment 5 David Hagood 2004-09-08 04:25:24 UTC
I'm not sure what "workaround" you are referring to - all I saw in bug #1282 was
the statement that "it was the GLX module".

Are you suggesting disabling the loading of the GLX module, and/or the other
modules beyond the driver?
Comment 6 James McCarthy 2004-09-20 00:17:38 UTC
I think he's referring to <a href="show_bug.cgi?id=1282#c6">this comment</a>.
Comment 7 Adam Jackson 2005-03-26 12:58:52 UTC
reporter: ping.
Comment 8 David Hagood 2005-03-26 15:20:53 UTC
The lastest X, and the latest fglrx driver from ATI do not show this behavior.


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.