Hi,
I have a floppyless multia and am currently attempting to install RH6.0.
I am running into problems with a signal 11 during the install and I am
using the updated ramdisk image (which I have downloaded from various
locations with identical results). The signal 11 is occuring just as the
"scanning packages" messages appears, which I find rather uncanny as
this is where the old ramdisk image failed also.
My setup is as such. I boot the kernel with an aboot header through
bootp and set the root directory to a nfs volume on a working i386 linux
box. The nfs volume is a loopback mounted ramdisk image. Thus the
command I use to boot from the SRM is:
boot ewa0 -file vmlinux.bootp -flags "root=/dev/nfs
nfsroot=192.168.0.5:/mnt/loopback2"
(where 192.168.0.5 is the i386 nfs server).
I then watch the kernel boot, and am dropped into the installer where I
select "INSTALL" and then "CUSTOM" I then struggle with disk druid,
partition my drives, with one swap, select "ok", I then format the swap
partition and as soon as I reach the "Scanning packages..." screen I get
the signal 11 and the install aborts. If I look at tty3 the last
operation that seems to occur is the "making symlink from tmp/rhimage to
image" operation - however this may be irrelevant.
I am sure I am using the new installer as it was built on May 28th 1999,
whilst the original image contained an installer built on April 19th
1999.
If somebody could shed some light upon this somewhat strange problem it
would be much appreciated.
Thanks in advance,
Dean.
Hi,I have a floppyless multia and am currently attempting to install RH6.0. I am running into problems with a signal 11 during the install and I am using the updated ramdisk image (which I have downloaded from various locations with identical results). The signal 11 is occuring just as the "scanning packages" messages appears, which I find rather uncanny as this is where the old ramdisk image failed also.
My setup is as such. I boot the kernel with an aboot header through bootp and set the root directory to a nfs volume on a working i386 linux box. The nfs volume is a loopback mounted ramdisk image. Thus the command I use to boot from the SRM is:
boot ewa0 -file vmlinux.bootp -flags "root=/dev/nfs nfsroot=192.168.0.5:/mnt/loopback2"
(where 192.168.0.5 is the i386 nfs server).
I then watch the kernel boot, and am dropped into the installer where I select "INSTALL" and then "CUSTOM" I then struggle with disk druid, partition my drives, with one swap, select "ok", I then format the swap partition and as soon as I reach the "Scanning packages..." screen I get the signal 11 and the install aborts. If I look at tty3 the last operation that seems to occur is the "making symlink from tmp/rhimage to image" operation - however this may be irrelevant.
I am sure I am using the new installer as it was built on May 28th 1999, whilst the original image contained an installer built on April 19th 1999.
If somebody could shed some light upon this somewhat strange problem it would be much appreciated.
Thanks in advance,
Dean.
--
To unsubscribe: send e-mail to axp-list-request@redhat.com with
'unsubscribe' as the subject. Do not send it to axp-list@redhat.com
This archive was generated by hypermail version 2a22 on Tue Feb 1 05:33:32 2000 PST
Send any problems or questions about this archive to webmaster@alphalinux.org.