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 about the agp bridge and some> memory mappings. I don't see that in your output.
The full diff between dmesg before loading agpgart and savage, and starting x, and after doing those, is:
> Linux agpgart interface v0.100 (c) Dave Jones
> savage: no version magic, tainting kernel.
> [drm:savage_probe] *ERROR* Cannot initialize the agpgart module.
> mtrr: 0xe0000000,0x2000000 overlaps existing 0xe0000000,0x1000000
> request_module: failed /sbin/modprobe -- char-major-226-0. error = 256
> atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
> atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
I cannot find any other agpgart output in places like the kernel log. All I see is that it cannot initialize the agpgart module. From the kernel log:
[EMAIL PROTECTED] kernel $ grep -i savage current
Jan 11 11:53:12 [kernel] savage: no version magic, tainting kernel.
Jan 11 11:53:12 [kernel] [drm:savage_probe] *ERROR* Cannot initialize the agpgart module.
perhaps you need to use the try-unsupported option?
What is that an option to?
Jesse Merriman [EMAIL PROTECTED]
------------------------------------------------------- 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+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
