Hello,
I have problems with the latest mach64 branch from dri-cvs. After a
successful view of an .avi clip next time the card memory does not
seem to be available, i.e. the card is left in a bad state? The only
way to rerun the application is to exit X and restart.
The example given below is
Dieter Nützel wrote:
1. start X or system start (init 5)
2. rcxdm stop
3. rrmod radeon
4. restart X (rcxdm start)
What happens:
* Screen corruption in several upper lines (the KDE panel)
* a copy of the graphical screen on console 1, 2, 3, etc. but without mouse or
anything else but the
Hello!
just tried it out with current trunk (where you just
committed this patch), but unfortunately it didnt help.
just got a xserver freeze, and after a restarting
of the xserver I tried it and got another error:
application died with segfault or with drmRadeonCmdBuffer: -22
Xlib: unexpected
Am Dienstag, 26. November 2002 10:03 schrieb Keith Whitwell:
Dieter Nützel wrote:
1. start X or system start (init 5)
2. rcxdm stop
3. rrmod radeon
4. restart X (rcxdm start)
What happens:
* Screen corruption in several upper lines (the KDE panel)
* a copy of the graphical screen
Hi.
Well, I have a Voodoo3 3000 PCI now thanks to Martin Spott, and am
preparing to remove the GLIDE dependencies from the driver (thats why I
have the card).
So, where to start? I have the card installed and working (2d), but
havent quite gotten things working - you see, I have a radeon 9000 as
On Tue, 2002-11-26 at 16:59, Ian Molton wrote:
the /only/ way I have gotten things to work at all without crashing
(solid!) is to run two completely seperate X servers. this works, but
only one display will work at a time - switching between them turns the
other one off (even if it just left
--- Alan Cox [EMAIL PROTECTED] wrote:
The Voodoo3 needs to be your primary display or it
doesnt work dual
head. My 4500 works dual head if its primary
I have a similar problem when using a PCI Rage128 with
any AGP card.
When booting the system BIOS executes the primary
video card's BIOS
Hello!
I have to double check it, just doing a make World of cvs-trunk...
didnt help, the bug is here.
for now I tried 2 times:
1st: xmms died with segfault:
Error: Radeon timed out... exiting
Xlib: unexpected async reply (sequence 0x2ba0)!
Segmentation fault
log shows:
Nov 26 19:45:51
Hi,
clipping of lines at the edges of the viewing volume doesn't seem to
work. The problem occurs both with RADEON_TCL_FORCE_DISABLE and with
LIBGL_ALWAYS_INDIRECT. If I use a glOrtho (-1.0, 1.0, -1.0, 1.0, -1.0,
1.0) projection this works:
glBegin(GL_LINES);
glColor3f(1.0, 0.0, 0.0);
On Tue, 26 Nov 2002 09:52:31 -0800 (PST)
Jon Smirl [EMAIL PROTECTED] wrote:
Would PCI cards work right as secondary displays if
the init code in the video BIOS was executed by X when
the driver gets initialized? Or is this a more
complicated problem having to do with plug and play
OSs and
Have you tried a lower resolution? If it's some sort of memory leak, I'd
expect that you'd run into it eventually even at a lower resolution. If
it doesn't happen at lower resolutions, maybe you really just don't have
enough offscreen memory at 1280x1024. Also, did you run any GL apps
before
Felix Kühling wrote:
Hi,
clipping of lines at the edges of the viewing volume doesn't seem to
work. The problem occurs both with RADEON_TCL_FORCE_DISABLE and with
LIBGL_ALWAYS_INDIRECT. If I use a glOrtho (-1.0, 1.0, -1.0, 1.0, -1.0,
1.0) projection this works:
glBegin(GL_LINES);
I recently e-mailed [EMAIL PROTECTED] about this, I am aware that DRI is
mostly a Linux thing.
But this is related to the ATI Radeon (R100 Core) drivers..
Attached is a core dump (the kernel panic'd on exit of XFree86 4.2.1)
And a copy of the dmesg.out showing you my system statistics...
If
On Mon, 2002-11-25 at 04:39, Eric Anholt wrote:
On Sun, 2002-11-24 at 17:42, Michel Dänzer wrote:
it locks up solid when I request a signal to be delivered. Now I'd very
much like to get this into 4.3.0, so I'd appreciate someone pointing
out the stupid mistake(s) I'm probably making.
Gentlemen: I'm having considerable difficulty with my current kernel compile.
gcc exists with code 1 every time on i810_dma.c.
I was hoping someone could check and make sure that this is compatible with gcc 3.2.
If this isn't the appropriate place for something like this, please direct me to
Title: (±¤°í)¡Ú¹«Á¡Æ÷,¼ÒÀÚº» â¾÷ÀÇ ±âȸ¸¦ ÀâÀ¸¼¼¿ä!¡Ú
:: ¿¬¶ôó ¾È³» ::
ÁÖ¼Ò : ¼¿ïƯº°½Ã ¼Ãʱ¸ ¼ÃÊ2µ¿ 1337-8 º¸Åëºôµù
405È£´ã´ç :
Is anyone else experiencing unresolved symbols from GLcore from CVS?
It seems that it can't resolve fabsf and xf86strncat (or some variant of).
I unfortunately trashed my logs when I reverted back to my previous build
of XFree86. I will try again today sometime to see if I can make it go
System:
dual Athlon MP 1900+
MSI K7D Master-L, AMD 768MPX
1 GB DDR SDRAM 266 CL
HIGHMEM
Radeon 8500 QL
UT and Q3A working better than ever.
VTK
TaskParallelism crash as always
/home/nuetzel /opt/VTK/V4.0/VTK/bin/TaskParallelism
TaskParallelism: r200_vtxfmt.c:926: r200FlushVertices: Assertion
Am Mittwoch, 27. November 2002 08:27 schrieb D. Hageman:
Is anyone else experiencing unresolved symbols from GLcore from CVS?
It seems that it can't resolve fabsf and xf86strncat (or some variant of).
This should be fixed for some days by Brian.
I unfortunately trashed my logs when I
19 matches
Mail list logo
