On Sat, 2004-01-10 at 11:30, Michel Dnzer wrote:
On Thu, 2004-01-08 at 00:40, Stephen Waters wrote:
System:
MSI K8T Master2-FAR
Dual Opteron
Radeon VE
Debian 'sid' (32-bit Xfree86)
Kernel 2.6.1-rc2-bk1
Have you tried the DRI snapshot packages described in
I'm attaching Xfree86 logs for 2.6.1-bk1-amd64 and Debian sid's 32-bit
2.6.0-k7-smp.
I still get the segfaults with amd64, but I haven't managed an strace.
Stupid forking keeps kill my strace! :)
-s
XFree86.0.log_2.6.0-1-k7-smp-DEBIAN.bz2
Description: application/bzip
Am Sonntag, 11. Januar 2004 23:44 schrieb Alan Cox:
On Sul, 2004-01-11 at 20:43, Jesse Merriman wrote:
Alex Deucher wrote:
hmmm... if both agpgart and savage are loaded before X starts, I'm not
sure what your problem would be. what does your kernel log or dmesg
say when you load the
On Mon, 2004-01-12 at 05:53, Stephen Waters wrote:
On Sat, 2004-01-10 at 11:30, Michel Dnzer wrote:
On Thu, 2004-01-08 at 00:40, Stephen Waters wrote:
What stability problem? Note that the getparam ioctl is only used by the
3D driver.
It crashed if you did much of anything. :)
Hmmm, I don't remember how to do this and I can't seem to find the CVS
command for setting permissions. Anyone?
-Brian
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System
On Mon, 12 Jan 2004 07:54:35 -0700
Brian Paul [EMAIL PROTECTED] wrote:
Hmmm, I don't remember how to do this and I can't seem to find the CVS
command for setting permissions. Anyone?
-Brian
IIRC the only way is to set the permissions of the RCS file directly in
the repository. Meta data
Keith Whitwell wrote:
Michel Dnzer wrote:
On Tue, 2004-01-06 at 11:50, Keith Whitwell wrote:
I haven't looked at them, but these sound like problems arising from
the fact that size-3 color arrays can now make it through to the
driver for incorporation into vertices.
The easiest way to deal
Finally some progress on this front! :)
I tracked down the lighting problems in the xscreensaver queens hack to
attenuation being broken. I noticed that the R200 DDK reference driver
does much more to handle it, in fact our driver doesn't seem to enable
it at all!
Andrew Morton wrote:
Andi Kleen [EMAIL PROTECTED] wrote:
I know what happened. 2.6.1-rc2-mm1 added the `-msoft-float' compiler
option. So what used to be inline 387 instructions became fp library
calls.
So it's not an _urgent_ problem, and I can probably just drop the
-msoft-float patch from
ok, changed the code and recompiled the source.
Now the drm module recognizes the card and inits it.
/dev/dri/card0 is present even though not accessable by any user besides root.
(flags are ok and i also have a proper DRI Section in config...)
glxinfo reports dri is enabled.
no gl stuff works.
--- Marco Strack [EMAIL PROTECTED] wrote:
ok, changed the code and recompiled the source.
Now the drm module recognizes the card and inits it.
/dev/dri/card0 is present even though not accessable by any user
besides root.
(flags are ok and i also have a proper DRI Section in config...)
This is just a friendly reminder that the weekly dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or
4:00PM EST or 1:00PM PST, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous
José Fonseca wrote:
Jan,
I'm a little out of the loop in the DRI scene as of lately as I'm quite
busy with my PhD (I'm still trying to catch the DRI mailing lists posts
sent during the christmas vacations).
I don't recall hearing any success using mach64 with kernel 2.6, and I
don't know exactly
Michel Dnzer wrote:
Finally some progress on this front! :)
I tracked down the lighting problems in the xscreensaver queens hack
to attenuation being broken. I noticed that the R200 DDK reference
driver does much more to handle it, in fact our driver doesn't seem
to enable it at all!
Stephen Waters wrote:
I'm attaching Xfree86 logs for 2.6.1-bk1-amd64 and Debian sid's 32-bit
2.6.0-k7-smp.
I still get the segfaults with amd64, but I haven't managed an strace.
Stupid forking keeps kill my strace! :)
The (EE) line in XFree86.0.log_2.6.1-bk1.amd64 indicates that DRM
On Mon, 2004-01-12 at 22:00, Roland Scheidegger wrote:
Michel Dnzer wrote:
I'm curious if this helps with NWN. There are still minor problems,
e.g. in the xscreensaver endgame hack, but those might be related to
colour material (known to horribly break trackballs, e.g.).
Yes! This did
On Mon, 2004-01-12 at 20:36, Xavier Hienne wrote:
Stephen Waters wrote:
I'm attaching Xfree86 logs for 2.6.1-bk1-amd64 and Debian sid's 32-bit
2.6.0-k7-smp.
I still get the segfaults with amd64, but I haven't managed an strace.
Stupid forking keeps kill my strace! :)
What forking,
Michel Dnzer wrote:
Some minor lighting problmes still remain (I spotted 3 which might be
related though):
- selected doorways should be half-transparent, blue. Instead they are
anything from almost black to grey (depending on map)
- If the main character is selected, it should shine. There is
On Mon, Jan 12, 2004 at 11:32:37PM +0100, Michel Dänzer wrote:
On Mon, 2004-01-12 at 20:36, Xavier Hienne wrote:
PS: Michel, since you're involve in DRM development, i'd like to bring
to your attention that two email addresses (given in several radeon drm
files) are obsolete : according
On Tue, 2004-01-13 at 01:01, Stephen Waters wrote:
On Mon, 2004-01-12 at 16:32, Michel Dnzer wrote:
On Mon, 2004-01-12 at 20:36, Xavier Hienne wrote:
Stephen Waters wrote:
I'm attaching Xfree86 logs for 2.6.1-bk1-amd64 and Debian sid's 32-bit
2.6.0-k7-smp.
I still get the
For the moment, and until x86_64 DRM modules support 32 bit ioctls, you
have two choices: either test the amd64 version of XFree86 or stay with
the 32 bit version without DRI.
well, the 32-bit version minus DRI is still flaky on AMD64. It's not
really usable as it crashes pretty easily. I
On Mon, 2004-01-12 at 16:32, Michel Dnzer wrote:
On Mon, 2004-01-12 at 20:36, Xavier Hienne wrote:
Stephen Waters wrote:
I'm attaching Xfree86 logs for 2.6.1-bk1-amd64 and Debian sid's 32-bit
2.6.0-k7-smp.
I still get the segfaults with amd64, but I haven't managed an strace.
I just fixed 3D at 32 bpp on savage4 and commited the changes. It
ended up being a define with the wrong bits set. I get between 280 and
300 fps in glxgears on savage4 at 32 bpp and around 600 at 16 bpp.
textures still aren't quite right on savage4. I suspect textures need
to be setup slightly
23 matches
Mail list logo
