Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Dec 2006 10:12:19 -0500
From:      Adam K Kirchhoff <adamk@voicenet.com>
To:        dri-devel@lists.sourceforge.net, freebsd-x11@FreeBSD.org
Subject:   Re: DRI on FreeBSD with a PCIe X800
Message-ID:  <45840CD3.50007@voicenet.com>
In-Reply-To: <1165319395.2762.2.camel@memory.visualtech.com>
References:  <1165004214.4122.10.camel@sorrow.ashke.com>	<1165079670.2034.0.camel@sorrow.ashke.com>	<1165239746.4376.310.camel@thor.sulgenrain.local>	<1165242369.1243.8.camel@sorrow.ashke.com>	<1165243320.4376.334.camel@thor.sulgenrain.local>	<1165254544.47336.7.camel@scroll.ashke.com>	<1165255291.4376.375.camel@thor.sulgenrain.local>	<1165256253.47336.11.camel@scroll.ashke.com>	<1165268816.30310.3.camel@scroll.ashke.com> <1165319395.2762.2.camel@memory.visualtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help

So I thought I might try and debug this problem further...

I was looking at the various options in the radeon man page and came 
across the BusType option.  I had tried both leaving that option out, 
and setting the option to "PCIE".  This morning, I decided to try 
setting it to "PCI" though, according to the man page, "PCIE" simply 
falls back to PCI at the present time, so I figured it wouldn't make a 
difference...  Except that it does make a difference.  If I set the 
BusType to "PCI" dmesg shows:

info: [drm] Initialized radeon 1.25.0 20060524
info: [drm] Setting GART location based on new memory map
error: [drm:pid1311:radeon_do_init_cp] *ERROR* Cannot use PCI Express 
without GART in FB memory

The only thing different that shows up in the Xorg log file is:

(WW) RADEON(0): Direct rendering disabled

This is after all the usual DRI setup including the opening of the 
/dev/dri/card0 device.

I'm not sure if this is at all related to the problem I'm seeing when I 
use BusType "PCIE" and get the screen corruption...  However, at the 
very least it shows that BusType "PCIE" does not, in fact, fall back to 
"PCI" and something is being setup differently.

If anyone wants to look at the full Xorg from the "PCI" session, it's 
available at:

http://www.visualtech.com/Xorg.0.log.PCI.txt.gz

Dmesg:

http://www.visualtech.com/dmesg.txt.gz

If anyone has any tips or pointers on debugging either of these problems 
further, I'm all ears :-)

Adam

Adam K Kirchhoff wrote:
> For anyone interested in following this, I've opened up a problem
> report:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=106370
>
> Adam
>
>   
>> Hello all,
>>
>>     I'm having a problem getting direct rendering working on one of
>> my 
>> workstations.  I'm running -CURRENT from November 17th with Xorg 
>> installed from the modular Xorg ports tree yesterday (though I first 
>> noticed this a couple weeks back when I built modular Xorg using
>> jhbuild):
>>
>> [ adamk@sorrow - ~ ]: Xorg -version
>>
>> X Window System Version 7.1.1
>> Release Date: 12 May 2006
>> X Protocol Version 11, Revision 0, Release 7.1.1
>> Build Operating System: FreeBSD 7.0-CURRENT i386
>> Current Operating System: FreeBSD sorrow.ashke.com 7.0-CURRENT
>> FreeBSD 
>> 7.0-CURRENT #7: Tue Nov 14 08:33:41 EST 2006     
>> root@sorrow.ashke.com:/usr/obj/usr/src/sys/GENERIC i386
>> Build Date: 28 November 2006
>>         Before reporting problems, check http://wiki.x.org
>>         to make sure that you have the latest version.
>> Module Loader present
>>
>> If I boot up with DRI enabled in the config file, the server starts,
>> but 
>> the very top of the screen shows some visual corruption. 
>>
>> http://www.visualtech.com/screenshot.png
>>
>> I dropped the resolution of the image from 2304x864 to 1600x800, but
>> you 
>> can still make out the corruption.  What's particularly odd, though,
>> is 
>> that the root window is never drawn.  The background you see is
>> actually 
>> the background from my previous X session (when I had DRI disabled), 
>> using windowmaker.  This time I launched X and had fvwm2 in
>> my .xinitrc 
>> file (you can see the outline of the fvwm pager in the screenshot, 
>> though that never finished drawing, either).
>>
>> After that nothing else gets drawn.  I can move the mouse pointer,
>> but 
>> that's about it.  I can safely kill X and restart it, but the same
>> thing 
>> happens unless I disable DRI.
>>
>> In comparison, I have another workstation with an AGP x700.  -CURRENT 
>> from the same date, and modular Xorg from the ports tree from
>> yesterday, 
>> too.  It works just fine (start up fine, and the mesa demos run with 
>> acceleration). 
>>
>> You can find the Xorg log file from the PCIe system at 
>> http://www.visualtech.com/Xorg.0.log.gz
>>
>> Any ideas?  Thanks!
>>
>> Adam
>>
>>     
>
> _______________________________________________
> freebsd-x11@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org"
>
>   




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45840CD3.50007>