[Bug 16520] [i915 i945 i965] tex corruption with Max Payne / ut2004 / WoW

http://bugs.freedesktop.org/show_bug.cgi?id=16520 --- Comment #41 from Tobias Jakobi liquid.a...@gmx.net 2008-12-13 04:32:11 PST --- Retested with latest mesa git master and Max Payne, issue is still there. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ---

[Bug 11938] Switch to VESA mode hangs on HD4850

http://bugzilla.kernel.org/show_bug.cgi?id=11938 a...@wagner.name changed: What|Removed |Added Status|NEW |REJECTED Resolution|

Re: [PATCH] libdrm merge of KMS bits

On Thu, 11 Dec 2008 15:11:23 -0800 Jesse Barnes jbar...@virtuousgeek.org wrote: Initially I thought the merge of the KMS bits into libdrm would be as easy as merging the modesetting-gem branch into master. But that branch has a ton of stuff in it, including code for radeon and nv that its

[Bug 12216] New: Error when drm is loaded

http://bugzilla.kernel.org/show_bug.cgi?id=12216 Summary: Error when drm is loaded Product: Drivers Version: 2.5 KernelVersion: 2.6.28-rc8 Platform: All OS/Version: Linux Tree: Mainline Status: NEW

[Bug 12216] Error when drm is loaded

http://bugzilla.kernel.org/show_bug.cgi?id=12216 --- Comment #1 from francois.valen...@tvcablenet.be 2008-12-13 10:00 --- Created an attachment (id=19280) -- (http://bugzilla.kernel.org/attachment.cgi?id=19280action=view) output of dmesg -- Configure bugmail:

[Bug 12028] i915 DRM is broken in 2.6.28-rc4

http://bugzilla.kernel.org/show_bug.cgi?id=12028 --- Comment #12 from r...@sisk.pl 2008-12-13 10:19 --- Adam, any news? -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug,

BUG: via_drmclient.h is referenced but does not exist

Hi David et al. After improving the headers_check.pl script to do a check for files included with: #include foo.h it reported the following error: /home/sam/kernel/knext.git/usr/include/drm/via_drm.h:34: included file '/home/sam/kernel/knext.git/usr/include/drm/via_drmclient.h' is not

[Bug 12216] Error when drm is loaded

http://bugzilla.kernel.org/show_bug.cgi?id=12216 --- Comment #2 from francois.valen...@tvcablenet.be 2008-12-13 11:42 --- After a git-bisect run, it appears that the following commit is the first bad one: 52440211dcdc52c0b757f8b34d122e11b12cdd50 is first bad commit commit

[Bug 12174] No backlight control on Samsung x360

http://bugzilla.kernel.org/show_bug.cgi?id=12174 --- Comment #1 from m.he...@gmx.net 2008-12-13 13:53 --- Created an attachment (id=19283) -- (http://bugzilla.kernel.org/attachment.cgi?id=19283action=view) decompiled acpidump According to the acpidump output NVID belongs to the

Re: intel text mode restore problem

Norbert Preining wrote: Where can I get this intel_reg_dumper from? Is there a tree to check out, or a ready made binary from x86_64 (Debian/unstable)? It is residing in the git repository of the intel driver. Cheers, Johannes.

[Bug 12216] Error when drm is loaded

http://bugzilla.kernel.org/show_bug.cgi?id=12216 r...@sisk.pl changed: What|Removed |Added CC||r...@sisk.pl OtherBugsDependingO|

[Bug 12216] Error when drm is loaded

http://bugzilla.kernel.org/show_bug.cgi?id=12216 --- Comment #3 from r...@sisk.pl 2008-12-13 15:01 --- First-Bad-Commit : 52440211dcdc52c0b757f8b34d122e11b12cdd50 -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because:

Re: [Intel-gfx] [PATCH] [intel] Dump out memory usage information when the kernel fails to pin

On Fri, 2008-12-12 at 10:42 -0800, Keith Packard wrote: The execbuffer ioctl returns ENOMEM when it fails to pin all of the buffers in the GTT. This is usually caused by the DRM client attempting to use too much memory in a single request. Dumping out the requested and available memory values

[Bug 18967] Xorg freeze after using xrandr, drm debug error.

http://bugs.freedesktop.org/show_bug.cgi?id=18967 --- Comment #12 from Eric Anholt e...@anholt.net 2008-12-13 16:58:19 PST --- Generally no user environment involves server regens, so it may be in your best interest to avoid running a testing environment involving that code path.