Hello,

I'm trying to keep up with Slackware current on my Thinkpad T30, but I
am encountering a problem with the X11 6.9.0 of the Slack 11.

I'm using the external port of the portable in xinerama mode with the
ATI Radeon Mobility M7 LW.

I have no problem with the 6.8.x. But version 6.9.0 fails to recognize
any external screen I may connect and starts with the internal display
only.

The problem has been present with either the stock 2.4 kernel or the
custom 2.6 I usually use.

I have not found any post related to this problem and I don't know if
it comes from : XOrg, Slack11, or me.

Thanks for any pointer / clue.

xorg.conf :http://www.goupilland.net/t30/xorg.conf.html
the log : http://www.goupilland.net/t30/Xorg.0.log.htm
hardware / kernel configuration :
http://www.goupilland.net/t30/infos.html
-
Christophe RENARD

"Christophe Renard" <crenard@gmail.com> wrote:
>Hello,
>
>I'm trying to keep up with Slackware current on my Thinkpad T30, but I
>am encountering a problem with the X11 6.9.0 of the Slack 11.
>
>I'm using the external port of the portable in xinerama mode with the
>ATI Radeon Mobility M7 LW.
>
>I have no problem with the 6.8.x. But version 6.9.0 fails to recognize
>any external screen I may connect and starts with the internal display
>only.

I went back to version 6.8 because xinerama would not work on 6.9.

Multiple monitors will work with a merged framebuffer. That
puts the entire screen into a single virtual screen buffer, and
each monitor is a view port into the same virtual screen. But
unfortunately the gamma correction is applied to the entire
virtual screen, not to the data fed to the monitors. Hence only
one gamma correction can be done and it affects both monitors.

That may not be a problem in some circumstances, but in my case
needed to use the X server's gamma correction on each individual
monitor; which works with xinerama and version 6.8.

--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@apaflo.com

Floyd L. Davidson wrote:
> "Christophe Renard" <crenard@gmail.com> wrote:
....
> >I have no problem with the 6.8.x. But version 6.9.0 fails to recognize
> >any external screen I may connect and starts with the internal display
> >only.
>
> I went back to version 6.8 because xinerama would not work on 6.9.
>
> Multiple monitors will work with a merged framebuffer. That
> puts the entire screen into a single virtual screen buffer, and
> each monitor is a view port into the same virtual screen.
.....
>
Thanks for the advice, I did not know about merged framebuffer.
I'll check it.

Anyway, I find strange not to find much protest about xinerama problems
in 6.9.

Regards

--
Christophe Renard

"Goupil" <crenard@gmail.com> wrote:
>Floyd L. Davidson wrote:
>> "Christophe Renard" <crenard@gmail.com> wrote:
>...
>> >I have no problem with the 6.8.x. But version 6.9.0 fails to recognize
>> >any external screen I may connect and starts with the internal display
>> >only.
>>
>> I went back to version 6.8 because xinerama would not work on 6.9.
>>
>> Multiple monitors will work with a merged framebuffer. That
>> puts the entire screen into a single virtual screen buffer, and
>> each monitor is a view port into the same virtual screen.
>....
>>
>Thanks for the advice, I did not know about merged framebuffer.
>I'll check it.
>
>Anyway, I find strange not to find much protest about xinerama problems
>in 6.9.

It appears that everyone assumes the merged framebuffer is a
better way to go, and under most circumstances that is probably
true. All questions about dual head configurations are being
answered with "use the merged framebuffer"...

Note that you might well have lots of fun trying to get it to
work the first time! I saved the config file that I used, if
you'd like a copy of it. It works with two LCD monitors and the
"radeon" driver with an ATI 9200se video card.

--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@apaflo.com