Jos� Fonseca wrote: >On Tue, Jul 16, 2002 at 02:41:14PM -0700, Diek Van Nort wrote: > >>Hi, >> >>I have a 3D visualization tool that crashes with the 3.X versions of the >>Mesa that are in <=XF86 4.2.0. I noticed in the changelog that Mesa >>4.0.2 has been add to the latest CVS so I thought I would give it a try. >>Without DRI everything works great (except for the speed of course). The >>problems arise when I want to use DRI. I'll try to give all the >>backgroud information first, if I miss an important detail please let me >>know. >> >>My system is a clean RedHat 7.3 install on a dual athlon machine. My >>graphics card is Matrox G550. DRI loads and 'glxgears' works great with >>the XF86 4.2.0 that comes with RedHat 7.3. >> >>I download the CVS on July 16 and did a 'make World' and then a 'make >>install'. Everything seems to install ok and X starts without any >> > >This isn't enough, you need to recompile the DRM as you say below. > >>problems. I recompiled the DRI module for mga and installed it in the >>appropriate /lib/modules directory and did a 'depmod -a' >> > >You recompiled the DRM from where? From the one included in the XFree86 >CVS or any other place? > >>Using the same XF86Config-4 file from the 4.2.0 version under 4.2.99, >>DRI fails to load....... >> >>(II) MGA(0): [drm] bpp: 32 depth: 24 >>(II) MGA(0): [drm] Sarea 2200+664: 2864 >>drmOpenDevice: minor is 0 >>drmOpenDevice: node name is /dev/dri/card0 >>drmOpenDevice: open result is -1, (No such device) >>drmOpenDevice: Open failed >>drmOpenDevice: minor is 0 >>drmOpenDevice: node name is /dev/dri/card0 >>drmOpenDevice: open result is -1, (No such device) >>drmOpenDevice: Open failed >>[drm] failed to load kernel module "mga" >>(II) MGA(0): [drm] drmOpen failed >>(EE) MGA(0): [drm] DRIScreenInit failed. Disabling DRI. >> >>I think the reason that DRI fails to load is found in 'dmesg'. The >>following appears during startup of the X server: >> >>[drm:drm_init] *ERROR* Cannot initialize the agpgart module. >> >>I find this very strange since the agpgart hasn't changed since it >>loaded perfectly well under 4.2.0. I tried loading the mga module >>manually. With 'modprobe mga' I get: >> >>/lib/modules/2.4.18-3smp/kernel/drivers/char/drm/mga.o: init_module: >>Cannot allocate memory >>Hint: insmod errors can be caused by incorrect module parameters, >>including invalid IO or IRQ parameters >>/lib/modules/2.4.18-3smp/kernel/drivers/char/drm/mga.o: insmod >>/lib/modules/2.4.18-3smp/kernel/drivers/char/drm/mga.o failed >>/lib/modules/2.4.18-3smp/kernel/drivers/char/drm/mga.o: insmod mga failed >> >>If I load the agpgart module first, then I can load the mga module >>without errors. However, If I manually load agpgart and mga, start X and >>then try to run 'glxgears' by system freezes and I have to reboot. >>Another interesting point is that if I start XF86 4.2.0 and exit, the >>modules remain installed. I can then start XF86 4.2.99 with the modules >>installed by 4.2.0 and have DRI and glxgears work great. So I have come >>to the conclusion (of course I could be wrong) that the 4.2.99 version >>of XF86 loads the DRI or agpgart modules incorrectly. >> > >This is pretty confusing! Don't forget that if you load modules by hand >they will have to be removed by hand too.. > >First thing, let's try not to mix the two XFree86 versions, to eliminate >a source of problems. Tell us how you installed: did you overwriten your > That did it. I had just made a directory of the old /usr/X11R6 and then installed 4.2.99 over the top. Once I started with no /usr/X11R6 directory, everything works.
Thanks for the help, Diek > >Second, to the agpgart be loaded you have to have a line in your >modules.conf like: > > below mga agpgart > >Now, a brief tutorial to have DRI installed properly from CVS is: > > $ shutdown X > $ make install > $ cd programs/Xserver/hw/xfree86/os-support/linux/drm/kernel > $ make -f Makefile.linux mga.o > $ cp mga.o /lib/modules/2.4.18-3smp/kernel/drivers/char/drm/mga.o > $ depmod -a > $ rmmod mga > $ restart X > >Check if you did all the above steps. > >>If I have overlooked something that I should try please let me know. If >>this isn't suppose to be supported yet and I just have to deal with >>Indirect rendering pelase let me know. Please just let me know anything, >>I have played around with this for a long time and it is becoming an >>obsession which needs to die so I can acutally do work. >> > >Don't forget to check out the binary snapshots from >http://dri.sf.net/snapshots . These are from the DRI CVS and not >XFree86's, but they also have Mesa 4.x. The install script automates most >of the process of installation so it could create > >>A few more outputs that might be of interest............. >> >>The thing that I find interesting is the "OpenGL version string:" When I >>try to load the modules manually I get 1.2 Mesa 4.0.2, when the modules >>fail to laod I get "1.3 Mesa 4.0.2" Could it be that DRI is trying to >>load the wrong version of OpenGL Mesa API? >> > >No. The software only Mesa always reports 1.3, but the drivers only >report 1.3 if they actually can accelerate the OpenGL extensions >required for 1.3 conformance. > >[...] > >Jos� Fonseca >_______________________________________________ >Xpert mailing list >[EMAIL PROTECTED] >http://XFree86.Org/mailman/listinfo/xpert > _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
