Linux installation

[simon_164]

I am trying to install linux RHEL 4 on a DL 380 G5. I needed a USB floppy to be able to put the driver.
I got the Floppy, connect it, loaded the driver, everything looks fine. but then I received the same error as before, no device has been found...
what could be the problem,
I tried many times with different drivers with no success

[Steven E. Protter · Accepted solution]

Shalom,

It would help to know what you need the driver for.

If the hardware is not critical, proceed with the installation and try and driver addition post installation.

SEP

[simon_164]

I want the driver to be able to install Linux, the drivers are not in the RHEL 4 i have. so I have to put the driver manually using the linux dd command. I tried that but it does not work.
I will try to get the RHEL 4 update 5. but till then what should i do?

[Steven E. Protter]

Simon,

Here is the thing. That server DL 380 G5 can do a Linux install without additional drivers.

So here is what to do.

Either boot the box with the CD/DVD that came with it and configure the internal storage or watch the boot process for configuring the scsi array controller and hit the F8 or F9 function key. Then configure the storage in the application built into the system bios.

Now its possible you are missing a raid controller card, in which case I recommend you contact HP and get yourself one.

SEP

[simon_164]

I have a RAID card,
I already configured my disks to have RAID 1,
the card is already set up as the first boot controller.
I am able to install windows using smart start with no problem.

and Yes the drivers are necessary to install the RHEL. If you just look at about 20 threads related to the issue you will see that the drivers are necessary and lots of people had the same issue. They resolve it by applying the drivers using the floppy drive or getting the new RHEL update.
I do not know why the driver is not working when i apply it with the floppy drive.

[Rick Beldin]

A customer had a similar issue not too long ago that had two different solutions. The problem was that the RH install kernel identified the usb-key as device /dev/sda, which appears to a scsi device to anaconda, the RH installer. anaconda wasn't expecting a scsi device for the floppy image...

Two solutions:

- later version of RHEL4 (I think U4) worked fine, but customer requirements wanted U3

- put the driver disk image on an http, ftp, or nfs share and use:

linux dd=nfs://path-to-image

to boot and install the system. anaconda could find the floppy image in that way.

Of course, option 2 requires you have another machine on the network...