https://bugs.freedesktop.org/show_bug.cgi?id=62578
Priority: medium Bug ID: 62578 Assignee: dri-devel@lists.freedesktop.org Summary: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state! Severity: major Classification: Unclassified OS: All Reporter: orion@cora.nwra.com Hardware: x86 (IA32) Status: NEW Version: 9.1 Component: Drivers/DRI/r300 Product: Mesa
Created attachment 76846 --> https://bugs.freedesktop.org/attachment.cgi?id=76846&action=edit Xorg.0.log
Running KDE 4.10.1 on Fedora 18. After login, screen flickers a bit but nothing is displayed other than the background image.
.xsession-errors contains: OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI RV370 OpenGL version string: 2.1 Mesa 9.1 OpenGL shading language version string: 1.20 Driver: R300G GPU class: R300 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 9.1 Linux kernel version: 3.8.3 Direct rendering: yes Requires strict binding: yes GLSL shaders: limited Texture NPOT support: limited Virtual Machine: no r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
this r300 messages keeps repeating.
kernel 3.8.3-203.fc18.i686.PAE
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV370 5B60 [Radeon X300 (PCIE)]
Just updated from Fedora 16 where this system was working fine.
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #1 from Orion Poplawski orion@cora.nwra.com --- Downgrading from llvm-libs-3.2-2.fc18 and mesa 9.1-1.fc18 to llvm-libs-3.1-11.fc18 and mesa 9.0.1-1.fc18 appears to fix the issue.
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #2 from Orion Poplawski orion@cora.nwra.com --- The problem is also present in mesa 9.0.3. With that I also get the following in dmesg:
Mar 20 13:51:28 aspen kernel: [162904.454217] [drm:r100_cs_track_check] *ERROR* [drm] No buffer for z buffer ! Mar 20 13:51:28 aspen kernel: [162904.454224] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
But I don't seem to get that with 9.1.
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #3 from Marek Olšák maraeo@gmail.com --- What's your screen resolution?
https://bugs.freedesktop.org/show_bug.cgi?id=62578
Marek Olšák maraeo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Drivers/DRI/r300 |Drivers/Gallium/r300
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #4 from Orion Poplawski orion@cora.nwra.com --- [ 23.308] (II) RADEON(0): Output VGA-0 using initial mode 1600x1200 +0+0 [ 23.308] (II) RADEON(0): Output DVI-0 using initial mode 1600x1200 +1600+0
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #5 from Orion Poplawski orion@cora.nwra.com --- Well, still reproducible with a different user with 9.0.1.
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #6 from Marek Olšák maraeo@gmail.com --- The issue seems to be that kwin or DDX allocates a texture of the size 2*1600x1200 and your hardware only supports 2560x2560 for rendering and 2048x2048 for texturing. Unfortunately I'm not an expert on X server internals.
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #7 from Orion Poplawski orion@cora.nwra.com --- I filed a bug against kwin. Looks like they will have checks in place in 4.11 to not use OpenGL on this hardware. Not sure if anything should still be done on the mesa side or not to help with this.
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #8 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #7)
I filed a bug against kwin. Looks like they will have checks in place in 4.11 to not use OpenGL on this hardware. Not sure if anything should still be done on the mesa side or not to help with this.
Depending on what features they are using, it should be fine to use GL on this hardware. They just have to respect the hw limits.
https://bugs.freedesktop.org/show_bug.cgi?id=62578
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED
--- Comment #9 from GitLab Migration User gitlab-migration@fdo.invalid --- -- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/355.
dri-devel@lists.freedesktop.org