On Wed, 17 Mar 2004 01:09:09 +0100 Arkadiusz Miskiewicz <[EMAIL PROTECTED]> wrote:
> Hi, > > I wanted to test new savage dri on my laptop - it has > 01:00.0 VGA compatible controller: S3 Inc. VT8636A [ProSavage KN133] AGP4X VGA > Controller (TwisterK) (rev 01) > > I've used 2.6.4 kernel + XFree86 4.4.0 + binaries from > http://www.freedesktop.org/~dri/snapshots/savage-20040316-linux.i386.tar.bz2 The install.sh in the binary snapshots doesn't work with 2.6 kernels at the momemt. I assume you patched it somehow to install the snapshot or installed the files manually. Please make sure that you didn't miss anything. There was a binary incompatibility that may be causing your problems that was fixed recently. The latest snapshots should include that fix. > > Result from glxinfo was > X Error of failed request: BadValue (integer parameter out of range for operation) > Major opcode of failed request: 128 (XFree86-DRI) > Minor opcode of failed request: 5 () > Value in failed request: 0x3f > Serial number of failed request: 26 > Current serial number in output stream: 26 > name of display: :0.0 > > There also were messages about overlaping mtrr - what can be done about that? I get this too. I believe it happens because the frame buffer driver allocates an MTRR for only part of the video memory. I'm not sure how to fix it. It may have a slight impact on performance but it's not fatal. > > dmesg > agpgart: Detected VIA Twister-K/KT133x/KM133 chipset > agpgart: Maximum main memory to use for agp memory: 409M > agpgart: AGP aperture is 64M @ 0xe0000000 > [drm] Initialized savage 1.0.0 20011023 on minor 0: ProSavage KN133 > mtrr: 0xd0000000,0x2000000 overlaps existing 0xd0000000,0x1000000 > atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). > atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. > atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). > atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. > mtrr: 0xd0000000,0x2000000 overlaps existing 0xd0000000,0x1000000 > mtrr: 0xd0000000,0x2000000 overlaps existing 0xd0000000,0x1000000 > agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. > agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode > agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode > mtrr: base(0xd2000000) is not aligned on a size(0x5000000) boundary > mtrr: base(0xd157e000) is not aligned on a size(0xa80000) boundary > atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). > atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. > atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). > atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. > mtrr: 0xd0000000,0x2000000 overlaps existing 0xd0000000,0x1000000 > mtrr: 0xd0000000,0x2000000 overlaps existing 0xd0000000,0x1000000 > agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. > agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode > agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode > mtrr: base(0xd2000000) is not aligned on a size(0x5000000) boundary > mtrr: base(0xd157e000) is not aligned on a size(0xa80000) boundary > > xfree log [snip] > II) SAVAGE(0): [drm] Could not create dummy context > (II) SAVAGE(0): [drm] Could not create dummy context > (II) SAVAGE(0): [drm] Could not create dummy context > (II) SAVAGE(0): [drm] Could not create dummy context Ian, you mentioned something like this before. What does it mean? Is it related to the driinterface changes? Felix ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
