>
> As for the glxgears thing, I got some output from it when I ran it with gdb
> from an ssh session:
>
> glxgears: vblank.c:338: driWaitForVBlank: Assertion `interval != (unsigned)-1'
> failed.
try updating from CVS both trees, I fixed this I just can't remember which
tree it went into :-) I th
On Sat, 14 Feb 2004 13:27:03 -0800
James Jones <[EMAIL PROTECTED]> wrote:
> Yeah, got a couple things here.
>
> First, the dmesg. the dma test is failing. It worked fine on the old branch.
> This of course happens when starting X. Here's a dmesg clip:
[snip]
>
> As for the glxgears thing, I
Yeah, got a couple things here.
First, the dmesg. the dma test is failing. It worked fine on the old branch.
This of course happens when starting X. Here's a dmesg clip:
--
agpgart: Putting AGP V2 device at :00:00.0 into 2x mode
agpgart: Putting AGP V2 device a
>
> -X starts up fine now, window manager comes up, etc.
> -xvinfo reports xv working, playing mpeg with mplayer confirms this.
> -glxinfo reports correct info
> -glxgears locks up. Rest of X is locked, but mouse can be moved around. I
> can ssh in, but can't seem to kill the X server. A reboot
Dave,
Here's a test report:
-X starts up fine now, window manager comes up, etc.
-xvinfo reports xv working, playing mpeg with mplayer confirms this.
-glxinfo reports correct info
-glxgears locks up. Rest of X is locked, but mouse can be moved around. I
can ssh in, but can't seem to kill the X
> When I updated and using the XFree86 from the snapshot directory, I was
> missing an I2C symbol, the ati driver in DRI CVS seems to need a newer
> version of libi2c.a, mine was from Fedora Core 1...
>
> The 2d driver builds now but 3d seems to crap it out .. it'll be a day or
> two until I figure
Okay I wasn't as complete as I thought, the Mesa and the DRM I was using
were from the branch but I never updated my 2d driver, it was still the
old branch... so then I noticed something else which might cause problems
with the snapshots
When I updated and using the XFree86 from the snapshot
