Steve,
Thanks for the tip. I could not remember (and did not think to look it up) how
to get to a command prompt during the install. The Ctl-Alt-F2 sequence will be
handy whether I need your tip about building my own kernel or Tani's tip about
the initrd works well enough. I have often wanted to make some small adjustments
to the installation before the first reboot. It is especially critical when both
the "make boot disk" and "install lilo" fail for some reason, as they sometimes
do. Until now I have resorted booting from an install disk and using the rescue
image to create these things, but this will save a lot of time.
Thanks again for the hint.
In article <[EMAIL PROTECTED]>, Steve Wampler wrote:
> Date: Tue, 29 Jun 1999 18:46:49 -0700
> From: Steve Wampler <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: aix7xxx install images...
>
> Werner Kliewer wrote:
> >
> > Hi,
> >
> > I am trying to install RedHat 6.0 in an IBM Netfinity 5000 server.
> >
> > I have a single hard drive at address 0 attached to the internal (B)
> > channel of the motherboard mounted AIC-7895 controller, and a single
> > tape drive at address 1 attached to the external (A) channel of the
> > same controller.
> >
> > When I run the RedHat 5.2 install process from CD-ROM I have no trouble
> > finding the controller and hard drive and installing, all using default
> > auto-probe methods.
> >
> > When I run the RedHat 6.0 install the SCSI controller is not found via
> > autoprobe, and I have not yet figured out what boot options I should
> > try to make this work. One significant difference between the installs
> > is that this one must be done via NFS as I have not yet received my
> > Official RedHat install package (it IS on order) nor do I have the
> > wherewithal to cut my own until my new Jaz drive arrives (also on
> > order). The built-in network interface is discovered without even
> > prompting me.
>
> The installed kernel has the AIC7xxx driver as a module, which means it
> can't load the driver if the module is on the drive (sigh). (The installation
> kernel has the driver embedded in it, which is why it works...)
>
> You might try the following, it's close to what I did to get around the
> problem (I tried a *lot* of things before stumbling on something that works).
>
> If you install using "expert" mode, CTRL+ALT+F2 is a bash shell. Before
> finishing the installation, but after the packages have been installed
> switch to this shell and build a new version of the kernel with the driver
> loaded directly (you will likely need to play games with chroot and mount,
> etc.
> before doing the build). Then install this custom kernel (exit chroot or
> whatever) and allow the installation to finish.
>
>
> ---
> Steve Wampler {[EMAIL PROTECTED]}
> The gods that smiled upon your birth are laughing now. -- fortune cookie
>
Werner Kliewer
Manitoba Public Insurance
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
