From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: xorg-x11-6.8.0-r1 ready to go stable on all archs
Date: Sat, 16 Oct 2004 03:08:52 -0700 [thread overview]
Message-ID: <pan.2004.10.16.10.08.51.873623@cox.net> (raw)
In-Reply-To: 1097902422.1755.6.camel@mirage
Lance Albertson posted <1097902422.1755.6.camel@mirage>, excerpted below,
on Fri, 15 Oct 2004 23:53:42 -0500:
> I know I'm a little late in responding to this thread, but I just found
> out that 6.8.0-r1 breaks xinerama/dual+ display support for anyone running
> the Radeon chipset.
>
> I'm curious, are there any Radeon users out there running Xinerama that
> aren't having problems with this version?
I'm running it here, with a Radeon 9200SE AGP dual output card, no
problems. That's using the libreware drivers, and dual monitors, both
running 2048x1536, oriented one above the other for a 2048x3072 virtual
desktop.
Further, I've run both the standard dual adaptor/monitor/screen xorg.conf
(my default setup), and tried the new "MergedFB" mode as well. I ended up
going back to standard Xinerama mode however, because MergedFB doesn't
handle a larger than 2048x2048 in 3D accelerated mode anyway, and while it
does handle a large enough 2D mode, the inflexibility of having a single
unified resolution list as opposed to being able to handle each screen
resolution separately, coupled with not being able to do 3D anyway due to
my chosen resolutions, meant the standard Xinerama mode was the better
solution for me.
OTOH, I haven't recently tried running with two separate video cards
entirely. I had tried back with kernel 2.4/XFree, and couldn't get that
to work, as it'd never seem to initialize the second card correctly, altho
I know what it's like working, as I had it working with an NVidia dual
output card and their proprietaryware drivers, using an old 4MB S3 Virge
PCI as the second card driving the third monitor. Just couldn't get the
libreware Radeon drivers to do it, tho. Anyway, maybe two physical cards
was working with kernel 2.6 and xorg, and isn't now, as I haven't tried
two physical cards, only two outputs on the same card, which as I said,
works, here.
It also may be that I'm running AMD64 and yes it does work on that, but
maybe it doesn't on legacy 32-bit x86, or whatever other arch you may be
using. (Of course, another variable is that I'm running gcc-3.4, which is
stable on amd64. Maybe it works with gcc-3.4, but not with 3.3 or
whatever. And.. yes I DID verify I'm running xorg-x11-6.8.0-r1, so we're
talking about the same thing there.)
--
Duncan - List replies preferred. No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-16 10:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 20:25 [gentoo-dev] xorg-x11-6.8.0-r1 ready to go stable on all archs Donnie Berkholz
2004-10-11 21:47 ` Stuart Bouyer
2004-10-11 20:57 ` Donnie Berkholz
2004-10-11 21:54 ` Mike Frysinger
2004-10-11 22:50 ` Daniel Goller
2004-10-11 21:52 ` Donnie Berkholz
2004-10-11 22:58 ` Luke-Jr
2004-10-11 22:04 ` Donnie Berkholz
2004-10-12 3:43 ` Daniel Goller
2004-10-12 8:47 ` Mike Williams
2004-10-11 21:53 ` Lars Weiler
2004-10-11 21:10 ` Donnie Berkholz
2004-10-11 22:43 ` Lars Weiler
2004-10-12 13:43 ` Paul de Vrieze
2004-10-12 14:09 ` Lars Weiler
2004-10-11 22:21 ` Luke-Jr
2004-10-11 21:27 ` Donnie Berkholz
2004-10-11 22:39 ` Luke-Jr
2004-10-11 21:47 ` Donnie Berkholz
2004-10-12 9:01 ` Christian Parpart
2004-10-12 10:01 ` [gentoo-dev] " Sebastian Bergmann
2004-10-12 14:48 ` Donnie Berkholz
2004-10-11 23:00 ` [gentoo-dev] " neuron
2004-10-12 10:36 ` Henrik Brix Andersen
2004-10-16 4:53 ` Lance Albertson
2004-10-16 8:32 ` Stefan Schweizer
2004-10-17 11:25 ` Henrik Brix Andersen
2004-10-16 10:08 ` Duncan [this message]
2004-10-16 19:22 ` Carsten Lohrke
2004-10-17 3:25 ` Donnie Berkholz
2004-10-17 12:37 ` Carsten Lohrke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2004.10.16.10.08.51.873623@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox