From: Michel Dänzer <daenzer@relog.ch>
To: Taylor Holliday <wtholliday@ucdavis.edu>
Cc: Linux PPC Developer List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Xfree 4.0.1 dual head attempt
Date: Thu, 13 Jul 2000 14:37:43 +0200 [thread overview]
Message-ID: <396DB817.4C2D82F1@relog.ch> (raw)
In-Reply-To: 396D1C7B.AA6864F5@ucdavis.edu
Taylor Holliday wrote:
> Attached is the latest XFree86.0.log as well as the XF86Config from my
> recent build (yesterday) of 4.0.1 with the drivers rsync'ed from
> penguinppc.org. Hey, at least it doesn't crash the machine (AGP G4, 2
> r128) :-). Any suggestions on what to do or where to start debugging?
A gdb backtrace mey be interesting, at least with a static server.
> (==) ServerLayout "DualHead"
> (**) |-->Screen "Screen0" (0)
> (**) | |-->Monitor "Monitor0"
> (**) | |-->Device "r128"
> (**) |-->Screen "Screen1" (1)
> (**) | |-->Monitor "Monitor0"
> (**) | |-->Device "r128.1"
You are using the same Monitor for both Screens. Have you tried using
different ones? (All in terms of XF86Config ;)
Michel
--
Pauli's exclusive, Heisenberg's uncertain, and Schroedinger just waves.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-13 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 1:33 Xfree 4.0.1 dual head attempt Taylor Holliday
2000-07-13 12:37 ` Michel Dänzer [this message]
2000-07-13 18:23 ` W. Taylor Holliday
2000-07-13 14:01 ` Nelson Abramson
2000-07-13 18:24 ` W. Taylor Holliday
2000-07-13 14:03 ` Kostas Gewrgiou
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=396DB817.4C2D82F1@relog.ch \
--to=daenzer@relog.ch \
--cc=daenzerm@student.ethz.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=wtholliday@ucdavis.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.