Path: utzoo!attcan!uunet!husc6!ukma!cwjcc!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.os.minix Subject: Re: Problem using mkfs on Miniscribe HD Message-ID: <12875@ncoast.UUCP> Date: 4 Nov 88 22:12:11 GMT References: <61500001@uxe.cso.uiuc.edu> <2523@mhres.mh.nl> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.os.minix Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 31 As quoted from <2523@mhres.mh.nl> by vrh@mh_co2.mh.nl (Michael Verheij): +--------------- | In article <61500001@uxe.cso.uiuc.edu> finn@uxe.cso.uiuc.edu writes: | >When I run mkfs, I just get an apparantly infinite loop of unexpected | >interrupt messages from the kernel. The message says that the interupt | | I've got a 10 MHz Tulip AT clone with a 20 MB Miniscribe HD and a | SCSI-controller. I can't get a file system on hard disk either. | MINIX supports on a AT only the standard (WD) AT-controller and nothing else. | So check your controller to see if it's a WD one. +--------------- Dunno if it's related, but... Back when Minix first came out I tried to set up my hard drive (ITT XTRA (an XT clone) with WD1002-WX2 controller) under Minix and got the symptoms you describe. It turned out that for some unknown reason the disk initialization had to be reversed: it was treating drive 0 as drive 1 and vice versa. Try building a Minix kernel with the drive 0 parameters used to initialize "drive 1" and vice versa and see if it works. I haven't the faintest idea why they're backwards (and why it works fine from DOS) but there it is. ++Brandon -- Brandon S. Allbery, comp.sources.misc moderator and one admin of ncoast PA UN*X uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu allberyb@skybridge.sdi.cwru.edu allbery@uunet.uu.net comp.sources.misc is moving off ncoast -- please do NOT send submissions direct Send comp.sources.misc submissions to comp-sources-misc@.