Re: "Basic graphics mode" feature and criterion discussion

2019-04-02 Thread Adam Williamson
On Tue, 2019-04-02 at 12:07 -0600, Chris Murphy wrote: > On Tue, Apr 2, 2019 at 4:19 AM Kamil Paral wrote: > > On Mon, Apr 1, 2019 at 9:04 PM Adam Williamson > > wrote: > > > "The boot menu for all release-blocking installer and live images > > > should include an entry which causes both

Re: "Basic graphics mode" feature and criterion discussion

2019-04-02 Thread Chris Murphy
On Tue, Apr 2, 2019 at 4:19 AM Kamil Paral wrote: > > On Mon, Apr 1, 2019 at 9:04 PM Adam Williamson > wrote: >> >> "The boot menu for all release-blocking installer and live images >> should include an entry which causes both installation and the >> installed system to use a generic, highly

Re: "Basic graphics mode" feature and criterion discussion

2019-04-02 Thread Kamil Paral
On Mon, Apr 1, 2019 at 9:04 PM Adam Williamson wrote: > "The boot menu for all release-blocking installer and live images > should include an entry which causes both installation and the > installed system to use a generic, highly compatible video driver (such > as 'vesa')." > Maybe change

Re: "Basic graphics mode" feature and criterion discussion

2019-04-01 Thread Ben Cotton
On Mon, Apr 1, 2019 at 3:04 PM Adam Williamson wrote: > So, here's the specific text I propose. At Basic we would change this > requirement: >> > To read only: > > "The boot menu for all release-blocking installer and live images > should include an entry which causes both installation and the

Re: "Basic graphics mode" feature and criterion discussion

2019-04-01 Thread Adam Williamson
On Tue, 2019-03-26 at 14:30 -0600, Chris Murphy 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,

Re: "Basic graphics mode" feature and criterion discussion

2019-03-27 Thread Kamil Paral
On Tue, Mar 26, 2019 at 9:31 PM Chris Murphy 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,

Re: "Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Chris Murphy
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

Re: "Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Julen Landa Alustiza
Due to the context and actual bugs, and what we see during the argues, the main idea about "work correctly" is that you should be able to launch a working desktop where typical use of some tools and specialy the installer process can be launched and executed with success. Yeah, with caveats, a

Re: "Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Adam Williamson
On Tue, 2019-03-26 at 16:02 -0400, Adam Jackson wrote: > So with the above caveat understood that "work correctly" has a bunch > of asterisks next to it and you will probably be able to tell that > you're using a fallback path, I don't think it's intrinsically less > likely that graphics fallback

Re: "Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Adam Jackson
On Tue, 2019-03-26 at 11:14 -0700, Adam Williamson wrote: > The justification for this is, I hope I am correctly representing all > views here (please say so if not), that this mechanism is both less > necessary (due to a general reduction in the amount of 'weird' graphics > hardware out there,

Re: "Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Adam Williamson
On Tue, 2019-03-26 at 15:33 -0400, Felix Miata wrote: > Adam Williamson composed on 2019-03-26 11:38 (UTC-0700): > > To be clear, this is about DDX drivers, not kernel drivers, right? Seeing > "driver" used willy nilly in discussing video issues and configuration is > confusing. The mail you're

Re: "Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Felix Miata
Adam Williamson composed on 2019-03-26 11:38 (UTC-0700): To be clear, this is about DDX drivers, not kernel drivers, right? Seeing "driver" used willy nilly in discussing video issues and configuration is confusing. > ...when a *new* graphics card comes out, one that the > nouveau driver

Re: "Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Adam Williamson
On Tue, 2019-03-26 at 11:14 -0700, Adam Williamson wrote: > > The justification for this is, I hope I am correctly representing all > views here (please say so if not), that this mechanism is both less > necessary (due to a general reduction in the amount of 'weird' graphics > hardware out there,

"Basic graphics mode" feature and criterion discussion

2019-03-26 Thread Adam Williamson
Hi folks! So at last week's Fedora 30 Beta Go/No-Go meeting, it was decided that the Basic release criterion: "Boot menu contents The boot menu for all supported installer and live images should include an entry which causes both installation and the installed system to use a generic, highly