| Summary: | dual radeon xserver crash on startup: destination is framebuffer incomplete: incomplete/missing attachment [8cd7] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | SMF <smf.linux> | ||||
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | medium | ||||||
| Version: | unspecified | ||||||
| Hardware: | x86 (IA32) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
Also tested with 4.15.8 kernel with the same result. [ 1146.551] (II) Loading /usr/lib/X11/modules/libglamoregl.so [ 1146.557] (II) Module glamoregl: vendor="X.Org Foundation" [ 1146.557] compiled for 1.19.6, module version = 0.6.0 You're using the old standalone glamor repository. Use glamor from the xserver repository. Removed old glamor components and rebuilt xserver: [ 517.455] (II) Loading /usr/lib/X11/modules/libglamoregl.so [ 517.474] (II) Module glamoregl: vendor="X.Org Foundation" [ 517.474] compiled for 1.19.6, module version = 1.0.0 problem solved thanks. |
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 138014 [details] Log and Configuration data This system had a 760G [Radeon 3000] and a Radeon X1550 video cards and had worked satisfactorily for a number of years. The Radeon X1550 recently started to show signs of age so I decided to replace it with a RV710 [Radeon HD 4350] I have available. The only change I made was to update the kernel with firmware blobs for the RV710 [Radeon HD 4350]. The xserver now crashes on startup and reports: destination is framebuffer incomplete: incomplete/missing attachment [8cd7] The user space system is a 32bit LFS/BLFS build (kept mostly up to date) and the kernel is 64bit currently version 4.14.25. I am attaching some relevant configuration and log files for information. Is this a configuration issue on my part or a real software problem ?