Created attachment 64783 [details] Xorg log file of failure details Not sure if this is an error with the video driver or with X, but the video driver did seem to compile correctly. Hardware (as listed from lspci and from a Dell XPS 8500): 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 7500 Series] Here's the relevant kernel config settings: Device Drivers ---> Generic Driver Options ---> [*] Include in-kernel firmware blobs in kernel binary (radeon/BARTS_mc.bin radeon/BARTS_me.bin radeon/BARTS_pfp.bin radeon/BTC_rlc.bin radeon/CAICOS_mc.bin radeon/CAICOS_me.bin radeon/CAICOS_pfp.bin radeon/CAICOS_rlc.bin radeon/TURKS_mc.bin radeon/TURKS_me.bin radeon/TURKS_pfp.bin) (firmware) Firmware blobs root directory Graphics support ---> <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---> <M> ATI Radeon [*] Enable modesetting on radeon by default - NEW DRIVER I've attached the Xorg.0.log file with the details of the failure. Any help at all in identifying the problem would be greatly appreciated. I'm unclear as to if it's in the video driver, as I suspect, or in X, or a combination of the two. Thanks. -Davey
Can you install debugging symbols and get a proper backtrace the gdb? http://wiki.x.org/wiki/Development/Documentation/ServerDebugging Also, please attach the dmesg output for your system.
(In reply to comment #1) > Can you install debugging symbols and get a proper backtrace the gdb? > http://wiki.x.org/wiki/Development/Documentation/ServerDebugging > > Also, please attach the dmesg output for your system. Sure thing, I'll add the dmesg file. As for the debugging symbols, I'm sure sure I'm clear on how to accomplish that. I followed the link provided and tried to do what I understood to do, which is to say I logged in from another machine and entered: gdb /usr/bin/Xorg $(pidof X) The output of which was: GNU gdb (Gentoo 7.3.1 p2) 7.3.1 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". For bug reporting instructions, please see: <http://bugs.gentoo.org/>... Reading symbols from /usr/bin/Xorg...(no debugging symbols found)...done. (gdb) I then tried to start an X session on the machine itself, while leaving that in it's current state, but nothing ever changed or output to the remotely connected machine running debug. The failure output on the machine itself was the same: Caught signal 11 (Segmentation fault) Am I not doing what you need correctly?
Created attachment 64808 [details] Boot log file output
(In reply to comment #2) > Reading symbols from /usr/bin/Xorg...(no debugging symbols found)...done. > (gdb) You need to enter 'run' at this prompt to actually run the X server in gdb. The attached dmesg output shows that the fglrx kernel module is loaded. For using the open source Radeon drivers, it's recommended to make sure no parts of fglrx are installed on the system, let alone loaded and active.
I appreciate your time in looking into this problem I was having, but I managed to get it resolved. I had a few issues going on with it, first of which I needed to manually remove the fglrx drivers that didn't get removed with the uninstall of the closed source drivers. I also needed to upgrade libdrm and xf86-video-ati to be the latest release, as well as configure my kernel to have AGP and the DRM options set to module, so they would auto-load. It was also necessary to install the radeon-ucode drivers, but not specify to install them in the kernel - not quite sure why that is, but it worked. At any rate, I'm up and running perfectly now and all is right in the world... okay, so the world is still pretty screwed up, but at least my computer is working. Thanks again for taking the time to look into this matter and I hope the information that fixed it for me helps you in some way.
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.