stefan djurdjanovic wrote:
> Hi,
>
> i have problem with DRI Missing file.
I doubt in the previous post you found your answer, better post what is your
video card.
DRIVER
check if your video driver is configured properly
check what it says regarding DRI in the log file
[77.287] (II) modese
Using the linux-image-2.6.24-1-686 version 2.6.24-5 which is in
unstable (sid) solves the problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
It does seem to be this incompatibility between i915,drm modules and the
kernel itself. I have downloaded and compiled the DRM modules and got further,
but now there seems to be another problem along the same lines as what users of
other distributions have faced and solved:
http://forums.fedo
Andras Lorincz wrote:
>
> ...
>
> As regarding direct rendering, I say hmm...:
>
> (II) RADEON(0): Direct rendering broken on XPRESS 200 and 200M
> (WW) RADEON(0): Direct rendering disabled
>
> It seems that direct rendering is broken in xorg for x200m chipsets.
> That expla
On 1/17/07, Andras Lorincz <[EMAIL PROTECTED]> wrote:
On 1/17/07, "Dr. Jörg-Volker Peetz" <[EMAIL PROTECTED]>
wrote:
>
> Andras Lorincz wrote:
> >
> >
> >
> > What is the output of
> > grep -i enabled /var/log/Xorg.0.log
> >
> >
> > This gives me:
> >
> > (==) AIGLX enabled
> > (II)
On 1/17/07, "Dr. Jörg-Volker Peetz" <[EMAIL PROTECTED]>
wrote:
Andras Lorincz wrote:
>
>
>
> What is the output of
> grep -i enabled /var/log/Xorg.0.log
>
>
> This gives me:
>
> (==) AIGLX enabled
> (II) RADEON(0): Color tiling enabled by default
> (II) RADEON(0): Acceleration enabled
Andras Lorincz wrote:
> >What is the output of
> > grep -i enabled /var/log/Xorg.0.log
>
>
> This gives me:
>
> (==) AIGLX enabled
> (II) RADEON(0): Color tiling enabled by default
> (II) RADEON(0): Acceleration enabled
> (**) RADEON(0): DPMS enabled
> (==) RADEON(0): Silken mouse enabled
What is the output of
grep -i enabled /var/log/Xorg.0.log
and
LIBGL_DEBUG=verbose glxinfo
?
Did you replace the libGL from fglrx?
Regards,
Jörg-Volker.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello /me.
Mathias Brodala, 13.01.2007 20:03:
> If that is the case, then have you should take a closer look […]
Yep, me have should take a closer one also.
Mathias
--
debian/rules
signature.asc
Description: OpenPGP digital signature
Hello Andras.
Andras Lorincz, 13.01.2007 18:45:
> On 1/13/07, Mathias Brodala <[EMAIL PROTECTED]> wrote:
>> Andras Lorincz, 13.01.2007 13:45:
>> > I'm using debian testing on my laptop that has x200 graphics chipset.
>> With
>> > the ati proprietary drivers, 3D acceleration is working but those
>>
On 1/13/07, Mathias Brodala <[EMAIL PROTECTED]> wrote:
Hello Andras.
Andras Lorincz, 13.01.2007 13:45:
> I'm using debian testing on my laptop that has x200 graphics chipset.
With
> the ati proprietary drivers, 3D acceleration is working but those
drivers
> don't support AIGLX, so I would like
Hello Andras.
Andras Lorincz, 13.01.2007 13:45:
> I'm using debian testing on my laptop that has x200 graphics chipset. With
> the ati proprietary drivers, 3D acceleration is working but those drivers
> don't support AIGLX, so I would like to use free radeon drivers. The
> problem
> is that I cann
Am 2006-09-10 15:40:46, schrieb David E. Fox:
> [EMAIL PROTECTED]:/var/log$ grep DRI Xorg.0.log
> (II) Loading extension XFree86-DRI
> (EE) MGA(0): [drm] DRIScreenInit failed. Disabling DRI.
Same problem here, Etch AND Sid.
Under Sarge I can not activate DRI too.
> I'm using a Matrox G450 card.
>Here is what happens with flightgear and its family:
>freeglut (fgfs): Unable to create direct context rendering for window
>'FlightGear'
>This may hurt performance.
>fgfs: indirect_vertex_array.c:1359: __indirect_glTexCoordPointer: Assertion
>`a != ((void *)0)' failed.
>Aborted
>Other program
On Thu, 15 Jun 2006 14:56:57 +0300
David Baron <[EMAIL PROTECTED]> wrote:
> Works just fine, for what it is worth.
After changing xorg.conf to default to 16 bit color depth, googleearth
does run. A bit slowly, but then I only have an Athlon Tbird.
Running apt-cache policy on 'xlibmesa-dri' sugg
On Thursday 15 June 2006 06:07, David E. Fox wrote:
> On Tue, 13 Jun 2006 20:30:29 +0300
>
> David Baron <[EMAIL PROTECTED]> wrote:
> > Other programs, ppracer, work in software mode and are unusable. Ysflight
> > actually seems to be using DRI though this program works nicely in
> > software mode
On Tue, 13 Jun 2006 20:30:29 +0300
David Baron <[EMAIL PROTECTED]> wrote:
>
> Other programs, ppracer, work in software mode and are unusable. Ysflight
> actually seems to be using DRI though this program works nicely in software
> mode as well.
I posted about this a few days ago when updating
"David E. Fox" <[EMAIL PROTECTED]> said on Tue, 10 Jan 2006 21:12:28 -0800:
> On Mon, 9 Jan 2006 22:49:18 +1100 (EST)
> Tim Connors <[EMAIL PROTECTED]> wrote:
>
> > G'day all,
> >
> > I have an Dull Inspiron 4000, which always used to have working DRI and XV
> > under kernel 2.4 and XFree86 4.x.
On Mon, 9 Jan 2006 22:49:18 +1100 (EST)
Tim Connors <[EMAIL PROTECTED]> wrote:
> G'day all,
>
> I have an Dull Inspiron 4000, which always used to have working DRI and XV
> under kernel 2.4 and XFree86 4.x. The video card is a Rage 128:
>
snipping some of this - as I have etch running xorg 6.
Using Mode 0666 does in fact work. What the problem is:
DRI dependent applications will not work correctly run from KDE menus/panels,
even if "run in terminal". One must explicitely open an xterm and run from
there. This is also a problem run as root!
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
On Thu, Jul 29, 2004 at 03:28:38PM +0300, David Baron wrote:
> On Thursday 29 July 2004 15:15, [EMAIL PROTECTED]
> wrote:
> > Section "dri"
> > Mode 0666
> > EndSection
> >
> > It works. Maybe the 0 is important.
>
The 0 is important since it means that the number is octal (base 8) and
not d
On Thursday 29 July 2004 15:15, [EMAIL PROTECTED]
wrote:
> Section "dri"
> Mode 0666
> EndSection
>
> It works. Maybe the 0 is important.
That is what I had originally.
Hi David
On Wed, Jul 28, 2004 at 03:26:15PM +0300, David Baron wrote:
> seems not to be permitted. I have the DRI section in XFConfig-4:
> Section "DRI"
> Mode 666
> EndSection
>
> I tried adding a Group "dri" and made the user's members of this group, no a
> avail.
In mine, it says
#
On Mon, Jul 05, 2004 at 09:52:18AM +0300, David Baron wrote:
> On Sunday 04 July 2004 19:39, [EMAIL PROTECTED]
> wrote:
> > What is the output of 'glxinfo'? Look at the top four lines.
>
> OK. Here follows the glxinfo output, apparently fairly typical for a mach64
> card.
>
> Actually, Tuxracer
On Sunday 04 July 2004 19:39, [EMAIL PROTECTED]
wrote:
> What is the output of 'glxinfo'? Look at the top four lines.
OK. Here follows the glxinfo output, apparently fairly typical for a mach64
card.
Actually, Tuxracer (full screen) runs perfectly!
However, gl117 (full screen) comes up with a l
On Sun, Jul 04, 2004 at 05:02:15PM +0300, David Baron wrote:
> Here is what I have so far. Just put in the 2.6.7 kernel (Hey, now the mouse
> is working immediately--enough of an improvement. :-) )
>
> # dmesg | grep AGP
> agpgart: AGP aperture is 64M @ 0xd000
> [drm] Initialized mach64 1.0.0
On Monday 19 April 2004 15:48, James Vahn wrote:
Hi,
> it no longer worked. Everything else is fine, glxgears included. I've no
> solution, but would wager that nobody can run Flightgear on a Sarge/Sid
> box at the moment.
I would expect to see some bug reports against xlibmesa-gl in that case,
On Thursday 15 April 2004 15:30, James Vahn wrote:
Hi,
> Having the same trouble here with Flightgear too, just last week it
> began running at 1 FPS. I strongly suspect "xlibmesa-gl" but that's
> just a guess. I've been running Sarge all along, the problem seems
> to have started about 2 weeks a
On Thursday 15 April 2004 17:38, Chris Metzler wrote:
Hi,
> I dunno, but I've been wondering too. Ever since I upgraded from
> X 4.2 to 4.3, my OpenGL performance has gone into the toilet. I
> used to be able to play bzflag normally; since I upgraded to 4.3,
> I've had to lower many graphics pa
Yup, that did it. Thanks...
--
John L. Fjellstad
web: http://www.fjellstad.org/ Quis custodiet ipsos custodes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Apr 16, 2004 at 07:39:00PM +0200, John L Fjellstad wrote:
> Does anyone know when and how /dev/dri/card0 is created? And where the
> permissions are set? I tried searching on google, but couldn't find
> anything.
>
> The problem is that the dri/card0 is created with permissions root.ro
On Thu, Apr 15, 2004 at 11:38:26AM -0400, Chris Metzler wrote:
> I dunno, but I've been wondering too. Ever since I upgraded from
> X 4.2 to 4.3, my OpenGL performance has gone into the toilet.
Same here, and also with a Matrox G550.
--
Bill Moseley
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, ema
On Thu, 15 Apr 2004 09:16:44 +0200
Gebhardt Thomas <[EMAIL PROTECTED]> wrote:
>
> during the easter holidays I upgraded from woody to sarge (and kernel
> 2.4.19 -> 2.4.25). Now my kids complain about slow-motion (< 1 fps)
> within several games.
>
> I have an ATI Rage 128 graphic chip, dri is work
Gebhardt Thomas <[EMAIL PROTECTED]> writes:
> Any idea about what might have gone wrong?
Nothing. But you try rendering a few dozen square miles of terrain,
including weather, ground textures, the sky, etc., and keep a smooth
picture. That requires *far* more processing than the glxgears "Hello
I have upgrade to 4.3.0-5 and still I have the similar
issue.. I wonder if I need a more recent .. but there
is none available on the unstable..
do you know what version I need to use?
Thanks
Manu
--- Sean O'Dubhghaill <[EMAIL PROTECTED]>
wrote:
> On Sunday 14 March 2004 3:50 pm, you wrote:
>
On Sunday 14 March 2004 3:50 pm, you wrote:
> here you go
>
>CPU0
> 0:8249206 XT-PIC timer
> 1: 12090 XT-PIC i8042
> 2: 0 XT-PIC cascade
> 5: 13173 XT-PIC eth0, uhci_hcd,
> uhci_hcd
> 8: 4 XT-PIC
I will try to upgrade. Do you know what version I
would need at least?
thanks
Manu
--- Alan Chandler <[EMAIL PROTECTED]> wrote:
> On Sunday 14 March 2004 13:50, Manu wrote:
> > Hi
> >
> > I am having some problems with my radeon 8500,
> kernel
> > 2.6.3 and XFree 4.3.0-1
>
> You need to update
here you go
CPU0
0:8249206 XT-PIC timer
1: 12090 XT-PIC i8042
2: 0 XT-PIC cascade
5: 13173 XT-PIC eth0, uhci_hcd,
uhci_hcd
8: 4 XT-PIC rtc
9: 0 XT-PIC acpi
11: 715637
On Sunday 14 March 2004 13:50, Manu wrote:
> Hi
>
> I am having some problems with my radeon 8500, kernel
> 2.6.3 and XFree 4.3.0-1
You need to update XFree - there is a bug that causes this which has gone away
in the later updates
--
Alan Chandler
[EMAIL PROTECTED]
First they ignore you, then
hi
could be something to do with your interrupts, could you post your
cat /proc/interrupts
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Are you using xinerama?
I haven't explicitly configured xinerama, though it appears its
built-in to the X server (from the XFree86 log): "(II) Initializing
built-in extension XINERAMA"
I'm afraid I'm a bit of a newbie when it comes to stuff like this in X,
is there any way I can disable a buil
On Sunday 12 October 2003 21:54, [EMAIL PROTECTED] wrote:
> Greetings all,
>
> I'm running Debian unstable and I'm attempting to get DRI working with
my Voodoo5 (AGP). I can't figure out where my problem lies, everything
seems correct. Help would be greatly appreciated.
>
> I'm running Linux
Some months ago I posted asking why DRI wasn't working on my system with
a Rage 128 PF/PRO AGP 4x TMDS (as reported by lspci) card. Everything
looked fine.
Just now I found this information at
https://listman.redhat.com/pipermail/xfree86-list/2001q3/74.html:
>It is critically important to eve
On Mon, Mar 25, 2002 at 07:10:59PM -0600, Dave Sherohman wrote:
> On Mon, Mar 25, 2002 at 06:46:31PM -0600, Matt Garman wrote:
> > Trying to use the DRI stuff is causing X to lockup. In fact, the
> > ...
>
> I have experienced this, but only while playing 3D-accelerated games.
> The system in que
On Tue, Mar 26, 2002 at 08:30:42AM +, Simon Hepburn wrote:
> Try going back to using mga_drv.o that ships with X4.1. Leave
> mga_drv_hal.o in place. Remove mga_dri.so. I'm sure it's not meant
> to be there. See how you get on.
I did that, and it seems stable so far (one night and one day of
xs
On Wed, Mar 27, 2002 at 01:43:39AM -0600, Adam Majer wrote:
> Look at the kernel output. I have Radeon here and in Wolfenstain MP
> it just gets stuck in a look returning NULL because Radeon's kernel
> driver screwed up. Sometthing like a few thousand messages should
> be visible in syslog.
While
On Mon, Mar 25, 2002 at 06:46:31PM -0600, Matt Garman wrote:
>
> Trying to use the DRI stuff is causing X to lockup. In fact, the
> whole system is almost locked up---the keyboard and mouse are
> impotent, and the monitor doesn't show anything. Fortunately, I can
> do a remote login, but the onl
Matt Garman wrote:
> After installing those unofficial debs, I downloaded and installed the
> Matrox g400 series drivers from matrox's website (the filename is
> "mgadrivers-2.0.tar.gz"). This installed the following files:
>
> /usr/X11R6/lib/modules/drivers/mga_drv.o (replacing the default
On Mon, Mar 25, 2002 at 06:46:31PM -0600, Matt Garman wrote:
>
> Trying to use the DRI stuff is causing X to lockup. In fact, the
> whole system is almost locked up---the keyboard and mouse are
> impotent, and the monitor doesn't show anything. Fortunately, I can
> do a remote login, but the onl
2 things i just found out...
1) make sure (obviously) that DRI is compiled in
your kernel...
2) and this was a REAL silly one on my part...DUH
it was so easy...make sure that you're X server is
using the newer version (XF86Config-4) config
file! or else it will continue to use the old one
(withou
On Thu, Mar 21, 2002 at 10:39:49PM -0600, Kent West wrote:
> Kent West wrote:
>
> I was running a custom 2.4.13, but someone mentioned it might be a
> kernel thing, so I upgraded to a custom 2.4.18.
Is agpgart support for your chipset compiled in or as a module? Also,
is the r128 drm support is
Kent West wrote:
I was running a custom 2.4.13, but someone mentioned it might be a
kernel thing, so I upgraded to a custom 2.4.18.
Joachim Fahnenmueller wrote:
Hi Kent,
everything you posted looks ok to me. What makes you think DRI
_isn't_ enabled? What is the answer if you type 'glxinfo
Bob Underwood wrote:
On Sunday 17 March 2002 21:31, Kent West wrote:
Near as I can tell, DIR should work. Below is my XF86Config-4 file, and
after that the output of "startx 2> startx.log".
What kernel? When I upgrade my kernel from 2.4.17 to 2.4.18, I also lost my
DRI with an ATI video
Joachim Fahnenmueller wrote:
Hi Kent,
everything you posted looks ok to me. What makes you think DRI _isn't_ enabled?
What is the answer if you type 'glxinfo'?
Regards, Joachim
direct rendering: No
Hi Kent,
everything you posted looks ok to me. What makes you think DRI _isn't_ enabled?
What is the answer if you type 'glxinfo'?
Regards, Joachim
--
Joachim Fahnenmüller
Lehrer für Mathematik und Physik
Herder-Gymnasium
Kattowitzer Straße 52
51065 Köln
On Wed, 2001-12-19 at 15:47, Andrei Verovski wrote:
> Hi,
>
>
> Anyone have any experience setting up DRI (direct rendering
> infrastructure) with nVidia GeForce cards on Woody (testing)?
It's not possible as far as I know. nVidia will not release the full
source to their drivers or hardware s
Thus spake Peter De Wachter:
> > (EE) MGA(0): [dri] MGADRIScreenInit failed because of a version
> > mismatch.
> > [dri] mga.o kernel module version is 2.0.1 but version 3.0.x is needed.
> > [dri] Disabling DRI.
> >
> > Seems I've got the wrong mga.o. But why?
>
> I had the same problem. Compili
On Thu, Sep 20, 2001 at 06:21:51PM +0200, Peter De Wachter wrote:
> On Thu, 20 Sep 2001, Sven Garbade wrote:
>
> > Hi all,
> >
> > I want to complete my previous posting. After upgrading from Xfree 402
> > to Xfree 410 the error log shows the following:
> >
> > (EE) MGA(0): [dri] MGADRIScreenIni
On Thu, 20 Sep 2001, Sven Garbade wrote:
> Hi all,
>
> I want to complete my previous posting. After upgrading from Xfree 402
> to Xfree 410 the error log shows the following:
>
> (EE) MGA(0): [dri] MGADRIScreenInit failed because of a version
> mismatch.
> [dri] mga.o kernel module version is 2
Eloy Aguirre wrote:
>
> On Sun, Sep 02, 2001 at 10:09:31PM -0700, Erik Steffl wrote:
> > note that DefaultDepth 16 is required for voodoo3. That's the most
> > annoying part - you cannot play games (or run other openGL programs)
> > using same X session as you generally would prefer to run your
On Sun, Sep 02, 2001 at 10:09:31PM -0700, Erik Steffl wrote:
> note that DefaultDepth 16 is required for voodoo3. That's the most
> annoying part - you cannot play games (or run other openGL programs)
> using same X session as you generally would prefer to run your other X
> apps in. That just pl
Eric Whitestone wrote:
>
> Ok, I have compiled the Direct Rendering Manager into my kernel,
> including the 3dfx Banshee/Voodoo3+. I have Xfree86 4.1.0. My Video card is a
> voodoo 4/5. I am wondering if I need to do anything besides compile the
> kernel for my vid card. Xfree86 works f
In addition to the X module and the kernel modules you need ALL of
the libraries and headers in the 'Resources' section of the DRI
homepage. I've written a small guide for DRI and the Voodoo3 which you
can read at home.earthlink.net/~earmando/v3guide.html. Let me know if
the guide helps you any. Go
On Thu, 30 Aug 2001, Eric Whitestone wrote:
> I have a Voodoo 4/5 and I am running kernel 2.4.8 on potato. I just installed
> quake and got it to run, but it runs so slow that it isn't playable. I was
> wondering if there was a way to check if i had the correct drivers, or if i
> need to downlo
I would try and make sure that the Voodoo portion is compiled as a module
rather than right in to the kernel. I'm running an r128, but it didn't work
unless it was a module. I would also make sure I have the right libraries
installed for DRI, although I don't know what those are in potato.
- Da
On Thu, Aug 30, 2001 at 08:15:43PM -0400, Eric Whitestone wrote:
> I have a Voodoo 4/5 and I am running kernel 2.4.8 on potato. I just
> installed quake and got it to run, but it runs so slow that it isn't
> playable. I was wondering if there was a way to check if i had the correct
> drivers, or if
Run glxinfo to see if DRI is working. If it is, it will say
"direct rendering: Yes", among many other things. If not,
make sure that XF86Config is loading the dri module and that
your video card is set up properly. Also be sure that dri
support is properly compiled into your kernel... it's not by
d
On Mon, Aug 27, 2001 at 11:16:34AM -0400, bill triplett wrote:
> On Mon, Aug 27, 2001 at 09:25:23AM -0500, Dave Sherohman wrote:
> > - The final step I had to take was fixing some device permissions.
> > /dev/dri/ and /dev/dri/card0 were owned by root.root, preventing
> > normal users from getting
On Mon, Aug 27, 2001 at 09:25:23AM -0500, Dave Sherohman wrote:
> - The final step I had to take was fixing some device permissions.
> /dev/dri/ and /dev/dri/card0 were owned by root.root, preventing
> normal users from getting at DRI, so I changed them to root.video
> (which matches /dev/agpgart).
Le Jeudi 23 Août 2001 10:42, Jim McCloskey a écrit :
> I upgraded to kernel 2.4.9 about a week ago. I'm using XFree 4.0.3 on
> a mostly woody system. My graphics card is a Matrox G400.
>
> Under 2.4.7 and 2.4.8, direct rendering under X worked without a
> problem. But under 2.4.9. I get these erro
Hey thanks! You just fixed my problem too. I didn't have the legacy stuff
installed, but I was missing xlibmesa3. Make sure you have an up to date
kernel. I'm not sure what version is required, but my 2.4.8 works fine with
it after a cursory try with glxgears. I'm going to go check and see if
t
* Cameron Matheson ([EMAIL PROTECTED]) wrote:
> Hey,
>
> I'm trying to get this cursed Voodoo 3 3000 working in Woody, but it
> doesn't seem to want to. I've installed the following packages:
>
> mesag-glide2
> glutg3
> libglide2
> libglide3 // i installed this after libglide2 didn't work alone
On Wed, Aug 22, 2001 at 04:19:34PM -0600, Cameron Matheson wrote:
> Hey,
>
> I'm trying to get this cursed Voodoo 3 3000 working in Woody, but it
> doesn't seem to want to. I've installed the following packages:
>
> mesag-glide2
> glutg3
> libglide2
> libglide3 // i installed this after libglid
On Wed, 8 Aug 2001, Herbert Pirke wrote:
> a debian woody with kernel 2.4.7-SMP and a Voodoo3.
>
> I get the following message:
> (II) TDFX(0): [drm] drmOpen failed
> (EE) TDFX(0): [dri] DRIScreenInit failed, disabling
> DRI.
>
> Does anybody know why I get this error? Is there any
> known SMP pro
Thank you that worked.
Now, DRI is enabled.
The only problem I have now is I am getting 50 frames per sec.
-Ted
On Thu, Jul 12, 2001 at 02:33:35AM -0500, Rob VanFleet wrote:
> On Thu, Jul 12, 2001 at 02:01:33AM -0400, Theodore Knab wrote:
> > Hi,
> >
> > I have the new version of XFree86 4
On Thu, Jul 12, 2001 at 02:01:33AM -0400, Theodore Knab wrote:
> Hi,
>
> I have the new version of XFree86 4.1.0 from
> people.debian.org/~branden running. Although the graphics look great,
> I need the DRI stuff to work. I am not sure how to do this.
>
> I installed the 3dfx modules. I create
On Sat, Jun 09, 2001 at 11:32:45AM +0200, Robert Voigt wrote:
>
> Ok, now I see things a bit clearer.
>
> I think (and hope) this is also possible with a 2.2. kernel. I found
> CONFIG_DRM and CONFIG_DRM_TDFX in the character devices section of the kernel
> configuration. Is that the same or eq
On Saturday 09 June 2001 13:02, Andrea Vettorello wrote:
>
> With mplayer? I think he's referring to the "Xvideo Extension" ouput of
> mplayer. To use the HW acceleration the card need to support the YUY2
> packed and YV12 planar pixel format, and with similar configuration here
> (kernel 2.4.5 XFr
"Michael P. Soulier" wrote:
> On Fri, Jun 08, 2001 at 09:52:06PM +0200, Robert Voigt wrote:
> > I want DRI for my Voodoo3 card. But I'm confused.
> >
> > Somewhere I read DRI is included in XFree86 4.0.1.
> > Somewhere else I read it's in the 2.4. kernel.
> > And in /var/log/XFree.0.log I found th
On Saturday 09 June 2001 00:03, Michael P. Soulier wrote:
>
> It's in both. X provides the DRI API, but to make use of it, you need a
> module for your video card. I'm using kernel 2.4.4, with a Voodoo3. The
> tdfx module is included with kernel 2.4.4. So, running at 16 bpp, I have 3D
> accel.
On Fri, Jun 08, 2001 at 09:52:06PM +0200, Robert Voigt wrote:
> I want DRI for my Voodoo3 card. But I'm confused.
>
> Somewhere I read DRI is included in XFree86 4.0.1.
> Somewhere else I read it's in the 2.4. kernel.
> And in /var/log/XFree.0.log I found the line:
>
> (EE) TDFX(0): DRIScreenIni
Hello Hans,
I've continued to try to achieve a working/useable DRI/X4 setup for my
G400 and last night I got a combination working with my 2.4.0test5
kernel by doing the following:-
1. I downloaded the mga_drv.o driver from the Matrox web site and
replaced the version that came with X4 -
/us
Hello Hans,
Thanks for making the effort to get the reply through:-) Interesting
info too.
I couldn't get DRI to compile, so that was a no-go, but your info about
the reversed situation with 2.4.0-test9 was interesting - I hadn't tried
the test11 kernel as I use lm-sensors-source to patch the ke
On Thu, Nov 23, 2000 at 11:33:55AM +0530, Viral wrote:
> I've got XFree 4 starting up with DRI (I'm running 2.4-test11, with
> the
> agpgart and dri modules).
>
> I can run the gears demo, but quake 3a fails to run.
> I get some Gart errors in my log.
> I'm attaching my log file. Does anyone know w
2000 16:48:33 +
> From: Colin Watson <[EMAIL PROTECTED]>
> To: debian-user@lists.debian.org
> Subject: Re: DRI diff in phase2v30 and offical?
> Resent-Date: Mon, 6 Nov 2000 08:46:36 -0800
> Resent-From: debian-user@lists.debian.org
>
> Erik Steffl <[EMAIL PROTECTED]&
Erik Steffl <[EMAIL PROTECTED]> wrote:
> yes, I am in similar situation, the DRI does not work (X 4.0.1, voodoo
>3), the rest seems to work OK (I didn't do much testing).
>
> what's the reason? is it just a minor thing that's going to be fixed
>soon or is it missing or?
>
> card is recognized:
>
yes, I am in similar situation, the DRI does not work (X 4.0.1, voodoo
3), the rest seems to work OK (I didn't do much testing).
what's the reason? is it just a minor thing that's going to be fixed
soon or is it missing or?
card is recognized:
(II) TDFX: Driver for 3dfx Banshee/Voodoo3 chi
87 matches
Mail list logo
