elevate on Gen 8 HP Enterprise Servers goes wrong

Operating System & Version


Aug 8, 2023
cPanel Access Level
DataCenter Provider

So we run elevate on a bl460c Gen 8 server, there was no warning, no blocker not even a warning info. It was being elevated to AlmaLinux 8.
It reached to level 4 and then stopped. The reason behind this was that the server no longer could see NIC's after the update.
The server already had the latest HP Service pack so it was something else.

Apparently , someone thought it was a good idea to remove the NIC drivers on Centos 8.

Don't despair there is a solution.

Before you start the installation or afterwards download this rpm

If you didn't do it before, then downlod it , make a simple iso with this file and attach it to iLO. After you do so , mount it. So do a
mount /dev/cdrom /mnt
rpm -i /mnt/kmod-be2net-

after you do so just reboot the machine.

In some cases , because of the way centos 7 was deployed , it is possible that after reboot the NIC will not come up.
If you issue a
service network restart
it will bring the network up.

The problem lies that there is no HWADDR=XX:XX:XX:XX in your network config file at /etc/sysconfig/network-scripts/ifcfg-something
Just make sure you add the MAC address there and then it will bring the network up normally after reboot.

There is also another issue where the console is super laggy or stops accepting input completely.

To resolve this just edit /etc/default/grub
and change your GRUB_CMDLINE_LINUX from this
GRUB_CMDLINE_LINUX="crashkernel=auto rhgb quiet"
to this
GRUB_CMDLINE_LINUX="crashkernel=auto rhgb quiet intel_iommu=on intremap=off"

after you do so , if your server is uefi execute
grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg
if its not uefi then execute this instead
grub2-mkconfig -o /boot/grub2/grub.cfg

and reboot

I am still puzzled that not many people have complained about it and its not that these machines are old. GEN 8 or (8.1)Servers are still very capable machines.
Last edited:
  • Like
Reactions: braecht