[Bug 23683] KMS: X1950 AGP: problems with dual-head setup

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=23683





--- Comment #4 from Daniel Vetter <daniel at ffwll.ch>  2009-09-04 05:29:21 PST ---
On Thu, Sep 03, 2009 at 01:04:51PM -0700, bugzilla-daemon at freedesktop.org
wrote:
> --- Comment #3 from Daniel Vetter <daniel at ffwll.ch>  2009-09-03 13:04:50 PST ---
> Created an attachment (id=29190)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=29190)
>  --> (http://bugs.freedesktop.org/attachment.cgi?id=29190)
> dmesg with kms
> 
> I've created this log by directly booting into kms X. To my surprise,
> everything worked, i.e. both displays at native resolution and cursor working
> on both screens. Now as soon as I've restarted X, the old, buggy behaviour
> reappeared. The log contains both runs. So it looks like the problem only
> happens when X has already run once (doesn't matter wheter ums or kms). I
> didn't notice this till now because usually I boot up in ums. Then I kill X,
> rmmod radeon and finally modprobe radeon with modesetting enabled.

Correction: When booting up directly with kms, it does only work because X
is actually using user mode setting. At least that's what's in the log
file. And the flickering when switching between X and the linux console
confirms this. So dual head with kms does not work, not even on the first
time.

I suspect that we have a race condition between when X loads the radeon
modules and when the kernel has finished initializing kms. This somehow
results in X assuming there's no kms support present

-Daniel


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.