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 compatible video driver (such as
'vesa'). This mechanism should work correctly, launching the installer
or desktop and attempting to use the generic driver."
should no longer apply to Beta - i.e. that it should no longer be a
Basic or Beta criterion.
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, and general improvement in the reliability and
coverage of the major drivers for the major graphics hardware
manufacturers) and inherently less likely to work (due to the general
trend of work on kernel modesetting and Wayland) than it used to be.
For context, it is worth noting that the *feature* predates the
introduction of both kernel modesetting *and* Wayland to Fedora. What
the feature initially did was tell anaconda to write an X config file
specifying the 'vesa' driver (instead of working out the correct
'native' driver for the adapter and writing a config file specifying
that). After KMS was introduced in Fedora 10, the mechanism was tweaked
to also pass the 'nomodeset' kernel parameter to disable KMS. Around
2012 (https://bugzilla.redhat.com/show_bug.cgi?id=858270) we noticed
that the X config file mechanism was a bit superfluous as 'nomodeset'
alone could basically be relied on to force some sort of 'fallback
mechanism', and so the feature was simplified to *only* specify the
'nomodeset' kernel parameter (this is all it does now).
The *criterion* dates to 2010, in the Fedora 15 release cycle: it
appears in the Fedora 15 Alpha criteria but not the Fedora 14 Alpha
criteria. It was added on 2010-08-16:
The group at the meeting did not, however, make any further decisions,
so this leaves us with some open questions:
0) Do we generally agree with the decision made at the meeting? If
anyone (especially a subject matter expert) strongly believes the
decision was wrong and this should still be a Basic/Beta requirement,
please say so.
1) Should the criterion be modified somehow, but some requirement in
relation to some kind of fallback graphical mode be kept at Basic or
2) Should the criterion be moved to Final, unchanged or changed
3) Should the requirement just basically be dropped entirely as no
4) (This one mainly for ajax and airlied) to what extent does the
concept of a 'fallback option' for our supported desktop environments
and graphical servers still actually make sense? Could a different
implementation of the same basic idea be envisaged, and would it be
useful? If so, should we do that, and what would be the consequences
for the criteria?
I realize this is quite a big and fuzzy topic, but I'm hoping the
responses to this mail will clarify our path :) So if you have any kind
of useful information or strong opinions on the general area here,
please do contribute them, and hopefully a clearer way forward will
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
Could someone please point me to the current method to determine if a
package passed testing prior to being shipped? I'm having issues with a
package on Fedora 29 and the errors I'm seeing make it look like it was
shipped without ever actually having been installed and run... (ceph and
Yesterday I tried to install Fed30 beta-1.7 on a Dell Precision 5530.
(late 2018 model, i5-8300H & UHD graphics 630, came with Ubuntu 18.04
and had Fed29 installed and working without problems)
Almost immediately after the first few lines of the startup messages
the screen went black and nothing further happened. Could not get any
info in this state (Ctrl-Alt-Fn not working) and had to use long press
of power button to quit.
Today I booted Fed29 on this laptop and there were updates waiting.
Updated and restarted and to my surprise the same thing happened as
when trying to install Fed30 beta. After the Dell logo when you
would expect the gdm screen the screen went black and stayed that way.
The updates included the 5.03 kernel. I could now of course activate
the grub menu and boot with the old 4.20.16 kernel and look with
journalctl in the previous boot journal. There seem to be some things
going on with hibernate and suspend that should not happen and maybe
some other irregularities. Should I file a bug report for Fed30 or
for the kernel and what info should I attach.
I have no time for this today, will have to wait till tomorow.
I also found this: https://bugs.freedesktop.org/show_bug.cgi?id=110193