[1731] in RedHat Linux List
HELP! I need an answer or an RMA.
daemon@ATHENA.MIT.EDU (Walter B Kulecz PhD)
Tue Oct 29 22:24:30 1996
Date: Tue, 29 Oct 1996 14:01:50 -0600 (CST)
From: Walter B Kulecz PhD <wally@wahine.jsc.nasa.gov>
To: redhat-list@redhat.com
cc: sales@redhat.com
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com
I've reported this once and seen one other report the same problem but
have seen no suggestions as to the fix.
Problem: P100, 32Mb RAM, Adaptec 2940 SCSI, IDE disk and CDROM.
Out of the box, booted the floppy, it found my controller and all 7 devices.
Fdisk: hda1 64 MB / (a 128Mb SyQuest EZ135 drive)
hda2 64 MB swap
sdb1 540 MB /usr.
Mounted the IDE CDROM, checked "everything", do "install" and all appears
fine. MS serial mouse even works in MetroX setup. None of the problems
others have reported, couldn't be smoother until the very last step:
Installing lilo does the "creating initial RAMDISK" then pops up "running
lilo" box briefly followed by "some kind of error occured" box. Retry
does the exact same thing. F12 reboots the system which hangs if I remove
the floppy. Booting the floppy and interrupting it to do: linux
root=/dev/hda1 appears to boot but dies with a fsck error leaving nothing
mounted and everything readonly.
I got the aic7xxxboot.img disk and repeated last night, exact same
behaviour. Instead of F12 I tried a shell with Alt-F2 and found /mnt looks
like a full install except no lilo.conf anywhere (find / -name lilo.conf)
and no /mnt/etc/fstab. "find / -name lilo" reports: /mnt/sbin/lilo
Running a few simple commands from /mnt/usr/bin or /mnt/bin seems to work.
This lack of lilo.conf probably explains why lilo fails but my question is
how can it work for anyone? The organization of the "RAMDISK" system from
the floppy boot is mysterious to me with no /dev entries but what appear
to be device entries in /tmp.
Will creating /mnt/etc/fstab and /mnt/etc/lilo.conf by hand and running
/mnt/sbin/lilo fix things? What do I put in lilo.conf? I assume the
standard fstab from 3.0.3 would work.
Since I can live without the modular auto-everything kernel which seems
to be causing all the problems, is there any reason I can't just update
to the new rpm on the 4.0 cd and then update/install all packages on my
3.0.3 system with the 4.0 CD packages (kernel 2.0 upgrades installed)
leaving my current 2.0.21 kernel and kernel source intact?
If 64 MB is too small for a / partition then the install dialog lies as
it said at least 50 MB is required.
--wally.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
________________________________________________________________________
http://www.redhat.com/RedHat-FAQ http://www.redhat.com/RedHat-Errata
http://www.redhat.com/RedHat-Tips http://www.redhat.com/mailing-lists
------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null
