Thank you all for your help.... just wanted to let you know the outcome
of the installs...
On the HP Vectra, there appears to be some hardware issues, as Windows 2K
boot floppy fails with a Boot I/O Error. This machine has been suspect,
and I will probably scavenge it for parts (CD, Memory) (It has had some
intermittent problems finding the HDD.)
On the HP Kayak..... it's UP! I downloaded the new boot disk image from
the email below, and the install ran without a hitch. It must not like the
7.2 standard boot image since it failed both from the install disk and
from the boot floppy I made straight from the CDROM. (This was a CD burned
from the WLUG installfest in February and it has installed faithfully on
about a dozen machines.)
Thank you again.
jeff
-----Original Message-----
From: Charles R. Anderson [mailto:cra@WPI.EDU]
Sent: Tuesday, June 25, 2002 7:49 PM
To: 'wlug@mail.wlug.org'
Subject: Re: [Wlug] Installing Redhat on HP machines
Have you tried booting the latest errata install disks? You can get
them here:
ftp://angus.ind.wpi.edu/pub/updates/7.2/en/os/images/i386/boot.img
ftp://angus.ind.wpi.edu/pub/updates/7.2/en/os/images/i386/update-disk-200201
17.img
Make sure you rawrite/dd them to brand new floppy disks, since if there
is even a single byte error on the floppy disk, the install will fail.
Boot the first one (boot.img) and see below...
On Tue, Jun 25, 2002 at 06:25:44PM -0400, Hemstreet, Jeffrey wrote:
jhemstreet> One is an HP Vectra (2Gb IDE, 56MB, P200). I can fdisk and
select
jhemstreet> packages, but when it goes to
jhemstreet> format the disk to install the packages, I get a signal 11 fatal
error. I
jhemstreet> think there may be something
jhemstreet> flaky with this system (HDD or memory problem?) Just wondering
if anyone
jhemstreet> else has seen this type
jhemstreet> of failure and could give me any more insight. I plan on
replacing the HDD
jhemstreet> to see if that is the problem.
It depends. Does the signal 11 always happen at exactly the same point?
If so, that doesn't necessarily point to flakey hardware, but rather a
software bug. If it IS random, then it does sound like a memory error.
You can test your RAM with memtest86, available here:
http://www.memtest86.com/
Another thing you can try is making sure the amount of memory is
detected correctly by Linux (check the boot up messages of the Linux
kernel). If not, you can force the correct amount by appending the mem
option to the linux boot command line:
linux updates mem=56M
You need the "updates" bit to use the update-disk mentioned earlier.
Insert the updates disk when it asks.
jhemstreet> The other is a dual-300 PII HP Kayak with a SCSI Drive. I get a
boot error
jhemstreet> when trying to boot from the
jhemstreet> CDROM or Install Disk. This system is currently running NT 5.
Any ideas
jhemstreet> why the boot would fail?
Bad floppy disk and/or CD-ROM? How did you acquire your Red Hat 7.2
CD-ROM? If it isn't an official disk, then it might have been burned
incorrectly. Red Hat recommends burning ISO's in Disk-At-Once mode, and
checking the images and disks with md5sum to be sure they burned
correctly.
--
Charles R. Anderson
participants (1)
-
Hemstreet, Jeffrey