RE: [Xpert]dri on the intel i810
Michael, I posted a small patch for this sometime back. Here is a web cvs link to the log. Looks like 1.69 or later of this file is needed. http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/i810 /i810_driver.c -Matt -Original Message- From: Michael Cardenas [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 6:48 PM To: [EMAIL PROTECTED] Subject: [Xpert]dri on the intel i810 Hello everyone. If you respond, please cc me as I'm not subscribed. Attach: /root/XFree86.0.log.fail xfree86 log I'm an engineer at Lindows.com and we're trying to ship xfree86 4.2.0 with our next release. In testing, our qa dept discovered that the intel i810 card no longer has dri acceleration since moving from 4.1.0 to 4.2.0. I found that we were not using the updated kernel modules required for dri, so I added those to our kernel. Unfortunately, the i810's are still not accelerated. From looking at /var/log/XFree86.0.log, everything seems to be fine, and it says "direct rendering enabled", but glxinfo says "direct rendering: no". I'm trying really hard to debug this problem and any suggestions as to what the problem is, or how to debug it, would be greatly appreciated. Attached are the output of glxinfo and xfree8.0.log. thank you, michael -- michael cardenas lead software engineer lindows.com . hyperpoem.net . "Be the change you want to see in the world." -Mahatma Gandhi ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]dri
On Wed 11 Sep 2002 10:18, Sam Halliday wrote: > hello there, > > i was wondering if somebody could please set me > straight on the whole dri thing... i am currently > recompiling my entire system (LFS... sometimes rpms > seem like a good idea!) and i have reached the > (almost) final stage... XFree86. > I've been playing with LFS, too! > I have a voodoo3000 card which i see is supported by > the dri system and i think it is about time i got the > accelerated graphics working! My question is this... > do i need to get the latest dri source from cvs, or > does the latest XFree86-4.2.1 have enough in it that i > can compile dri support without any additional adons? > (well, besides libglide3) and if so, what must i > specify in my host.def? > Alexander Stohr recommends: For a startup its the simplest thing to get the set of XF86 source tarballs, extract them to something ~/xc and do an echo "#define BuildXF86DRM YES" >~/xc/config/cf/host.def followed by a cd ~/xc; make World Installation? Hmm, i never needed that for my purposes. ;-) Try a "make install". I have done this, yes, it is make install. You might also want to run make install.man to install the man pages. I've played with the dri cvs stuff, but I'm no expert, so I can not really say if the voodoo3000 stuff is in the XFree86 tree, or if you still need to fetch the dri stuff as well. But if you do need it, I would recommend getting the XFree86 cvs stuff, compile and install that first, then the dri cvs stuff. You will NEED the XFree86 installled for the dri stuff to work. > i noticed in my (partial) compile of XFree86 today > that i had a few dri_xxx.o files in the lib/modules > folder. Are these what i think they are? ie. are these > the accelerated graphics modules for the associated > cards? > For dri to work, you will need two modules, the kernel modules, in xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel and the Xserver modules in xc/programs/Xserver/hw/xfree86/drivers/ > i quess what i am tryign to ask is this... is dri in > the stable XFree86 release now? > I don't know, and I'm no expert. I've only been playing with the dri cvs stuff because my card is under active development and I am hoping to provide some feedback. > i hope i have made sense... probably haven't Kinda did, but not really ;-) Of course, after Xfree86, you still need a Window/Desktop manager. I've built KDE3.0Beta2 on mine. > thanks in advance! > Sam > Hope this helps... and I defer to the experts for anything I might have got wrong. Cheers, John Gay ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]dri
Title: RE: [Xpert]dri I dont know about recent improvement to the vodoo series in DRI or XF86. For a startup its the simplest thing to get the set of XF86 source tarballs, extract them to something ~/xc and do an echo "#define BuildXF86DRM YES" >~/xc/config/cf/host.def followed by a cd ~/xc; make World Installation? Hmm, i never needed that for my purposes. ;-) Try a "make install". > I have a voodoo3000 card which i see is supported by > the dri system and i think it is about time i got the > accelerated graphics working! My question is this... > do i need to get the latest dri source from cvs, or > does the latest XFree86-4.2.1 have enough in it that i > can compile dri support without any additional adons? > (well, besides libglide3) and if so, what must i > specify in my host.def? > > i noticed in my (partial) compile of XFree86 today > that i had a few dri_xxx.o files in the lib/modules > folder. Are these what i think they are? ie. are these > the accelerated graphics modules for the associated > cards? > > i quess what i am tryign to ask is this... is dri in > the stable XFree86 release now? > > i hope i have made sense... probably haven't > thanks in advance! > Sam good question. -Alex.
Re: [Xpert]DRI and glXCopyContext, or one context for 2 windows
Joe Krahn wrote: > > I am trying to use one context state for two windows. > Is glXCopyContext supposed to work for DRI? > > Alternatively, I can actually use one context and point > it to the window I want to render in. Apparently, this > is an unusual thing to do. It works on SGI (as uaual) > but was able to crash XFree86 DRI, Nvidia, and Xig servers. > Nvidia and Xig fixed the problem, but DRI is still broken. > DRI doesn't crash from this any more, but it gives serious > artifacts. > > Without glXCopyContext, a workaround is really hard, > other than not using DRI. > > Any ideas? This is probably another case of trying the DRI CVS. Joe, Post a pointer to your test app on [EMAIL PROTECTED] -- /\ Jens Owen/ \/\ _ [EMAIL PROTECTED] /\ \ \ Steamboat Springs, Colorado ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI Unresolved Symbols
On Sat, 2002-05-04 at 20:48, Kyle Super wrote: > > I recently downloaded and installed XFree86 version 4.2.0. I was using > kernel version 2.4.2-2 and had to install the latest DRI r128 binary from > http://dri.sourceforge.net/download.phtml. This went fine and I had no > problems starting the xserver. > > I then updated the kernel to version 2.4.9-31 to fix some mtrr problems. > Once again, I installed the latest DRI r128 binary, but now on xserver > startup r128.o does not load (although the xserver does start). This is what > appeared in the dri.log file after I installed r128.o for the new kernel: > > make: `r128.o' is up to date. > /usr/X11R6/lib > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol boot_cpu_data_R3gig_0657d037 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol do_mmap_pgoff_R3gig_1b290628 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol __pollwait_R3gig_918efb08 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol si_meminfo_R3gig_7e9ed292 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol fasync_helper_R3gig_a2f89fd0 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol remove_wait_queue_R3gig_6db6b627 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol create_proc_entry_R3gig_e59fa486 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol kill_fasync_R3gig_c299f6cc > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol init_mm_R3gig_ae8035af > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol register_chrdev_R3gig_27f77796 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol remove_proc_entry_R3gig_8a3df140 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol mem_map_R3gig_0826217e > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol add_wait_queue_R3gig_307a0918 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol pci_find_slot_R3gig_0517f8e1 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: insmod > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o failed > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: insmod > r128 failed The kernel module needs to be built against the source which was used to build the kernel you want to run it with. Usually, just make -f Makefile.linux clean r128.o should work while you're running that kernel, but if it picks up the wrong tree for some reason, try make -f Makefile.linux TREE=/include clean r128.o -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI Unresolved Symbols
On Sunday 05 May 2002 01:52, Kyle Super wrote: > I installed the modules from > http://www.xfree86.org/~alanh/linux-drm-4.2.0-kernelsource.tar.gz but I > still receive the unresolved symbol errors and r128 fails to load. Kyle, after having had 'uresolved symbol' problems too, I'm now running this very kernel module on a RedHat 7.1 based system. What finally led me to success was a complete kernel recompile, using the above kernelsources from xfree86.org. I can see from your last posting that you did a recompile of the RH kernel v. 2.4.9-31. I'm no longer using a RH kernel but 2.4.18 from kernel.org instead. My steps in detail (YMMV): - remove /usr/src/linux/drivers/char/drm - untar linux-drm-4.2.0-kernelsource.tar.gz into /usr/src/linux/drivers/char/, thus having a new /drm folder - rename /usr/src/linux/drivers/char/drm/Makefile.kernel to (...)Makefile - config the kernel with the following settings: [snip] CONFIG_AGP=m # CONFIG_AGP_INTEL is not set # CONFIG_AGP_I810 is not set CONFIG_AGP_VIA=y # CONFIG_AGP_AMD is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_ALI is not set # CONFIG_AGP_SWORKS is not set CONFIG_DRM=y # CONFIG_DRM_OLD is not set # # DRM 4.1 drivers # CONFIG_DRM_NEW=y CONFIG_DRM=y # CONFIG_DRM_TDFX is not set # CONFIG_DRM_GAMMA is not set CONFIG_DRM_R128=m # CONFIG_DRM_RADEON is not set # CONFIG_DRM_I810 is not set # CONFIG_DRM_I830 is not set # CONFIG_DRM_MGA is not set # CONFIG_MWAVE is not set [snip] (...perhaps you should enable different or all chipsets, mine is a VIA) - recompile in the usual way. It seems to be crucial to disable support for the 'old' DRM, and to enable 'new' DRM. I have read somewhere that you should load the agpgart kernel module before r128.o gets loaded, so I added the following line to modules.conf : pre-install r128 modprobe agpgart but I don't know if this is essential; dri would get enabled without agpgart. HTH, Klaus ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]DRI Unresolved Symbols
Am I correct in thinking that the kernel modules located at http://www.xfree86.org/~alanh/linux-drm-4.2.0-kernelsource.tar.gz are the same kernel modules located in the CVS directory mentioned above? I installed the modules from http://www.xfree86.org/~alanh/linux-drm-4.2.0-kernelsource.tar.gz but I still receive the unresolved symbol errors and r128 fails to load. Any ideas? Thanks, Kyle Super ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI Unresolved Symbols
Kyle Super wrote: > > Hi, > I recently downloaded and installed XFree86 version 4.2.0. I was using > kernel version 2.4.2-2 and had to install the latest DRI r128 binary from > http://dri.sourceforge.net/download.phtml. This went fine and I had no > problems starting the xserver. > > I then updated the kernel to version 2.4.9-31 to fix some mtrr problems. > Once again, I installed the latest DRI r128 binary, but now on xserver > startup r128.o does not load (although the xserver does start). This is what > appeared in the dri.log file after I installed r128.o for the new kernel: > > make: `r128.o' is up to date. > /usr/X11R6/lib > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol boot_cpu_data_R3gig_0657d037 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol do_mmap_pgoff_R3gig_1b290628 ... > > Does anyone know how to fix this? > > Thanks, > Kyle Super I'm not sure why the DRI module didn't build, but you should be aware that the dri drivers at dri.sourceforge.net are not the same as from XFree86. DRI development has a completely different CVS, which gets merged to XFree86 occasionally. If you just want to get XFree86 working, use the DRI drivers from the same source tree. Look in: xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel Joe Krahn ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI and i810
I had the same problem, take a look at the following, fixed it for me. http://xfree86.org/pipermail/xpert/2002-February/015571.html On Mon, Feb 25, 2002 at 05:48:16PM -0500, Antonio MATTA wrote: > > Hello guys: > > I hava a i810 video chipset. I have followed all the instructions to make > dri to work in this chipset, but with negative results. > Can anybody please tell me, what can I do? > > Thanks, > > Antonio. > > -- > ANTONIO ALEJANDRO MATTA GÓMEZ > WebMaster > Facultad de Ingeniería > Pontificia Universidad Javeriana - Seccional Cali > Calle 18 No. 118 - 250 Av. Cañasgordas > Cali, Colombia > Tel. (+2) 3218200 Ext 575 > Fax. 5552823 > > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI and i810
Hi Antonio! > I hava a i810 video chipset. I have followed all the instructions to make > dri to work in this chipset, but with negative results. > Can anybody please tell me, what can I do? Make sure you've compiled 1. the i830m agpgart modules (only in >= 2.4.11) (agpgart.o) 2. the i830m DRI module (included in the XFree86 source - not the kernel) 3. make sure you XF86Config is setup correctly and that you've inserted the abovementioned modules -- Regards Abraham In 1962, you could buy a pair of SHARKSKIN SLACKS, with a "Continental Belt," for $10.99!! __ Abraham vd Merwe - 2d3D, Inc. Device Driver Development, Outsourcing, Embedded Systems Cell: +27 82 565 4451 Snailmail: Tel: +27 21 761 7549Block C, Antree Park Fax: +27 21 761 7648Doncaster Road Email: [EMAIL PROTECTED] Kenilworth, 7700 Http: http://www.2d3d.comSouth Africa msg04461/pgp0.pgp Description: PGP signature
Re: [Xpert]DRI fails with CVS X
> > if so, how do I tell it where the proper libraries are? > > Set LD_LIBRARY_PATH=/usr/local/X11R6/lib:$LD_LIBRARY_PATH or add it to > /etc/ld.so.conf (probably before /usr/X11R6/lib) and run ldconfig. thanks. I figured it was something like that. still new to library path configurations. :) > > attached is the output of 'startx 2>cvs-x.log' > > The server writes a detailed log to /var/log/XFree86.*.log. I do the 'startx 2>x.log' thing partly out of habit (was doing it before X 4 came out); and partly becuase it captures slightly different data than the /var/log/XFree86.*.log; and partly because it's a private copy of the log file, so if I test another user's X configuration, it doesn't blow it away. just personal preference. :) thanks! Carl Soderstrom -- Network Engineer Real-Time Enterprises (952) 943-8700 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI fails with CVS X
On Tue, 2001-12-11 at 07:45, Carl Wilhelm Soderstrom wrote: > I built X from CVS; and got it to install. however, DRI doesn't work. :( > glxinfo says it's using indirect rendering, and games are dead slow. > > this was a config that had DRI working before; so I know it's possible. > I installed X to /usr/local/X11R6; and in my .xserverrc pointed to > /etc/X11/X, which was symlinked to /usr/local/X11R6/bin/XFree86. > I edited the XF86Config-4 file to use /usr/local/X11R6/lib/ for fonts and > modules. the DRI modules are indeed in /usr/local/X11R6/lib/modules/dri. > however, if i run an strace on glxgears and capture the output, it's going > to /usr/X11R6/lib for its libraries, rather than /usr/local/X11R6/lib. > > could this be the problem? It likely is. > if so, how do I tell it where the proper libraries are? Set LD_LIBRARY_PATH=/usr/local/X11R6/lib:$LD_LIBRARY_PATH or add it to /etc/ld.so.conf (probably before /usr/X11R6/lib) and run ldconfig. > is there a way to tell what X modules are currently loaded (not kernel > modules)? (other than capturing stderr). > > attached is the output of 'startx 2>cvs-x.log' The server writes a detailed log to /var/log/XFree86.*.log. But this problem is unlikely to be related to X server modules. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI/DRM
On Sat, 2001-12-08 at 15:02, Barry Benowitz wrote: > I was looking for what I will be able to do if I build and install the DRI > patches? What patches? The DRI CVS doesn't have any major improvements over XFree86 CVS right now. > I already compiled the kernel to include the drm, but compiling X looks > daunting and I wanted to be sure that I will be able to do something usefull. It's only likely to be useful if there are any problems with the 4.1 binaries you use. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]dri trouble
On Sun, 9 Dec 2001, Peter Surda wrote: > On Sun, Dec 09, 2001 at 04:07:27AM +0100, Michel Dänzer wrote: > > On Sun, 2001-12-09 at 03:49, Peter Surda wrote: > > > - there are minor display distortions (parts of screen remain black, basically > > > the kde splash screen is completely fscked, but it sorts out later). > > Does the R128BlockHandler() function of the driver you're using contain > > a FLUSH_RING(); ? > Yes it does. It could be possible that this bug is triggered by tvout int10, > because it manifests itself as overwriting certain videoram parts with 0's. > OTOH splash screen looks ok if I disable dri > > > > - when I do a chvt 1;chvt 7, X starts eating all the CPU time and 2d > > > accelerated functions seize working (mouse can be moved but kde panel > > > doesn't pop up). killall X doesn't work, killall -9 X does. When this bug > > > feels like it should become especially mean to me, this killall -9 X causes > > > a complete machine lockup. > > In R128EnterVT(), try moving the R128ModeInit() and R128EngineInit() > > calls before the code guarded by #ifdef XF86DRI. > Yes, you were absolutely right, as always, this wasn't there and moving the > lines fixed the bug for good. > > Syslog still complains CONTINUOSLY though, but I think that isn't so important > now. > > > Those are fixes I made in DRI CVS some time ago, but at least the first > > one is in XFree86 CVS now. > I see. > > Volodya, pls commit the second one. In r128_driver.c, there is a R128EnterVT > function, and you only have (as Michel says) move ModeInit and EngineInit (3 > lines) before the #ifdef XF86DRI. I will only merge it after it gets into whatever CVS tree we are currently against. Otherwise it's a pain to upgrade. On a different topic - Michel, do you know how DRI gets it's DMA able memory, from agpgart or not ? - Thanks ! Vladimir Dergachev > > Same goes for xf86 maintainers (Marc, Mike, Michel, whoever feels like doing > it), pls commit in case it isn't there yet. > > Now I hope this was the last thing that prevented me from reaching normal > uptimes. > > Bye, > > Peter Surda (Shurdeek) <[EMAIL PROTECTED]>, ICQ 10236103, +436505122023 > > -- >They called their place of existence the "Universe", not the > "Great Programmer/Universe". > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]dri trouble
On Sun, Dec 09, 2001 at 04:07:27AM +0100, Michel Dänzer wrote: > On Sun, 2001-12-09 at 03:49, Peter Surda wrote: > > - there are minor display distortions (parts of screen remain black, basically > > the kde splash screen is completely fscked, but it sorts out later). > Does the R128BlockHandler() function of the driver you're using contain > a FLUSH_RING(); ? Yes it does. It could be possible that this bug is triggered by tvout int10, because it manifests itself as overwriting certain videoram parts with 0's. OTOH splash screen looks ok if I disable dri > > - when I do a chvt 1;chvt 7, X starts eating all the CPU time and 2d > > accelerated functions seize working (mouse can be moved but kde panel > > doesn't pop up). killall X doesn't work, killall -9 X does. When this bug > > feels like it should become especially mean to me, this killall -9 X causes > > a complete machine lockup. > In R128EnterVT(), try moving the R128ModeInit() and R128EngineInit() > calls before the code guarded by #ifdef XF86DRI. Yes, you were absolutely right, as always, this wasn't there and moving the lines fixed the bug for good. Syslog still complains CONTINUOSLY though, but I think that isn't so important now. > Those are fixes I made in DRI CVS some time ago, but at least the first > one is in XFree86 CVS now. I see. Volodya, pls commit the second one. In r128_driver.c, there is a R128EnterVT function, and you only have (as Michel says) move ModeInit and EngineInit (3 lines) before the #ifdef XF86DRI. Same goes for xf86 maintainers (Marc, Mike, Michel, whoever feels like doing it), pls commit in case it isn't there yet. Now I hope this was the last thing that prevented me from reaching normal uptimes. Bye, Peter Surda (Shurdeek) <[EMAIL PROTECTED]>, ICQ 10236103, +436505122023 -- They called their place of existence the "Universe", not the "Great Programmer/Universe". msg02300/pgp0.pgp Description: PGP signature
Re: [Xpert]dri trouble
On Sun, 2001-12-09 at 03:49, Peter Surda wrote: > - there are minor display distortions (parts of screen remain black, basically > the kde splash screen is completely fscked, but it sorts out later). Does the R128BlockHandler() function of the driver you're using contain a FLUSH_RING(); ? > - when I do a chvt 1;chvt 7, X starts eating all the CPU time and 2d > accelerated functions seize working (mouse can be moved but kde panel > doesn't pop up). killall X doesn't work, killall -9 X does. When this bug > feels like it should become especially mean to me, this killall -9 X causes > a complete machine lockup. In R128EnterVT(), try moving the R128ModeInit() and R128EngineInit() calls before the code guarded by #ifdef XF86DRI. Those are fixes I made in DRI CVS some time ago, but at least the first one is in XFree86 CVS now. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI/DRM
On Sat, 8 Dec 2001, Barry Benowitz wrote: > I was looking for what I will be able to do if I build and install the DRI > patches? > I already compiled the kernel to include the drm, but compiling X looks > daunting and I wanted to be sure that I will be able to do something usefull. X isn't all that bad. It just takes quite a while... As to what you can do; the main purpose of DRI is to allow you to run hardware-accelerated OpenGL programs, using your graphics card processor, instead of software-rendering using your main processor. Unless you're planning to run intensive OpenGL applications (such as Quake 2, Chromium etc), you probably won't see much improvement. -- Regards, [EMAIL PROTECTED] My website: http://www.iain.thomas.dial.pipex.com/ XMMS not playing ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]dri/drm from Xfree 4.1.0 for kernel 2.2.19?
On Fri, Sep 21, 2001 at 12:05:42PM +0200, Sven Garbade wrote: > Hi all, > > does dri/drm from Xfree 4.1.0 is also avaiable for the 2.2.19 kernel > series, and if yes, where can I get the corrct kernel modules? > No. 2.2.x support has been withdrawn. Alan. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]DRI in multiple X sessions?
division by zero wrote: > So, is it possible to have two X sessions both with DRI enabled > running simultaneously? Or is this only a dream? :-) The latter unfortunately, with the current DRI architecture. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
