From: "James B. Parker" <pajama1@mindspring.com>
To: LinuxPPC Developer <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Xfree86 4.0
Date: Mon, 13 Mar 2000 14:59:50 -0500 [thread overview]
Message-ID: <B4F2B2E6.152D%pajama1@mindspring.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10003131953540.6906-100000@opal.biophys.uni-duesseldorf.de>
<snip> from schmitz@mail.biophys.uni-duesseldorf.de on 3/13/00 1:59 PM
> You'll need to create a new XF86Config (XFree86 -configure should, in
> theory, do that).
> Depending on your kind of video hardware, XFree 4.0 will just not work at
> this time. I spent the last few days debugging the X server on my Lombard
> and almost trashed my installation in the process. It seems with the new
> XFree release, the X server on PPC finally became equally unstable as the
> Intel one :-)
> Michael
>
>
Actually, I do have a XF86Config file. After the build/install I ran
Xconfigurator (it finally recognized 6mb of vram) and then just skipped the
test section.
BTW, my video hardware is the basic rage pro found in rev. 2 G3's. I am
pretty sure Xconfig recognized the chip. My main problem now is just
solving the "no screens" issue.
So what are screens and where are they located?
James
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-13 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 18:39 Xfree86 4.0 James B. Parker
2000-03-13 18:55 ` Nelson Abramson
2000-03-13 19:56 ` James B. Parker
2000-03-13 18:59 ` Michael Schmitz
2000-03-13 19:59 ` James B. Parker [this message]
2000-03-13 22:07 ` phandel
2000-03-14 9:51 ` Michael Schmitz
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=B4F2B2E6.152D%pajama1@mindspring.com \
--to=pajama1@mindspring.com \
--cc=linuxppc-dev@lists.linuxppc.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 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.