Bug 165251

Description of problem:

We're trying to get a kickstart install going with a boot cd, install tree
available through NFS.  We have some hardware that doesn't work automatically in
RHEL 3 (an Adaptec AIC-9410 using the adp94xx driver).  It comes with a driver
disk image, so we have attempted to use this with the kickstart install.

When booting off of the CD, we use the following boot parameters (from
isolinux.cfg):

  kernel linuzas
  append initrd=initrdas.img ks=nfs:(server):/home/kickstart/rhel3_as.ks
ksdevice=eth0

The rhel3_as.ks file has the following driverdisk line:

driverdisk
--source=nfs:(server):/home/kickstart/dist/adp94xx-0.0.5-7.rhel3qu4.i686.img

We have also tried distributing the file through http:

driverdisk --source=http://(server)~kloostec/adp94xx-0.0.5-7.rhel3qu4.i686.img

The problem is that the installer cannot mount the image file using either NFS
or HTTP distribution.  I can mount it file on my FC4 machine, it's just in the
RHEL installer.  It copies the file to /tmp/dd.img just fine; the problem is
something to do with "cannot assign a loopback device" when it actually tries to
mount the disk to /tmp/drivers.  It appears to be trying to use /tmp/loop6.  I
checked /tmp and loop6 is there, with the proper node and subnode.

Is there any way around this problem, or can it be fixed?

Version-Release number of selected component (if applicable):

RHEL 3.0 update 4

How reproducible:

Always

Steps to Reproduce:
1. Set up a kickstart with installation over NFS
2. Set up a driverdisk line, and distribute the image over NFS, too
3. Boot up the kickstart installation
  
Actual results:

Cannot mount driverdisk.

Expected results:

Drivers extracted from the driverdisk image, hard drives detected, install to
continue painlessly.