> "a011" is precisely the last entry found in
>
https://src.fedoraproject.org/rpms/xorg-x11-server/blob/HEAD/f/06_use-int...
> which explains why Xorg picks "intel" as seen in the Xorg logs:
>
> [ 7821.917] (==) Matched intel as autoconfigured driver 0
> [ 7821.917] (==) Matched modesetting as autoconfigured driver 1
> [ 7821.917] (==) Matched fbdev as autoconfigured driver 2
> [ 7821.917] (==) Matched vesa as autoconfigured driver 3
>
>
> > Additionally, Xorg is also non-default, we use Wayland since
> > some
> >
> > time.
>
> That's correct, on the Fedora Workstation using GNOME - But Wayland
> is a protocol, just like X11, it requires a display server which is
> gnome-shell, and Alexei mentioned in the bug he's using another
> spin instead, so no Wayland there.
>
> So indeed, that bug would unlikely affect the default Fedora
> Workstation.
>
You don't seem to mind shipping Fedora 32 with a broken git snapshot
of the intel drivel. What are realistic chances to get it fixed
eventually given apparent lack of testing? Therefore, I asked to
downgrade it.
so I guess Intel drive is not the default drive ...
I built and tested xorg-x11-drv-intel-2.99.917-43.20190621.fc31.src.rpm
[1] for a long time without problems , you may try it ... . Now I
bought a new laptop so I can't test it anymore.
HTH
[1]
I can test modesetting on Gen3 GMA 3150 if that is easy. I dusted
off
this netbook for my kids' distant learning during COVID19. I would
not be surprised if more old junk surfaces on your bugzilla soon.
_______________________________________________devel mailing list --
devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org --
Sérgio M. B.