William,

Kernel is making right now, but here is from the .config:
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_RZ1000=y

HDs are
Orig /dev/hdb and New One is /dev/hdc (2nd MoBo Slot)
w/ /dev/hda being 1.2GB Win95 and /dev/hdd Goldstar CD

Next steps after new kernel is 
a) swap Ram
b) take /dev/hdc (New 4.3) out of machine and move
   CD back to /dev/hdc. (yup, changed /dev/cdrom link)

Thanks for the reply,
Rick

On Tue, 19 May 1998, William T Wilson wrote:

> On Tue, 19 May 1998, Rick L. Mantooth wrote:
> 
> > Opinions?
> 
> I'd suggest running fsck on your drive.  But a corrupt filesystem by
> itself shouldn't cause a kernel panic.

Having to do this every time it locks up.
Can be a couple of days or maybe even a few hours between lock-ups.
Boot single, 
umount /home /usr /usr1 /test /opt
# for i in 2 5 6 7 8
> do
> echo "Doing /dev/hdb$i....."
> fsck /dev/hdb$i
> done

Time for a script...

> 
> Do you have both hard drives installed at the same time on the same IDE
> channel?  Try moving one of them to its own IDE channel and/or recompiling
> your kernel with RZ1000 and/or CMD640 support.  A lot of Pentium-100's
> were equipped with one of these broken IDE controllers which will cause
> data corruption if you try to put two drives on the one channel, unless
> you use the workaround.  Maybe a kernel panic could be caused by this, I
> guess; but it shouldn't cause more than a VFS panic really.  I bet the
> kernel developers might like to see your trace. 
> 
--
Rick L. Mantooth        [EMAIL PROTECTED]
http://www.why.net/users/rickdman/index.html
Love:  two vowels, two consonants, two fools.


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to