*BSD News Article 2566


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!csus.edu!netcomsv!mork!alm
From: alm@netcom.com (Andrew Moore)
Subject: Floppy woes (was Re: Beginner's problems with 386BSD)
Message-ID: <kmlmd!a.alm@netcom.com>
Date: Mon, 27 Jul 92 09:54:12 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
References: <712169547snx@rama.demon.co.uk> <14u9deINNoa5@rodan.UU.NET>
Lines: 20

>Due to a couple of niggling things, it will not work.  Remove the
>/dev/rfd0a and /dev/fd0a devices, then MAKEDEV fd0.  As it turns
>out, mtools wants /dev/rfd0c, not the "a" partition on the floppy
>drives.  Alturnatively, you can re-compile mtools to use
>/dev/rfd0a instead of /dev/rfd0c (I found that creating the correct
>devices was more expediante.)

    Another problem is the floppy gets "stuck" after 386bsd boots.  Any
    mtools operation seems not to work and to be uninterruptable.   I
    thought I had solved this problem by moving my video card from a 16
    bit isa slot to an 8 bit one.  This allowed me to install 386bsd on
    the hard disk.  But now that it's installed, the floppy is acting
    up again!  There might still be a memory conflict (though in
    principle there shouldn't be), but maybe there is a work around
    too?

    The video card is a OEM Paradise SVGA.  I don't see any mention of
    interrupts (someone had IRQ 2 problems).  The floppies are run off
    an Adaptec 1542B SCSI controller.  
    -Andrew Moore <alm@netcom.com>