From: ichi@ihug.co.nz
To: James Miller <jamtat@mailandnews.com>
Cc: Ray Olszewski <ray@comarre.com>, linux-newbie@vger.kernel.org
Subject: Re: more X problems
Date: Thu, 14 Nov 2002 16:23:57 +0000 [thread overview]
Message-ID: <3DD3CE1D.3CC4333A@ihug.co.nz> (raw)
In-Reply-To: Pine.LNX.4.44.0211132030330.21708-100000@localhost.localdomain
James Miller wrote:
>
> The text file that accompanies the xserver file Steven
> suggested does, in fact, mention support for the S3Trio 64+
> (not V+, as my card is supposed to be). But then, if
> XFree86 4.2.0 does not support this card, why is it listed
> in the database of cards one can choose when running xf86config
> under XFree86 4.2.0? Doesn't make much sense to me.
False alarm. Your card is supported. I found this
at http://www.xfree86.org/4.2.0/Status28.html#28
-----------------------------------------------
4.2.0: Support for the 964 (revisions 0 and 1),
968, Trio32, Trio64, Trio64, Trio64V+,
-----------------------------------------------
However, I also found (elsewhere) that the framebuffer (fb)
requires VESA 2.0. It does not work with VESA 1.2 (which
is what the Trio ^64+ is). What effect (if any) this has
on XFree 4.2.0, I do not know.
Cheers,
Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-11-14 16:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 2:23 XFree86 crash log james miller
2002-11-13 3:02 ` Ray Olszewski
2002-11-14 13:14 ` ichi
2002-11-13 16:28 ` ichi
2002-11-13 5:04 ` James Miller
2002-11-13 19:23 ` more X problems James Miller
2002-11-13 19:33 ` hackob
2002-11-13 20:29 ` James Miller
2002-11-13 21:07 ` hackob
[not found] ` <Pine.LNX.4.44.0211131425440.21708-100000@localhost.localdo main>
2002-11-13 21:00 ` Ray Olszewski
2002-11-13 21:37 ` James Miller
2002-11-14 12:22 ` ichi
2002-11-14 1:34 ` James Miller
[not found] ` <Pine.LNX.4.44.0211131911530.21708-100000@localhost.localdo main>
2002-11-14 1:39 ` Ray Olszewski
2002-11-14 2:41 ` James Miller
2002-11-14 16:23 ` ichi [this message]
2002-11-14 16:49 ` ichi
2002-11-14 4:36 ` James Miller
[not found] ` <Pine.LNX.4.44.0211131215130.21708-100000@localhost.localdo main>
2002-11-13 20:13 ` Ray Olszewski
2002-11-13 20:55 ` James Miller
2002-11-14 2:13 ` XFree86 crash log Peter
2002-11-14 2:45 ` James Miller
2002-11-15 0:53 ` Peter
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=3DD3CE1D.3CC4333A@ihug.co.nz \
--to=ichi@ihug.co.nz \
--cc=jamtat@mailandnews.com \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/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