http://bugzilla.opensuse.org/show_bug.cgi?id=1110041 Neil Rickert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx@yahoo.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110041 http://bugzilla.opensuse.org/show_bug.cgi?id=1110041#c8 --- Comment #8 from Felix Miata --- What about having included a #2 (extra) stanza added to first Grub menu page 1 specifically labeled to have or not have nomodeset, opposite of its presence or not during installation in #1 stanza, if both Intel and AMD or NVidia gfx present? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110041 http://bugzilla.opensuse.org/show_bug.cgi?id=1110041#c11 --- Comment #11 from Felix Miata --- https://forums.opensuse.org/showthread.php/533479-Installing-Leap-15-error is a fresh example of how nomodeset trouble starts: "I was trying to install openSUSE on my new laptop, but installator stuck at "Starting hardware detection", I waited about 2 hours and nothing was done. I think that in could be because I have got NVIDIA graphic card, that was problem when I was trying to install other linux distros. I was trying to change installation resolution, but on my installation menu there wasn't any option for it. F3 didn't work too. Help!" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110041 http://bugzilla.opensuse.org/show_bug.cgi?id=1110041#c14 --- Comment #14 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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110041 http://bugzilla.opensuse.org/show_bug.cgi?id=1110041#c16 --- Comment #16 from Stefan Dirsch --- Well, I'm not convinced changing the behaviour would help to improve the situation. 1) nvidia nomodeset doesn't hurt afterwards when switching to NVIDIA driver unless you want to use the experimental modeset feature of this driver, which needs to be enabled manually (nvidia_drm.modeset=1). Otherwise you need to use fbdev driver anyway unless updated kernels fix the issue with modesetting in nouveau driver, which is unfortunately unlikely. 2) AMD nomodeset is also still needed afterwards (fallback to fbdev driver) unless an updated kernel fixes the issue in the radeon/amdgpu driver, which doesn't happen often. 3) Optimus Long, sad story. But easiest workaround is still disabling NVIDIA GPU in BIOS/Firmware (if this is possible). Otherwise disabling nouveau driver (kernel module) completely should help. Which means intel only. Things are improving a lot with Optimus on TW when using NVIDIA driver. See bsc#1103816. But in that case you disable nouveau driver anyway. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1110041 http://bugzilla.opensuse.org/show_bug.cgi?id=1110041#c20 --- Comment #20 from Felix Miata --- (In reply to Stefan Dirsch from comment #2)

So if nomodeset is needed during installation, it's probably also needed afterwards on the installed system.

Is it? https://forums.opensuse.org/showthread.php/534802-Unable-to-install-Tumblewe...) suggests not. That it is so often needed for installation to succeed suggests a significant difference between X during and after installation. Why is XVideo= a discrete linuxrc option when video= from the kernel's modedb could have the same effect? When xf86-video-intel is in use, Xorg dutifully obeys e.g. video=1440x900 where supported and not explicitly overridden by xrandr or xorg.conf or some DE setting. -- You are receiving this mail because: You are on the CC list for the bug.