| Summary: | [r300g] 0 AD graphic problem and crash | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | adres7 |
| Component: | Drivers/DRI/R100 | Assignee: | Marek Olšák <maraeo> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Log 1
Log 2 Xorg log Graphic problem Report correct shader limits. RADEON_DEBUG=fp Fixed graphic |
||
Created attachment 35008 [details]
Log 2
Created attachment 35009 [details]
Xorg log
Created attachment 35010 [details]
Graphic problem
I've hopefully fixed the issue with dummy shaders causing crashes in git. However, I don't think we can do anything with the failing shader right now because it surpasses hardware limitations of R300 and instead it loads a shader which does nothing. I'd like not to discuss here whether this is good or not, but it's something which will be revisited in the future. The fact that the driver continues rendering "something" gives you enough time to switch to lower graphics settings if your application permits that. Closing because the game loads shaders longer than hardware can handle. But on Windows XP this game working... so it isn't the fault of hardware. Created attachment 35519 [details] [review] Report correct shader limits. Could you please try the attached patch? Let me know if it helps. If not, please run this in console: RADEON_DEBUG=fp (put the game executable here) And send me the output. Can you add patch to this repository: https://launchpad.net/~xorg-edgers/+archive/ppa ? I can't compile patchs. Created attachment 35526 [details]
RADEON_DEBUG=fp
Is this still an issue with current git? (I can't update a PPA) Graphic problem is resolved, but game doesn't start ('Game is starting' is written on the screen). It takes 100% CPU and nothing happens.
Created attachment 36382 [details]
Fixed graphic
|
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.
Created attachment 35007 [details] Log 1