Summary: | Hack'n'Slash hangs with Nouveau driver | ||
---|---|---|---|
Product: | Mesa | Reporter: | Steven Zakulec <spzakulec> |
Component: | Drivers/DRI/nouveau | Assignee: | Nouveau Project <nouveau> |
Status: | RESOLVED MOVED | QA Contact: | Nouveau Project <nouveau> |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Dmesg from boot that includes playing Hack'n'Slash |
Description
Steven Zakulec
2016-01-02 18:42:40 UTC
The error appears to indicate that you ran out of VRAM... nouveau handles this in a less-than-graceful manner as you've observed. I would recommend trying to turn down graphics quality settings in the game if that's possible. You might also try a more recent kernel, although it is unlikely to affect the issue. I just tested Hack'n'Slash with the Nvidia driver to be sure I wasn't remembering the wrong thing, and that it really did work with that driver. With Nvidia's 340.96 driver, the game runs just fine, and gets past that trouble spot without an issue. Is there anything else I can do to help you figure out what's going on here, and hopefully end up with the same behavior for both drivers?? Thanks! Yeah, I'm sure it works with blob drivers... they probably move some of the resources to sysmem. Nouveau sadly doesn't support that right now. It just hopes for the best, and when a submit fails, you end up with a ton of additional errors due to things not being where they are supposed to be. Making it more resilient to errors is on my list... better resource management is too, but even further down =/ Your best bet for now is turning down some sort of quality knob so that the game doesn't use as many resources. FWIW it does say it wants 512MB VRAM while you only have 256... -- 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/1094. |
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.