On Sat, 2016-05-21 at 22:50 -0400, Felix Miata wrote: > > Nomodeset has three primary purposes: > > 1-workaround for Anaconda, which can't always work with all hardware. It > causes fallback to a low-performance generic Xorg video driver, good only to > make X work at all when something is broken. This is not really accurate. There is nothing special about anaconda. (If anything it's *more* likely to work than GNOME or KDE, as it requires no 3D acceleration). The boot entry is provided as a workaround to get the system installed when there is a bug preventing the adapter working with the native driver *at all*, not just in anaconda... > Only in case 2 should it be included in a normal Grub menu. Unfortunately, > when needed for case 1, it typically remains included in in Grub > configuration post-installation, ...so this is not "unfortunately". It is intended. As I already said: if you need 'nomodeset' to install, you likely need it to boot the installed system too. It would make no sense to leave it out of the installed system, as there would then be a very high chance that the installed system wouldn't boot. > which causes grief for those who aren't > aware of its nature and need for removal as a part of installation cleanup. > Anaconda simply doesn't have the sophistication to do that kind of cleanup. Sure it does. It could easily *not* include nomodeset in the installed system kernel parameters if we thought that made sense. But we don't think that. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
