Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
: Well, I built kernel 2.4.18-0.26 (from RH Rawhide SRPM) and got much trouble. The worst of it that my vmware does not work any more:( The vm* modules are built OK but I get OOPS loading them. Well, but even drm does not work any better. I rebuilt mach64.o again and still get those Permission denied messages. Any clues? Regards, Sergey ___ 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
Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
Hi, I submitted another message about this yesterday. It didn't show up in the SourceForge archive and you didn't refer to it, so I'm submitting it again: -- [Michel Dänzer [EMAIL PROTECTED]] 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 had a closer look at this. I get a lockup when I run the Xserver without DRI after switching from a 2D accelerated XFree86 4.1 server to the text console. If DRI is loaded there is no problem. If I start the Mach64-Xserver after a reboot and without DRI there is no problem either. I guess this means that the 3D driver puts the card in some state that the 2D driver relies on and the old Xserver messes it up. -- Maybe it's again a problem with the FIFO size. Just a guess. Anyway, I think I'll switch to the new accelerated server as you proposed. It seems that I'm just asking for trouble with my current config :) Regards, Felix On Sat, 1 Jun 2002 22:02:14 -0400 (EDT) Leif Delgass [EMAIL PROTECTED] wrote: 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 __\|/_____ ___ ___ __Tschüß___\_6 6_/___/__ \___/__ \___/___\___You can do anything,___ _Felix___\Ä/\ \_\ \_\ \__U___just not everything [EMAIL PROTECTED]o__/ \___/ \___/at the same time! ___ 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
Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
On Sun, 2 Jun 2002 13:48:02 -0400 (EDT) Leif Delgass [EMAIL PROTECTED] wrote: [...] I had a closer look at this. I get a lockup when I run the Xserver without DRI after switching from a 2D accelerated XFree86 4.1 server to the text console. If DRI is loaded there is no problem. If I start the Mach64-Xserver after a reboot and without DRI there is no problem either. I guess this means that the 3D driver puts the card in some state that the 2D driver relies on and the old Xserver messes it up. Since the dri branch driver works on it's own without dri enabled, I don't see how it could be a 3D driver dependency. Unless I'm not understanding you, the problem is with two 2D drivers without dri enabled on either. What I mean is that the problem does not occur when I start the new Xserver with DRI. So I concluded that the 3D driver does something that prevents the problem from happening that the 2D driver should better do himself. But when I think about it again it could also be the 2D acceleration which is disabled when DRI is loaded. So 4.2 2D accel locks up when 4.1 2D accel has been running just before. Maybe it's a bad interaction between xfree 4.1 and 4.2? I just tried Yes, definitely. starting a 4.2 based gatos driver, then switching to a text console and starting the dri branch driver with dri disabled. I can switch back and forth between them and to a text console without a lockup. I don't have a 4.1 server anymore so I can't test that. -- Maybe it's again a problem with the FIFO size. Just a guess. This shouldn't be a problem when dri isn't enabled. Ok, it's probably 2D acceleration. Anyway, I think I'll switch to the new accelerated server as you proposed. It seems that I'm just asking for trouble with my current config :) ok. I'm still curious about what the problem is, though. How recent is the dri branch build you're using? Is the 4.1 server a vanilla xfree release or a gatos driver? This is the start of the server output: This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.17 i686 [ELF] It's the one that comes with Debian Woody. I wouldn't take any bets on how vanilla that is. Unfortunately there is no XFree86 4.2 in Debian, not even in unstable. Regards, Felix __\|/_____ ___ ___ __Tschüß___\_6 6_/___/__ \___/__ \___/___\___You can do anything,___ _Felix___\Ä/\ \_\ \_\ \__U___just not everything [EMAIL PROTECTED]o__/ \___/ \___/at the same time! ___ 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
Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
On 31 May 2002 23:20:19 +0200 Michel Dänzer [EMAIL PROTECTED] 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: [...] 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 had a closer look at this. I get a lockup when I run the Xserver without DRI after switching from a 2D accelerated XFree86 4.1 server to the text console. If DRI is loaded there is no problem. If I start the Mach64-Xserver after a reboot and without DRI there is no problem either. I guess this means that the 3D driver puts the card in some state that the 2D driver relies on and the old Xserver messes it up. Regards, Felix __\|/_____ ___ ___ __Tschüß___\_6 6_/___/__ \___/__ \___/___\___You can do anything,___ _Felix___\Ä/\ \_\ \_\ \__U___just not everything [EMAIL PROTECTED]o__/ \___/ \___/at the same time! ___ 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
Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
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
Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
On 2002.05.31 02:03 Felix Kühling wrote: On Fri, 31 May 2002 02:30:11 +0200 Felix Kühling [EMAIL PROTECTED] wrote: Hi, 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: [...] 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. I couldn't sleep, so I tried it right away :). The permission problem disappeared after recompiling the entire kernel with gcc-3.0. Sergey, I hope you're familiar with compiling your own kernel ;-). Regards, Felix Great Felix! I bet that you slept much better after too! ;-) José Fonseca ___ 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
Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
On Fri, 2002-05-31 at 14:35, Sergey V. Udaltsov wrote: Great Felix! I bet that you slept much better after too! ;-) But the question is still open - what in DRM interfaces makes them so gcc-dependable? Why gcc3-built module cannot properly interact with gcc2.96-built kernel? Kernel modules may rely on kernel internal data structures, which may be laid out differently in memory by different compilers. I don't think you can expect this to work, but if I'm wrong I'm sure Linus will LART me. :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ 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
Re: [Dri-devel] Mach64: atimisc_drv.o relies on drm
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! Symbol drmMach64EngineReset from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRIUnlock from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRIUnlock from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRIUnlock from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! 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! Symbol drmMach64EngineReset from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRILock from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRIUnlock from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpAcquire from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpGetMode from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpVendorId from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpDeviceId from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpEnable from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpAlloc from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpBind from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAddMap from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmMap from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAddMap from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmMap from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpFree from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpRelease from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpRelease from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAgpRelease from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRIQueryVersion from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRICreateInfoRec from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRIScreenInit from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmGetVersion from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmFreeVersion from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmFreeVersion from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAddMap 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! Symbol DRIDestroyInfoRec 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! Symbol DRIFinishScreenInit from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmAddBufs from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmMach64InitDMA from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmMapBufs from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol DRIGetSAREAPrivate from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmUnmapBufs from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmMach64CleanupDMA from module /usr/X11R6-mach64004/lib/modules/drivers/atimisc_drv.o is unresolved! Symbol drmUnmap from module
