On 11 Jul 2016 5:35 PM, "Felix Miata" <<a href="mailto:mrmazda@earthlink.net">mrmazda@earthlink.net</a>> wrote: > > More precisely: > (WW) glamor requires at least 128 instructions (64 reported) > (EE) modeset(0): Failed to initialize glamor at ScreenInit() time. > > I've been seeing a lot of this over the past several months on various hardware in both Rawhide, F24, various openSUSEs and Stretch, trying intentionally to get built-in modeset driver used instead of the otherwise default intel or radeon driver. Instructions at what level? How can one find out whether there is some bug causing it, or if the real problem is a hardware limitation, or something else, maybe a broken depends for a not installed package? This is fine, we don't want glamor to run on the that can't support it. Dave. > -- > "The wise are known for their understanding, and pleasant > words are persuasive." Proverbs 16:21 (New Living Translation) > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata *** <a href="http://fm.no-ip.com/">http://fm.no-ip.com/</a> > _______________________________________________ > <a href="mailto:xorg@lists.x.org">xorg@lists.x.org</a>: X.Org support > Archives: <a href="http://lists.freedesktop.org/archives/xorg">http://lists.freedesktop.org/archives/xorg</a> > Info: <a href="https://lists.x.org/mailman/listinfo/xorg">https://lists.x.org/mailman/listinfo/xorg</a> > Your subscription address: %(user_address)s