From: Jorge Nerin <comandante@zaralinux.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Linux Framebuffer <linux-fbdev@vuser.vu.union.edu>,
"Rickard E. (Rik) Faith" <faith@valinux.com>,
Daryll Strauss <daryll@valinux.com>,
Hannu Mallat <hmallat@cc.hut.fi>
Subject: Voodoo 3 pci issues
Date: Wed, 28 Mar 2001 00:30:00 +0200 [thread overview]
Message-ID: <3AC11468.9030308@zaralinux.com> (raw)
Hello, I'm using 2.4.2-ac24, Xfree86 4.0.2 + 4.0.3 upgrade,
Glide_V3-2.60-16 & Glide_V3-DRI-3.10-6, and tdfx framebuffer.
My system is a 2x200MMX on a Gigabyte 586DX with 96Mb, a Voodoo3 2000
pci and a bt848 tv card.
I have the card working ok, except for a few nonstopers.
- I cannot use the 3D part of my card with XFree 4.x (it worked with
3.3.x) it doesn't matter whether I use or not tdfx.o or whether or not I
put a LoadModule dri in the XF86Config. Only root can run the test3Dfx
program, and when the program finish X is restored but freezed, so I
have to do a SysRQ-K to kill it.
- If I try to use fbtv (watch tv in FB) the system hangs, the program
starts, and I can see the tv on the screen, but the system is freezed.
- If I put a LoadModule dri in the XF86Config, I cannot use the virtual
consoles. If I go to a text console (tdfx frame buffer at 100x37) I see
the contents of the text console (issue and login prompt), but I see a
line near the top of the console of random pixels of one pixel that
paints pixels from left to rigth from top to botttom, and I cannont see
what I'm typing. I can ony come back to X. When I'm on that VT if I
switch to another VT I still see the contents of the first VT that I
switched from X.
Thanks for your patience.
--
Jorge Nerin
<comandante@zaralinux.com>
reply other threads:[~2001-03-27 22:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AC11468.9030308@zaralinux.com \
--to=comandante@zaralinux.com \
--cc=daryll@valinux.com \
--cc=faith@valinux.com \
--cc=hmallat@cc.hut.fi \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox