On 02/07/10 13:24, Kristian Høgsberg wrote:
On Sun, Feb 7, 2010 at 1:32 AM, Catalin Patuleac...@vv.carleton.ca wrote:
Hello,
I am interested in getting DRI working on my ATI Rage XL card under
2.6.31-14 with mach64_drv 6.8.2 (Xorg 1.6.3 from Ubuntu Karmic koala).
Git says that the
On Sunday 29 November 2009 14:16:13 vehemens wrote:
[snip]
Your missing the point of using a development structure which supports
collobration.
[snip]
The difference is that you are the only one doing the work now.
[snip]
Again, your missing the point of using a development structure
On Sunday 29 November 2009 18:54:31 vehemens wrote:
On Sunday 29 November 2009 14:23:44 Adam K Kirchhoff wrote:
On Sunday 29 November 2009 14:16:13 vehemens wrote:
[snip]
Your missing the point of using a development structure which supports
collobration.
[snip
Markus Amsler
Thu, 10 Apr 2008 18:10:53 -0700
Adam K Kirchhoff wrote:
Before I open up a bug report, I was wondering if anyone wanted to
comment on this problem. I was recently doing some testing of r300 vs.
fgrlx for one of the compiz dev's when I noticed that the reflection
plugin
On Friday 11 April 2008 07:38:31 Markus Amsler wrote:
Adam K Kirchhoff wrote:
Markus Amsler
Thu, 10 Apr 2008 18:10:53 -0700
Adam K Kirchhoff wrote:
Before I open up a bug report, I was wondering if anyone wanted to
comment on this problem. I was recently doing some testing of r300
On Tuesday 26 June 2007 14:14:06 [EMAIL PROTECTED] wrote:
http://bugs.freedesktop.org/show_bug.cgi?id=8056
--- Comment #19 from [EMAIL PROTECTED] 2007-06-26 11:13 PST ---
Patches implementing micro tiling on r300, if someone wants play with them.
FYI,
I just gave these
On Wednesday 20 June 2007 18:07:52 Brian Paul wrote:
Adam K Kirchhoff wrote:
On Wednesday 20 June 2007 13:02:47 Brian Paul wrote:
Eric Anholt wrote:
On Tue, 2007-06-19 at 12:20 -0400, Adam K Kirchhoff wrote:
On Sat, 2007-06-16 at 09:44 -0700, [EMAIL PROTECTED]
wrote:
http
On Wednesday 20 June 2007 13:02:47 Brian Paul wrote:
Eric Anholt wrote:
On Tue, 2007-06-19 at 12:20 -0400, Adam K Kirchhoff wrote:
On Sat, 2007-06-16 at 09:44 -0700, [EMAIL PROTECTED]
wrote:
http://bugs.freedesktop.org/show_bug.cgi?id=11283
--- Comment #4 from [EMAIL
On Sat, 2007-06-16 at 09:44 -0700, [EMAIL PROTECTED]
wrote:
http://bugs.freedesktop.org/show_bug.cgi?id=11283
--- Comment #4 from [EMAIL PROTECTED] 2007-06-16 09:44 PST ---
Finished with git-bisect:
9e8a961dd7d7b717a9fb4ecdea1c1b60ea355efe is first bad commit
commit
FYI,
DRM from git is broken on FreeBSD:
cc -O2 -fno-strict-aliasing -pipe --param large-function-growth=1000
-Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I- -I. -I.. -I. -I@
-I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100
--param large-function-growth=1000
Adam K Kirchhoff wrote:
On Mon, 2007-03-05 at 14:13 -0500, Adam K Kirchhoff wrote:
On Mon, 2007-03-05 at 20:03 +0100, Michel Dänzer wrote:
On Sun, 2007-03-04 at 11:16 -0500, Adam K Kirchhoff wrote:
I've been trying to track down this problem I've been having with the
r300
Michel Dänzer wrote:
On Tue, 2007-03-06 at 04:32 -0500, Adam K Kirchhoff wrote:
commit 09e4df2c65c1bca0d04c6ffd076ea7808e61c4ae causes the lockup.. If
I'm reading the git log properly this is right after the merge from
vbo-0.2. However, commit 47d463e954efcd15d20ab2c96a455aa16ddffdcc
On Mon, 2007-03-05 at 20:03 +0100, Michel Dänzer wrote:
On Sun, 2007-03-04 at 11:16 -0500, Adam K Kirchhoff wrote:
I've been trying to track down this problem I've been having with the
r300 driver and Googleearth. Sometime, since 6.5.2 was released. It's
an odd problem as I've only
On Mon, 2007-03-05 at 14:13 -0500, Adam K Kirchhoff wrote:
On Mon, 2007-03-05 at 20:03 +0100, Michel Dänzer wrote:
On Sun, 2007-03-04 at 11:16 -0500, Adam K Kirchhoff wrote:
I've been trying to track down this problem I've been having with the
r300 driver and Googleearth. Sometime
Sorry, I just realized I sent two e-mails about this problem to
[EMAIL PROTECTED] Not even sure how that address
got into my address book in the first place, or where that mail actually
goes... But, onto my problems:
I've been trying to track down this problem I've been having with the
r300
FYI,
I decided to give ut2004 a spin this morning, for the first time with
the free driver in quite a while. I had heard good things since the VBO
merge... Unfortunately, I very quickly ran into a problem with I loaded
up the Icefields Bombing Run level:
Mesa 6.5.3 implementation
On Wed, 2007-02-14 at 16:39 +0100, Roland Scheidegger wrote:
Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
FYI,
I decided to give ut2004 a spin this morning, for the first time with
the free driver in quite a while. I had heard good things since the VBO
merge... Unfortunately
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
On Mon, 2006-12-04 at 14:42 +0100, Michel Dänzer wrote:
On Sat, 2006-12-02 at 12:14 -0500, Adam K Kirchhoff wrote:
So something occurred to me last night... I've seen these same symptoms
before when trying to get DRI working on FreeBSD a long time ago... On
another machine, if I
On Mon, 2006-12-04 at 15:42 +0100, Michel Dänzer wrote:
On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote:
The log file on FreeBSD doesn't show the same warning as the log file on
linux about the support being experimental.
Hmmm... FreeBSD shows:
(II) RADEON(0): [drm
On Mon, 2006-12-04 at 19:01 +0100, Michel Dänzer wrote:
On Mon, 2006-12-04 at 12:49 -0500, Adam K Kirchhoff wrote:
On Mon, 2006-12-04 at 15:42 +0100, Michel Dänzer wrote:
On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote:
The log file on FreeBSD doesn't show the same
On Mon, 2006-12-04 at 13:17 -0500, Adam K Kirchhoff wrote:
On Mon, 2006-12-04 at 19:01 +0100, Michel Dänzer wrote:
On Mon, 2006-12-04 at 12:49 -0500, Adam K Kirchhoff wrote:
On Mon, 2006-12-04 at 15:42 +0100, Michel Dänzer wrote:
On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote
(but
not in Linux, which didn't have any problem with that particular
situation). I don't have any config options set for GARTSize, but could
something similar be happening now?
Adam
On Fri, 2006-12-01 at 15:16 -0500, Adam K Kirchhoff wrote:
Hello all,
I'm having a problem getting direct rendering
Patrick McFarland wrote:
As such, I'd love to use the R300 driver (and maybe even help development, if
not just testing), but as it stands, on my run of the mill RV350 AP revision
hardware (a Radeon 9600), initialization of X hangs if I enable DRI, but
continues fine if DRI is off (ie, its
Jacek Poplawski wrote:
I tried doom3, while it doesn't work correctly with default renderer,
it is quite playable with arb renderer. And it has much more than 5fps.
Sorry, but not here it doesn't.
I updated my drivers from CVS on August 29th and have just run demo1.
800x600 resolution,
Jacek Poplawski wrote:
Hi,
I removed fglrx from my system yesterday.
I was using it to initialize my Radeon 9800 Pro before (old DRI driver
crashed without that).
Then I installed new drivers, and I tested following applications:
snip
I think that it is safe to say that Radeon 9800 Pro
Jacek Poplawski wrote:
While the r300 driver has, indeed, come a long way, I'm hesitant
to call
it the best OpenGL implementation I've ever seen. As of July, the
r200
driver still out performed the r300 driver at nearly every OpenGL
application and game on my
FYI, Apparently Xi Graphics has kicked off a new marketing campaign
again... This PDF is linked to from their homepage:
ftp://ftp.xig.com/pub/docs/State_of_Accelerated-X.pdf
Adam
-
Using Tomcat but need to do more? Need
Just thought I'd post some updated benchmarks of Doom3. These were all
run with the first timedemo at 640x480, and (for the open source
drivers) with ColorTiling turned on in the xorg.conf file. I'll list
all tests with the open source drivers first:
x700 + r300 (with arb renderer) - 5.5 FPS
Jacek Poplawski wrote:
On 6/18/06, *Adam K Kirchhoff* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:Jacek Poplawski wrote:
It's interesting that both Blender and Neverball work for you. I
tried
them (about a month ago) with the r300 driver from CVS, and was
getting
Jacek Poplawski wrote:
I use 9800 Pro and it works stable under two circumstances:
- start X with fglrx once (I put it in my /etc/rc.d/rc.local)
Unfortunately, that's not an option for users where fglrx won't work :-)
- avoid some applications
Stuff like Blender, Enemy Territory or
Rune Petersen wrote:
Adam K Kirchhoff wrote:
Rune Petersen wrote:
set r_renderer arb
r_renderer arb2 is broken. My guess is that with Mesa 6.5, Doom 3
(demo) defaults to arb unlike with Mesa CVS.
Another thing:
I think we need an up-to-date list of what is working and what
Rune Petersen wrote:
set r_renderer arb
r_renderer arb2 is broken. My guess is that with Mesa 6.5, Doom 3
(demo) defaults to arb unlike with Mesa CVS.
Another thing:
I think we need an up-to-date list of what is working and what is
still missing.
I have a small list for my own
So last night I decided to give the new vertex programs on the r200
driver a shot and to see how doom3 stacked up with the r200 driver vs
the fglrx driver now. With both drivers, I was getting approximately 12
FPS with demo1 (with the r200 renderer, of course).
This morning I decided to give
Rune Petersen wrote:
Adam K Kirchhoff wrote:
So last night I decided to give the new vertex programs on the r200
driver a shot and to see how doom3 stacked up with the r200 driver vs
the fglrx driver now. With both drivers, I was getting approximately
12 FPS with demo1 (with the r200
Rune Petersen wrote:
Adam K Kirchhoff wrote:
Rune Petersen wrote:
Adam K Kirchhoff wrote:
So last night I decided to give the new vertex programs on the r200
driver a shot and to see how doom3 stacked up with the r200 driver vs
the fglrx driver now. With both drivers, I
Brian Paul wrote:
Alan Hourihane wrote:
On Thu, 2006-06-01 at 17:07 +0100, Alan Hourihane wrote:
On Thu, 2006-06-01 at 08:53 -0700, Ian Romanick wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jacek Poplawski wrote:
On 5/30/06, Pedro Maia [EMAIL
Philipp Klaus Krause wrote:
Adam K Kirchhoff wrote:
I was running some test comparing the r200 vs the r300 driver this
morning, and noticed a slight rendering issue with the r200 driver with
reflections in the game neverball.
I suggest you file a bug, so that this problems isn't
I was running some test comparing the r200 vs the r300 driver this
morning, and noticed a slight rendering issue with the r200 driver with
reflections in the game neverball.
http://68.44.156.246/neverball-9200.jpg
As you can see, the reflections for the coins on the two bridges on the
right
FYI,
I downloaded the hwspirit timedemo for quake4 yesterday and decided
to compare the framerate between the fglrx, r200, and xig drivers with
my Radeon 9000:
9000 - xig - 14.7
9000 - fgl - 11.3
9000 - xorg - 16.2
Today I decided to give it a shot with my 9600. The fglrx drivers
Just wanted to point out that freebsd-dri no longer builds on two of my
machines running -CURRENT. It manages to build libGL.so.1, but dies
with Bad fd number when it goes to build the DRI drivers:
[ [EMAIL PROTECTED] - ~/saved/source/Mesa ]: make freebsd-dri
(cd configs rm -f current ln
I had some time yesterday and thought I'd do a quick comparision of the
DRI drivers and fglrx drivers for three different cards I have, and I
thought others on this list might be interested in the results. All
tests were conducted on a dual 2.8 xeon, with a gig of RAM. The cards
are a
Just want to give a heads up that the above combination is broken again:
cc -O2 -fno-strict-aliasing -pipe -Werror -D_KERNEL -DKLD_MODULE
-nostdinc -I- -I. -I.. -I. -I@ -I@/contrib/altq -finline-limit=8000
--param inline-unit-growth=100 --param large-function-growth=1000
-fno-common
I have a radeon mobility U1, with the latest and greatest from Mesa and
drm CVS. Blender launches fine, but as soon as I right click on a light
souce to move it around, the display gets very screwed up, making the
application unusable.
http://68.44.156.246/blender.png
Any ideas before I open
On Wednesday 15 February 2006 14:34, Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
I have a radeon mobility U1, with the latest and greatest from Mesa and
drm CVS. Blender launches fine, but as soon as I right click on a light
souce to move it around, the display gets very screwed up
For the past day or two I've been getting the following error when trying to
compile DRI from Mesa CVS:
gcc -c -I. -I../../../include -I../../../include/GL/internal
-I../../../src/mesa/main -I../../../src/mesa/glapi
-I../../../src/mesa/drivers/dri/common `pkg-config --cflags libdrm`
FYI, this patch works here. Now I have a working current DRI with DRM
1.22.0.
Adam
Hi list!
I am very happy to announce that I got my Radeon X600 working on both
Linux/i386 and FreeBSD/amd64. I needed to apply Benjamin's latest
patches and also the small attached patch for FreeBSD. The
On Thursday 26 January 2006 08:41, Jerome Glisse wrote:
On 1/26/06, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Marbleblast, a game from GarageGames, seems to have an issue with the
r300 driver... The game crashes when it goes to start a new level. It
crashes with:
drmRadeonCmdBuffer
Just thought I'd point out that DRM has stopped compiling on FreeBSD again:
=== radeon (all)
Warning: Object directory not changed from original
/home/adamk/saved/source/drm/bsd-core/radeon
cc -O2 -fno-strict-aliasing -pipe -Werror -D_KERNEL -DKLD_MODULE
-nostdinc -I- -I. -I.. -I. -I@
On Wednesday 25 January 2006 19:01, Aapo Tahkola wrote:
On Wed, 25 Jan 2006 20:29:05 +0100
khaqq [EMAIL PROTECTED] wrote:
On Wed, 25 Jan 2006 11:51:17 +0100
Kristoffer [EMAIL PROTECTED] wrote:
I'm thinking of trying the radeon driver again, but i'm wondering
wether or not it will
Marbleblast, a game from GarageGames, seems to have an issue with the
r300 driver... The game crashes when it goes to start a new level. It
crashes with:
drmRadeonCmdBuffer: -22 (exiting)
drmRadeonCmdBuffer: -22 (exiting)
dmesg shows:
[drm:r300_emit_carefully_checked_packet0] *ERROR*
On Thu, 2006-01-05 at 06:11 -0500, Adam K Kirchhoff wrote:
Anish Mistry wrote:
On Wednesday 04 January 2006 10:05 pm, khaqq wrote:
On Thu, 5 Jan 2006 04:51:31 +
Aapo Tahkola [EMAIL PROTECTED] wrote:
On Wed, 04 Jan 2006 21:07:41 -0400
Jon [EMAIL PROTECTED] wrote
Jerome Glisse wrote:
On 1/7/06, Jerome Glisse [EMAIL PROTECTED] wrote:
On 1/5/06, Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
Have you tried checking what's going on with the card memory map ?
(values of MC_AGP_LOCATION, MC_FB_LOCATION, CONFIG_MEMSIZE,
CONFIG_APER_SIZE, HDP
Benjamin Herrenschmidt wrote:
On Thu, 2006-01-05 at 11:05 +0100, Jerome Glisse wrote:
On 1/5/06, Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
On Thu, 2006-01-05 at 02:30 +0100, Jerome Glisse wrote:
On 1/5/06, Jon [EMAIL PROTECTED] wrote:
I have a ATI AIW Radeon
Alex Deucher wrote:
On 1/6/06, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Benjamin Herrenschmidt wrote:
On Thu, 2006-01-05 at 11:05 +0100, Jerome Glisse wrote:
On 1/5/06, Benjamin Herrenschmidt [EMAIL PROTECTED] wrote:
On Thu, 2006-01-05 at 02:30 +0100, Jerome
Aapo Tahkola wrote:
On Wed, 04 Jan 2006 21:07:41 -0400
Jon [EMAIL PROTECTED] wrote:
I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of freezing
with r300 DRI module. I tried Quake3 (wont get past beginning of opening
game video, locks computer solid) and Xmoto (lasts for a few
Anish Mistry wrote:
On Wednesday 04 January 2006 10:05 pm, khaqq wrote:
On Thu, 5 Jan 2006 04:51:31 +
Aapo Tahkola [EMAIL PROTECTED] wrote:
On Wed, 04 Jan 2006 21:07:41 -0400
Jon [EMAIL PROTECTED] wrote:
I have a ATI AIW Radeon 9800 Pro (r350), I'm getting plenty of
Michel Dänzer wrote:
On Thu, 2006-01-05 at 06:09 -0500, Adam K Kirchhoff wrote:
[...] it might make sense to have the server
automatically disable 3D on those cards unless the users specifies an
option (EnableUnstableDRIon9800Hardware) in their xorg.conf file.
Agreed, except
Felix Kühling wrote:
Am Donnerstag, den 29.12.2005, 20:40 -0500 schrieb Adam K Kirchhoff:
[snip]
What's really bizarre, however, is that if I set hw.dri.0.debug to 1,
glxgears gets roughly 200 FPS, faster than software Mesa, but slower
than it can get (undoubtedly due to the massive
I sent this to the freebsd-current mailing list yesterday, but haven't
heard back from anyone. And, since I'm not sure if this is an AGP issue
or a DRM specific issue, I thought I'd mention it here as well:
When I boot up, the agp driver is loaded properly:
agp0: ATI RS100 AGP bridge on
Adam K Kirchhoff wrote:
I sent this to the freebsd-current mailing list yesterday, but haven't
heard back from anyone. And, since I'm not sure if this is an AGP
issue or a DRM specific issue, I thought I'd mention it here as well:
When I boot up, the agp driver is loaded properly:
agp0
Eric Anholt wrote:
On Mon, 2005-12-26 at 15:49 -0500, Adam K Kirchhoff wrote:
So at some point in the not too distant past, I managed to get current
Mesa/DRI CVS working on my FreeBSD workstation (with an X700Pro). Just
earlier today, though, I did a make buildworld and make installworld
Adam K Kirchhoff wrote:
As of yesterday morning, my HP Laptop, with a Mobility RS100 Radeon,
is running -CURRENT. Unfortunately, I seem to be having problems with
Direct Rendering.
When I boot up, the agp driver is loaded properly:
agp0: ATI RS100 AGP bridge on hostb0
When I launch X
So at some point in the not too distant past, I managed to get current
Mesa/DRI CVS working on my FreeBSD workstation (with an X700Pro). Just
earlier today, though, I did a make buildworld and make installworld
and suddenly Direct Rendering is not working any more. It turns out
that
The DRI snapshots can be used with the Xorg packages in Debian
experimental. I've edited the wiki to reflect this. Hope that's OK!
I've got the r200 snapshot working happily[1].
cheers, Phil
[1] PageFlip seems broken however -- rendering errors with Quake4[2] at
least, which go away when
Roland Scheidegger wrote:
Stephane Marchesin wrote:
Philipp Klaus Krause wrote:
Adam K Kirchhoff schrieb:
I'm sure this confirms what are already known issues with the r300
driver, but felt it'd be worth posting anyway. There's definitely
something bizarre going on with textures
Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
I've narrowed down this problem to something that changed in Mesa
between the 5th of December and the 11th, when I first noticed this
problem. I have a system at work with a 9800. I started up NWN
(after first initializing the card
Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
I've narrowed down this problem to something that changed in Mesa
between the 5th of December and the 11th, when I first noticed this
problem. I have a system at work with a 9800. I started up NWN
(after first initializing the card
FYI,
Just wanted to post a few screenshots of Neverwinter Nights with the
r300 driver vs Neverwinter Nights with the fgl driver. This is with a
Radeon X700, drm 1.20.0, and a Mesa from CVS this weekend.
http://68.44.156.246/NWN-fgl.png
This is a scene with the fglrx driver from
Since yesterday afternoon, starting many (though not all) GL apps
results in:
No ctx-FragmentProgram._Current!!
drmRadeonCmdBuffer: -22 (exiting)
dmesg shows:
[drm] Loading R300 Microcode
[drm:r300_emit_carefully_checked_packet0] *ERROR* Register 4500 failed
check as flag=00
FYI, I'm attaching two very small patches that get the r300 driver
working with my AGP X700 card.
Adam
Index: shared-core/drm_pciids.txt
===
RCS file: /cvs/dri/drm/shared-core/drm_pciids.txt,v
retrieving revision 1.29
diff
Felix Kühling wrote:
Am Samstag, den 12.11.2005, 11:01 -0500 schrieb Adam K Kirchhoff:
So I heard from someone on the transgaming forums that Morrowind is
running just as fast with the DRI drivers as it with the drivers from
ATI on their system. Which surprised me, since it was painfully
So I heard from someone on the transgaming forums that Morrowind is
running just as fast with the DRI drivers as it with the drivers from
ATI on their system. Which surprised me, since it was painfully slow on
my machine. I gave it another shot, but this time setting LIBGL_DEBUG
to
Mattias Nissler wrote:
snip
Any ideas what could be causing those problems? Is quake3 rendering
correctly on x86 at the moment? /snip
Yes, I just played it for a while on Sunday, with the latest and
greatest in CVS at the time.
Adam
FYI, doom3 seems to run with the latest r300 drivers. It's slow, and
there are definite texture problems (lots of flickering), but it doesn't
crash. You can see a screenshot at http://68.44.156.246/doom3.png
It looks washed out because I had to increase the brightness in gimp to
make
Vitaliy A. Matuschenko wrote:
Adam Jackson wrote:
On Wednesday 21 September 2005 06:51, Vitaliy A. Matuschenko wrote:
So i've decided to install libdrm manually. I've downloaded libdrm-1.0.3
but it also didn't want to install at any way.
If you'd tell me how it failed to install
[EMAIL PROTECTED] wrote:
Sergio [EMAIL PROTECTED] dijo:
[EMAIL PROTECTED] a écrit :
I try to build following http://dri.freedesktop.org/wiki/Building. I
succeeded before, but now xc compilation stops with this:
make[5]: *** There is not any rule to build target `grammar_mesa.o'
Vladimir Dergachev wrote:
And so on, through /dev/dri/card254
Mind you, /dev/dri/card0 exists:
[ [EMAIL PROTECTED] - ~ ]: ls -la /dev/dri
total 1
dr-xr-xr-x 2 root wheel 512 Aug 21 18:37 .
dr-xr-xr-x 5 root wheel 512 Dec 31 1969 ..
crw-rw-rw- 1 root wheel0, 162 Aug 21
Jung-uk Kim wrote:
On Monday 22 August 2005 02:49 pm, Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
And so on, through /dev/dri/card254
Mind you, /dev/dri/card0 exists:
[ [EMAIL PROTECTED] - ~ ]: ls -la /dev/dri
total 1
dr-xr-xr-x 2 root wheel 512 Aug 21 18:37 .
dr-xr-xr
Jung-uk Kim wrote:
It seems you built DRM from DRI CVS, right?
Yep. Is that not the correct way to do it these days?
Can you try the following
patch and do the test again?
http://people.freebsd.org/~jkim/fbsd_vs_drm-20050818.diff
That patched solved my problems. I now have DRI
I'm curious if anyone has gotten r300 working on FreeBSD now that the
driver has been merged with Mesa and the DRM cvs tree?
I managed to get Mesa CVS to build on FreeBSD with some help from Adam
Jackson and Daniel Stone on irc today. DRM from the cvs tree compiled
as well. The kernel
Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
Thanks for the tip. I updated to not only the latest Mesa cvs and
drm cvs, but the latest xorg cvs. This is a vast improvement, and
XFCE4
works with DRI enabled. But... glxgears segfaults:
(gdb) run
Starting program: /usr/X11R6/bin
Jerome Glisse wrote:
On 8/8/05, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Jerome,
Thanks for the tip. I updated to not only the latest Mesa cvs and
drm cvs, but the latest xorg cvs. This is a vast improvement, and XFCE4
works with DRI enabled. But... glxgears segfaults:
(gdb) run
Jerome Glisse wrote:
On 8/8/05, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Adam K Kirchhoff wrote:
I have an interesting problem with an HP Pavilion. It's an IGP320M
with a Radeon Mobility. DRI works just fine when using WindowMaker or
gnome. However, when I try to use xfce4
Adam K Kirchhoff wrote:
I have an interesting problem with an HP Pavilion. It's an IGP320M
with a Radeon Mobility. DRI works just fine when using WindowMaker or
gnome. However, when I try to use xfce4 instead, X locks up when the
splash screen would normally be displayed. I can move
I have an interesting problem with an HP Pavilion. It's an IGP320M with
a Radeon Mobility. DRI works just fine when using WindowMaker or
gnome. However, when I try to use xfce4 instead, X locks up when the
splash screen would normally be displayed. I can move the mouse around,
but I
FYI
I've had a chance today to test the r300 driver (using a Radeon
9550) with every 3d game and application I have installed. This
includes UnrealTournament, ut2004, q3a, RTCW, Rune, Tribes2, Orbz,
MarbleBlast (both from GarageGames), neverball, neverputt, NWN, doom3,
blender, ppracer,
Jung-uk Kim wrote:
On Wednesday 22 June 2005 06:55 pm, Adam K Kirchhoff wrote:
At one point in the not-too-distant past, the r300 drm would
compile on FreeBSD 5.4.
After bringing a Radeon 9550 home from work to test out and being
really impressed with how well the driver works (without
At one point in the not-too-distant past, the r300 drm would compile on
FreeBSD 5.4.
After bringing a Radeon 9550 home from work to test out and being really
impressed with how well the driver works (without those pesky 9800
specific lockups), I decided to give it a whirl in FreeBSD.
Vladimir Dergachev wrote:
On Wed, 1 Jun 2005, Adam K Kirchhoff wrote:
Nicolai Haehnle wrote:
What you can do: Please, test the attached
patch.drm-cmdbuf-more-pacifiers, and report if there are any
regressions (I don't believe there are any) and/or if it removes
certain lockups you
Vladimir Dergachev wrote:
Adam,
Great, thank you very much ! No, the system did not need to be actively
swapping in fact this would probably have confused the results. (this is
why I asked for passive apps)
Could you also let me know the following information:
Output of free
At the
Aapo Tahkola wrote:
I did some figuring on the CB_DPATH problem.
After little testing it turns out that the lock up with
progs/demos/isosurf goes away when the pacifier sequences are applied to
clearbuffer.
Im starting to think that this sequence is needed whenever overwriting
certain states
Aapo Tahkola wrote:
Jerome Glisse wrote:
On 6/1/05, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Nicolai Haehnle wrote:
What you can do: Please, test the attached
patch.drm-cmdbuf-more-pacifiers,
and report if there are any regressions (I don't believe there are any
Adam K Kirchhoff wrote:
Aapo Tahkola wrote:
Jerome Glisse wrote:
On 6/1/05, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Nicolai Haehnle wrote:
What you can do: Please, test the attached
patch.drm-cmdbuf-more-pacifiers,
and report if there are any regressions (I don't
Adam K Kirchhoff wrote:
Aapo Tahkola wrote:
Jerome Glisse wrote:
On 6/1/05, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Nicolai Haehnle wrote:
What you can do: Please, test the attached
patch.drm-cmdbuf-more-pacifiers,
and report if there are any regressions (I don't
Nicolai Haehnle wrote:
What you can do: Please, test the attached patch.drm-cmdbuf-more-pacifiers,
and report if there are any regressions (I don't believe there are any)
and/or if it removes certain lockups you are seeing.
Well, it's hard for me to judge this patch :-) I played Q3A for
Jerome Glisse wrote:
On 6/1/05, Adam K Kirchhoff [EMAIL PROTECTED] wrote:
Nicolai Haehnle wrote:
What you can do: Please, test the attached patch.drm-cmdbuf-more-pacifiers,
and report if there are any regressions (I don't believe there are any)
and/or if it removes certain lockups
Adam K Kirchhoff wrote:
Vladimir Dergachev wrote:
Are you doing a cold restart ?
I would help a lot if you could try this with glxgears and/or quake3:
I just gave it a shot with UnrealTournament. I'll try with Q3A in a
little bit
* cold restart
* start one of 3d programs
measure
Nicolai Haehnle wrote:
Hi everybody,
I once again tripped upon an R300 lockup (possibly the same one that
everybody's been talking about) and spent the last one and half days
chasing it down.
It turns out that writing the vertex buffer age to scratch registers (the
ones that are written
Vladimir Dergachev wrote:
Vladimir Dergachev wrote:
In the past I found useful not to turn drm debugging on, but, rather,
insert printk statements in various place in radeon code. This should
also provide more information about what is actually going on.
I can't make any promises. My
1 - 100 of 327 matches
Mail list logo
