Summary: | Problem with libopencascade - salome-platform | ||
---|---|---|---|
Product: | DRI | Reporter: | Paulo César Pereira de Andrade <pcpa> |
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | przanoni |
Version: | XOrg git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Paulo César Pereira de Andrade
2010-03-26 12:22:55 UTC
The current solution I am using in the package is to add export LIBGL_ALWAYS_INDIRECT=true to the runSalome script. Also, the problem doesn't happen in all files; probably an issue if there is a vertice at the 0,0,0 coordinate, in association with the Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72) Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72) errors Just tested with a build of salome version 5.1.4. Unlike when running on a computer with an intel card (bug #27333), it now works without setting LIBGL_ALWAYS_INDIRECT, and this way becomes fast/responsive in the opencascade viewer; vtk viewer is very slow on both test systems (i586/i965 and x86_64/r300), and should be a software issue as it was not so slower with salome 5.1.3. But still fills the console with these warnings: Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72) Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72) Mesa: 1 similar GL_INVALID_ENUM errors Software version is: $ rpm -q x11-server-xorg x11-driver-video-ati mesa lib64drm2 x11-server-xorg-1.9.2-1mdv2011.0 x11-driver-video-ati-6.13.99-0.20101029.1mdv2011.0 mesa-7.9-1mdv2011.0 lib64drm2-2.4.22-1mdv2011.0 -- 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/drm/amd/issues/120. |
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.