Schedule for Wednesday's FESCo Meeting (2021-02-10)
by Miro Hrončok
Following is the list of topics that will be discussed in the
FESCo meeting Wednesday at 15:00UTC in #fedora-meeting-2 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2021-02-10 15:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
Nonresponsive maintainer: Praveen Kumar kumarpraveen
https://pagure.io/fesco/issue/2551
APPROVED (+3,0,-0)
May a package require ISA extensions (e.g., AVX-512)?
https://pagure.io/fesco/issue/2569
APPROVED (+6,0,-0)
= Followups =
#2572 Proposal: Abstain (0) votes should be split evenly between +1 and -1 votes
https://pagure.io/fesco/issue/2572
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
3 years, 2 months
Re: New memory tester application potentially to replace memtest86+: PCMemTest
by Chris Murphy
On Mon, Feb 8, 2021 at 4:47 PM Martin Whitaker
<mailing-lists(a)martin-whitaker.me.uk> wrote:
>
> On 07/02/2021 22:23, Chris Murphy wrote:
> > On Sun, Feb 7, 2021 at 2:08 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
> >>
> >> Hey all,
> >>
> >> I discovered today that there's a new replacement for memtest86+ that
> >> appears to even have UEFI support called PCMemTest[0].
> >>
> >> The main reason I call out to this is because we don't have a memory
> >> tester offering in our UEFI boot variant for the Fedora live media,
> >> and this is actively maintained (unlike memtest86+, which we currently
> >> use...).
> >>
> >> Mageia is shipping this starting with Mageia 8[1], and we should
> >> consider shipping this with Fedora 34.
> >
> >
> > * A listed limitation: "When booted on a UEFI system, keyboard input
> > will only be seen if the CSM is enabled in the BIOS. Without this, the
> > test will run, but you will be unable to alter the configuration."
> >
> > - How does a CSM provide keyboard input to an EFI application? Or does
> > this mean with CSM enabled, we'd use the BIOS version of the memory
> > tester; and with CSM disabled, we'd use the UEFI version of the memory
> > tester?
>
> On all the machines in my possession, enabling the CSM enables emulation
> of the keyboard controller ports (ports 0x60 and 0x64), even when booted
> in UEFI mode. That may not be true for all BIOSs of course.
OK. I'm confused (not unusual) and also ignorant of how the keyboard
driver situation works on UEFI without the CSM enabled. Because
without it enabled, I definitely have working keyboard on all my
systems in EFI shell. That suggests the keyboard driver is available,
isn't due to GRUB providing one.
I see GRUB has usb_keyboard.mod but I don't see it as one of the
modules we're baking into Fedora's grubx64.efi.
https://src.fedoraproject.org/rpms/grub2/blob/rawhide/f/grub.macros
I guess I'm trying to figure out the scope of the "does not have
working keyboard with native UEFI plus Secure Boot" problem.
> > - As far as I'm aware, enabling CSM requires disabling UEFI Secure Boot.
>
> Probably so. At which point you are limited to running the memory tests
> with the default configuration (which is to run all tests using a single
> processor).
>
> As I don't use secure boot, I wasn't really motivated to start writing a
> replacement keyboard driver.
Yeah I definitely do not want Fedora in a position where anyone has to
give users advice like "you need to disable UEFI Secure Boot" in order
to do X. Be it testing RAM or anything else.
--
Chris Murphy
3 years, 2 months
our containers with alias vim=vi
by clime
Hello,
could Fedora and CentOS containers for docker and podman come with
`alias vim=vi` in ~/.bashrc?
I would very much welcome it as I am used to type vim everywhere but
if vi starts instead I am happy too. I know that the solution is to
create a customized container but often I want to try something on
vanilla containers from the whole range.
Didn't want to write about this first but maybe there are more people
with the same problem.
clime
3 years, 2 months
Orphaned: all my elementary AppCenter application packages
by Fabio Valentini
Hi everybody,
Due to lack of time and interest, I have orphaned the elementary
AppCenter applications I have maintained so far:
- agenda (simple todo-list)
- appeditor (GUI .desktop file and menu editor)
- dippi (display DPI / scaling factor calculator)
- harvey (visual WCAG color contrast compliance checker)
- notejot (simple sticky notes, needs an update to 2.6.x series to fix bugs)
- sequeler (GUI database manager with libgda backend, supports
connecting to MariaDB / MySQL, PostgreSQL, SQLite, etc.)
I no longer use any of those applications and do not have time or
interest to maintain them further. If somebody wants to pick them up,
they should be in good shape and up-to-date - with the exception of
notejot, which should be updated to the latest version.
Fabio
3 years, 2 months