I think that in Adam?s case Xinerama is disabled already.
Announcement
Collapse
No announcement yet.
Dual monitors on fglrx 10.5 / Slackare 13.1
Collapse
X
-
Well, I?m not sure, but maybe Adam could try to explicitly disable the XRandr extension in xorg.conf. Sometimes this extension conflicts with some resources in the Catalyst driver. But it is just a possibility...
And in my case, I can?t disable de Xinerama extension, unfortunatelly, since It is needed in cases when one have a multi-card setup and one large desktop (ATI?s Big Desktop does not work in multi-card setup).
Comment
-
Originally posted by pflynn View PostAnd in my case, I can?t disable de Xinerama extension, unfortunatelly, since It is needed in cases when one have a multi-card setup and one large desktop (ATI?s Big Desktop does not work in multi-card setup).
No matter what, Xinerama is a pile of bugs. Prepare for pain and don't expect compositing to work.
Btw, that segfault you posted seems to come from within X, not from fglrx.
Comment
-
Originally posted by rohcQaH View PostI'm aware of that. Just saying that you should try to get working xorg.conf's for each of the cards, make sure each card is working fine on it's own. Once that's done, you can try joining them and add Xinerama. That'll help you narrow down the problems.
Code:aticonfig --initial
Originally posted by rohcQaH View PostNo matter what, Xinerama is a pile of bugs. Prepare for pain and don't expect compositing to work.
Originally posted by rohcQaH View PostBtw, that segfault you posted seems to come from within X, not from fglrx.
Comment
-
Originally posted by pflynn View PostAlso, the three monitor setup was working fine too, until the upgrade to 13.1 (using the same Catalyst 10.5).
It may be worth filing a bug-report. Prepare to be asked to re-create the bug with the OS drivers, blaming fglrx is always sooo easy
Originally posted by pflynn View PostI?m trying to disable it in xorg.conf file, but I?m not sure if Xorg cares about it, since it look like it?s just ignoring my configuration.
Comment
-
Originally posted by rohcQaH View Postso the driver version remains the same, but you're using a different version of Xorg? I have a strong suspicion about the real culprit here.
It may be worth filing a bug-report. Prepare to be asked to re-create the bug with the OS drivers, blaming fglrx is always sooo easy
Originally posted by rohcQaH View Postwhat makes you think the configuration is ignored? Any hints in Xorg.0.log?
Comment
-
Hi, good news.
I filled a bug report yesterday ( Bug 1828 - http://ati.cchtml.com/show_bug.cgi?id=1828 ), and today, an engineer from AMD, Felix Kuehling, replied to it:
Hi Pedro,
We know about the problem and a fix is in the pipe for release in July. In the
mean time you can try some workarounds:
- delete /dev/vga_arbiter before you start X, you'll have to do this again
every time you reboot
- if that doesn't work, try recompiling your kernel with CONFIG_VGA_ARB
disabled
Hope this helps.
Comment
Comment