From: Leif D. <lde...@re...> - 2003-04-29 22:37:52
|
I'm cc:ing the dri-users mailing list, please reply to that list if you have questions... You need to have a working install of XFree86 4.3.0 first. Then you have two options: 1. Try the binary snapshots (Linux x86 only) at: http://dri.sourceforge.net/snapshots/bleeding-edge/ Download, unpack, exit X, become root, run ./install.sh. You'll need kernel sources installed to build the kernel module -- note that kernel headers are not enough, you need a full tree. The build is done by the install script, but you'll need the sources installed first. 2. Check out DRI cvs with the 'mach64-0-0-6-branch' branch tag. Build and install. See: http://dri.sourceforge.net/doc/DRIcompile.html To get the branch, use 'co -r mach64-0-0-6-branch xc' instead of 'co xc' for the CVS checkout command. --Leif On 29 Apr 2003, Philippe Moutarlier wrote: > Is there a way to retrieve this branch and give it a shot or is the > integration less than obvious ? > > Thanks, > > Philippe > > On Tue, 2003-04-29 at 16:33, Marc Aurele La France wrote: > > On 28 Apr 2003, Philippe Moutarlier wrote: > > > > > a while ago it 3D accel used to work with the old utah-glx code. > > > It was not there in early stages of the new DRI architecture. > > > Is it there now (I don't seem to be able to get it to work though...). > > > It is just that all my laptops seem to just have this one only card :-) > > > > There's a branch for this in the DRI tree which has yet to be integrated > > into XFree86's CVS. > > > > Marc. > > > > +----------------------------------+-----------------------------------+ > > | Marc Aurele La France | work: 1-780-492-9310 | > > | Computing and Network Services | fax: 1-780-492-1729 | > > | 352 General Services Building | email: ts...@ua... | > > | University of Alberta +-----------------------------------+ > > | Edmonton, Alberta | | > > | T6G 2H1 | Standard disclaimers apply | > > | CANADA | | > > +----------------------------------+-----------------------------------+ > > XFree86 Core Team member. ATI driver and X server internals. > > > > _______________________________________________ > > XFree86 mailing list > > XFree86@XFree86.Org > > http://XFree86.Org/mailman/listinfo/xfree86 > -- Leif Delgass http://www.retinalburn.net |
From: Philippe M. <phi...@at...> - 2003-04-30 05:34:07
|
Thanks ! I'll try it. I would love to see those "old" laptop cards 3d accelerated ! Philippe On Tue, 2003-04-29 at 18:36, Leif Delgass wrote: > I'm cc:ing the dri-users mailing list, please reply to that list if you > have questions... > > You need to have a working install of XFree86 4.3.0 first. Then you have > two options: > > 1. Try the binary snapshots (Linux x86 only) at: > http://dri.sourceforge.net/snapshots/bleeding-edge/ > > Download, unpack, exit X, become root, run ./install.sh. You'll need > kernel sources installed to build the kernel module -- note that kernel > headers are not enough, you need a full tree. The build is done by the > install script, but you'll need the sources installed first. > > 2. Check out DRI cvs with the 'mach64-0-0-6-branch' branch tag. Build and > install. See: > > http://dri.sourceforge.net/doc/DRIcompile.html > > To get the branch, use 'co -r mach64-0-0-6-branch xc' instead of > 'co xc' for the CVS checkout command. > > --Leif > > On 29 Apr 2003, Philippe Moutarlier wrote: > > > Is there a way to retrieve this branch and give it a shot or is the > > integration less than obvious ? > > > > Thanks, > > > > Philippe > > > > On Tue, 2003-04-29 at 16:33, Marc Aurele La France wrote: > > > On 28 Apr 2003, Philippe Moutarlier wrote: > > > > > > > a while ago it 3D accel used to work with the old utah-glx code. > > > > It was not there in early stages of the new DRI architecture. > > > > Is it there now (I don't seem to be able to get it to work though...). > > > > It is just that all my laptops seem to just have this one only card :-) > > > > > > There's a branch for this in the DRI tree which has yet to be integrated > > > into XFree86's CVS. > > > > > > Marc. > > > > > > +----------------------------------+-----------------------------------+ > > > | Marc Aurele La France | work: 1-780-492-9310 | > > > | Computing and Network Services | fax: 1-780-492-1729 | > > > | 352 General Services Building | email: ts...@ua... | > > > | University of Alberta +-----------------------------------+ > > > | Edmonton, Alberta | | > > > | T6G 2H1 | Standard disclaimers apply | > > > | CANADA | | > > > +----------------------------------+-----------------------------------+ > > > XFree86 Core Team member. ATI driver and X server internals. > > > > > > _______________________________________________ > > > XFree86 mailing list > > > XFree86@XFree86.Org > > > http://XFree86.Org/mailman/listinfo/xfree86 > > -- Philippe Moutarlier <phi...@at...> |
From: Martin D. <md...@st...> - 2003-05-03 02:06:55
|
I have a dell 7500 with a ATI Rage Mobilty card. I am assuming that it is a supported card for the dri to work with. Maybe it is not supported? I downloaded the bleeding edge source as you mention. I have the kernel source full tree installed as you also mention. I wanted to just compile the drm mmodules first without running the install.sh to make sure that they compile So I ran "make -f Makefile.linux" from the drm directory and I get the errors below. I could follow the steps that you outline for installing without disturbing the existing installation if that would help... any help would be appreciated [root@localhost drm]# make -f Makefile.linux === KERNEL HEADERS IN /lib/modules/2.4.20-9/build/include === SMP=0 MODULES=1 MODVERSIONS=1 AGP=1 === Compiling for machine i686 === WARNING === WARNING Use 2.4.x kernels ONLY ! === WARNING cc -O2 -Wall -Wwrite-strings -Wpointer-arith -Wcast-align -Wstrict-prototypes -Wnested-externs -Wpointer-arith -D__KERNEL__ -DMODULE -fomit-frame-pointer -DCONFIG_AGP -DCONFIG_AGP_MODULE -DCONFIG_DRM_SIS -DMODVERSIONS -include /lib/modules/2.4.20-9/build/include/linux/modversions.h -DEXPORT_SYMTAB -I/lib/modules/2.4.20-9/build/include -c gamma_drv.c -o gamma_drv.o In file included from /lib/modules/2.4.20-9/build/include/linux/irq.h:69, from /lib/modules/2.4.20-9/build/include/asm/hardirq.h:6, from /lib/modules/2.4.20-9/build/include/linux/interrupt.h:46, from /lib/modules/2.4.20-9/build/include/asm/highmem.h:25, from /lib/modules/2.4.20-9/build/include/linux/highmem.h:11, from /lib/modules/2.4.20-9/build/include/linux/vmalloc.h:8, from /lib/modules/2.4.20-9/build/include/asm/io.h:47, from /lib/modules/2.4.20-9/build/include/asm/pci.h:35, from /lib/modules/2.4.20-9/build/include/linux/pci.h:657, from drmP.h:50, from gamma_drv.c:34: /lib/modules/2.4.20-9/build/include/asm/hw_irq.h: In function `x86_do_profile': /lib/modules/2.4.20-9/build/include/asm/hw_irq.h:195: warning: nested extern declaration of `prof_cpu_mask' /lib/modules/2.4.20-9/build/include/asm/hw_irq.h:196: warning: nested extern declaration of `_stext' In file included from /lib/modules/2.4.20-9/build/include/linux/vmalloc.h:8, from /lib/modules/2.4.20-9/build/include/asm/io.h:47, from /lib/modules/2.4.20-9/build/include/asm/pci.h:35, from /lib/modules/2.4.20-9/build/include/linux/pci.h:657, from drmP.h:50, from gamma_drv.c:34: /lib/modules/2.4.20-9/build/include/linux/highmem.h: In function `bh_kmap': /lib/modules/2.4.20-9/build/include/linux/highmem.h:20: warning: pointer of type `void *' used in arithmetic In file included from gamma_drv.c:99: drm_vm.h: In function `gamma_mmap': drm_vm.h:462: warning: passing arg 1 of `remap_page_range_R2baf18f2' makes pointer from integer without a cast drm_vm.h:462: incompatible type for argument 4 of `remap_page_range_R2baf18f2' drm_vm.h:462: too few arguments to function `remap_page_range_R2baf18f2' make: *** [gamma_drv.o] Error 1 [root@localhost drm]# On Tue, 2003-04-29 at 17:36, Leif Delgass wrote: > I'm cc:ing the dri-users mailing list, please reply to that list if you > have questions... > > You need to have a working install of XFree86 4.3.0 first. Then you have > two options: > > 1. Try the binary snapshots (Linux x86 only) at: > http://dri.sourceforge.net/snapshots/bleeding-edge/ > > Download, unpack, exit X, become root, run ./install.sh. You'll need > kernel sources installed to build the kernel module -- note that kernel > headers are not enough, you need a full tree. The build is done by the > install script, but you'll need the sources installed first. > > 2. Check out DRI cvs with the 'mach64-0-0-6-branch' branch tag. Build and > install. See: > > http://dri.sourceforge.net/doc/DRIcompile.html > > To get the branch, use 'co -r mach64-0-0-6-branch xc' instead of > 'co xc' for the CVS checkout command. > > --Leif > > On 29 Apr 2003, Philippe Moutarlier wrote: > > > Is there a way to retrieve this branch and give it a shot or is the > > integration less than obvious ? > > > > Thanks, > > > > Philippe > > > > On Tue, 2003-04-29 at 16:33, Marc Aurele La France wrote: > > > On 28 Apr 2003, Philippe Moutarlier wrote: > > > > > > > a while ago it 3D accel used to work with the old utah-glx code. > > > > It was not there in early stages of the new DRI architecture. > > > > Is it there now (I don't seem to be able to get it to work though...). > > > > It is just that all my laptops seem to just have this one only card :-) > > > > > > There's a branch for this in the DRI tree which has yet to be integrated > > > into XFree86's CVS. > > > > > > Marc. > > > > > > +----------------------------------+-----------------------------------+ > > > | Marc Aurele La France | work: 1-780-492-9310 | > > > | Computing and Network Services | fax: 1-780-492-1729 | > > > | 352 General Services Building | email: ts...@ua... | > > > | University of Alberta +-----------------------------------+ > > > | Edmonton, Alberta | | > > > | T6G 2H1 | Standard disclaimers apply | > > > | CANADA | | > > > +----------------------------------+-----------------------------------+ > > > XFree86 Core Team member. ATI driver and X server internals. > > > > > > _______________________________________________ > > > XFree86 mailing list > > > XFree86@XFree86.Org > > > http://XFree86.Org/mailman/listinfo/xfree86 > > -- Martin Duffy <md...@st...> StarSoft, Inc. |
From: Leif D. <lde...@re...> - 2003-05-03 03:10:42
|
It looks like the snapshots aren't up to date with the lastest CVS branch code (maybe they are still being built from the older branch?). The best thing right now is probably to go with option 2 and checkout the CVS branch and follow the compile guide. On 2 May 2003, Martin Duffy wrote: > I have a dell 7500 with a ATI Rage Mobilty card. I am assuming that it > is a supported card for the dri to work with. Maybe it is not supported? > > I downloaded the bleeding edge source as you mention. > > I have the kernel source full tree installed as you also mention. I > wanted to just compile the drm mmodules first without running the > install.sh to make sure that they compile > > > So I ran "make -f Makefile.linux" from the drm directory and I get the > errors below. > > I could follow the steps that you outline for installing without > disturbing the existing installation if that would help... > > any help would be appreciated > > > [root@localhost drm]# make -f Makefile.linux > === KERNEL HEADERS IN /lib/modules/2.4.20-9/build/include > === SMP=0 MODULES=1 MODVERSIONS=1 AGP=1 > === Compiling for machine i686 > === WARNING > === WARNING Use 2.4.x kernels ONLY ! > === WARNING > cc -O2 -Wall -Wwrite-strings -Wpointer-arith -Wcast-align > -Wstrict-prototypes -Wnested-externs -Wpointer-arith -D__KERNEL__ > -DMODULE -fomit-frame-pointer -DCONFIG_AGP -DCONFIG_AGP_MODULE > -DCONFIG_DRM_SIS -DMODVERSIONS -include > /lib/modules/2.4.20-9/build/include/linux/modversions.h -DEXPORT_SYMTAB > -I/lib/modules/2.4.20-9/build/include -c gamma_drv.c -o gamma_drv.o > In file included from > /lib/modules/2.4.20-9/build/include/linux/irq.h:69, > from > /lib/modules/2.4.20-9/build/include/asm/hardirq.h:6, > from > /lib/modules/2.4.20-9/build/include/linux/interrupt.h:46, > from > /lib/modules/2.4.20-9/build/include/asm/highmem.h:25, > from > /lib/modules/2.4.20-9/build/include/linux/highmem.h:11, > from > /lib/modules/2.4.20-9/build/include/linux/vmalloc.h:8, > from /lib/modules/2.4.20-9/build/include/asm/io.h:47, > from /lib/modules/2.4.20-9/build/include/asm/pci.h:35, > from > /lib/modules/2.4.20-9/build/include/linux/pci.h:657, > from drmP.h:50, > from gamma_drv.c:34: > /lib/modules/2.4.20-9/build/include/asm/hw_irq.h: In function > `x86_do_profile': > /lib/modules/2.4.20-9/build/include/asm/hw_irq.h:195: warning: nested > extern declaration of `prof_cpu_mask' > /lib/modules/2.4.20-9/build/include/asm/hw_irq.h:196: warning: nested > extern declaration of `_stext' > In file included from > /lib/modules/2.4.20-9/build/include/linux/vmalloc.h:8, > from /lib/modules/2.4.20-9/build/include/asm/io.h:47, > from /lib/modules/2.4.20-9/build/include/asm/pci.h:35, > from > /lib/modules/2.4.20-9/build/include/linux/pci.h:657, > from drmP.h:50, > from gamma_drv.c:34: > /lib/modules/2.4.20-9/build/include/linux/highmem.h: In function > `bh_kmap': > /lib/modules/2.4.20-9/build/include/linux/highmem.h:20: warning: pointer > of type `void *' used in arithmetic > In file included from gamma_drv.c:99: > drm_vm.h: In function `gamma_mmap': > drm_vm.h:462: warning: passing arg 1 of `remap_page_range_R2baf18f2' > makes pointer from integer without a cast > drm_vm.h:462: incompatible type for argument 4 of > `remap_page_range_R2baf18f2' > drm_vm.h:462: too few arguments to function `remap_page_range_R2baf18f2' > make: *** [gamma_drv.o] Error 1 > [root@localhost drm]# > > > > > > > > On Tue, 2003-04-29 at 17:36, Leif Delgass wrote: > > I'm cc:ing the dri-users mailing list, please reply to that list if you > > have questions... > > > > You need to have a working install of XFree86 4.3.0 first. Then you have > > two options: > > > > 1. Try the binary snapshots (Linux x86 only) at: > > http://dri.sourceforge.net/snapshots/bleeding-edge/ > > > > Download, unpack, exit X, become root, run ./install.sh. You'll need > > kernel sources installed to build the kernel module -- note that kernel > > headers are not enough, you need a full tree. The build is done by the > > install script, but you'll need the sources installed first. > > > > 2. Check out DRI cvs with the 'mach64-0-0-6-branch' branch tag. Build and > > install. See: > > > > http://dri.sourceforge.net/doc/DRIcompile.html > > > > To get the branch, use 'co -r mach64-0-0-6-branch xc' instead of > > 'co xc' for the CVS checkout command. > > > > --Leif > > > > On 29 Apr 2003, Philippe Moutarlier wrote: > > > > > Is there a way to retrieve this branch and give it a shot or is the > > > integration less than obvious ? > > > > > > Thanks, > > > > > > Philippe > > > > > > On Tue, 2003-04-29 at 16:33, Marc Aurele La France wrote: > > > > On 28 Apr 2003, Philippe Moutarlier wrote: > > > > > > > > > a while ago it 3D accel used to work with the old utah-glx code. > > > > > It was not there in early stages of the new DRI architecture. > > > > > Is it there now (I don't seem to be able to get it to work though...). > > > > > It is just that all my laptops seem to just have this one only card :-) > > > > > > > > There's a branch for this in the DRI tree which has yet to be integrated > > > > into XFree86's CVS. > > > > > > > > Marc. > > > > > > > > +----------------------------------+-----------------------------------+ > > > > | Marc Aurele La France | work: 1-780-492-9310 | > > > > | Computing and Network Services | fax: 1-780-492-1729 | > > > > | 352 General Services Building | email: ts...@ua... | > > > > | University of Alberta +-----------------------------------+ > > > > | Edmonton, Alberta | | > > > > | T6G 2H1 | Standard disclaimers apply | > > > > | CANADA | | > > > > +----------------------------------+-----------------------------------+ > > > > XFree86 Core Team member. ATI driver and X server internals. > > > > > > > > _______________________________________________ > > > > XFree86 mailing list > > > > XFree86@XFree86.Org > > > > http://XFree86.Org/mailman/listinfo/xfree86 > > > > -- Leif Delgass http://www.retinalburn.net |
From: F. <jrf...@tu...> - 2003-05-03 11:25:11
|
On Fri, May 02, 2003 at 10:09:33PM -0500, Leif Delgass wrote: > It looks like the snapshots aren't up to date with the lastest CVS branch > code (maybe they are still being built from the older branch?). Yes. Fixed and just fired a new build now which should complete soon. > The best > thing right now is probably to go with option 2 and checkout the CVS > branch and follow the compile guide. José Fonseca |
From: Leif D. <lde...@re...> - 2003-05-03 17:12:08
|
On Sat, 3 May 2003, =5Biso-8859-15=5D Jos=E9 Fonseca wrote: > On Fri, May 02, 2003 at 10:09:33PM -0500, Leif Delgass wrote: > > It looks like the snapshots aren't up to date with the lastest CVS br= anch > > code (maybe they are still being built from the older branch?). = > = > Yes. Fixed and just fired a new build now which should complete soon. Thanks, Jos=E9. btw, it looks like the old bleeding-edge snapshots aren'= t = being deleted. iirc, there used to be about a week's worth or so at any = = given time, but there are more than a month's worth now. -- = Leif Delgass = http://www.retinalburn.net |
From: F. <jrf...@tu...> - 2003-05-05 14:02:34
|
On Sat, May 03, 2003 at 12:11:01PM -0500, Leif Delgass wrote: > On Sat, 3 May 2003, [iso-8859-15] José Fonseca wrote: > > > On Fri, May 02, 2003 at 10:09:33PM -0500, Leif Delgass wrote: > > > It looks like the snapshots aren't up to date with the lastest CVS branch > > > code (maybe they are still being built from the older branch?). > > > > Yes. Fixed and just fired a new build now which should complete soon. > > Thanks, José. I had changed the build to the mach64-0-0-6-branch once but it must have been reversed when syncing the scripts with the copy in my SF shell account. > btw, it looks like the old bleeding-edge snapshots aren't > being deleted. iirc, there used to be about a week's worth or so at any > given time, but there are more than a month's worth now. I had disabled the snapshot purging cron job when the snapshots were also disabled, but I've re-enabled them now. José Fonseca |
From: Martin D. <md...@st...> - 2003-05-04 05:42:47
|
I may have accidentally sent a reply directly to some individuals on a previous message. Please excuse me for doing that...... I tried to run the make with the bleeding edge snapshot for May 3, 2003 and I got a different error this time. Here is a snip of dri.log where the error happened =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D touch: creating `/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jf s/jfs_debug.h': No such file or directory make[2]: *** [/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jfs/j fs_debug.h] Error 1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D I do have the file that is mentioned on my file system: /usr/src/linux-2.4.20-9/fs/jfs/jfs_debug.h I am running Redhat 9 kernel 2.4.20-9 I have a mach64 ATI Rage Mobility card in a Dell Inspiron 7500 Here is the output to dri.log =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [root@localhost drm]# make -f Makefile.linux rm -f /lib/modules/2.4.20-9/build/.config ln -s /lib/modules/2.4.20-9/build/configs/kernel-2.4.20-i686.config /lib/modules /2.4.20-9/build/.config rm -f .config ln -s /lib/modules/2.4.20-9/build/configs/kernel-2.4.20-i686.config .config rm -f linux ln -s . linux + ln -s Makefile.linux Makefile make -C /lib/modules/2.4.20-9/build SUBDIRS=3D`pwd` DRMSRCDIR=3D`pwd` modules make[1]: Entering directory `/usr/src/linux-2.4.20-9' gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/split-include scripts/split-include.c scripts/split-include include/linux/autoconf.h include/config make -r -f tmp_include_depends all make[2]: Entering directory `/usr/src/linux-2.4.20-9' touch: creating `/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jf s/jfs_debug.h': No such file or directory make[2]: *** [/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jfs/j fs_debug.h] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.20-9' make[1]: *** [tmp_include_depends] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.20-9' make: *** [modules] Error 2 On Sat, 2003-05-03 at 06:24, Jos=C3=A9 Fonseca wrote: > On Fri, May 02, 2003 at 10:09:33PM -0500, Leif Delgass wrote: > > It looks like the snapshots aren't up to date with the lastest CVS br= anch > > code (maybe they are still being built from the older branch?). =20 >=20 > Yes. Fixed and just fired a new build now which should complete soon. >=20 > > The best > > thing right now is probably to go with option 2 and checkout the CVS=20 > > branch and follow the compile guide. >=20 > Jos=C3=A9 Fonseca >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dri-users mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-users --=20 Martin Duffy <md...@st...> StarSoft, Inc. |
From: Martin D. <md...@st...> - 2003-05-05 05:58:02
|
I was able to get the drm modules to compile by creating a directory structure that was in the tmp_include_depends file and copying my complete kernel source tree into it. I created the following directory structure (as referenced by the tmp_include_depends file) /usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9 and copied all of the file and directories in=20 /usr/src/linux-2.4.20-9 into that new directory=20 I have not tried the drm modules that compiled successfully yet. I will pass it on if I can get it to work. On Sun, 2003-05-04 at 00:46, Martin Duffy wrote: > I may have accidentally sent a reply directly to some individuals on a > previous message. Please excuse me for doing that...... >=20 > I tried to run the make with the bleeding edge snapshot for May 3, 2003 > and I got a different error this time. >=20 > Here is a snip of dri.log where the error happened > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > touch: creating > `/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jf > s/jfs_debug.h': No such file or directory > make[2]: *** > [/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jfs/j > fs_debug.h] Error 1 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > I do have the file that is mentioned on my file system: >=20 > /usr/src/linux-2.4.20-9/fs/jfs/jfs_debug.h >=20 >=20 > I am running Redhat 9 kernel 2.4.20-9 I have a mach64 ATI Rage Mobility > card in a Dell Inspiron 7500 >=20 > Here is the output to dri.log >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > [root@localhost drm]# make -f Makefile.linux > rm -f /lib/modules/2.4.20-9/build/.config > ln -s /lib/modules/2.4.20-9/build/configs/kernel-2.4.20-i686.config > /lib/modules > /2.4.20-9/build/.config > rm -f .config > ln -s /lib/modules/2.4.20-9/build/configs/kernel-2.4.20-i686.config > .config > rm -f linux > ln -s . linux > + ln -s Makefile.linux Makefile > make -C /lib/modules/2.4.20-9/build SUBDIRS=3D`pwd` DRMSRCDIR=3D`pwd` > modules > make[1]: Entering directory `/usr/src/linux-2.4.20-9' > gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o > scripts/split-include > scripts/split-include.c > scripts/split-include include/linux/autoconf.h include/config > make -r -f tmp_include_depends all > make[2]: Entering directory `/usr/src/linux-2.4.20-9' > touch: creating > `/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jf > s/jfs_debug.h': No such file or directory > make[2]: *** > [/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jfs/j > fs_debug.h] Error 1 > make[2]: Leaving directory `/usr/src/linux-2.4.20-9' > make[1]: *** [tmp_include_depends] Error 2 > make[1]: Leaving directory `/usr/src/linux-2.4.20-9' > make: *** [modules] Error 2 >=20 >=20 > On Sat, 2003-05-03 at 06:24, Jos=C3=A9 Fonseca wrote: > > On Fri, May 02, 2003 at 10:09:33PM -0500, Leif Delgass wrote: > > > It looks like the snapshots aren't up to date with the lastest CVS = branch > > > code (maybe they are still being built from the older branch?). =20 > >=20 > > Yes. Fixed and just fired a new build now which should complete soon. > >=20 > > > The best > > > thing right now is probably to go with option 2 and checkout the CV= S=20 > > > branch and follow the compile guide. > >=20 > > Jos=C3=A9 Fonseca > >=20 > >=20 > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Dri-users mailing list > > Dri...@li... > > https://lists.sourceforge.net/lists/listinfo/dri-users --=20 Martin Duffy <md...@st...> StarSoft, Inc. |
From: Martin D. <md...@st...> - 2003-05-05 06:40:30
|
dri is working now. Not really that fast I think - I am getting 281 fps vs. about 112 without dri. I imagine that I will need to play with the settings for the driver to get anything faster. One thing that I have seen if that the dri only works if I start in console mode (3) and then do a startx from my home directory. If I set the startup mode to 5 for a graphical start I do not get dri. I will figure that out I guess. I appreciate the howtos and the help that has been given... Thanks Martin On Mon, 2003-05-05 at 01:00, Martin Duffy wrote: > I was able to get the drm modules to compile by creating a directory > structure that was in the tmp_include_depends file and copying my > complete kernel source tree into it. >=20 > I created the following directory structure (as referenced by the > tmp_include_depends file) >=20 > /usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9 >=20 > and copied all of the file and directories in=20 >=20 > /usr/src/linux-2.4.20-9 >=20 > into that new directory=20 >=20 > I have not tried the drm modules that compiled successfully yet. I will > pass it on if I can get it to work. >=20 >=20 >=20 > On Sun, 2003-05-04 at 00:46, Martin Duffy wrote: > > I may have accidentally sent a reply directly to some individuals on = a > > previous message. Please excuse me for doing that...... > >=20 > > I tried to run the make with the bleeding edge snapshot for May 3, 20= 03 > > and I got a different error this time. > >=20 > > Here is a snip of dri.log where the error happened > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > touch: creating > > `/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jf > > s/jfs_debug.h': No such file or directory > > make[2]: *** > > [/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jfs/j > > fs_debug.h] Error 1 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >=20 > > I do have the file that is mentioned on my file system: > >=20 > > /usr/src/linux-2.4.20-9/fs/jfs/jfs_debug.h > >=20 > >=20 > > I am running Redhat 9 kernel 2.4.20-9 I have a mach64 ATI Rage Mobili= ty > > card in a Dell Inspiron 7500 > >=20 > > Here is the output to dri.log > >=20 > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >=20 > > [root@localhost drm]# make -f Makefile.linux > > rm -f /lib/modules/2.4.20-9/build/.config > > ln -s /lib/modules/2.4.20-9/build/configs/kernel-2.4.20-i686.config > > /lib/modules > > /2.4.20-9/build/.config > > rm -f .config > > ln -s /lib/modules/2.4.20-9/build/configs/kernel-2.4.20-i686.config > > .config > > rm -f linux > > ln -s . linux > > + ln -s Makefile.linux Makefile > > make -C /lib/modules/2.4.20-9/build SUBDIRS=3D`pwd` DRMSRCDIR=3D`pwd= ` > > modules > > make[1]: Entering directory `/usr/src/linux-2.4.20-9' > > gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o > > scripts/split-include > > scripts/split-include.c > > scripts/split-include include/linux/autoconf.h include/config > > make -r -f tmp_include_depends all > > make[2]: Entering directory `/usr/src/linux-2.4.20-9' > > touch: creating > > `/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jf > > s/jfs_debug.h': No such file or directory > > make[2]: *** > > [/usr/src/build/236023-i386/install/usr/src/linux-2.4.20-9/fs/jfs/j > > fs_debug.h] Error 1 > > make[2]: Leaving directory `/usr/src/linux-2.4.20-9' > > make[1]: *** [tmp_include_depends] Error 2 > > make[1]: Leaving directory `/usr/src/linux-2.4.20-9' > > make: *** [modules] Error 2 > >=20 > >=20 > > On Sat, 2003-05-03 at 06:24, Jos=C3=A9 Fonseca wrote: > > > On Fri, May 02, 2003 at 10:09:33PM -0500, Leif Delgass wrote: > > > > It looks like the snapshots aren't up to date with the lastest CV= S branch > > > > code (maybe they are still being built from the older branch?). =20 > > >=20 > > > Yes. Fixed and just fired a new build now which should complete soo= n. > > >=20 > > > > The best > > > > thing right now is probably to go with option 2 and checkout the = CVS=20 > > > > branch and follow the compile guide. > > >=20 > > > Jos=C3=A9 Fonseca > > >=20 > > >=20 > > > ------------------------------------------------------- > > > This sf.net email is sponsored by:ThinkGeek > > > Welcome to geek heaven. > > > http://thinkgeek.com/sf > > > _______________________________________________ > > > Dri-users mailing list > > > Dri...@li... > > > https://lists.sourceforge.net/lists/listinfo/dri-users --=20 Martin Duffy <md...@st...> StarSoft, Inc. |