Summary: | [855GM] glxgears segfaults | ||
---|---|---|---|
Product: | Mesa | Reporter: | Luke Camden <luke.camden> |
Component: | Drivers/DRI/i915 | Assignee: | Eric Anholt <eric> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | medium | CC: | net147 |
Version: | unspecified | Keywords: | NEEDINFO |
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Luke Camden
2009-06-20 00:34:08 UTC
Perhaps I should post these things too. If there is anything else that might be helpful, let me know. $ lspci 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) .... $ dmesg ... glxgears[13168]: segfault at 1300 ip b7b0c384 sp bfc79930 error 4 in libdricore.so[b7a33000+1fe000] Please attach Xorg.0.log. It will be good if you could try xf86-video-intel 2.8.x and kernel 2.6.30/31. Mesa 7.4 at this point is really old. Could you update to Mesa 7.5 or the 7.6 development branch and retest? (In reply to comment #0) > Running as normal user, glxgears segfaults. Running as root, it doesn't crash > but the graphical output is garbage (I can just about see the gears rotating, > but there are a lot of horizontal lines obscuring my view). This looks like incorrect permissions. The user you are running as does not have permission to access /dev/dri/card0. Ensure you have added your user to the video group (http://wiki.archlinux.org/index.php/Intel_Graphics#Configuration): sudo gpasswd -a myusername video This is fixed in the latest version. |
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.