Problems with dri/drm using Radeon 7000 VE in -stable

[Eric Anholt]

On Wed, 2003-04-23 at 12:01, Anders Nordby wrote:
> Hi,
> 
> I tried applying
> http://people.freebsd.org/~anholt/dri/files/drm-stable-20030411.diff to
> stable from today (using device radeondrm and options DRM_LINUX).
> Kernel reports drm seems to be there:
> 
> drm0: <ATI Radeon QY RV100 VE> port 0x9000-0x90ff mem
> 0xed000000-0xed00ffff,0xe$
> info: [drm] Initialized radeon 1.8.0 20020828 on minor 0
> 
> Now, when I try to start XFree86 everything looks fine at first:
> 
> root at noname:~# startx
> Using authority file /root/.Xauthority
> Writing authority file /root/.Xauthority
> Using authority file /root/.Xauthority
> Writing authority file /root/.Xauthority
> 
> 
> XFree86 Version 4.3.0
> Release Date: 27 February 2003
> X Protocol Version 11, Revision 0, Release 6.6
> Build Operating System: FreeBSD 4.8 i386 [ELF] 
> Build Date: 23 April 2003
>         Before reporting problems, check http://www.XFree86.Org/
>         to make sure that you have the latest version.
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
>          (++) from command line, (!!) notice, (II) informational,
>          (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/XFree86.0.log", Time: Wed Apr 23 20:36:28 2003
> (==) Using config file: "/etc/X11/XF86Config"
> 
> But I get this in /var/log/messages:
> 
> Apr 23 20:36:29 noname /kernel: error: [drm:radeon_unlock] *ERROR*
> Process 338 using kernel context 0

That's interesting.  I thought those messages were dead.  I assume you
get that every time you start X?

> And glxinfo reports that I have no direct rendering (output:
> http://anders.fix.no/test/glxinfo.txt). :(

Could you do it again with LIBGL_DEBUG=verbose set?  Also, could you
send the XFree86.0.log.

-- 
Eric Anholt                                eta at lclark.edu          
http://people.freebsd.org/~anholt/         anholt at FreeBSD.org