On 31 May 2002, Michel Dänzer wrote: > On Fri, 2002-05-31 at 02:30, Felix Kühling wrote: > > > > I reported lockups shortly after starting the Xserver with a gcc 3.0 > > compiled drm module that triggered the strange permission problem. Now I > > tested it without loading the dri Xserver module in XF86Config and got > > the same lockup. The following messages in XFree86.1.log indicate that > > the problem is that the 2D driver currently doesn't work without drm: > > > > (II) ATI(0): Direct rendering disabled > > Symbol DRILock from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o >is unresolved! > > Symbol drmMach64WaitForIdle from module >/usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved!
[ yadda yadda yadda ... ] > > Symbol DRICloseScreen from module >/usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! > > Symbol DRIDestroyInfoRec from module >/usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! > > > > I will recompile my entire kernel with gcc-3.0 tomorrow to see if the > > permission goes away, but this is still a problem, I think. The 2D > > Xserver should work without DRI loaded. > > These messages are harmless unless one of the unresolved symbols is > referenced, which shouldn't happen when DRI is disabled. And even if one > of them was referenced, that would cause a server crash and not a > lockup. (Unless the crash causes a lockup...) > > I think the messages can be silenced by adding the symbols to the > xf86LoaderRefSymLists() call. Thanks for the tip. I commited a fix for this that quiets these messages. I used xf86LoaderRefSymLists() in ATIPreInit (atipreinit.c) a la the r128 and Radeon drivers. Felix, 2D accel should work when dri is disabled with the current branch, so you might try running two Xservers based on the branch, one with dri enabled and one with it disabled and see if you still have the lockup. A couple of weeks ago, I also made sure that the DDX in the DRI branch explicitly sets the FIFO size to 128 entries, rather than reading the regsiter and saving that value (which is restored on mode/vt switches), in order to avoid the problem you mentioned before. IIRC, you had started the DRI enabled server from a console with the xfree 4.1 server already running. In that case, the DDX in the newly started server saved the value set by the 4.1 server, which would cause a lockup with dri. In this case though, without dri enabled, I don't how that could be the problem. -- Leif Delgass http://www.retinalburn.net _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
