Am Sonntag, 11. Januar 2004 23:44 schrieb Alan Cox:
> 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
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
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.
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
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
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
Hi,
I've got a ProSavage DDR and wanted to try out the driver in the
savage-2-0-0 CVS branch and I'm having a bit of trouble setting it up
right. First I did this:
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvs/dri
co -rsavage-2-0-0-branch xc
Then I compiled and installed xfree normally with no er
13 matches
Mail list logo
