Created attachment 53303 [details] made a photo of the monitor when it is messed up When booting the distribution through normal BIOS (Asus P8Z68-V LX and Sapphire Radeon 6870) my screen is just fine, if i boot through UEFI 2/5th of the right hand side of the screen continue from the left side of the monitor. The plymouth login is messed up the same way.
I have alos uploaded dmesg from normal boot as in through BIOS: http://fpaste.org/WQ1a/ and the messed up one: http://fpaste.org/E2Kq
Please attach your dmesg outputs as they may become unavailable on fpaste eventually.
Created attachment 53304 [details] NORMAL BOOT
Created attachment 53305 [details] UEFI BOOT
Please advise me on how to debug this issue, i am available from 5 to 11 PM London Time. I have also reported this bug to fedora with a "shortcut" to this report.
You need to build git://people.freedesktop.org/~airlied/radeontool and use avivotools reg crtc1 and attach output in both efi and bios mode
Created attachment 53539 [details] BIOS BOOT (VGA through DVI to VGA adapter)
Created attachment 53540 [details] UEFI BOOT (through VGA to VGA adapter)
Created attachment 53541 [details] UEFI BOOT WITH HDMI
Been unlucky need avivotool regs crtc2 Just use the same connector in both uefi & bios mode to avoid any difference on that front.
avivotool doesn't support dumping crtc registers on newer asics, it also doesn't properly support different sized mmio apertures. Try: radeonreg regs dce5
Created attachment 56296 [details] Output of radeonreg regs dce5 when booting with normal BIOS
Created attachment 56297 [details] Output of radeonreg regs dce5 when booting with UEFI All this happening on Fedora 16, not tested on other distros
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
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.