On Tue, 2004-01-06 at 11:50, Keith Whitwell wrote:
>
> I haven't looked at them, but these sound like problems arising from the fact
> that size-3 color arrays can now make it through to the driver for
> incorporation into vertices.
>
> The easiest way to deal with this is to convert to using
Right now no one has tested on supersavage. You will need to add the
supersavage PCI ID's to the DRM
(xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/savage.h)and
and also fix savage_driver.c in the 2D driver so that the DRI init
functions get called. you will need to add:
||
Hi.
I managed to get everything compiled cleanly.
Hardware is t23/ S3 Supersavage / 1400x1050
Kernel Module loads cleanly.
but xfree writes in log :
snip
II) SAVAGE(0): map aperture:0x41301000
(--) SAVAGE(0): SavageMatchBiosMode:chose mode 13e at 75Hz.
(II) SavageSetVESAMode:mode=0x13
just do a cvs update and rebuild the kernel module
(xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel), DRI
driver (xc/xc/lib/GL/mesa/src/drv/savage) and 2D driver
(xc/xc/programs/Xserver/hw/xfree86/drivers/savage). in most cases you
can just copy the new versions over you old ones. yo
One other quick question: when the driver is updated, what all do I need
to redownload/recompile?
Jesse Merriman
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management S
On Sul, 2004-01-11 at 20:43, Jesse Merriman wrote:
> Alex Deucher wrote:
> > hmmm... if both agpgart and savage are loaded before X starts, I'm not
> > sure what your problem would be. what does your kernel log or dmesg
> > say when you load the modules?
>
> Here's the end of my dmesg:
>
> Linux
Roland Scheidegger wrote:
> It looks like you're running a 2.6 kernel. Did you load the chipset
specific agp module, like via-agp etc.?
Doh! Yeah, that was it. It works now when I:
modprobe via-agp
modprobe savage
Thanks for the help Roland and Alex. Now to get on with crashing X...
P.S. Sorry
Alex Deucher wrote:
it also may be a problem with mtrr's. they don't seem to be set up
right. do you have mtrr support in your kernel?
Yes. But what can I do to set them up right? There are no further kernel
options besides just turning them on or off.
Also, agpgart should print some info abou
Jesse Merriman wrote:
Alex Deucher wrote:
hmmm... if both agpgart and savage are loaded before X starts, I'm not
sure what your problem would be. what does your kernel log or dmesg
say when you load the modules?
Here's the end of my dmesg:
Linux agpgart interface v0.100 (c) Dave Jones
savage:
it also may be a problem with mtrr's. they don't seem to be set up
right. do you have mtrr support in your kernel? Also, agpgart should
print some info about the agp bridge and some memory mappings. I don't
see that in your output. perhaps you need to use the try-unsupported
option?
Alex
---
Alex Deucher wrote:
hmmm... if both agpgart and savage are loaded before X starts, I'm not
sure what your problem would be. what does your kernel log or dmesg
say when you load the modules?
Here's the end of my dmesg:
Linux agpgart interface v0.100 (c) Dave Jones
savage: no version magic, taintin
hmmm... if both agpgart and savage are loaded before X starts, I'm not
sure what your problem would be. what does your kernel log or dmesg
say when you load the modules?
Alex
--- Jesse Merriman <[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > I assume you have agpgart compiled into the kerne
I use a Logitech MX700 mouse with 8 buttons (number 8 is the "window button").
But can only use 7 with X/KDE (3.2 beta2).
XF86Config looks like:
Section "InputDevice"
Driver "mouse"
Identifier "Mouse[1]"
Option "ButtonNumber" "7"
Option "Buttons" "7"
Option "De
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=1059
[EMAIL PROTECTED] changed:
What|Removed |Added
-
does this patch help:
--- Mesa_orig/src/mesa/drivers/dri/r200/r200_state_init.c Wed Jan 7 18:47:59
2004
+++ Mesa/src/mesa/drivers/dri/r200/r200_state_init.c Sun Jan 11 20:53:09 2004
@@ -504,11 +504,16 @@
0x10); /* Small default bias */
rmesa->hw.cube[i].cmd[C
Alex Deucher wrote:
I assume you have agpgart compiled into the kernel?
All agpgart compiled as modules.
> DO you get any errors when you modprobe the savage module?
Nope. agpgart and savage both modprobe fine.
module, make sure to run 'depmod -a' to update your module
dependancies.
Did that.
On Sun, 11 Jan 2004 09:31:05 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> --- Felix K_hling <[EMAIL PROTECTED]> wrote:
> > On Fri, 9 Jan 2004 16:00:46 -0800 (PST)
> > Alex Deucher <[EMAIL PROTECTED]> wrote:
> >
> > > whoops. I'll have to check that out. Can you point me to the
> > c
I assume you have agpgart compiled into the kernel? DO you get any
errors when you modprobe the savage module? after you copy the savage
module, make sure to run 'depmod -a' to update your module
dependancies.
Also did you compile module support into your kernel?
Alex
--- Jesse Merriman <[EMAI
On Sun, 11 Jan 2004 12:54:31 +0100
Andreas Stenglein <[EMAIL PROTECTED]> wrote:
> will the savage driver work with savage4 pci cards?
>
> greetings,
> Andreas
It should, though I think you'd be the first one to test it on a PCI
card. PCI support is currently disabled with 2.6 kernel. Your best b
--- Felix Kühling <[EMAIL PROTECTED]> wrote:
> On Fri, 9 Jan 2004 16:00:46 -0800 (PST)
> Alex Deucher <[EMAIL PROTECTED]> wrote:
>
> > whoops. I'll have to check that out. Can you point me to the
> code?
> > I'm assuming savage_span in the DRI somewhere? Also, only 16 bpp
> works
> > at the m
It should. I haven't tested it though.
Alex
--- Andreas Stenglein <[EMAIL PROTECTED]> wrote:
> will the savage driver work with savage4 pci cards?
>
> greetings,
> Andreas
>
> Am 2004.01.09 22:47:40 +0100 schrieb(en) Alex Deucher:
> > just an FYI, I switched the code in savage_dri.c to use the
Greetings,
Dieter
--
Dieter Nützel
@home:
---
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platfo
Hi,
Alex Deucher wrote:
make -f Makefile.linux
Okay, did that with no errors.
If you are using redhat 9 (possibly fedora as well), the build will
fail because redhat is using the MM code from 2.6 in their 2.4 kernels.
I'm on a Gentoo system with 2.6.1-mm1. The build went through with no
problem
Olivier Chapuis wrote:
On Fri, Jan 09, 2004 at 11:51:18AM -0700, Brian Paul wrote:
Olivier Chapuis wrote:
Hello,
I use "current cvs" from 2003-12-17 (dri - Mesa-newtree) on an Ati
Mobility M7 LW. When dri is enabled (OpenGL renderer string: Mesa DRI
Radeon 20030328 AGP 4xTCL) I get a memory leak
Olivier Chapuis wrote:
On Sat, Jan 10, 2004 at 06:15:38PM +0100, Dieter Nützel wrote:
I just:
cvs update # in Mesa-newtree
cvs update # in dri/xc
Do you have the right link to Mesa-newtree (now, Mesa)?
So now I've to co Mesa and not Mesa-newtree? One day I saw this
lines in con
progs/demos> ./gears
7323 frames in 5.000 seconds = 1464.600 FPS
8783 frames in 5.000 seconds = 1756.600 FPS
8713 frames in 5.000 seconds = 1742.600 FPS
progs/demos> ./ipers
IperS V1.0
Written by David Bucciarelli ([EMAIL PROTECTED])
drmCommandWrite: -22
drmRadeonCmdBuffer: -22 (exiting)
progs
will the savage driver work with savage4 pci cards?
greetings,
Andreas
Am 2004.01.09 22:47:40 +0100 schrieb(en) Alex Deucher:
> just an FYI, I switched the code in savage_dri.c to use the global
> bitmap descripter for the front buffer, the primary BD for the back
> buffer and the secondary BD fo
I check the mailing-list archive regularly, and noticed the Radeon/R200 TMU
increase patch. It looks like it does not touch the radeon files? Does the
web-based archive cutoff messages after a certain length, or was that all
there is...(not touching radeon_context.c etc..).
If someone has the
On Fri, 9 Jan 2004 16:00:46 -0800 (PST)
Alex Deucher <[EMAIL PROTECTED]> wrote:
> whoops. I'll have to check that out. Can you point me to the code?
> I'm assuming savage_span in the DRI somewhere? Also, only 16 bpp works
> at the moment on savage4. I've only been able to run one 3d app at 32
- Forwarded message from Andrew Cohen <[EMAIL PROTECTED]> -
> Date: Sat, 10 Jan 2004 11:30:13 -0500
> From: Andrew Cohen <[EMAIL PROTECTED]>
> Subject: Re: Question about mach64/DRI/Kernel 2.6
> To: José Fonseca <[EMAIL PROTECTED]>
>
> Oops, sorry about the blank message---cold fingers hi
you need to build the savage kernel module. The code is in:
xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel
Change to that directory and then type:
make -f Makefile.linux
or
make -f Makefile.linux LINUXDIR=/path/to/kernel/src
If you are using redhat 9 (possibly fedora as well), the
31 matches
Mail list logo
