search for: 8192x8192

https://bugs.freedesktop.org/show_bug.cgi?id=95282 Bug ID: 95282 Summary: system hang on video playback via vdpau Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=107919 Bug ID: 107919 Summary: RandR unable to set Screen Size when using Intel+nouveau Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...cce70f671afcaf3cfc76c624b3467b7834 # bad: [c1e4a6bfbf015801c6a8b0ae694482421a22c2d9] nv50,nvc0: handle SQRT lowering inside the driver git bisect bad c1e4a6bfbf015801c6a8b0ae694482421a22c2d9 # good: [a651bc027d5ed4150bb5240fc9f46a6ca569f665] nvc0: fix blit triangle size to fully cover FB's > 8192x8192 git bisect good a651bc027d5ed4150bb5240fc9f46a6ca569f665 # good: [b3e7fb52349848b24f005c07859bc43691bd64bd] nv50/ir: avoid folding mul + add if the mul has a dnz git bisect good b3e7fb52349848b24f005c07859bc43691bd64bd # first bad commit: [c1e4a6bfbf015801c6a8b0ae694482421a22c2d9] nv50,nvc0: handle...

...he GPU chipset name and bus ID, allowing several GPUs supported by this driver to be distinguished by name. * The RandR primary output is now always explicitly marked as such. * The driver can now make use of more than 256MB of VRAM for scanout buffers, allowing e.g. virtual desktop sizes >= 8192x8192 to work. * The driver can prevent clients trying to use the DRI3 extension over a display connection forwarded via SSH from hanging. * Many more fixes for issues using the DRI3/Present extensions. Plus many other small improvements and fixes. Thanks to everybody who contributed to this release i...

https://bugs.freedesktop.org/show_bug.cgi?id=51971 Bug #: 51971 Summary: MacBook Pro 10,1 Retina - Display Resets, No Connectors Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...