Bug 14803 - nv driver incredibly slow on Quadro NVS 104M
Summary: nv driver incredibly slow on Quadro NVS 104M
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nVidia (open) (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86-64 (AMD64) OpenBSD
: medium major
Assignee: Aaron Plattner
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-04 07:00 UTC by Owain Ainsworth
Modified: 2010-03-30 00:25 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments
openbsd xorg.log (32.81 KB, text/plain)
2008-03-04 07:00 UTC, Owain Ainsworth
no flags Details
OpenBSD dmesg (7.16 KB, text/plain)
2008-03-04 07:02 UTC, Owain Ainsworth
no flags Details
Ubuntu xorg.log (39.97 KB, text/plain)
2008-03-04 07:03 UTC, Owain Ainsworth
no flags Details
Ubuntu dmesg (32.67 KB, text/plain)
2008-03-04 07:03 UTC, Owain Ainsworth
no flags Details
i386 x log (39.66 KB, text/plain)
2008-03-04 13:02 UTC, Owain Ainsworth
no flags Details
i386 dmesg (35.21 KB, text/plain)
2008-03-04 13:02 UTC, Owain Ainsworth
no flags Details
Xorg.log of 2.1.8 version of nv driver (git head) (32.97 KB, application/octet-stream)
2008-03-13 12:32 UTC, Marco Peereboom
no flags Details

Description Owain Ainsworth 2008-03-04 07:00:01 UTC
Created attachment 14804 [details]
openbsd xorg.log

(submitted on behalf of a friend of mine)

Using the nv driver on OpenBSD, and also on ubuntu 7.10 (desktop edition), X performs VERY slowly on the quadro NVS 104M (pciid 0x9429). The vesa driver is faster.

Attached are dmesgs for both osen, and xorg.logs for both as well. The architecture is amd64, but an i386 test will be performed soon as well.
Comment 1 Owain Ainsworth 2008-03-04 07:02:39 UTC
Created attachment 14805 [details]
OpenBSD dmesg
Comment 2 Owain Ainsworth 2008-03-04 07:03:12 UTC
Created attachment 14806 [details]
Ubuntu xorg.log
Comment 3 Owain Ainsworth 2008-03-04 07:03:36 UTC
Created attachment 14807 [details]
Ubuntu dmesg
Comment 4 Owain Ainsworth 2008-03-04 13:02:06 UTC
Created attachment 14819 [details]
i386 x log

Tested on i386, also very slow.
Comment 5 Owain Ainsworth 2008-03-04 13:02:56 UTC
Created attachment 14820 [details]
i386 dmesg
Comment 6 Marco Peereboom 2008-03-10 13:58:27 UTC
What is the normal turnaround time for a response on these issues?
Comment 7 Joris Vink 2008-03-12 07:20:52 UTC
I'm currently also affected by this problem, my X environment is
incredibly slow and seems to drag down my overal performance of my laptop.

Anybody gotten any replies yet?
Comment 8 Marco Peereboom 2008-03-13 12:32:53 UTC
Created attachment 15095 [details]
Xorg.log of 2.1.8 version of nv driver (git head)
Comment 9 David Goodlad 2008-03-16 22:16:24 UTC
I don't mean to make 'noise' here, but I'd just like to confirm that my system (with Quadro NVS 140M 128MB) exhibits what are apparently the same symptoms as described here: very slow 2d performance, especially when redrawing large parts of windows. Switching desktops in xmonad, scrolling with the keyboard in firefox, etc, are noticeably choppy, but are fine when using the proprietary driver.

Let me know if I should provide any logs beyond those already submitted by the original reporter.
Comment 10 Marco Peereboom 2008-03-17 17:12:18 UTC
Obviously one can not run binary blobs on OpenBSD.  It is in fact unhealthy that people promote the use of such useless drivers.  This only encourages bad behavior in companies that claim that there is IP inside a driver and fail to understand that copyright has them covered.
Comment 11 David Goodlad 2008-03-17 18:45:37 UTC
Marco - I'm not sure whether your comment about the proprietary drivers was directed at me, but I certainly wasn't advocating their use. I only mentioned them in order to provide a baseline to which I am comparing performance.
Comment 12 Matthieu Herrb 2010-03-30 00:25:17 UTC
xf86-video-nv is not supported anymore.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.