Bug 693195

Summary: [RV570] KMS:X1950: Non smooth transition from plymouth with multi mon setup
Product: [Fedora] Fedora Reporter: Hans de Goede <hdegoede>
Component: xorg-x11-drv-atiAssignee: Jérôme Glisse <jglisse>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xorg.log
none
dmesg output on the system in question, in the multi mon setup in question. none

Description Hans de Goede 2011-04-03 13:18:47 UTC
I've been having a non smooth transition from plymouth for a while now (at least in F-14 too). I didn't bother filing a bug before because I blamed plymouth / initscripts / whatever and wanted to investigate first.

The problem is that when gdm (and thus Xorg) starts the screen gets corrupted, with a pattern which looks as if it has switched to a wrong pitch.

I've a single monitor, which is attached to my main workstation both through
a good old vga connector with a kvm so I can display my other systems too, as well as through a dvi cable for better picture quality (my monitor allows my to switch and unless I'm using multiple machines I'm using the dvi input.

FWIW the dvi cable is plugged to the "primary" dvi port of my X1950 where as the vga cable is connected to the secondary dvi port through a vga to dvi adapter.

Xorg thus sees my single monitor twice (which is fine). I've investigated the
non smooth transition from plymouth, and I think it is caused by Xorg choosing
a different layout for the 2 monitors (next to each other rather then clones) then kvm initially does, see xorg.log (which I will attach later, currently I booted with only the dvi cable connected to verify my theory.

Comment 1 Hans de Goede 2011-04-03 13:42:00 UTC
Created attachment 489653 [details]
xorg.log

Note this is on a fully up2date F-15 system. Also I just noticed the following in dmesg, which is not there with a single monitor (one cable connected) setup, which could be relevant:
kernel: [   12.719101] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

Comment 2 Matěj Cepl 2011-04-04 08:58:18 UTC
Could we get output of dmesg attached to this bug as well? Most funny stuff (as you certainly know) is going on in the kernel these days. Xorg.0.log doesn't look like anything special.

Comment 3 Hans de Goede 2011-04-04 09:06:35 UTC
Created attachment 489722 [details]
dmesg output on the system in question, in the multi mon setup in question.

Comment 4 Jérôme Glisse 2011-04-12 17:27:30 UTC
Quick guess is that we copy from plymouth which is untiled to X which is tiled.

Comment 5 Fedora End Of Life 2012-08-06 19:57:05 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2012-08-06 19:58:57 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping