MGA9x64 slowness issue during boot

[Markus Robert Kessler]

Hello everyone!

A few years ago there was the same issue with MGA6 or 7 on a notebook
"ESPRIMO Mobile D9510 1.0":

I disabled the not needed Wifi interface in the BIOS, but during boot
network service hung. It took / takes around one minute just for starting
the network service.

Someone (cannot remember who, maybe David H.?) gave me some advice how to
force the system to not include Wifi interface via (I think so) UDEV rule
or so.

This worked fine during lifetime of the OS. In the meantime I completely
overwrote this to install MGA9. I forgot to document the changes made. The
message in alt.os.linux.mageia is also no longer available, so not
possible to look it up.

Whenever I deleted
/etc/sysconfig/network-scripts/ifcfg-wlp8s0
manually, during next boot it is there again, but without execute flag.

Can anyone point me in the right direction how to get rid of this please?

Thanks!

Best regards,

Markus

[William Unruh]

Post by Markus Robert Kessler
Hello everyone!
A few years ago there was the same issue with MGA6 or 7 on a notebook
I disabled the not needed Wifi interface in the BIOS, but during boot
network service hung. It took / takes around one minute just for starting
the network service.
Someone (cannot remember who, maybe David H.?) gave me some advice how to
force the system to not include Wifi interface via (I think so) UDEV rule
or so.
This worked fine during lifetime of the OS. In the meantime I completely
overwrote this to install MGA9. I forgot to document the changes made. The
message in alt.os.linux.mageia is also no longer available, so not
possible to look it up.
Whenever I deleted
/etc/sysconfig/network-scripts/ifcfg-wlp8s0
manually, during next boot it is there again, but without execute flag.
Can anyone point me in the right direction how to get rid of this please?

One thing you can do is to hit Esc as soon as the bootup starts so that
all of the boot commands scroll by and you can see what it is hanging
on.
The system will look at your hardware and install missing stuff during
boot, so it thinks that the wifi card is a newly installed card and
helpfully installs it for you.

It is not clear to me why you care if the system initiallises the wifi
software
assuming the hardware exists. You do not have to use it.

Also ifconfig-wlp8s0 is the wrong thing to attack. That is the software to
set up the wireless to be useful to you. It does not stop
the wireless from being installed and being opertional. It just stops it
from being properly set up. You could stop the module driving the wifi
chipset from being initialised (/etc/module*) by not loading the module.
But Why?

[Markus Robert Kessler]

Post by William Unruh

Post by Markus Robert Kessler
Hello everyone!
A few years ago there was the same issue with MGA6 or 7 on a notebook
I disabled the not needed Wifi interface in the BIOS, but during boot
network service hung. It took / takes around one minute just for
starting the network service.
Someone (cannot remember who, maybe David H.?) gave me some advice how
to force the system to not include Wifi interface via (I think so) UDEV
rule or so.
This worked fine during lifetime of the OS. In the meantime I
completely overwrote this to install MGA9. I forgot to document the
changes made. The message in alt.os.linux.mageia is also no longer
available, so not possible to look it up.
Whenever I deleted /etc/sysconfig/network-scripts/ifcfg-wlp8s0
manually, during next boot it is there again, but without execute flag.
Can anyone point me in the right direction how to get rid of this please?

One thing you can do is to hit Esc as soon as the bootup starts so that
all of the boot commands scroll by and you can see what it is hanging
on.
The system will look at your hardware and install missing stuff during
boot, so it thinks that the wifi card is a newly installed card and
helpfully installs it for you.
It is not clear to me why you care if the system initiallises the wifi
software assuming the hardware exists. You do not have to use it.
Also ifconfig-wlp8s0 is the wrong thing to attack. That is the software
to set up the wireless to be useful to you. It does not stop the
wireless from being installed and being opertional. It just stops it
from being properly set up. You could stop the module driving the wifi
chipset from being initialised (/etc/module*) by not loading the module.
But Why?

Hi,

the annoying thing is the relatively long time to wait during boot:

https://www.dipl-ing-kessler.de/tmp/mga9boot_10fps.mp4

It runs fast and seamlessly until network.service is invoked and then
something blocks everything for nearly one minute. In the movie there is
nothing inserted, no slow motion or so. Just original recording.

That was why I asked here, since some years ago I got a hint (from, cannot
remember, Bit T., Dave H., etc.) how to prevent this and massively speed
up booting by inventing some udev rules or similar.

Well, I did not expect the issue to occur again in MGA9, so I just
overwrote the old install without saving everything.

Any idea how to get around this?

Thanks!

Best regards,

Markus

[David W. Hodgins]

Post by Markus Robert Kessler

Post by William Unruh

Post by Markus Robert Kessler
Hello everyone!
A few years ago there was the same issue with MGA6 or 7 on a notebook
I disabled the not needed Wifi interface in the BIOS, but during boot
network service hung. It took / takes around one minute just for
starting the network service.
Someone (cannot remember who, maybe David H.?) gave me some advice how
to force the system to not include Wifi interface via (I think so) UDEV
rule or so.
This worked fine during lifetime of the OS. In the meantime I
completely overwrote this to install MGA9. I forgot to document the
changes made. The message in alt.os.linux.mageia is also no longer
available, so not possible to look it up.
Whenever I deleted /etc/sysconfig/network-scripts/ifcfg-wlp8s0
manually, during next boot it is there again, but without execute flag.
Can anyone point me in the right direction how to get rid of this please?

One thing you can do is to hit Esc as soon as the bootup starts so that
all of the boot commands scroll by and you can see what it is hanging
on.
The system will look at your hardware and install missing stuff during
boot, so it thinks that the wifi card is a newly installed card and
helpfully installs it for you.
It is not clear to me why you care if the system initiallises the wifi
software assuming the hardware exists. You do not have to use it.
Also ifconfig-wlp8s0 is the wrong thing to attack. That is the software
to set up the wireless to be useful to you. It does not stop the
wireless from being installed and being opertional. It just stops it
from being properly set up. You could stop the module driving the wifi
chipset from being initialised (/etc/module*) by not loading the module.
But Why?

Hi,
https://www.dipl-ing-kessler.de/tmp/mga9boot_10fps.mp4
It runs fast and seamlessly until network.service is invoked and then
something blocks everything for nearly one minute. In the movie there is
nothing inserted, no slow motion or so. Just original recording.
That was why I asked here, since some years ago I got a hint (from, cannot
remember, Bit T., Dave H., etc.) how to prevent this and massively speed
up booting by inventing some udev rules or similar.
Well, I did not expect the issue to occur again in MGA9, so I just
overwrote the old install without saving everything.
Any idea how to get around this?

In /etc/sysconfig/network-scripts/ifcfg-wlan0 (or whatever file the wireless is using) change
ONBOOT=yes
to
ONBOOT=no

That's for wireless hardware that does exist. For wireless config files that are left over from
a different configuration, delete the ifcfg-w???? file.

I use net.ifnames=0 in the kernel command line in /etc/default/grub as I know I won't have
more than one ethernet interface and one wireless interface, so I can just use the old names
of eth0 and wlan0.

Regards, Dave Hodgins

[Markus Robert Kessler]

On Sat, 25 Jan 2025 16:28:18 -0500, Markus Robert Kessler

Post by Markus Robert Kessler

Post by William Unruh

Post by Markus Robert Kessler
Hello everyone!
A few years ago there was the same issue with MGA6 or 7 on a notebook
I disabled the not needed Wifi interface in the BIOS, but during boot
network service hung. It took / takes around one minute just for
starting the network service.
Someone (cannot remember who, maybe David H.?) gave me some advice
how to force the system to not include Wifi interface via (I think
so) UDEV rule or so.
This worked fine during lifetime of the OS. In the meantime I
completely overwrote this to install MGA9. I forgot to document the
changes made. The message in alt.os.linux.mageia is also no longer
available, so not possible to look it up.
Whenever I deleted /etc/sysconfig/network-scripts/ifcfg-wlp8s0
manually, during next boot it is there again, but without execute flag.
Can anyone point me in the right direction how to get rid of this please?

One thing you can do is to hit Esc as soon as the bootup starts so
that all of the boot commands scroll by and you can see what it is
hanging on.
The system will look at your hardware and install missing stuff during
boot, so it thinks that the wifi card is a newly installed card and
helpfully installs it for you.
It is not clear to me why you care if the system initiallises the wifi
software assuming the hardware exists. You do not have to use it.
Also ifconfig-wlp8s0 is the wrong thing to attack. That is the
software to set up the wireless to be useful to you. It does not stop
the wireless from being installed and being opertional. It just stops
it from being properly set up. You could stop the module driving the
wifi chipset from being initialised (/etc/module*) by not loading the
module.
But Why?

Hi,
https://www.dipl-ing-kessler.de/tmp/mga9boot_10fps.mp4
It runs fast and seamlessly until network.service is invoked and then
something blocks everything for nearly one minute. In the movie there
is nothing inserted, no slow motion or so. Just original recording.
That was why I asked here, since some years ago I got a hint (from,
cannot remember, Bit T., Dave H., etc.) how to prevent this and
massively speed up booting by inventing some udev rules or similar.
Well, I did not expect the issue to occur again in MGA9, so I just
overwrote the old install without saving everything.
Any idea how to get around this?

In /etc/sysconfig/network-scripts/ifcfg-wlan0 (or whatever file the
wireless is using) change ONBOOT=yes to ONBOOT=no
That's for wireless hardware that does exist. For wireless config files
that are left over from a different configuration, delete the
ifcfg-w???? file.
I use net.ifnames=0 in the kernel command line in /etc/default/grub as I
know I won't have more than one ethernet interface and one wireless
interface, so I can just use the old names of eth0 and wlan0.
Regards, Dave Hodgins

Hello Dave,

In /etc/sysconfig/network-scripts/ifcfg-wlan0 (or whatever file the
wireless is using) change ONBOOT=yes to ONBOOT=no

Firstly, I tried to deactivate loading the kernel module for that device,
but your solution is easier and much better. Thanks!

B.t.w., before applying your hint, I was wondering why the first boot
after power-on was always fast, but every following warm-boot was slow,
waiting for network.service.
After modifying the ifcfg file, booting is always fast now.

Thanks again,
best regards,

Markus

[David W. Hodgins]

On Sat, 25 Jan 2025 14:34:13 -0500, William Unruh <***@invalid.ca> wrote:
<snip>

Post by William Unruh
Also ifconfig-wlp8s0 is the wrong thing to attack. That is the software to
set up the wireless to be useful to you. It does not stop
the wireless from being installed and being opertional. It just stops it
from being properly set up. You could stop the module driving the wifi
chipset from being initialised (/etc/module*) by not loading the module.
But Why?

The ifcfg-wlp8s0 is the right file to change.

By changing ONBOOT=yes to ONBOOT=no then during boot /etc/sysconfig/network-scripts/ifup
will know not to wait for that device to get an ip address (or timeout).

If the ifcfg-w???? file is just deleted, it will be recreated with ONBOOT=yes if the device is found
during the next boot.

You can use mcc to change the "Start the connection at boot" flag for the device, but I find it
easier to just edit the file.

Regards, Dave Hodgins