Summary: | r6xx-r7xx-support: EXA and Xv not working on M82 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Sascha Steinbiss <satta> | ||||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||
Status: | RESOLVED NOTABUG | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | minor | ||||||||||
Priority: | low | ||||||||||
Version: | unspecified | ||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Sascha Steinbiss
2009-02-11 07:54:55 UTC
Created attachment 22826 [details]
xorg.conf
You need to install the kernel modules from the r6xx-r7xx-support branch of the drm. You also need to add: Option "DRI" "TRUE" to the device section of your config. Oh yes, that did the trick. Now EXA and Xv seem to work. The only thing that still looks strange is the log contains thousands of lines with 'Ran out of VB space!' but seemingly without negative effects: $ grep 'Ran out of VB space!' /var/log/Xorg.0.log | wc -l 80318 Anyway, thanks! grab the latest bits from git. they should provide more info. (In reply to comment #4) > grab the latest bits from git. they should provide more info. Just did. It's 'Copy: Ran out of VB space!' now. Let me know if you need more info, I'm closing this bug for now as my original problem is solved. Can you my latest commit? I attempted to handle the out of VB case properly. (In reply to comment #6) > Can you my latest commit? I attempted to handle the out of VB case properly. I just pulled (to bd141aa) to try your latest work. Sadly, using any version newer than commit ec60ef0 causes my system to lock up hard on X start, rebooting after a few seconds. Created attachment 22844 [details]
xorg.log.old from crash case
seems fixed as for now (commit 7cde00f49) |
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.