Bug 30835 - install exited abnormally -- recieved signal 15
install exited abnormally -- recieved signal 15
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-03-06 13:54 EST by Need Real Name
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-06 13:54:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2001-03-06 13:54:14 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (Win98; I)

anaconda justs exits without any meaningful reason why. Just signal 15.
I assume it is looking for USB and this motherboard does not have any.

Reproducible: Always
Steps to Reproduce:
1.Boot off of boot.img using 'linux updates'
2.Yes for driver Disk, insert Driver Disk
3. Insert Update disk (RHBA-2000:084-04)
4. Select SCSI CD-ROM
5. aha154x 


Actual Results:  Running anaconda - may take some time to load...
install exited abnormally -- recieved signal 15
sending termination signals...done
sending kill signals...done
disabling swap..
unmounting filesystems...
           /mnt/source umount failed (16)
you may safely reboot your system

when I hit alt-f3, the last message it gives is *looking for USB mouse...
when I hit alt-f4, the last message is <4>VM: terminating process anaconda

I notice that there is one message: <4>VFS: Can't find a valid MSDOS 
filesystem on dev 02:00.

Expected Results:  I expected for the installer to start installing

I have seen atleast 3 other people with this same problem and they all have in common:
   486 cpu
2 both have
   8 MB RAM
Comment 1 Michael Fulbright 2001-03-06 15:06:07 EST
You need at least 24M to install 7.0.

Note You need to log in before you can comment on or make changes to this bug.