Description of problem:
Start X via either xdm or startx with aticonfig's xorg.conf and X server segfaults.
Steps to reproduce:
1. aticonfig --initial to produce an /etc/X11/xorg.conf
2. startx or start the xdm/kdm system service.
3. X server segfaults
Actual result: X server segfaults.
Expected result: X server does not segfault.
atisysteminfo-report.txt and Xorg.8.log to be attached.
Created attachment 550 [details]
Created attachment 551 [details]
log for the segfault
My X server build-info as follows:
X.Org X Server 1.12.3
Release Date: 2012-07-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.5.0-gentoo x86_64 Gentoo
Current Operating System: Linux localhost 3.5.0-gentoo #1 SMP Fri Jul 27 11:01:49 SGT 2012 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-gentoo root=/dev/sda6 ro rootfstype=jfs raid=noautodetect resume=/dev/sda5 selinux=1 video.allow_duplicates=1 keymap=us modprobe.blacklist=radeon pcie_aspm=force i915.semaphores=1 i915.lvds_downclock=1 i915.i915_enable_fbc=1 i915.i915_enable_rc6=1
Build Date: 04 August 2012 09:48:07AM
Current version of pixman: 0.27.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
However, xf86-video-intel 2.20.2 works quite well with Catalyst 12.6.
My speculation is that Intel changed/added new PCI-ID's in the release and FGLRX did not recognize them.
link for Gentoo's bugzilla:
for added intel's hardware id:
This message is a reminder that your bug is marked as Catalyst 12.6.
The current legacy Catalyst version is 13.1.
The current Catalyst version is 13.4.
The current Catalyst beta version is 13.8.
Approximately 7 days from now the Bugzilla administrator will be removing the 12.6 version. At that time your bug will be CLOSED as WONTFIX.
Bug Reporter: Thank you for reporting this issue. However, the Bugzilla administrator provides this as a unofficial, free service to AMD customers, and I like to keep my systems neat and tidy. If you would like to keep your bug from being closed, please try a new Catalyst version and update the 'version' field if the issue still occurs.
If you are unable to update the version, please make a comment and someone will change it for you.
This bug is being closed due to the 'version' being 12.6 after 7 days of the previous closure notice.
Thank you for your bug report.