From: phandel@cise.ufl.edu
To: sabotage <kcz84@dial.pipex.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Voodoo 3 bug on 2.3.99pre3
Date: Tue, 28 Mar 2000 14:01:47 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.21.0003281359550.14912-100000@adsl-78-160-189.gnv.bellsouth.net> (raw)
In-Reply-To: <200003280946.DAA21846@lists.linuxppc.org>
On Wed, 29 Mar 2000, sabotage wrote:
> I have a voodoo 3 2000 PCI card on my UMAX s900 SMP and i was trying to get
You can try the _experimental_ kernel & XFree86 3.9.16 rpm from Kostas:
ftp://idd-01.imbc.gr/pub/voodoo3
NOTE: XFree86 4.0 REQUIRES a very different /etc/X11/XF86Config file from
XFree86 3.x. I have some different XF86Config files at:
http://www.cise.ufl.edu/~phandel/linux/sample/
Also, you *may* need to change the BusID number based on what slot your
Voodoo3 is in (BusID "PCI:0:15:0" for me) if commenting it out doesn't
work.
3.9.16 runs well, although not as fast as 4.0. I've put a comparison of
the Rage128-x86, TNT2, and Voodoo3 XF86 3.9.16 & 4.0 on my web page:
http://www.cise.ufl.edu/~phandel/linux/txt/r128_tnt2_v3.txt
I believe these were all done at 1024x768 16bpp.
Thanks,
Peter
[btw- you can also copy the tdfxfb.c from 2.3.x to a 2.2.14 tree and apply
Kostas' tdfxfb patch, which is what I'm running]
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-28 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-29 9:48 Voodoo 3 bug on 2.3.99pre3 sabotage
2000-03-28 19:01 ` phandel [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-28 10:29 Michel D?nzer
2000-03-28 15:22 ` 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=Pine.LNX.4.21.0003281359550.14912-100000@adsl-78-160-189.gnv.bellsouth.net \
--to=phandel@cise.ufl.edu \
--cc=kcz84@dial.pipex.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.