[uae] Re: Pointer trails
- From: Montag <montag@xxxxxxxx>
- To: uae@xxxxxxxxxxxxx
- Date: Tue, 09 Mar 2004 19:17:36 +0500
On 03/09/2004, Richard wrote:
>
> I understand the symptoms - just not the cause or the remedy. ;-)
Well, I can live with the trail... no problem.:)
I prefer to know you at work on some bsdemulation and AHI enanchements
> I wonder if the common factor causing this problem for you and Keith is
> that you both have NVidia chipsets. Are you both using NVidia's X drivers?
Yes, I'm using NVidia's proprietary drivers.
But I have an SDL UAE-- so, after reading this mail, I just tried to run it
directly in the console, without X.
I had to change to a 16bit screen, because, unlike X, there were no 32bit
screens. I played a couple of minutes with YAM and there was no trail, but
then I fired up IBrowse... and it locked my computer!
It's a bit too dangerous... I'll try again later, without important tasks in
the background. :)
I can also try what happens using the driver for nvidia cards that ships
with X.
I'll let you know tomorrow.
> (And does anybody out there experience this problem who doesn't have an
> NVidia chipset and X drivers?)
>
> Perhaps there is some caching problem with the framebuffer memory?
Who knows :D
> Do you both have MTRR enabled in your kernel? And does the NVidia X driver
> enable write-combining on your gfx card's memory? (Have a look in
> /proc/mttr).
Yes, I have MTTR enabled in the kernel.
I report here my /proc/mttr because I don't know what I'm looking for :P
reg00: base=0xfeda0000 (4077MB), size= 128KB: write-back, count=1
reg01: base=0xfff80000 (4095MB), size= 512KB: write-protect, count=1
reg02: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg03: base=0x10000000 ( 256MB), size= 128MB: write-back, count=1
reg04: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1
reg05: base=0xe0000000 (3584MB), size= 256MB: write-combining, count=1
Ciao
--
S+E
[ Perche' tanto odio? ]
Other related posts:
