Comment # 14 on bug 1110041 from Felix Miata

(In reply to Steffen Winterfeldt from comment #13)
> In my view this is not so much about adding and removing a boot option but
> more about helping to work around video driver problems.

Why does it seem so common for users to be unable to install without disabling
KMS? If this could be answered with a good solution, then $SUBJECT would be
functionally moot.

> And here nomodeset
> is just an easy band-aid to get the installation done. What's missing is
> some guidance after that to help the user to configure the graphics card more
> or less optimally. Maybe simply a pointer to some landing page on
> opensuse.org.

Steffen seems to embrace my macro/meta thought processes leading to filing
this. It seems as though every user of:

    1-Optimus of any age
    2-recent AMD gfx
    3-NVidia gfx, mostly recent, but not necessarily

seems to be unable to install without using nomodeset (or textmode). But
nomodeset is incompatible with the distribution as installed, that is, software
entirely from openSUSE OSS and Non-OSS repos, software that has come through
the QA and release processes. Users who do not in fact have hardware that is
too new to be supported by the software ought to be able to enjoy a reasonably
usable installation result, one that uses the FOSS video drivers to run X. That
isn't happening when nomodeset is on the installer cmdline, and that is bad for
the distribution as well as the users.

The mailing list and forum assistants seem to be presuming in virtually every
case that non-FOSS drivers are supposed to follow completion of initial
installation. With Optimus this may be true, if Bumblebee won't work without a
proprietary NVidia component, but it shouldn't be otherwise. Even though the
bandaid worked to get the installation "completed", this ultimately means KMS
must not be defeated via cmdline - the FOSS drivers provided by the
distribution depend on KMS.