Re: [Dri-devel] DRI, MGA, kernel 2.4.9 + devfs

[Alan H. <al...@fa...>]

Check the /var/log/XFree86.0.log file again.

It looks like your loading older modules from XFree86 4.0.x rather than
the 4.1.0 ones.

Alan.

On Tue, Sep 18, 2001 at 10:27:05AM -0500, Mark Bainter wrote:
> ====
> Note:  I posted this on the dri-users list about a week or so ago
> and no-one there was able to help me.  I'm still not convinced 
> it's a bug, but I can't figure it out either.  Advice would be
> appreciated.
> 
> Also, everything (DRI, the mga driver, etc) is built into my kernel.
> ====
> 
> Ok, I think I screwed something up here along the way.  I had a working
> setup here but then I upgraded my glibc, and then (once that was working
> for sure) my kernel.  Now it doesn't work.  Obv, something I changed 
> caused the setup to break.
> 
> Relevant Data:
> Kernel 2.4.9, straight.  The only patches are for LVM. devfs enabled
> XFree86 4.1.0 (upgraded from 4.0.3 today trying to fix this)
> glut 3.7
> 
> Ok.  So I start X, and I get this in my log:
> (==) MGA(0): Write-combining range (0xea000000,0x1000000)
> (--) MGA(0): 16 DWORD fifo
> (II) MGA(0): [drm] Sarea 2176+624: 2800
> (0): [drm] created "mga" driver at busid "PCI:1:0:0"
> (0): [drm] added 4096 byte SAREA at 0xcaab3000
> (0): [drm] mapped SAREA 0xcaab3000 to 0x4001c000
> (0): [drm] framebuffer handle = 0xea000000
> (0): [drm] added 1 reserved context for kernel
> (EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 3.0.2, expected
> 1.0.x).  Disabling DRI.
> (0): [drm] failed to remove DRM signal handler
> (0): failed to destroy server context
> (0): [drm] removed 1 reserved context for kernel
> (0): [drm] unmapping 4096 bytes of SAREA 0xcaab3000 at 0x4001c000
> (II) MGA(0): Using 5529 lines for offscreen memory.
> (II) MGA(0): Using XFree86 Acceleration Architecture (XAA)
> 
> [snip]
> 
> (II) MGA(0): direct rendering disabled
> 
> 
> And glxinfo says: 
> % glxinfo                            %(11:26PM)
> display: :0.0  screen:0
> direct rendering: No
> 
> And DRIsetup says:
> % ./DRIsetup-linux-i386
> Direct Rendering Infrastructure testing program
> 
> Checking your system.......
> 
> Your config file is /etc/X11/XF86Config
> Your module path is /usr/X11R6/lib/modules
> You are running in GLX Indirect Rendering Mode
> The kernel module has not been loaded
> 
> (note that I build it into the kernel.  I don't load it as a module.)
> 
> dev has the files:
> 
> % ls -l /dev/misc
> total 0
> crw-rw-rw-   1 root     root      10, 175 Dec 31  1969 agpgart
> ...
> 
> % ls -l /dev/dri
> total 0
> crw-rw-rw-   1 root     root     226,   0 Sep  9 09:03 card0
> 
> 
> If anyone can clue me in as to where I'm fouling this up I'd
> appreciate it.  I looked through recent archives and through
> some google searches but came up with nada.  
> 
> ====
> This is not entirely true I guess.  There were some older hits
> on the devel list regarding devfs, but they were in relation to
> the possibility of devfs not getting into the kernel around the 
> time of 2.3.99.  Obv, it /is/ in the kernel at this point...I
> assume you have support for it in dri?
> 
> Also, I pulled glxgears in case it could provide me with more
> information, it dies with:
> ./glxgears: error in loading shared libraries: /opt/glut/lib/libglut.so.3: undefined symbol: XmuLookupStandardColormap
> ====
> 
> _______________________________________________
> Dri-devel mailing list
> Dri...@li...
> https://lists.sourceforge.net/lists/listinfo/dri-devel