you don't have those modules or you disabled them what's output of "lsmod" in booted kali if those modules will show then you have installed them and you just need to load them "insmod kernel_module" that's about modprobe about second you may have to set static address to your card what's output of dmesg | grep error and journalctl -xe

FIRST: for the modules, none of them are disabled or loaded
lsmod | grep efivar
efivarfs 16384 1
lsmod | grep raid
raid10 65536 0
raid456 180224 0
async_raid6_recov 24576 1 raid456
async_memcpy 20480 2 raid456,async_raid6_recov
async_pq 20480 2 raid456,async_raid6_recov
async_xor 20480 3 async_pq,raid456,async_raid6_recov
async_tx 20480 5 async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
raid6_pq 122880 4 async_pq,btrfs,raid456,async_raid6_recov
libcrc32c 16384 2 btrfs,raid456
raid1 53248 0
raid0 24576 0
md_mod 180224 6 raid1,raid10,raid0,linear,raid456,multipath

SECOND: for the network IP-Config warning, I don't have any static IP, and I did dmesg | grep error, only have a touchpad issues related to Thinkpads
as for journalctl -xe I don't see anything related to this warning

what happens at the boot process after grub could record that maybe this can help us find solution i found this for first two problems http://forums.debian.net/viewtopic.php?f=16&t=113616 for second i found this
https://askubuntu.com/questions/1043810/pxe-boot-fails-with-ip-config-no-response-giving-up hope it helps

Yeah I tired both solutions from Debian forum and Ubuntu forum, Not working....

I'm not really worried about the modprobe warning, I'll check it later on. I'm more worried about the IP-Config warning which is annonying and for sure it's the cause of my boot delays
I tried to modify /etc/initramfs-tools/initramfs.conf and update-initramfs, but I still see the IP-Config warning

I modified the /etc/dhcp/dhcpd.conf, still no result...

Ok I fixed both modprobe warnings

• delete "force_load efivars || true" from /usr/share/initramfs-tools/hooks/mdadm
• delete "force_load dm-raid45" from /usr/share/initramfs-tools/hooks/dmraid
• update-initramfs -u
  Then warning disappeared after reboot

Now I still have to get rid of the IP-Config warning... Any ideas where to look ?

try this https://askubuntu.com/questions/1043810/pxe-boot-fails-with-ip-config-no-response-giving-up hope it helps

I already tired it out, didn't fix it

I even tried to apt purge isc-dhcp-server, didn't fix it too

i remembered now that systemd-analyze will give you explanation what makes you linux loading longer maybe try this maybe those modules are not problem if there could be a problem then there will be errors in dmesg because it makes linux load longer so dmesg will MUST gotten message that those modules causes the booting time problem try and show the output maybe there is solution

The boot process has been optimized since I fixed the modules warning, so no error in dmesg related to that.

The IP-Config warning message is still there though, it's not critical, just annonying to have for each boot

Is there any other ways to disable boot messages if it can't be fixed ?

in /etc/default/grub there is a line lemme give a pic with highlighted line there is a bunch of options e.g acpi=off maybe try to set ip statically after boot and after log in set ip netmask gateway dns manually because maybe dhcp server on router have problems or networkd is messing with you try static addressing in right corner in network settings save and reboot and try to see if this error still there

Yesssss I fixed it finally!!!! :D

It wasn't related to Grub parameters, nor to static IP.

It was this package which gave me headaches for months "aoetools" so when I inspected /usr/share/initramfs-tools/hooks/aoe then I saw a probing operation
When I purged it, the warning finally disappeared=, phew :)
apt purge aoetools

A quick description of the package for your knowledge: apt show aoetools:
The aoetools are the client-side programs of the ATA over Ethernet (AoE) network storage protocol, a simple protocol for using storage over an ethernet LAN.

You can close the incident ;)

Thanks, closing.