Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!axion!rtf.bt.co.uk!grundy From: grundy@rtf.bt.co.uk (Martin Grundy) Newsgroups: comp.os.minix Subject: Re: Memory manager panic: problem & what does minix 386 offer Message-ID: <1991Feb8.092509.12452@rtf.bt.co.uk> Date: 8 Feb 91 09:25:09 GMT References: <43907@nigel.ee.udel.edu> Organization: British Telecom Customer Systems, Brighton, UK Lines: 40 In article <43907@nigel.ee.udel.edu> KHATUKA%ROSEVC.Rose-Hulman.Edu@uicvm.uic.edu (Aditya Khatuka) writes: >Hi, > > I have installed minix 1.5 on a Zenith Z386/25 with 150MB hard drive >and 640K + 1024 K entended memory. My partation 3 ( approx 2 MB) contains the >ram disk image while partition 2 is for the rest of the stuff. > I used the command >/etc/setup_root /dev/hd3 512 113903 12500 2016 22680 > | | | | | > ram | minix | minix - (for future use!) > tried other sizes too <--| dos ram image > > for creating root file system. (rest deleted) Hi, I think your problem may be that your blocksize spec for hd3 in the /etc/setup_root should be 512 instead of 2016. Otherwise, when minix tries to load the ram disk off /dev/hd3, it tries to load 2016 blocks and you haven't got that much memory ! Try: /etc/setup_root /dev/hd3 512 113903 12500 512 22680 (I also set my dos partition size to 0. It seems to work). I am not too sure without looking, whether /etc/setup_root performs the mkfs for /dev/hd3; if it doesn't, then you have to "mkfs /dev/hd3 512" beforehand, to make a 512k filesystem on /dev/hd3. I am sorry but I don't any info on mx386; I am about to try it myself ! -- Martin Grundy | email: grundy@rtf.bt.co.uk British Telecom Customer Systems | Hyperion House | phone: +44 273 762102 96-99 Queens Road | fax: +44 273 722038 or Brighton BN1 3XF. | +44 273 762071 (netfax)