On Tue, Aug 27, 2013 at 01:15:02AM -0700, patrick keshishian wrote: > On 8/26/13, Jonathan Gray <j...@jsg.id.au> wrote: > > On Mon, Aug 26, 2013 at 10:45:00PM -0700, patrick keshishian wrote: > >> On 8/26/13, Jonathan Gray <j...@jsg.id.au> wrote: > >> > On Mon, Aug 26, 2013 at 12:35:18PM -0700, patrick keshishian wrote: > >> >> help? > >> >> should I wait for next snapshot? > >> > > >> > Some of the integrated graphics parts were previously disabled > >> > due to various issues. The radeondrm code we have now is a > >> > complete re-port though so try this: > >> > >> Thanks for the reply. I'll give this a go as soon as I get > >> a breather. > >> > >> Curious, the snapshot from Aug 17th worked "just fine". > >> I didn't scrutinize it too much then, but the X session seemed > >> fine to me, vs. the VESA one now that looks "just wrong". > > > > xf86-video-ati was updated to version 7.2.0 which no longer > > supports userland modedesetting. So if a device doesn't > > match radeondrm it won't have any way of doing modesetting > > and will fall back to using vesa. > > > > I think I'll just commit the diff to enable the igp devices > > as it should work. Let us know how it goes, and remember > > to install the radeon firmware if you haven't already. > > The patched worked very nicely! :-) > > I just added fw_update'ed after noticing the drm error message > in the dmesg output. > > Thank you, > --patrick
You'll have to reboot for the firmware to be found. Then you'll have acceleration in Xorg instead of the basic shadowfb mode.
