--- cunha17 <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm experiencing some problem with my
> Savage2000(Viper II) card and DRI.
> Just for the records, I followed all
> recomendation I could find in and out
> of this list.
>
> First of all I recompiled my
> kernel(vanilla 2.4.24, since
> fedora/
I have found something disterbing about DRI and was
hoping you would be able to give a solution.
It turns out, through recent QuakeForge changes,
the DRI is faster in multipass rendering than with multitexture (mtex)
rendering. The same method, and with no alteration to the code,
with nVid
On Sun, 2004-02-15 at 00:45, Vladimir Dergachev wrote:
>
> Code that handles trasferred apertures - this code looks like it adds a
> constant value (aperture location in PCI address space) to some values,
> but not others.
>
> You need to ask DRM driver to transfer aperture to the same position
>
mtrr: 0xe000,0x400 overlaps existing 0xe000,0x100
request_module: failed /sbin/modprobe -- char-major-226-0. error = 256
Do I something missing in /etc/modprobe.conf?
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected AMD 760MP chipset
agpgart: Maximum main memory to
Hi Cristiano,
short answer to a long mail: The Savage driver does not support
Savage2000 chips at the moment. We have no hardware documentation nor a
reference driver implementation. Unless this changes it's unlikely that
Savage2000 support will be available any time soon. :-/
At the moment the d
# lspci -n
00:00.0 Class 0600: 8086:1130 (rev 02)
00:01.0 Class 0604: 8086:1131 (rev 02)
00:1e.0 Class 0604: 8086:244e (rev 02)
00:1f.0 Class 0601: 8086:2440 (rev 02)
00:1f.1 Class 0101: 8086:244b (rev 02)
00:1f.2 Class 0c03: 8086:2442 (rev 02)
00:1f.3 Class 0c05: 8086:2443 (rev 02)
00:1f.4 Class 0
> UT2004 was to new for me...;-)
> Should I download it, now or should I wait some hours after
> your fix is in?
We have no plans to patch the UT2004 demo at this point so you shouldn't
wait. I was merely mentioning that if we do, it's going to be fixed and the
fix is also going to be in the reta
> >
> > 2. *_video.c files - these are heavily modified. Take care of atixv.c -
> > Marc Aurele merged part of GATOS code into XFree86
>
> Yes, I noticed that... these files were *FULL* of conflicts against the
> current DRI CVS... to the extent that I'm worried about being able to
> untangle
Hi all,
I'm experiencing some problem with my
Savage2000(Viper II) card and DRI.
Just for the records, I followed all
recomendation I could find in and out
of this list.
First of all I recompiled my
kernel(vanilla 2.4.24, since
fedora/redhat kernel-source has some
incompatibilities) without DRM,
Am Samstag, 14. Februar 2004 23:22 schrieb Daniel Vogel:
> > With or without S3TC?
>
> Without S3TC. I checked in a fix so the retail version and any subsequent
> patches to the demo version will have the fix.
UT2004 was to new for me...;-)
Should I download it, now or should I wait some hours aft
Am Samstag, 14. Februar 2004 23:38 schrieb Daniel Kasak:
> Jacek Popławski wrote:
> >On Sat, Feb 14, 2004 at 07:38:58PM +1100, Daniel Kasak wrote:
> >>Just downloaded the UT2004 demo, and tried it out under
> >> XFree86-4.3.99.902. I'm pleasantly surprised.
> >>It runs quite nicely,
> >
> >What abo
On Sat, 14 Feb 2004 12:45:45 -0300
Rafael Maximo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> First i would like to say that Alex and Felix are doing a great
> job with savage driver and every day it's getting better.
>
> I found some problems here with my savage4, now the textures ar
Jacek Popławski wrote:
On Sat, Feb 14, 2004 at 07:38:58PM +1100, Daniel Kasak wrote:
Just downloaded the UT2004 demo, and tried it out under XFree86-4.3.99.902.
I'm pleasantly surprised.
It runs quite nicely,
What about speed? On my R200 (Athlon 1800 XP, low settings) it is slow like
hell
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
FWIW, just checked in a fix so any demo patches and the retail version will
have proper menus if texture compression isn't supported. You can use the
software renderer to change your settings in the mean time if you don't want
to manually edit your .ini files ;-)
-- Daniel, Epic Games Inc.
> --
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
On Sat, 2004-02-14 at 10:53, Vladimir Dergachev wrote:
> Checkout HEAD (and/or tv_output) branches from GATOS CVS.
>
> Checkout "orig" branch - this is the original XFree86 code we started
> from.
>
> diff -u one against the other.
Doing that now. I'd been working against a pristine copy of
> Has anyone tried UT2004 out yet, and if so, what card & what version of
> XFree are you using, and do your menus display properly?
I believe the OpenGL renderer drops miplevels there were it shouldn't when
it decompresses the DXT textures. I'll fix that for the full game.
-- Daniel, Epic Games
On Sat, 2004-02-14 at 10:41, Dieter Nützel wrote:
> Do you get an empty/black window only?
Yes! That's exactly what I'm getting...
>
> Then it could be the same bug as with quake3-smp (multiple contexts)
> introduced in June/July by Ian.
>
> I'm hunting on it...
>
> Greetings,
> Dieter
At 02:06 PM 14/2/2004, Alex Deucher wrote:
--- Rafael Maximo <[EMAIL PROTECTED]> wrote:
>
> I found some problems here with my savage4, now the textures
> are
> showing correctly and working just fine but i did some tests with
> Chromium
> BSU and it lockup on the main menu after sometim
--- Rafael Maximo <[EMAIL PROTECTED]> wrote:
> Hi,
>
> First i would like to say that Alex and Felix are doing a
> great
> job with savage driver and every day it's getting better.
>
> I found some problems here with my savage4, now the textures
> are
> showing correctly and
Daniel Kasak wrote:
Hi all.
Just downloaded the UT2004 demo, and tried it out under
XFree86-4.3.99.902.
I'm pleasantly surprised.
It runs quite nicely, and I can't spot any rendering bugs ( though I
wasn't looking closely - I was more interested in shooting at things
). Anyway, congrats to all
Hi Hod,
There is an easy way to generate patch with GATOS-specific changes:
Checkout HEAD (and/or tv_output) branches from GATOS CVS.
Checkout "orig" branch - this is the original XFree86 code we started
from.
diff -u one against the other.
The changes should classify as following:
1
Hi,
First i would like to say that Alex and Felix are doing a great
job with savage driver and every day it's getting better.
I found some problems here with my savage4, now the textures are
showing correctly and working just fine but i did some tests with Chromium
BSU and it l
Am Samstag, 14. Februar 2004 05:31 schrieb Hod McWuff:
> All of the experimenting I've done points to the idea that memory setup
> problems cause either X locks or instant reboots. With Gatos unmodified,
> and the DRI DRM left alone except for the version minor number, and
> everything else as Gen
Am 2004.02.14 00:11:35 +0100 schrieb(en) Roland Scheidegger:
> Andreas Stenglein wrote:
> > Just tried ut2003 on R100 with current DRI+MESA cvs HEAD.
> >
> > Now with the "MULT-code" in radeon_state.c radeon_state_init.c
> > (change lighting to use MULT instead of PREMULT ...) the
> > shading/lig
Roland Scheidegger wrote:
Ok, I was wrong that the radeon driver also doesn't implement this
correctly. It just always uses a fallback, it just doesn't support it in
hardware. That said, I'm wondering what's the purpose of announcing
ARB_imaging support, at least out of the three blend extension
Ok, I was wrong that the radeon driver also doesn't implement this
correctly. It just always uses a fallback, it just doesn't support it in
hardware. That said, I'm wondering what's the purpose of announcing
ARB_imaging support, at least out of the three blend extensions this
includes (EXT_blen
Michel DÃnzer wrote:
On Sat, 2004-02-14 at 00:11, Roland Scheidegger wrote:
Just the other day, I've noticed not even the good old tuxracer runs
correct on the R100 on my 2nd PC - the ice areas flickered a lot,
That's a long standing tuxracer bug, Z fighting between several passes.
I think the
Oops! I mean of course ut2004demo, not 2003.
--
Free Software - find interesting programs and change them
NetHack - meet interesting creatures, kill them and eat their bodies
Usenet - meet interesting people from all over the world and flame them
Decopter - unrealistic helicopter simulator, get i
Hi all.
Just downloaded the UT2004 demo, and tried it out under XFree86-4.3.99.902.
I'm pleasantly surprised.
It runs quite nicely, and I can't spot any rendering bugs ( though I
wasn't looking closely - I was more interested in shooting at things ).
Anyway, congrats to all those responsible for
>
> -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
32 matches
Mail list logo
