Rocky Install Issue

There no drivers for the embedded NICs of HP C7000 G8 Blades :frowning:

Can you get lspci -nn | grep -i net to show the PID ID of the NICs?

root@dedi-20752:~# lspci -nn | grep -i net
04:00.0 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC (be3) [19a2:0710] (rev 01)
04:00.1 Ethernet controller [0200]: Emulex Corporation OneConnect 10Gb NIC (be3) [19a2:0710] (rev 01)

Hi,

I think this is rpm you need:-

http://ftp.icm.edu.pl/pub/Linux/distributions/elrepo/elrepo/el9/x86_64/RPMS/kmod-be2net-12.0.0.0-10.el9_1.elrepo.x86_64.rpm

http://linux1.fnal.gov/linux/elrepo/dud/el9/x86_64/dd-be2net-12.0.0.0-15.el9_4.elrepo.iso

(Sorry initially linked the wrong version for point release, thanks to leteaa & jlehtone for providing the correct version).

Someone else had a similar issue with a gen7 and a rocky8 (Although in there case they were trying to install the wrong version of the rpm initially). HP proliant bl460c gen7 - network interface - rocky 8.5

The easiest way would be to probably create iso containing the rpm. If you then install Rocky using the minimal or dvd iso. After the OS is booted attach the iso via the console in the ilo and install the rpm dnf.

Regards Tom.

Thanks for the answer!

So for Rocky 9.4 it would be: ftp.icm.edu.pl/pub/Linux/distributions/elrepo/elrepo/el9/x86_64/RPMS/
(https://ftp.icm.edu.pl/pub/Linux/distributions/elrepo/elrepo/el9/x86_64/RPMS/kmod-be2net-12.0.0.0-15.el9_4.elrepo.x86_64.rpm), correct?

I will give that to my Hosting Support.

1 Like

That was for the 9.1. With current 9.4 one should use
kmod-be2net-12.0.0.0-15.el9_4.elrepo.x86_64.rpm
because the kernel in each point update differs to the extent that kernel modules must be rebuilt.


It is also possible to give the installer additional drivers with Driver Update Disks (DuD).
ELRepo has image for such disk: http://linux1.fnal.gov/linux/elrepo/dud/el9/x86_64/dd-be2net-12.0.0.0-15.el9_4.elrepo.iso

One could even append inst.dd=http://linux1.fnal.gov/linux/elrepo/dud/el9/x86_64/dd-be2net-12.0.0.0-15.el9_4.elrepo.iso to installer’s cmdline and have it downloaded&used automatically. Alas, with no network the “download URL” is not an option. The image written to USB should do. (Haven’t used, Red Hat’d documentation hides from Google search, perhaps: Updating Drivers During Installation on AMD64 and Intel 64 Systems :: CentOS Docs Site )

2 Likes

I prob have to make a Custom ISO to be able to use Rocky, but idk how that works on Linux. so GG ig ^^

Hi,

No need to make a custom ISO. I can’t recall if the ILO allows you to mount 2 isos at once, if it does you can use the DuD method posted by jlehtone above.

If not complete the install without networking with a minimal or dvd ISO. Then you mount DuD the via virtual media in the ILO, then you can install the rpm from disk via dnf.

Then configure the network via nmtui.

Regards Tom.

Simple question, would it be possible for me to simply install CentOS 9 and then simply migrate to Rocky 9 on the Fresh system

There is no CentOS (Linux) 9. There is CentOS Stream 9, but it is at best no better than Rocky 9. So no, installing something like Rocky 9 will not help.

Unfortunately, that wasn’t the question at all.

Hi,

What was the question then?

jlehtone’s answer seems correct to me. You can’t install Centos 9 as it doesn’t exist. I don’t believe the nic drivers for G8 blades exist in centos9-stream, so I don’t think trying to migrate will resolve this issue.

Regards Tom.

CentOS 9 of course means CentOS Stream 9 ._.

I just don’t know anyone who wants to write the stream every time because they actually know what it means

A post was split to a new topic: Unable to access web interface

Fair point – everybody should know by now. Alas, there seem to be casual readers, who still don’t.


Back to Stream 9. It supposedly has now content that might be included in RHEL 9.5.
If Red Hat has decided to add be2net to RHEL 9 in 9.5, then Stream 9 could now have it.
Following that Stream 9 could install, and Rocky 9.5 would install too.

However, isn’t the reason for lacking support because the NIC are old? RH is not inclined to add drivers for old hardware that they have already decided not to support.

Ya all RHEL based got the issue with the NIC drivers …

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.