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
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
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
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
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,
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,
I don't know what it's like with GNOME, but running KDE spin with the
compositor set to use XRender APIs, I have had no issues with various Nvidia
cards both without their nasty proprietary code thrown into an otherwise
pristine system.
On March 26, 2019 7:13:18 PM EDT, Wolfgang Ulbrich
I noticed that with f30-beta-1.7 an installation with a 1030GT nvidia card is
much improved.
First time since more than 1 year that you can really use a livecd for
installation without thinking ` better finishing the installation as far as
possible`.
Thanks a lot ajax.
But honestly, for
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
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
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,
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,
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
13 matches
Mail list logo
