On 25 Sep 2002, James D Strandboge wrote:
> > >
> > > 2. 16 bit color depth at 1400x1050 (max resolution of the laptop) looks
> > > great, but 24 bit has problems with gradients (eg background in
> > > nautilus)-- they appear 'barred'. I tried different modelines and
> > > options in XF86Config-4 to no avail. Is this a known issue?
> >
> > I don't recall seeing that problem with the nv driver. Does
> > it do that from startup or only after doing bios-related hotkey
> > switches? Flat panel scaling is not used in the nv - it always
> > runs in the native resolution and centers the image if the programmed
> > resolution is smaller than the panel - and there should be no problems
> > in that mode. When scaling at high resolutions the hardware can
> > drop to a lower-bandwidth mode where it has lower color accuracy.
> > Maybe the bios can set up something like that if you did a hotkey
> > switch. When that happens does VT switching fix it? If it's banding
> > from startup, I'll have to try to repro that.
> >
> From X startup. I have a 15" SXGA+ screen for 1400x1050 default depth.
> This is the resolution that I am encountering the barring as well. VT
> switching does nothing to help.
I'll see if I can scrounge one up and try to repro.
> > >
> > > Finally, this is not a problem, but more a question about the driver.
> > > The driver is noticably slower if I don't have ShadowFB enabled. In the
> > > Xfree86.0.log, it says:
> > >
> > > (**) NV(0): Option "ShadowFB" "on"
> > > (**) NV(0): Using SW cursor
> > > (**) NV(0): Using "Shadow Framebuffer" - acceleration disabled
> > > (--) NV(0): Linear framebuffer at 0xE0000000
> > > (--) NV(0): MMIO registers at 0xFC000000
> > >
> > > Note, 'acceleration is disabled.' I am assuming this means 2D
> > > acceleration, but having ShadowFB enabled is much better. With it
> > > disabled, launching a gnome-terminal is slow with high cpu usage until
> > > it pops up (about 2 seconds), and closing windows is also slow (via the
> > > 'X' button in sawfish). Should ShadowFB typically be enabled with this
> > > driver? The performance is perfectly acceptable with it enabled.
> >
> > Something is amiss. What does /proc/mtrr say?
> > The 2D acceleration should clobber ShadowFB. Could you send
> > me the Xfree86.0.log from a run without ShadowFB?
> >
> >
>
> I should also mention that simply left clicking on the title bar of
> a window and dragging to move it does not always work with ShadowFB off.
> It's like the mouse just didn't grab it or it takes a couple of seconds to
> grab (with a cpu spike).
This shouldn't have anything to do with ShadowFB or not.
The only unusual thing I see in the server output is that you've
disabled the hardware cursor. You shouldn't do that, sw cursor
is pretty expensive.
I'm wondering if this laptop got stuck in some strange power save
mode and the graphics engine clocks got turned down really low.
What do you get on a benchmark like:
x11perf -repeat 1 -shmput500
and
x11perf -repeat 1 -copywinwin500
Mark.
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
