Well I've got rid of all the problems other than the MTRR issue, which
doesn't so far seem to be causing any real problem with my machine, but
we'll see over time.
I noticed today after playing with some settings that the display was
behaving OK, the only difference was that SuSE was no longer displaying
it's fancy graphical console (don't ask me what I did to disable it, I
wasn't aware I had).
So I went ahead and increased the memory back up to 16Mb so that I could
play with 3D.
As soon as I did this, X complained that DRI was being disabled as it
couldn't grab the interrupt for the 810 graphics card as it was being used
by something else.
Checking my BIOS PCI settings showed that indeed the sound card was sharing
the interrupt.
Moving the sound card to another PCI slot cleared the interrupt for the
i810's dedicated use, and away went that problem.
So now I have the i810 working OK with X4.1, antialiasing.
The only remaining "problem" I have is the MTRR message, and I still have
to see if that's more of a warning than an error.
There are some emails on the Xpert mailing list at XFree86.org that
indicate problems with using FrameBuffers at the same time as X on the i810
(basically they don't want to share the memory space). Perhaps the fancy
graphical console that SuSE put up is using the framebuffer? This would
explain why the screen cleared up after I somehow disabled this graphical
console?!
If that is the problem, then it's not a problem with every card, as my
RADEON All-In-Wonder at home works fine, and I still have the graphical
console enabled on it. Perhaps the issue is only with the i810 and
FrameBuffers.
Gordon
Gordon McCrae wrote:
> Do you get any messages like this :
>
> kernel: mtrr: base(0xf4000000) is not aligned on a size(0x180000)
> boundary
> kernel: mtrr: base(0xf4000000) is not aligned on a size(0x180000)
> boundary
>
> I get these every time I start X, and it cross references with the
> following snippet from dmesg :
>
> agpgart: Detected an Intel i810 DC100 Chipset.
> agpgart: detected 4MB dedicated video ram.
> agpgart: AGP aperture is 64M @ 0xf4000000
> [drm] AGP 0.99 on Intel i810 @ 0xf4000000 64MB
> [drm] Initialized i810 1.1.0 20010215 on minor 0
>
> There are no options within my BIOS to change the AGP aperture settings,
> by the way I'm running X4.1 right now.
>
> So I'm wondering if the mtrr warnings are causing (or at least
> aggravating) the problem.
>
> Gordon
>
> David Aikema wrote:
>
> > ----- Original Message -----
> > From: Gordon McCrae <[EMAIL PROTECTED]>
> > To: David Aikema <[EMAIL PROTECTED]>
> > Sent: Monday, July 16, 2001 6:07 AM
> > Subject: Re: Problems with i810 under SuSE 7.2.
> >
> > > Not yet, although I can categorically say that adjusting the memory
> > > settings does not solve the problem.
> >
> > I think I've all but confirmed that by now
> >
> > > I've set the system to not use 4Mb of memory, and set X to use only
> > 4,
> > > and I still get the problem.
> >
> > Does the settings for the display cache memory come on top of the 11
> > megs of video memory that according to the intel site the cards can
> > dynamically allocate? Perhaps you're only adjusting one of these
> > factors.
> >
> > > I suspect the driver to be honest, and I'll be trying the CVS
> > version
> > > shortly.
> >
> > Ok.... can you let me know your results?
> >
> > David Aikema
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
