The screen with the query marks is still there, but disappears after a
few seconds, and a normal boot follows. I am treating it as a nuisance,
like the family friend who had 3 message boxes on booting Windows. He
treated them as normal for the OS, and said that he was lucky to have
only 3.

Looking at the journal, the following line looked puzzling but normal:

Unknown kernel command line parameters "splash noiswmd
BOOT_IMAGE=/boot/vmlinuz-5.17.11-desktop-1.mga8 vga=791", will be passed
to user space.

/etc/default/grub has it as follows:

GRUB_CMDLINE_LINUX_DEFAULT="ro splash quiet noiswmd
root=UUID=f71c302b-10b7-4849-ab69-ab90c91a8ee0 audit=0
resume=UUID=36eb141e-fa35-4df0-bce4-b169d7177ecb vga=791"

Somehow, the boot process reads the parameters in a different sequence.
I don't need the "resume." I have only just noticed that "nokmsboot" is
not there. That is because I was running the "nouveau" driver. It needs
to be fixed.

On Tue, 07 Jun 2022 13:18:17 -0400, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:

> The screen with the query marks is still there, but disappears after a
> few seconds, and a normal boot follows. I am treating it as a nuisance,
> like the family friend who had 3 message boxes on booting Windows. He
> treated them as normal for the OS, and said that he was lucky to have
> only 3.

Unless it causes problems, best to just ignore it.

> Looking at the journal, the following line looked puzzling but normal:
> Unknown kernel command line parameters "splash noiswmd
> BOOT_IMAGE=/boot/vmlinuz-5.17.11-desktop-1.mga8 vga=791", will be passed
> to user space.

Quite normal. The kernel command line is used to pass parameters to the kernel,
and to pass parameters to systemd and other processes.

> /etc/default/grub has it as follows:
> GRUB_CMDLINE_LINUX_DEFAULT="ro splash quiet noiswmd
> root=UUID=f71c302b-10b7-4849-ab69-ab90c91a8ee0 audit=0
> resume=UUID=36eb141e-fa35-4df0-bce4-b169d7177ecb vga=791"

I normally remove splash and quiet so that I can see the messages during boot.
Makes it easier to spot problems that may not be annoying later.

The noiswmd is to stop the mdadm process from taking control of intel raid
controllers. Systems that need it will not boot without it and it causes no
harm on other systems which is why it's included by default. You can safely
remove it if you're not using an intel hardware raid controller.

You can remove the resume if you never plan on using the hibernate feature.

> Somehow, the boot process reads the parameters in a different sequence.
> I don't need the "resume." I have only just noticed that "nokmsboot" is
> not there. That is because I was running the "nouveau" driver. It needs
> to be fixed.

I can never remember when nokmsboot is needed and when it must not be present.
If it's working without it, then don't add it.

Regards, Dave Hodgins

On 07.06.2022 at 14:06, David W. Hodgins scribbled:

> I can never remember when nokmsboot is needed and when it must not be
> present. If it's working without it, then don't add it.

As I understand it, it is only really needed if you're using the
proprietary Nvidia driver. With nouveau, or with AMD or Intel
graphics hardware, you don't need it.

--
With respect,
= Aragorn =

On 8/6/22 03:18, Doug Laidlaw wrote:
> The screen with the query marks is still there, but disappears after a
> few seconds, and a normal boot follows.  I am treating it as a nuisance,
> like the family friend who had 3 message boxes on booting Windows.  He
> treated them as normal for the OS, and said that he was lucky to have
> only 3.
>
> Looking at the journal, the following line looked puzzling but normal:
>
>  Unknown kernel command line parameters "splash noiswmd
> BOOT_IMAGE=/boot/vmlinuz-5.17.11-desktop-1.mga8 vga=791", will be passed
> to user space.

I removed splash also. I like the kernel messages

--
faeychild
Running plasmashell 5.20.4 on 5.15.43-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On 2022-06-07, faeychild <faeychild@nomail.afraid.org> wrote:
> On 8/6/22 03:18, Doug Laidlaw wrote:
>> The screen with the query marks is still there, but disappears after a
>> few seconds, and a normal boot follows.  I am treating it as a nuisance,
>> like the family friend who had 3 message boxes on booting Windows.  He
>> treated them as normal for the OS, and said that he was lucky to have
>> only 3.
>>
>> Looking at the journal, the following line looked puzzling but normal:
>>
>>  Unknown kernel command line parameters "splash noiswmd
>> BOOT_IMAGE=/boot/vmlinuz-5.17.11-desktop-1.mga8 vga=791", will be passed
>> to user space.
>
> I removed splash also. I like the kernel messages

I agree (although you can also put in nosplash). When it fails, you can
at least see where it failed. Mind you usually everything whizzes by at
such a speed that those read warnings are impossible to read.

Note that I also like to put in
dmesg -D
into /etc/rc.local, as otherwise those kernel messages really mess up
the consoles every time you want to use them.
I also put in

/bin/rm -f ~unruh/.config/autostart/skypeforlinux.desktop
into rc.local to get rid of skype always being started up after I have
used it once.

>
>

On Wed, 8 Jun 2022 03:18:17 +1000, Doug Laidlaw wrote:
> The screen with the query marks is still there, but disappears after a
> few seconds, and a normal boot follows. I am treating it as a nuisance,
> like the family friend who had 3 message boxes on booting Windows. He
> treated them as normal for the OS, and said that he was lucky to have
> only 3.
>
> Looking at the journal, the following line looked puzzling but normal:
>
> Unknown kernel command line parameters "splash noiswmd
> BOOT_IMAGE=/boot/vmlinuz-5.17.11-desktop-1.mga8 vga=791", will be passed
> to user space.
>
> /etc/default/grub has it as follows:
>
> GRUB_CMDLINE_LINUX_DEFAULT="ro splash quiet noiswmd
> root=UUID=f71c302b-10b7-4849-ab69-ab90c91a8ee0 audit=0
> resume=UUID=36eb141e-fa35-4df0-bce4-b169d7177ecb vga=791"
>
> Somehow, the boot process reads the parameters in a different sequence.
> I don't need the "resume." I have only just noticed that "nokmsboot" is
> not there. That is because I was running the "nouveau" driver. It needs
> to be fixed.

Might I suggest "noresume" instead of removing it. Serves as a reminder
that you disabled it. Example from my grub customization script

misc_flags="ipv6.disable=1 audit=0 splash=off plymouth.enable=0 noresume"

Me thinks/guesses the three asterisks come from plymouth. With an A type
personality I want as fast as boot as possible so I have it disabled.

Should be east enough to test. Just get to grub command line prompt
an add your changes then boot.

On 8/6/22 09:36, William Unruh wrote:

>
> I agree (although you can also put in nosplash). When it fails, you can
> at least see where it failed. Mind you usually everything whizzes by at
> such a speed that those read warnings are impossible to read.

They are a lot faster in this new box. I got talked into an SSD and
found the boot process to be vastly quicker. So is installation from a
stick

regards

--
faeychild
Running plasmashell 5.20.4 on 5.15.43-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso