ajax wrote:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Major opcode of failed request: 144 (XFree86-DRI)
Minor opcode of failed request: 5 ()
Value in failed request: 0x1e2
Serial number of failed request: 30
Current serial number in outp
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=314
[EMAIL PROTECTED] changed:
What|Removed |Added
--
I've moved the i810 driver to the new interface also..
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person
---
This SF.Net email is sponsored by:
> > anything after that did not have working direct rendering. But since the
> > snaps are generated from the head... I've seen this error posted here
> > before but I haven't seen a resolution, maybe I missed it.
>
> Ian, does this look at all like it could be related to your libGL, etc.
> chang
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> On the Savage IX it freezes now, when the 3D window gets too close to
> the bottom of the screen. There is an extra allocation of 128kb at
> the
> end of the frame buffer that is not included in RamNeedeFor3D. It
> doesn't seem to be used though.
>
>
--- Mental Patient <[EMAIL PROTECTED]> wrote:
> Hello. I'm trying to determine a workaround/fix for a problem I'm
> having
> with my laptop ( an ibm thinkpad t22 ).
>
> Whenever the laptop comes out of suspend, any DRI app (game,
> screensaver, etc) causes the screen to hang. If I happen to be
Hello. I'm trying to determine a workaround/fix for a problem I'm having
with my laptop ( an ibm thinkpad t22 ).
Whenever the laptop comes out of suspend, any DRI app (game,
screensaver, etc) causes the screen to hang. If I happen to be on the
network, I can ssh in and look around. But killing/
I've checked in the changes for the mach64 to use the new interface, I
haven't turned it on as I had to change some stuff I'm unsure off...
I've had to set
modes->drawableType = GLX_WINDOW_BIT | GLX_PIXMAP_BIT;
the r200 just had the GLX_WINDOW_BIT ..
Apart from that, 24-bit needs looking at..
On the Savage IX it freezes now, when the 3D window gets too close to
the bottom of the screen. There is an extra allocation of 128kb at the
end of the frame buffer that is not included in RamNeedeFor3D. It
doesn't seem to be used though.
Also the computation of the HW cursor location is off by on