topic Re: Red Hat Linux scripted install missing drivers for BL460c in ProLiant Deployment and Provisioning

Red Hat Linux scripted install missing drivers for BL460c

A. Edens — Wed, 16 May 2007 18:57:47 GMT

Has anyone been able to successfully deploy Red Hat AS 4U4 to a BL460c Blade Server?

In my particular case, the install is running fine until the script needs to copy the files from the FTP server.

The problem appears to be that the stock vmlinuz that comes with RDP 3.50 doesn't contain the new broadcom gigabit NIC drivers that ship with the BL460c Blade Server.

Hitting F3 when the install stops reveals the following error messages.

* no network devices in choose network device!
* no network drivers for doing kickstart
* unable to bring up network

Any help would be greatly appreciated.

Re: Red Hat Linux scripted install missing drivers for BL460c

Adrian Clint — Thu, 17 May 2007 10:29:15 GMT

Is this the one you have?
It seems to support the onboard BL460 nics.
http://h18023.www1.hp.com/support/files/server/us/download/26807.html

You might find help on what is happening in the Linux smartstart scripting toolkit.
http://h18023.www1.hp.com/support/files/server/us/download/27221.html

Re: Red Hat Linux scripted install missing drivers for BL460c

A. Edens — Thu, 17 May 2007 13:30:31 GMT

Adrian, thank you for your reply.

I received some assistance from our Linux expert this morning. It appears the problem isn't with RDP per se, but with the distribution of Red Hat that I am using.

We walked through the scripted install and found that it is trying to load the file:

/lib/osdist/rhas4u4.64/images/pxeboot/initrd.img

This file is where the driver must be in order for the RDP scripted install to work.

It has the tg3 driver, but not the newer bnx2 driver (NetExtream II) that the 460c uses.

This being the case, our Linux expert has been working with this initrd.img file and has injected the bnx2 driver into it.

That fixed the problem of the missing driver but caused another as the custom initrd.img file is missing some description file that lets the install know that it is really a Red Hat image. I think once he works that out the problem will be solved.

Thanks again for your assistance.