vesa driver is forced through grub instead of xorg.conf

[Kamil Paral]

> It should in fact do both. The fact that it doesn't is a bug.
> 'nomodeset' will have the effect of forcing the use of vesa in the
> case
> of *most* drivers, these days, since they have no UMS code any more.
> But
> it's really more of a lucky side-effect, and it's not 100%; for
> drivers
> which do have UMS code, the right thing won't happen.
> 
> It's really the xdriver=vesa that's meant to work, and nomodeset was
> added because if you don't stop the KMS drivers from loading, they
> will
> conflict with the vesa driver. The intent is that nomodeset should be
> specified *and* a config file explicitly requesting the vesa driver
> (or,
> in fact, whatever driver is specified with xdriver=foo) should be
> created.
> 
> So we do need to fix the xdriver= function, really. File a bug.

Thanks for the reply, I adjusted the test case and reported a new bug:
https://bugzilla.redhat.com/show_bug.cgi?id=858270