Bug ID 1110041
Summary omit nomodeset from installation's proposal bootloader
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.1
Hardware x86-64
OS Other
Status NEW
Severity Enhancement
Priority P5 - None
Component YaST2
Assignee yast2-maintainers@suse.de
Reporter mrmazda@earthlink.net
QA Contact jsrain@suse.com
CC jreidinger@suse.com
Found By ---
Blocker ---

Created attachment 784521 [details]
.tgz of y2logs from test installation using nomodeset on Kaby Lake in UEFI mode

In mailing list thread "nomodeset abuses new users and their supporters"
https://lists.opensuse.org/yast-devel/2018-09/msg00035.html Josef R asked that
I "open bug report".

Time and time again, NVidia gfx and Optimus users are unable to install without
appending nomodeset to the installer's cmdline.
cf. https://bugzilla.opensuse.org/show_bug.cgi?id=822769 resolved feature
No mention is made in that bug if a feature request was ever filed. The bug
request was to make appending nomodeset easier for users.

Such trouble with installation is routinely followed by a new support request,
to resolve problems either with low resolution video modes, or black screens,
or
both. e.g.
https://forums.opensuse.org/showthread.php/533157-How-change-screen-resolution

More often than not, resolving this failure means the gratis supporters must
explain that
nomodeset needs to be removed from Grub configuration, and how to go about it,
which means temporarily at the Grub screen, and ultimately via
/etc/default/grub
and grub2-mkconfig.

Nomodeset is primarily for troubleshooting, not normal operation, main
exception being for users who post-installation add non-FOSS software. Those
users can add it or nouveau.modeset=0 back according to the instructions they
must follow to successfully add their non-FOSS software.

IMO it would be much a better user and support experience, and ultimately
better
for openSUSE's reputation, that when the YaST installer finds nomodeset has
been
used to install that, by default, it *not* be preserved in either
/etc/default/grub or in YaST's bootloader proposal.


You are receiving this mail because: