On Fri, Oct 06, 2000 at 11:59:28AM -0600, Joshua Shagam wrote: > Did you later see 'DMA initialization failed?' That would be the
No. Here are the DMA messages I got: (II) MGA(0): [drm] Registers = 0xe4000000 [drm] drmAgpEnabled succeeded (II) MGA(0): WARP Microcode Loaded (II) MGA(0): [drm] calced backoffset: 0x22f000 (II) MGA(0): [drm] added 31 65536 byte DMA buffers (II) MGA(0): [drm] Mga Dma Initialization start (II) MGA(0): [drm] Mga Dma Initialization done (II) MGA(0): [drm] Initialized Dma Engine (II) MGA(0): [drm] dma control initialized, using IRQ 11 (II) MGA(0): visual configs initialized (II) MGA(0): Using 128 lines for offscreen memory. (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) This issue is mostly moot anyway. My main point in trying XFree86 4.0.x with the G200 was to smooth the transition when I move my hard disks to my new system which has a GeForce2/MX. > What I do is I use the libGL from xlibmesa3 and the libGLU compiled from > Mesa's sources (which I already have on-hand because of formerly using > Utah-GLX). I just copied libGLU from mesag3 to /usr/local/lib. On Fri, Oct 06, 2000 at 01:02:12PM -0500, Branden Robinson wrote: > The patches you're talking about aren't really Debian-specific: Debian-specifici was probably a poor choice of words. My intent was that the change was not in the plain 4.0.1 upstream version. > Please review my mini-FAQ, last posted to this list on Oct 1. Sorry about that. I read your mini-FAQ when it was sent, but I didn't understand the issue and I also didn't think I was using anything that needed libGLU either so I didn't worry about it. Anyway, have you considered using a dpkg-diversion? xlibmesa3 could divert any existing libGL out of the way but leave libGLU in place. David -- David Engel [EMAIL PROTECTED]
