Description of problem: After configuring xorg.conf for dualhead on my PowerBook G4, with the radeon driver, startx locks up the machine. SSH sessions die, pings time out. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. run system-config-display, set up dual head 2. run startx 3. Actual results: system freeze Expected results: dual head x starts Additional info: also tried modifying the xorg.conf file, which seems to be missing a few pieces, based on a previously working fc5 conf file. still locked up.
Created attachment 152862 [details] output of startx from ssh window
Please attach /var/log/Xorg.0.log from the failed startup.
Created attachment 154650 [details] xorg log for system-config-dsiplay dual head
Created attachment 154651 [details] xorg log from single display startup (just FYI)
Created attachment 154652 [details] xorg conf fiel generated by s-c-d
Created attachment 154653 [details] xorg conf, fixing pb screen size, using mergedfb
Created attachment 154654 [details] xorg log using merged fb Note that after fixing pb screen size and using mergedfb, X crashes but does not lock up the machine. (see stack trace in log file)
Fedora Core 6 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora 7, 8, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. [This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or Gecko. If you see any other reason, why this bug shouldn't be closed, please, comment on it here.]
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA. {This is mass-closing of all obsolete bugs; if this bug was in your opinion closed by mistake, please, reopen it with additional information; thanks a lot and I am sorry for bothering you in such case.}