Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!munnari.oz.au!cluster!metro!natmlab.dap.csiro.au!ditsyda!evans
From: evans@ditsyda.oz (Bruce Evans)
Newsgroups: comp.os.minix
Subject: Re: Minix on a Z-386
Message-ID: <2403@ditsyda.oz>
Date: 16 Jan 90 04:53:41 GMT
References: <12500001@ucf-cs.ucf.edu>
Reply-To: evans@ditsyda.mq.oz (Bruce Evans)
Organization: CSIRO DIT Sydney, Australia
Lines: 22

In article <12500001@ucf-cs.ucf.edu> richard@ucf-cs.ucf.edu writes:
>I am interested in running minix on a Zenith Z-386.  A friend gave me a
>copy of minix v1.2 that he compiled with the AT-wini driver.  The system
>[...]
>  Unrecoverable disk error on device 2/0, block 1
>  File system panic: Diskette in drive 0 is not root file system.

The 1.2 floppy driver had problems on fast machines. This was fixed in
1.3. There is a probably-better fix in 1.5.0.

>If anyone out there is running on a 386 machine and can verify or deny
>the LOCK, NOP claim, I would appreciate hearing about it.  Or, if any

Yes, LOCK had to be changed for the 386 to stop it locking the bus for
too long on certain instructions. For some reason it was disallowed for
harmless instructions like NOP too. So LOCK, NOP generates an exception
in the video driver and Minix panics. The crash becomes worse when the
video driver is called again to print the panic message...

Bruce
-- 
Bruce Evans		evans@ditsyda.oz.au