On Tue, Sep 23, 2008 at 01:28:31PM +0200, Hans Ekbrand wrote:
> On Tue, Sep 23, 2008 at 12:50:04PM +0200, Hans Ekbrand wrote:
>
> [...]
>
> > - The only client that I have tried that does not work is wdm (the X
> > server dies when wdm opens its login-window).
[...]
> Here is what wdm logs to
On Tue, Sep 23, 2008 at 12:50:04PM +0200, Hans Ekbrand wrote:
[...]
> - The only client that I have tried that does not work is wdm (the X
> server dies when wdm opens its login-window). The following four lines
> are printed to Xorg.log.0 when wdm opens its' login window on the X
> server:
>
>
On Tue, Sep 23, 2008 at 09:39:43AM +0200, Michel Dänzer wrote:
> On Tue, 2008-09-23 at 08:48 +0200, Hans Ekbrand wrote:
> >
> > 1. added experimental to sources.list
> >
> > $ grep experimental /etc/apt/sources.list
> > deb-src http://ftp.se.debian.org/debian/ experimental main
> >
> > 2. Backpo
On Tue, 2008-09-23 at 08:48 +0200, Hans Ekbrand wrote:
>
> 1. added experimental to sources.list
>
> $ grep experimental /etc/apt/sources.list
> deb-src http://ftp.se.debian.org/debian/ experimental main
>
> 2. Backported drm-modules-source from experimental to lenny
>
> # apt-get build-dep drm
On Fri, Sep 19, 2008 at 11:51:29AM +0200, Hans Ekbrand wrote:
> On Fri, Sep 19, 2008 at 11:29:32AM +0200, Michel Dänzer wrote:
> > On Fri, 2008-09-19 at 10:23 +0200, Hans Ekbrand wrote:
> > >
> > > What is the step needed to compile the drm kernel module for mach64 on
> > > a up-to-date lenny (pow
On Fri, Sep 19, 2008 at 11:29:32AM +0200, Michel Dänzer wrote:
> On Fri, 2008-09-19 at 10:23 +0200, Hans Ekbrand wrote:
> >
> > What is the step needed to compile the drm kernel module for mach64 on
> > a up-to-date lenny (powerpc) system?
>
> Install the drm-modules-source package from experimen
On Fri, 2008-09-19 at 10:23 +0200, Hans Ekbrand wrote:
>
> What is the step needed to compile the drm kernel module for mach64 on
> a up-to-date lenny (powerpc) system?
Install the drm-modules-source package from experimental and use e.g.
module-assistant, or see http://dri.freedesktop.org/wiki/B
Processing commands for [EMAIL PROTECTED]:
> reassign 369167 xserver-xorg-video-ati
Bug#369167: libgl1-mesa-dri: [Powerpc] "Load dri" in xorg.conf crashes Powerbook
Bug reassigned from package `libgl1-mesa-dri' to `xserver-xorg-video-ati'.
> severity 369167 important
Bug#369167: libgl1-mesa-dri:
On Wed, Dec 15, 2004 at 03:40:47PM -0500, Dan Christensen wrote:
>
> You can put
>
>-xf86config XF86Config-4.dri
>
> at the end of the :0 line and alter the config files so just this one
> has DRI loaded.
>
> I'd also like it if the order in which multiple X servers started
> was more cons
Tomas Nykung <[EMAIL PROTECTED]> writes:
> So, here is what I want:
> - 3 X servers running at the same time, started from kdm
> (for graphical login)
>
> - the first server running at 1024x768, with 16 bits colours, DRI enabled
> (for the kids, they mostly play games...)
>
> - the two others runn
On Mon, 2004-08-09 at 13:56 +0200, Samuel Thibault wrote:
> Le lun 09 aoû 2004 à 11:31:15 +0200, Samuel Thibault a tapoté sur son clavier
> :
> > I'm trying the dri-mach64-sid packages to get acceleration on my
> > mach64, but I noticed that it is quite old (mach64-0-0-6-branch),
> > there's a ma
Le lun 09 aoû 2004 à 11:31:15 +0200, Samuel Thibault a tapoté sur son clavier :
> I'm trying the dri-mach64-sid packages to get acceleration on my
> mach64, but I noticed that it is quite old (mach64-0-0-6-branch),
> there's a mach64-0-0-7-branch that appeared, and now its content is
> in the mainl
On Fri, Feb 20, 2004 at 12:27:19AM +0100, Moritz Muehlenhoff wrote:
> First of all thanks for the 4.3.0 packages, my new Radeon 9200 ran out
> of the box with completely libre 3D support (expect that I had to down-
> grade xlibmesa-dri, which has already been reported several times).
> Great work!
--- Ariel Garcia <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > > > > both on my desktop and my laptop i am getting strange hangs
> > > > > when running XFree packages (both debian testing/unstable,
> > > > > 4.2.1-{12.1,15}) with the newer linux kernels. This happens
> > > > > for me since one of th
On Mon, Aug 11, 2003 at 11:40:57AM +0200, Moritz Muehlenhoff wrote:
> Sven Luther wrote:
> > > Is this a bug in the debian-package? Judging from the XFree86.log.0
> > > my system seems properly configured, but I'm in no way an X11 expert.
> >
> > What is the output of glxinfo ?
>
> Here we go.
>
Sven Luther wrote:
> > Is this a bug in the debian-package? Judging from the XFree86.log.0
> > my system seems properly configured, but I'm in no way an X11 expert.
>
> What is the output of glxinfo ?
Here we go.
Cheers,
Moritz
$ glxinfo -v
name of display: :0.0
display: :0 screen: 0
d
Michel D?nzer wrote:
> > 330 to 440 fps (agp4, enablepageflip) in glxgears (normal size
> > on a 1024x768 screen on a Athlon 1700+),
>
> I hope you mean the size the window comes up in by 'normal size' ?
Yes, that's what I meant. glxgears runs in 300x300 pixels or something
like that.
> Does se
On Mon, 2003-08-11 at 18:49, Moritz Muehlenhoff wrote:
> Michel D?nzer wrote:
> >
> > Does setting the RADEON_NO_USLEEPS and/or RADEON_NO_IRQS environment
> > variable(s) make a difference? (See
> > http://dri.sourceforge.net/doc/dri_driver_features.phtml for a list of
> > other environment varia
On Mon, 2003-08-11 at 00:59, Moritz Muehlenhoff wrote:
> Hi,
> the update from 4.2.1-6 towards 4.3.0-pre1v1 was pretty smooth,
> everything works as expected. I never really used 3D with my
> Radeon 7500 QW (64 MB SDRAM) before, but I thought I'd give it
> a try with 4.3.0. With the included drm-sr
On Mon, 2003-08-11 at 18:49, Moritz Muehlenhoff wrote:
> Michel D?nzer wrote:
> >
> > Does setting the RADEON_NO_USLEEPS and/or RADEON_NO_IRQS environment
> > variable(s) make a difference? (See
> > http://dri.sourceforge.net/doc/dri_driver_features.phtml for a list of
> > other environment varia
Michel D?nzer wrote:
> > 330 to 440 fps (agp4, enablepageflip) in glxgears (normal size
> > on a 1024x768 screen on a Athlon 1700+),
>
> I hope you mean the size the window comes up in by 'normal size' ?
Yes, that's what I meant. glxgears runs in 300x300 pixels or something
like that.
> Does se
On Mon, 2003-08-11 at 00:59, Moritz Muehlenhoff wrote:
> Hi,
> the update from 4.2.1-6 towards 4.3.0-pre1v1 was pretty smooth,
> everything works as expected. I never really used 3D with my
> Radeon 7500 QW (64 MB SDRAM) before, but I thought I'd give it
> a try with 4.3.0. With the included drm-sr
On Mon, Aug 11, 2003 at 11:40:57AM +0200, Moritz Muehlenhoff wrote:
> Sven Luther wrote:
> > > Is this a bug in the debian-package? Judging from the XFree86.log.0
> > > my system seems properly configured, but I'm in no way an X11 expert.
> >
> > What is the output of glxinfo ?
>
> Here we go.
>
Sven Luther wrote:
> > Is this a bug in the debian-package? Judging from the XFree86.log.0
> > my system seems properly configured, but I'm in no way an X11 expert.
>
> What is the output of glxinfo ?
Here we go.
Cheers,
Moritz
$ glxinfo -v
name of display: :0.0
display: :0 screen: 0
d
On Mon, Aug 11, 2003 at 12:59:27AM +0200, Moritz Muehlenhoff wrote:
> Hi,
> the update from 4.2.1-6 towards 4.3.0-pre1v1 was pretty smooth,
> everything works as expected. I never really used 3D with my
> Radeon 7500 QW (64 MB SDRAM) before, but I thought I'd give it
> a try with 4.3.0. With the in
On Mon, Aug 11, 2003 at 12:59:27AM +0200, Moritz Muehlenhoff wrote:
> Hi,
> the update from 4.2.1-6 towards 4.3.0-pre1v1 was pretty smooth,
> everything works as expected. I never really used 3D with my
> Radeon 7500 QW (64 MB SDRAM) before, but I thought I'd give it
> a try with 4.3.0. With the in
On Fri, Aug 02, 2002 at 10:53:04PM +0200, Michel D?nzer wrote:
> On Sat, 2002-08-03 at 03:52, Michael Cardenas wrote:
> > Hello everyone. Again, please cc me if you respond as I'm not
> > subscribed.
> >
> > Attach: /root/glxout glxinfo output
> >
> > I'm still trying to debug the dri on intel i
On Sat, 2002-08-03 at 03:52, Michael Cardenas wrote:
> Hello everyone. Again, please cc me if you respond as I'm not
> subscribed.
>
> Attach: /root/glxout glxinfo output
>
> I'm still trying to debug the dri on intel i810 video cards for our
> next release, and strangely the xfree86 log says th
On Thu, 1 Aug 2002, Sven LUTHER wrote:
>Date: Thu, 1 Aug 2002 11:22:47 +0200
>From: Sven LUTHER <[EMAIL PROTECTED]>
>To: Mike A. Harris <[EMAIL PROTECTED]>
>Cc: Branden Robinson <[EMAIL PROTECTED]>, debian-x@lists.debian.org
>Content-Type: text/plain; charset=us-a
On Thu, 2002-08-01 at 11:22, Sven LUTHER wrote:
> On Wed, Jul 31, 2002 at 09:27:33PM -0400, Mike A. Harris wrote:
> > M6 == Radeon Mobility (Radeon)
> > M7 == Radeon Mobility (Radeon)
>
> I guess the M7 is also called Radeon Mobility 7500 (Radeon 7500) (the
> one currently used in the tibooks wit
On Wed, Jul 31, 2002 at 09:27:33PM -0400, Mike A. Harris wrote:
> M6 == Radeon Mobility (Radeon)
> M7 == Radeon Mobility (Radeon)
I guess the M7 is also called Radeon Mobility 7500 (Radeon 7500) (the
one currently used in the tibooks with 32MB of memory).
The nice thing about the M7 is that it ha
On Wed, 31 Jul 2002, Branden Robinson wrote:
>Date: Wed, 31 Jul 2002 16:44:10 -0500
>From: Branden Robinson <[EMAIL PROTECTED]>
>To: debian-x@lists.debian.org
>Content-Type: multipart/signed; micalg=pgp-sha1;
> protocol="application/pgp-signature"; boundary=
On Wed, 2002-07-31 at 23:44, Branden Robinson wrote:
> On Wed, Jul 31, 2002 at 08:34:16AM +0200, Michel Dänzer wrote:
> > That's not corrrect, ATI calls all their mobile chips 'Rage Mobility',
> > M3 through M5 have a Rage128 core.
>
> Eh? Apple, at any rate, has started calling the newest ATI mo
On Wed, Jul 31, 2002 at 08:34:16AM +0200, Michel Dänzer wrote:
> That's not corrrect, ATI calls all their mobile chips 'Rage Mobility',
> M3 through M5 have a Rage128 core.
Eh? Apple, at any rate, has started calling the newest ATI mobile chips
"Radeon Mobility".
--
G. Branden Robinson
En réponse à "Mike A. Harris" <[EMAIL PROTECTED]>:
> Just be sure that if you are using any XFree86 4.2.0 release,
> that the 2.4.x kernel you are using must be patched to use
> XFree86 4.2.0 DRM in order to work properly.
Where may I find such a patch ?
Do I have the choice of using something
On Wed, 31 Jul 2002, ISHIKAWA Mutsumi wrote:
>Date: Wed, 31 Jul 2002 12:18:05 +0900
>From: ISHIKAWA Mutsumi <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Cc: debian-x@lists.debian.org
>Content-Type: text/plain; charset=US-ASCII
>Subject: Re: DRI on XFree86 4.x with
On Wed, 2002-07-31 at 05:18, ISHIKAWA Mutsumi wrote:
>
> > In <[EMAIL PROTECTED]>
> > [EMAIL PROTECTED] (Bruno BEAUFILS) wrote:
>
> >> Hello,
>
> >> I have a Dell Inspiron 8000 with an ATI Rage Mobility M4 AGP video card.
>
> >> I just installed the dri.sf.net modules (and also their X
Hi,
> In <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] (Bruno BEAUFILS) wrote:
>> Hello,
>> I have a Dell Inspiron 8000 with an ATI Rage Mobility M4 AGP video card.
>> I just installed the dri.sf.net modules (and also their X server after many
>> unfortunater try with debian one).
>>
>> I
> In <[EMAIL PROTECTED]>
> Will Newton <[EMAIL PROTECTED]> wrote:
>> Direct rendering is only working for root on my system (unstable/4.1.0). The
>> permissions for the DRI device files are:
>>
>> /dev/dri:
>> drwxrwx---2 root root 4096 Aug 1 15:22 dri
>>
>> /dev/dri/*
> In <[EMAIL PROTECTED]>
> Will Newton <[EMAIL PROTECTED]> wrote:
>> Direct rendering is only working for root on my system (unstable/4.1.0). The
>> permissions for the DRI device files are:
>>
>> /dev/dri:
>> drwxrwx---2 root root 4096 Aug 1 15:22 dri
>>
>> /dev/dri/
On Fri, Jun 29, 2001 at 02:03:43AM -0700, Ian Eure wrote:
> hm. dri works great for me with 2.4.5 & 4.1.0-0pre1v1.3 - will it break if
> i upgrade to 4.2.1-0pre1v2?
Probably not. Only some of the modules are affected, but to explain this
would go into far more detail than is appropriate for a deb
On Fri, Jun 29, 2001 at 02:03:43AM -0700, Ian Eure wrote:
> hm. dri works great for me with 2.4.5 & 4.1.0-0pre1v1.3 - will it break if
> i upgrade to 4.2.1-0pre1v2?
Probably not. Only some of the modules are affected, but to explain this
would go into far more detail than is appropriate for a de
On Thu, 28 Jun 2001, Branden Robinson wrote:
> On Thu, Jun 28, 2001 at 02:55:29PM -0700, Mark Montague wrote:
> > Just as a note, the "kernel version may be too old" message came up
> > for me even though I'm running 2.4.5-686-smp. I don't know if the
> > 686-smp is what triggers it, or if that's k
On Thu, 28 Jun 2001, Branden Robinson wrote:
> On Thu, Jun 28, 2001 at 02:55:29PM -0700, Mark Montague wrote:
> > Just as a note, the "kernel version may be too old" message came up
> > for me even though I'm running 2.4.5-686-smp. I don't know if the
> > 686-smp is what triggers it, or if that's
On Thu, Jun 28, 2001 at 02:55:29PM -0700, Mark Montague wrote:
> Just as a note, the "kernel version may be too old" message came up
> for me even though I'm running 2.4.5-686-smp. I don't know if the
> 686-smp is what triggers it, or if that's known to be a non-working
> version of the kernel for
On Thu, Jun 28, 2001 at 02:55:29PM -0700, Mark Montague wrote:
> Just as a note, the "kernel version may be too old" message came up
> for me even though I'm running 2.4.5-686-smp. I don't know if the
> 686-smp is what triggers it, or if that's known to be a non-working
> version of the kernel for
Benjamin Redelings I wrote:
>
> Hi, according to /proc/pci, I have a "ATI Technologies Inc 3D Rage Pro
> AGP 1X/2X".
>
> I compiled agp and the r128 DRI driver for kernel 2.4.3-ac5.
Your chip isn't a Rage128. There is only rudimentary support for the mach64
family in a branch of the DRI CVS yet.
Benjamin Redelings I wrote:
>
> Hi, according to /proc/pci, I have a "ATI Technologies Inc 3D Rage Pro
> AGP 1X/2X".
>
> I compiled agp and the r128 DRI driver for kernel 2.4.3-ac5.
Your chip isn't a Rage128. There is only rudimentary support for the mach64
family in a branch of the DRI CVS yet
On Tue, Mar 27, 2001 at 01:53:13PM +0100, Jules Bean wrote:
> On Tue, Mar 27, 2001 at 02:51:14PM +0200, Michel D?nzer wrote:
> > Alan Hourihane wrote:
> > >
> > > On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel D?nzer wrote:
> > > > Jules Bean wrote:
> > > >
> > > > > [EMAIL PROTECTED] [17] LIBGL
Alan Hourihane wrote:
>
> Indeed, but from the code, you should be able to set
>
> LIBGL_DRIVERS_PATH
>
> to point to your *_dri.so files.
DRI User's Giude
Section 8.6 Environment Variables
...
3. LIBGL_DRIVERS_PATH can be used to override the default directories
which are searched for 3D dri
On Tue, Mar 27, 2001 at 02:51:14PM +0200, Michel Dänzer wrote:
> Alan Hourihane wrote:
> >
> > On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel Dänzer wrote:
> > > Jules Bean wrote:
> > >
> > > > [EMAIL PROTECTED] [17] LIBGL_DEBUG=1 glxinfo
> > > > libGL error: dlopen failed: /usr/X11R6/lib/module
Alan Hourihane wrote:
>
> On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel Dänzer wrote:
> > Jules Bean wrote:
> >
> > > [EMAIL PROTECTED] [17] LIBGL_DEBUG=1 glxinfo
> > > libGL error: dlopen failed: /usr/X11R6/lib/modules/dri/tdfx_dri.so:
> > > cannot open shared object file: No such file or dire
On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel Dänzer wrote:
> Jules Bean wrote:
>
> > [EMAIL PROTECTED] [17] LIBGL_DEBUG=1 glxinfo
> > libGL error: dlopen failed: /usr/X11R6/lib/modules/dri/tdfx_dri.so:
> > cannot open shared object file: No such file or directory
> > libGL error: dlopen failed
On Tue, Mar 27, 2001 at 01:53:13PM +0100, Jules Bean wrote:
> On Tue, Mar 27, 2001 at 02:51:14PM +0200, Michel D?nzer wrote:
> > Alan Hourihane wrote:
> > >
> > > On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel D?nzer wrote:
> > > > Jules Bean wrote:
> > > >
> > > > > jules@pear [17] LIBGL_DEBUG
Alan Hourihane wrote:
>
> Indeed, but from the code, you should be able to set
>
> LIBGL_DRIVERS_PATH
>
> to point to your *_dri.so files.
DRI User's Giude
Section 8.6 Environment Variables
...
3. LIBGL_DRIVERS_PATH can be used to override the default directories
which are searched for 3D dr
On Tue, Mar 27, 2001 at 02:51:14PM +0200, Michel Dänzer wrote:
> Alan Hourihane wrote:
> >
> > On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel Dänzer wrote:
> > > Jules Bean wrote:
> > >
> > > > jules@pear [17] LIBGL_DEBUG=1 glxinfo
> > > > libGL error: dlopen failed: /usr/X11R6/lib/modules/dri/
Alan Hourihane wrote:
>
> On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel Dänzer wrote:
> > Jules Bean wrote:
> >
> > > jules@pear [17] LIBGL_DEBUG=1 glxinfo
> > > libGL error: dlopen failed: /usr/X11R6/lib/modules/dri/tdfx_dri.so:
> > > cannot open shared object file: No such file or directory
On Tue, Mar 27, 2001 at 02:33:19PM +0200, Michel Dänzer wrote:
> Jules Bean wrote:
>
> > jules@pear [17] LIBGL_DEBUG=1 glxinfo
> > libGL error: dlopen failed: /usr/X11R6/lib/modules/dri/tdfx_dri.so:
> > cannot open shared object file: No such file or directory
> > libGL error: dlopen failed: /usr
Stuart Ballard wrote:
>
> Michel Dänzer wrote:
> >
> > Stuart Ballard wrote:
> >
> > The latter. Go to xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
> > and run 'make -f Makefile.linux'.
>
> Excellent answer, and much appreciated. However, I think I'm ignorant or
> stupid or somethin
Michel Dänzer wrote:
>
> Stuart Ballard wrote:
>
> The latter. Go to xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
> and run 'make -f Makefile.linux'.
Excellent answer, and much appreciated. However, I think I'm ignorant or
stupid or something... after running that command, what is
Stuart Ballard wrote:
> The relevant line in my X server output seems to be the following:
> (EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 2.0.1,
> expected 2.1.x). Disabling DRI.
>
> Does this mean I don't have a high enough version of DRM in my kernel,
> even though 2.4.2 is practi
"Charl P. Botha" wrote:
>
> Why can't you just use 4.0.2 with the drivers which are available at
> http://www.matrox.com/mga/support/drivers/files/linux_05.cfm. I'm afraid
> the closest I have is a G400 running with 4.0.2, but as far as I understand
> from the aforementioned web page, your G450 s
Why can't you just use 4.0.2 with the drivers which are available at
http://www.matrox.com/mga/support/drivers/files/linux_05.cfm. I'm afraid
the closest I have is a G400 running with 4.0.2, but as far as I understand
from the aforementioned web page, your G450 should just work in 4.0.2 with
those
Stuart Ballard wrote:
>
> Michel Dänzer wrote:
> >
> > Stuart Ballard wrote:
> >
> > The latter. Go to xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
> > and run 'make -f Makefile.linux'.
>
> Excellent answer, and much appreciated. However, I think I'm ignorant or
> stupid or somethi
Michel Dänzer wrote:
>
> Stuart Ballard wrote:
>
> The latter. Go to xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
> and run 'make -f Makefile.linux'.
Excellent answer, and much appreciated. However, I think I'm ignorant or
stupid or something... after running that command, what is
Stuart Ballard wrote:
> The relevant line in my X server output seems to be the following:
> (EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 2.0.1,
> expected 2.1.x). Disabling DRI.
>
> Does this mean I don't have a high enough version of DRM in my kernel,
> even though 2.4.2 is pract
"Charl P. Botha" wrote:
>
> Why can't you just use 4.0.2 with the drivers which are available at
> http://www.matrox.com/mga/support/drivers/files/linux_05.cfm. I'm afraid
> the closest I have is a G400 running with 4.0.2, but as far as I understand
> from the aforementioned web page, your G450
Why can't you just use 4.0.2 with the drivers which are available at
http://www.matrox.com/mga/support/drivers/files/linux_05.cfm. I'm afraid
the closest I have is a G400 running with 4.0.2, but as far as I understand
from the aforementioned web page, your G450 should just work in 4.0.2 with
thos
glxinfo runs okay. I'm trying to see if I can find other programs that bail
out like this...but still no luck.
On Thu, Oct 19, 2000 at 06:49:01PM -0700, Seth Arnold wrote:
> Joel, how well does "glxinfo" run? I too noticed this with q3a, and
> glxinfo also dies in a similar manner. Since I don't
Joel, how well does "glxinfo" run? I too noticed this with q3a, and
glxinfo also dies in a similar manner. Since I don't have time to play
games at the moment, I didn't investigate further -- I figured I broke
something. :)
I am still running kernel 2.4.0-test7 with my MGA 400 Max, matrox's
driver
glxinfo runs okay. I'm trying to see if I can find other programs that bail out like
this...but still no luck.
On Thu, Oct 19, 2000 at 06:49:01PM -0700, Seth Arnold wrote:
> Joel, how well does "glxinfo" run? I too noticed this with q3a, and
> glxinfo also dies in a similar manner. Since I don'
Joel, how well does "glxinfo" run? I too noticed this with q3a, and
glxinfo also dies in a similar manner. Since I don't have time to play
games at the moment, I didn't investigate further -- I figured I broke
something. :)
I am still running kernel 2.4.0-test7 with my MGA 400 Max, matrox's
drive
72 matches
Mail list logo
