Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 6478 - RH 6.1 on a 386 installation.
RH 6.1 on a 386 installation.
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 1999-10-28 16:23 EDT by banasw01
Modified: 2015-01-07 18:39 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-08 14:23:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description banasw01 1999-10-28 16:23:33 EDT 
I am installing RH 6.1 on a 386 6800SX By Leading
Technology INC, the computer has a floppy, 8x cdrom, 200MB
IDE HD, 8MB of Ram, and a SMC Ultra 16 ISA.
I have installed RH 6.1 on one of my computers already many
times, but I usually use the bootable cdrom feature. On the
386 I use a floppy "boot.img" then it asks me for a "driver
disk" so I just skip this step, oh, and the HD and cdrom
are detected when the kernel boots. After I skip
the "driver disk" prompt, it asks me if I want to install
any other drivers, SCSI or Network, and I chose the SMC
card drivers, and the card gets detected. The install cd,
DOES of course get mounted, and then after installing the
SMC card I get a blue screen with something
like "Installing Redhat Linux" on the top right, and the
cursor blinking on the bottom righ. Then the install
program copies something from the cdrom for a while (this
is a sloooow computer), and then it exits from the blue
screen and writes on the black backround:

install exited abnormally -- recieved signal 7
sending termination signals...done
sending kill signals...done
unmounting filesystems...
          /mnt/source
          /dev/pts
          /proc
you may safely reboot your system

And that is all I get... I know this computer is old, but
it does run dos and windoze 3.1 fine. Humm... Any ideas?
Comment 1 john.hosage 1999-11-13 01:30:59 EST 
Same problem on a Gateway 486/33 with 8MB RAM, 250 WD Hard drive, Sony 4X CD,
Diamond SpeedPro 1MB graphics and SMC network cards.  Tried with the boot.img
from October 21 and received the signal 7.  Tried running the autoboot in
dosutils on the CD (the system currently run W95) and received the signal 7.
HDA and HDC show up as detected.  Didn't load the network drivers and still
received the signal 7.

The last line on screen 3 was "* going to insmod raid5.o (path is null)"

The last line on screen 4 was "<6> raid5 personality registered"
Comment 2 Cristian Gafton 2000-01-27 03:06:59 EST 
assigned to the right component
Comment 3 Jay Turner 2000-02-08 14:23:59 EST 
A signal 7 is the result of running out of memory during the installation.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.