Summary: | Blender menus are not drawn with Matrox G400 DualHead(FreeBSD 4.10, Slackware-current) | ||
---|---|---|---|
Product: | Mesa | Reporter: | lauri järvenpää <lauri.jarvenpaa> |
Component: | Drivers/DRI/MGA | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | major | ||
Priority: | high | CC: | jacekpoplawski |
Version: | 6.1 | ||
Hardware: | x86 (IA32) | ||
OS: | FreeBSD | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
C source code - test case
Backtrace from Blender crash |
Description
lauri järvenpää
2004-08-30 01:47:33 UTC
Created attachment 4117 [details]
C source code - test case
This test case demonstrates that glDrawBuffer() is essentially non-functional,
in that it appears to fail more often than it works.
(In reply to comment #1) > Created an attachment (id=4117) [edit] > C source code - test case > > This test case demonstrates that glDrawBuffer() is essentially non-functional, > in that it appears to fail more often than it works. > (In reply to comment #1) > Created an attachment (id=4117) [edit] > C source code - test case > > This test case demonstrates that glDrawBuffer() is essentially non-functional, > in that it appears to fail more often than it works. > This bug has been present for more than 2 years now. Blender is unusable on DRI/G400 (FreeBSD and Linux) because of it. Disabling hardware accelleration is not an option because the program becomes very slow. Its very bad that this hasnt been fixed yet, especially because g400 is a well documented card and often brought up in the open source vs closed 3d drivers arguments. Created attachment 5361 [details]
Backtrace from Blender crash
*** Bug 6858 has been marked as a duplicate of this bug. *** Probably the MGA bugs can be closed now that the driver is removed from git? (In reply to Marcin Baczyński from comment #5) > Probably the MGA bugs can be closed now that the driver is removed from git? Yes. :) |
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.