From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 42168] New: false reporting of GL_MAX_TEXTURE_SIZE for nvidia geforce 9800 gt
Date: Mon, 24 Oct 2011 17:20:24 +0000 [thread overview]
Message-ID: <bug-42168-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=42168
Bug #: 42168
Summary: false reporting of GL_MAX_TEXTURE_SIZE for nvidia
geforce 9800 gt
Classification: Unclassified
Product: Mesa
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: jimmac-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org
The driver claims to only support GL_MAX_TEXTURE_SIZE=4096 when the hardware
limit seems to be 8192. The limit is used by GNOME 3
(gnome-session-check-accelerated-helper) as a pre check to being able to run
gnome-shell, preventing me from using a 1600x1200 + 2560x1440px monitor setup.
If, however, I attach the secondary monitor after the session starts up, the
hardware seems to be perfectly capable of running the 3D accelerated
environment across both displays with no glitches and artifacts.
This is on Fedora 16 and the card is recognised as "nVidia Corporation G92
[GeForce 9800 GT] (rev a2)"
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-10-24 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 17:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-42168-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-10-24 17:51 ` [Bug 42168] false reporting of GL_MAX_TEXTURE_SIZE for nvidia geforce 9800 gt bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-10-24 21:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-42168-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.