During the installation when I do Alt-Ctl-F2 I go to shell.
There in /sbin there some common programs.
Among them there modprobe, insmod , etc
which are symlinked to ./loader
by the ./loader itself is missed,
So I can not do modprobe during the installation.
The fix is to add this program ./loader
Brent please check into this, as well as with the latest internal tree.
This works for me under 7.0. Also works in the latest internal trees.
I used RedHat 7.0 kickstart installation.
There is no loader in /sbin/
when I did Alt-F2
The loader exists in /sbin if I use standard boot disk and start
standard installation procedure.
In case I use kickstart installation
(or probably any other which uses bootnet.img)
THERE IS NO /sbin/loader.
I did not try bootpcmcia.img may be this problem exists with this disk also.
Oh, I wasn't aware you were using boot disks. I was using the cd. I was able
to reproduce the problem with a bootnet boot disk for 7.0. However, it doesn't
happen with the bootnet boot disk in our internal testing builds, so apparently
this problem has been fixed. However, the issue still exists if you use a
pcmcia boot disk.
>However, it doesn't
>happen with the bootnet boot disk in our internal testing builds, so
>this problem has been fixed. However, the issue still exists if you use a
>pcmcia boot disk.
I hope you will fix this for 7.1 release,
because inability to do run modprobe
in case when installation process failed is very annoyning.
what module do you need to insert?
>what module do you need to insert?
device scsi ...
device eth ...
in ks.cfg for the devices
the easiest thing to check whether the driver/parameters will work
is just to do
modprobe module_name options
If it works - I just put module name and options to ks.cfg and start
The inability to do try manually wheter modprobe would work requires to make new
try kickstart again , what is very time consuming.
It's too late to make this kind of change for the next release, but this is
something to think about for future releases. Deferring for now.
This appears to have been fixed in our internal builds.