The Retina 5K iMac has a 5K screen but it is only possible to go up to 4K with Linux. I should probably attach some files here but I am not sure which.... Tested with 3.18.2-200.fc21
The output of dmesg and the Xorg.0.log would be a good start.
Created attachment 982524 [details] dmesg
There does not seem to be any /var/log/Xorg.0.log.....
(In reply to Andreas Tunek from comment #3) > There does not seem to be any /var/log/Xorg.0.log..... Sorry, I forgot Xorg output is in the journal now. You can get it by running: journalctl -b 0 _COMM=Xorg.bin > Xorg.0.log
please boot with drm.debug=6 and get the dmesg log also thanks.
The Xorg log is empty if I boot normally. How do I boot with other debug mode?
journalctl -b 0 _COMM=Xorg might work either, or just dump the full journal, for drm.debug=6 you need to add it to the kernel on the kernel command line in grub when you boot up.
Created attachment 984390 [details] Grub From the state in the attached file, how do you actually boot the system. Ctrl-x does not do anything....
[tuna@iMacLinux ~]$ journalctl -b 0 _COMM=Xorg -- Logs begin at Mon 2015-01-19 21:39:39 CET, end at Mon 2015-01-26 21:15:50 CET. -- That is all I get.... if I just do journalctl I get a lot of unneeded stuff....
journalctl -b -u gdm > journal_gdmxorg.log In GRUB, usually either F10 (could be one button, could be Fn + F10) or control-x will work. Sometimes both work. On my Macs I use fn + F10, because control-x doesn't work.
[tuna@iMacLinux ~]$ journalctl -b -u gdm -- Logs begin at Mon 2015-01-19 21:39:39 CET, end at Mon 2015-01-26 21:40:47 CET lines 1-1/1 (END)
you need to add drm.debug=6 on the end of the linuxefi line and I think fn-f10 or something to boot, or ctrl-x.
Created attachment 984406 [details] dmesg with drm.debug=6
(In reply to Andreas Tunek from comment #11) > [tuna@iMacLinux ~]$ journalctl -b -u gdm > -- Logs begin at Mon 2015-01-19 21:39:39 CET, end at Mon 2015-01-26 21:40:47 > CET > lines 1-1/1 (END) Assuming you have any xorg lines, this should work: journalctl -b | grep -i xorg > journalxorg.log Weird though, because -u gdm works for me on Fedora 21. If you just do journalctl -b --no-pager in a terminal window so you can scroll around, do you see any entries like this? I have maybe a hundred lines in a row of gdm-Xorg-:0 Jan 26 11:18:20 f21t.localdomain gdm-Xorg-:0[851]: This is a pre-release version of the X server from Fedora Project. Optional, using -o short-monotonic (before or after -b) is a bit cleaner.
(In reply to Andreas Tunek from comment #9) > [tuna@iMacLinux ~]$ journalctl -b 0 _COMM=Xorg > -- Logs begin at Mon 2015-01-19 21:39:39 CET, end at Mon 2015-01-26 21:15:50 > CET. -- > > That is all I get.... if I just do journalctl I get a lot of unneeded > stuff.... The binary is named *Xorg.bin* not Xorg so use journalctl -b 0 _COMM=Xorg.bin
[tuna@iMacLinux ~]$ journalctl -b 0 _COMM=Xorg.bin -- Logs begin at Mon 2015-01-19 21:39:39 CET, end at Mon 2015-01-26 22:15:48 CET lines 1-1/1 (END)
Created attachment 984411 [details] 4K info from gnome screen
Created attachment 984412 [details] dmidecode output
Created attachment 984413 [details] lspci -vvnn output
Should I report this to another upstream?
No this is fine for now, okay the drm.debug=6 didn't get put in the right place, it needs to go at the end of the linuxefi line with the rhgb quiet etc on it Alternatively it might give me enough info if you as root: echo 6 > /sys/module/drm/parameters/debug then run xrandr in your X session, and atttach the dmesg and xrandr output.
Created attachment 985374 [details] dmesg with drm.debug=6 Hopefully this is correct....
Created attachment 992867 [details] xrandr output
Created attachment 992868 [details] dmesg after xrands
Tested with F23 Linux (4.2 rc4).
Created attachment 1172544 [details] Fedora 24 xrandr New xrandr from F24. A new screen appeared :)
I would like to note that 2560x1440 does not display correctly (strange double columns on the screen. (Actually anything above 1920x1080 or 1920x1200) doesn't seem to work correctly besides 3840x2160
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I'll try a rawhide image some day.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.