Re: dual displays
On Thu, Aug 23, 2001 at 10:17:30AM +0200, Cyan Ogilvie wrote:
> On Wed, Aug 22, 2001 at 06:13:44PM -0700, Jeremiah Mahler wrote:
> [...snip...]
>
> > Gary,
> >
> > Well, inspired by your success with the G450 I decided to go through my
> > Radeon setup again and see exatcly what is going on. I am getting dual
> > head output from the card which did not work in the past but I cannot
> > get Xinerama to work. I have had Xinerama working with two seperate
> > cards (Radeon and another card) but it does not work with just the
> > Radeon by itself. I do not understand how to configure a dual
> > headed card. Is it two seperate devices or just two screens with the
> > same card. How did you configure your G450 and what are the important
> > parts of the XF86Config to set up with dual-head cards.
> >
>
> You need two Device sections, pretty much identical, but with
> different identifiers of course. Get the busid for the card from
> lspci or XFree86 -scanpci. It'll prolly be 1:0:0 if it's AGP and
> add it to each of the device sections like so:
>
> BusID "PCI:1:0:0"
>
> I also had to put a "Screen 1" in the second head's Device section.
>
> Then two Monitor sections with different identifiers, and two screen
> sections with the Device and Monitor options pointing to the ones
> defined above.
>
> Then a ServerLayout section including lines something like:
> Screen "Display 1" LeftOf "Display 2"
> Screen "Display 2" 0 0
>
> And all should be well. For those with a G400 or G450 I highly
> recommend Matrox's mgapdesk util (get the rpm from matrox.com and
> alien it). It sets up multi head really easily.
>
> Cyan
>
Cyan,
Thanks for all the tips, they have helped greatly. I have now worked
the errors into this new one.
file: XFree86.0.log
.
.
.
(II) Loading sub module "radeon"
(II) LoadModule: "radeon"
(II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o
Fatal server error:
Requested Entity already in use!
.
.
.
I am confused by this error because I do not know what is referred to
by "entity". Everything else looks good up until this error. I have
no idea what configuration option would effect this type of error.
--
Jeremiah Mahler
<jmahler@pacbell.net>
Reply to: