Created attachment 13796 [details]
update-errors.log

Here comes what is to be seen, yet. - and I am feeling ready to have a reboot now.

Please check for existing bugs before creating new ones.

Duplicate of bug 28055

*** This bug has been marked as a duplicate of bug 28055 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED

And regarding "missing" modules. They are not missing but this is the basic concept of dracut and can easily be understood by reading the relevant documentation.

The man pages for dracut are a good starting point to understand the whole concept.

https://man7.org/linux/man-pages/man7/dracut.modules.7.html 6
https://linux.die.net/man/8/dracut 2

"dracut creates an initial image used by the kernel for preloading the block device modules (such as IDE, SCSI or RAID) which are needed to access the root filesystem."

"dracut uses a modular system to build and extend the initramfs image."

"Adding dracut Modules
Some dracut modules are turned off by default and have to be activated manually. You can do this by adding the dracut modules to the configuration file
/etc/dracut.conf or /etc/dracut.conf.d/myconf.conf. See dracut.conf(5). You can also add dracut modules on the command line by using the -a or --add
option:"

Only modules that are needed for your hardware/software setup are installed and get loaded.

  I just know that dracut did not throw any of these errors before. The modules requested by dracut here go clearly beyond a minimal setting: f.i. I don´t have an SCSI controller on that notebook (though on other legacy systems I do). Pentium4 systems like the one being tested here are too old for the TPM (Trusted Platform Module, since 2010). I didn´t enable any of these modules manually either. Some things like memstrack appear to need packaging. Finally there are some other error messages like "'systemd-initrd' depends on 'systemd', which can't be installed". Systemd is of course present on that system, though the message appears to be about a systemd-dracut module. The question here isn´t that much on how to add a dracut module but how to remove unneeded dracut modules and how to determine what a specific dracut module does. Also it would be interesting for me to know 'why the new messages': is software/ are dracut modules being added or repackaged? If yes my laudation on the Mageia team to bring everything on rail!

No, that report isn´t about the missing white spaces in dracut.conf, but about on what happens if you fix that problem!

Resolution: DUPLICATE => (none)
Ever confirmed: 1 => 0
Status: RESOLVED => UNCONFIRMED

actually the dracut messages has been there for eons, and are informal ones

It's just that we have silenced some of the output from dracut, so those now stand out...

just compare the output of the older

dracut -f

and the now used

dracut -fq


I guess we need to patch dracut to not output the informal messages by default... and maybe replace with some "oneliner" so people know we updated the initrd

Please don't abuse bugzilla again for your basic user education! Please use the forum if you have questions about basics of dracut and how it operates the same on all linux distributions since the beginning.

Use any other linux distribution and see the same messages!

Dracut produces messages like dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found!" as this module is not needed on this system for creation of the initramfs.

The message regarding systemd is on purpose and this can can simply be identified by inspecting the content of /etc/dracut.conf.d/51-mageia-resume.conf:
"# Do not include the network module by default which saves about 10megs
# Users can still generate a network friendly initrd by editing this file
# or overriding omit_dracutmodules from another config file
omit_dracutmodules+=" network systemd "

So we ommit on purpose the dracut modules "network" and "systemd" as this are also basics how dracut works.

If you try to install all unneded modules like you did (see your output: # urpmi nvme-cli pcsc-lite squashfs-tools open-iscsi connman mksh tpm2-tools cifs-tools rng-utils) you only blow up your initramfs and increase the booting time of your machine. Congratulations!



Please do a basic research:
https://github.com/dracutdevs/dracut/blob/master/README.md
https://github.com/dracutdevs/dracut/blob/master/man/dracut.asc
https://github.com/dracutdevs/dracut/blob/master/man/dracut.usage.asc

Turning this into INVALID.

Resolution: (none) => INVALID
Status: UNCONFIRMED => RESOLVED

(In reply to Thomas Backlund from comment #6)
 
> I guess we need to patch dracut to not output the informal messages by
> default... and maybe replace with some "oneliner" so people know we updated
> the initrd

Other major distributions like openSUSE don't suppress this informational messages. Users who are able to use a terminal, normaly know how to deal with basic terminal output. Suppressing this messages because of some "confused" users makes it harder for all who need and want this output (either for troubleshooting or debugging or simply self education...).

Just fyi. In Mageia 8 ...
# dracut -f 2>&1|grep systemd
dracut: systemd-initrd needs systemd in the initramfs
dracut: systemd-networkd needs systemd in the initramfs
dracut: dracut module 'rngd' depends on 'systemd', which can't be installed
dracut: dracut-systemd needs systemd-initrd in the initramfs
dracut: dracut-squash only supports systemd bases initramfs
dracut: dracut module 'rngd' depends on 'systemd', which can't be installed
dracut: dracut-squash only supports systemd bases initramfs

It's about whether systemd gets loaded from the initrd before switching root
or loaded from /usr/lib/systemd/systemd on the root file system after the root
pivot. Mageia loads after.

CC: (none) => davidwhodgins

(In reply to sturmvogel from comment #8)
> (In reply to Thomas Backlund from comment #6)
>  
> > I guess we need to patch dracut to not output the informal messages by
> > default... and maybe replace with some "oneliner" so people know we updated
> > the initrd
> 
> Other major distributions like openSUSE don't suppress this informational
> messages. Users who are able to use a terminal, normaly know how to deal
> with basic terminal output. Suppressing this messages because of some
> "confused" users makes it harder for all who need and want this output
> (either for troubleshooting or debugging or simply self education...).


Yeah, I did not mean to suppress them completely from normal usage, only so one suppress them when requested with a flag or so... 

technically when I request something to be quiet "-q", I'd expect it to be so :)

but we'll see if I get to it or not...

Supressing a warning or error message is under normal circumstances not the right way to deal with it (i.e. compare with gcc -Wall: usually the messages point you to an error if it is not exactly that what you want to do what the message says). I don´t understand why you do not simply disable the modules not needed by Mageia (like systemd-loading from initrd which I have not heard of before - by the way what would be the advantage in doing so??). I´d think it should be possible to switch on/off modules that pertain to a specific hardware configuration like scsi, tpm or pcscd depending on whether you need that for your boot process. Pcscd is a pleasure if your root file system should reside on a PCCard/PCMCIA CompactFlash to give you an example, but if not you don´t want to bloat your initrd with a kernel module and additional code for handling pccards. Basically it would be the kernel module that bloated the initrd and not  a few lines of script code to handle it (which could then simply remain in the initrd whether of use or not). If yes, please tell so and don´t be unfriendly if someone reports there being an error message (which apparently shouldn´t be there). Why not make an /etc/dracut.conf.d/disabled/ or /etc/dracut.conf.disabled/ folder and tell explicitly which modules are not supported and/or used by Mageia??

(In reply to Elmar Stellnberger from comment #11)

> I don´t understand why you do not simply disable the modules not needed by Mageia
> .... Why not make an
> /etc/dracut.conf.d/disabled/ or /etc/dracut.conf.disabled/ folder and tell
> explicitly which modules are not supported and/or used by Mageia??

You simply do not understand how dracut works. ALL modules are supported. The needed modules depend on the users hardware and software environment. So omiting to much modules will screw users setup. For modules that get not loaded, dracut shows an informal message "can not install". This only means, that this particular module don't get loaded into initramfs as it is not needed for this particular machine setup.

If you wan't to learn something about how dracut works, read the documentation (links provided).
Or install another major distribution like openSUSE and have a look there. They dont suppress any of the dracut messages. That means every time you update kernel/grub/kernel module you get the complete unfiltered output of dracut. It's quite impressive...

... and what will you tell me about there being no memstrack package available neither for x86, nor for amd64?

It's easy to find the info on the package.
https://awesomeopensource.com/project/ryncsn/memstrack

It's a low level debugging tool. Not something any regular users or most
developers can use.

It isn't packaged for Mageia as no Mageia packager has chosen to add and
maintain the package for Mageia. The type of people that can make use of
it are the same people who can easily install it themselves from the
upstream source.

With packages that are not written by Mageia packagers, it's normal to
apply Mageia specific patches when it's needed to get the package to work.

Keeping things as close to what comes from the writers of the packages makes
it easier to maintain.

Just because the majority of Mageia users do not use some of the available
features doesn't mean others should not be allowed to, or have it made different
than what they will will encounter on other distributions.

As above, this is not the place to have this discussion. Please move the
discussion to the discuss mailing list or one of the forums.

(In reply to Dave Hodgins from comment #9)
Having just installed memstrack I have the problem that memstrack´s messages don´t end up in the system journal (though being displayed on screen). Its doc/README says that I should rebuild the initrd but that does not seem to do what is desired since dracut still complains it can not install memstrack (package installed) because of systemd. Apparently I need to get systemd started by the initrd to accomplish this. How do I do that using Mageia? 
BTW, please don´t strip the error messages; they appear to be meaningful.

As per comment 14, bugzilla is not the place for user education.

Ask on the dev or discuss mailing list, and I'll answer.