[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-desktop-list
Subject:    Re: "Basic graphics mode" feature and criterion discussion
From:       Kamil Paral <kparal () redhat ! com>
Date:       2019-03-27 11:00:11
Message-ID: CA+cBOTdwViAFvnq3w+Zusqn2R1XQ21n6o5HA+nCPi+_NKgQsUA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Tue, Mar 26, 2019 at 9:31 PM Chris Murphy <lists@colorremedies.com>
wrote:

> My two cents:
>
> If there's a fallback option, and if the user selects it, they
> shouldn't end up in an unambiguous state. Right now we're seeing
> systems hanging. I'd rather see a crash than a hang where the user
> can't get to a shell, and sees no useful information on the screen
> that tells them why they're hung up; or even generically that "by now
> you should see a login screen and if you don't we've faceplanted
> somewhere, sorry".
>
> Maybe split the criterion:
>
> Basic criterion: installation media must have a basic video boot entry
> that uses the accepted fallback boot parameter(s), e.g. nomodeset. The
> criterion just means the media must have the menu entry, and that it
> passes something intentional for this purpose as a boot parameter.
>

Sounds good.


>
> Final criterion: installation media's basic video boot entry should
> either work (we get a successful graphical boot), or it should
> faceplant in some unambiguous way.
>

I'd rather require it to just work. Based on Ajax's response that the code
path is here to stay and they still need to support it because of VMs and
fresh new graphics cards.

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar \
26, 2019 at 9:31 PM Chris Murphy &lt;<a \
href="mailto:lists@colorremedies.com">lists@colorremedies.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">My two cents:<br> <br>
If there&#39;s a fallback option, and if the user selects it, they<br>
shouldn&#39;t end up in an unambiguous state. Right now we&#39;re seeing<br>
systems hanging. I&#39;d rather see a crash than a hang where the user<br>
can&#39;t get to a shell, and sees no useful information on the screen<br>
that tells them why they&#39;re hung up; or even generically that &quot;by now<br>
you should see a login screen and if you don&#39;t we&#39;ve faceplanted<br>
somewhere, sorry&quot;.<br>
<br>
Maybe split the criterion:<br>
<br>
Basic criterion: installation media must have a basic video boot entry<br>
that uses the accepted fallback boot parameter(s), e.g. nomodeset. The<br>
criterion just means the media must have the menu entry, and that it<br>
passes something intentional for this purpose as a boot \
parameter.<br></blockquote><div><br></div><div>Sounds good.<br></div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"> <br>
Final criterion: installation media&#39;s basic video boot entry should<br>
either work (we get a successful graphical boot), or it should<br>
faceplant in some unambiguous way.<br></blockquote><div><br></div>I&#39;d rather \
require it to just work. Based on Ajax&#39;s response that the code path is here to \
stay and they still need to support it because of VMs and fresh new graphics \
cards.<br></div><div class="gmail_quote"><br></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
desktop mailing list -- desktop@lists.fedoraproject.org
To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org


[prev in list] [next in list] [prev in thread] [next in thread]