Created attachment 742670 [details] dmesg Description of problem: Gdm does not start on 2011 iMac.
Created attachment 742673 [details] gdm logs
Created attachment 742674 [details] journalctl -a output 2011 iMac
Created attachment 742675 [details] lspci output 2011 iMac
Created attachment 742676 [details] X.org logs 2011 iMac
Might be a problem in the radeon driver, I am not sure.
it's a problem in X somewhere, it sure seems like. Can you follow the https://fedoraproject.org/wiki/How_to_debug_Xorg_problems instructions? We might possibly get something more out of the drm debug stuff. There may also be some kind of conflict between Intel and Radeon, I guess this is a dual adapter system.
You mean this: output of the dmesg command (please add drm.debug=14 log_buf_len=16M as boot parameters and reboot), especially in case of crashes How exactly should my boot parameters look on the live image booter?
Just add those two parameters to whatever's there already.
Created attachment 744105 [details] dmesg with proper command line argument (from TC3)
Tested on TC3, same results.
Re-assigning to X server for now - this seems to be an X issue, but I'm not sure if it's in the intel driver, radeon driver, or something that needs to bash both their heads together. ajax?
Tested on TC4, same results.
Proposed for freeze exception.
Discussed at 2013-05-15 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-15/f19beta-blocker-review-6.2013-05-15-16.02.html . We would need some input from the developer before we could really vote on this - how intrusive is the fix? How safe? How many users are affected? It's hard to make a call without some kind of idea about the nature of the bug and the fix.
Discussed at 2013-05-20 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-20/f19beta-blocker-review-7.2013-05-20-16.07.log.txt . We still don't have developer input here, but as it's now later in the Beta cycle we are stricter on FE status: this is rejected, as it's not clear what needs to be done and this bug appears to be limited in impact.
Seems to work now.....