No, I skipped LILO installation because the RH-installer
suggested it - I suppose Redhat still uses a LILO that
has problems with partitions beyond 1024 cylinder?
I am new to Redhat - I use SuSE on my other pc's, so
I am not sure.
But I have created several bootdisks, and none of them
can boot my partition, so I don't think it's a floppy problem
Looks like I got to do it the hard way - install RH7.1 with ext2,
which works without problems, and change to
a XFS root later on.
thanks
- Simon
> Does the system boot without the boot disk, ie, via the HD?
>
> If so, recreate your boot disk by running "mkbootdisk" as root.
>
> On Wed, 2 May 2001, Simon Pabst wrote:
>
> > Thanks, but this doesn't solve anything -
> > I don't think this is APIC-related.
> > It's NOT the boot.img bootdisk to start the installation
> > that locks up, it's after using the installer-created bootdisk
> > (instead of LILO) to boot the installed system.
> >
> > - Simon
> >
> > > "Russell Cattelan wrote:"
> > > > The boot images has APIC enabled to solve a problem with the SGI
1200's
> > > > apparently enabling this does break on some motherboards.
> > >
> > > boot with "noapic" as one of the boot parameters.
> > >
> > > > One option is to download the Release-1.0-test3 iso image.... err
> > > > scratch that download the bootnet.img from the test3 dir.
> > >
> > > Peter
> > >
> >
> >
>
|