Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:1404 comp.sys.ibm.pc.hardware:49579 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!usc!cs.utexas.edu!rutgers!njitgw.njit.edu!hertz.njit.edu!kxn3796 From: kxn3796@hertz.njit.edu (Ken Nakata CIS stnt) Newsgroups: comp.os.386bsd.questions,comp.sys.ibm.pc.hardware Subject: Re: Problems upgrading to 16M Message-ID: <1993Apr6.180154.7681@njitgw.njit.edu> Date: 6 Apr 93 18:01:54 GMT References: <DFR.93Apr2113836@rhino.ioc.co.uk> Sender: news@njit.edu Organization: New Jersey Institute of Technology, Newark, N.J. Lines: 36 Nntp-Posting-Host: hertz.njit.edu In article <DFR.93Apr2113836@rhino.ioc.co.uk> dfr@ioc.co.uk (Doug Rabson) writes: >I just upgraded my 486DX33 system from 8M to 16M of ram and I am >having problems. I am running 386bsd-0.1 + patchkit-0.2.1 + >keycap-0.1.1 + julians scsi drivers and the system was very stable >before the upgrade. I have used the same kernel binary on a 486DX266 >with 16M of ram with no problems. > >Basically, since the upgrade, the machine is prone to spontaneously >reboot when it is being worked fairly hard in 386bsd. Most recently >it crashed while trying to compile tif_fax3.c from the xv-2.21 >distribution (which can take upto 30M of virtual memory and >consequently gives the memory system a good workout). [deleted] >It seems likely that I have a hardware problem here but I guess it >could be 386bsd. Does anyone have any ideas? I don't want to mess >about getting my dealer to replace the memory if it isn't going to fix >the problem. Some motherboards have a feature to remap unused memory to high address. For example, my 486 motherboard with 16M memory can remap a 256k block to address 0x1000000 (If I had 8M memory, it would be remapped at 0x800000). On the ISA bus, 1542 cannot access to the memory above 16M, and I have a 256k block above 16M. Then I would have had a problem if I were using SCSI drives. You might be in the same situation. Probably, you can disable the remapping feature by BIOS setup utility. If so, it'll work properly. Hope this helps. Ken Nakata -- /* I apologize if there are incorrect, rude, and/or impolite expressions in this mail or post. They are not intended. Please consider that English is a second language for me and I don't have full understanding of certain words or each nuance of a phrase. Thank you. -- Ken Nakata, CIS student, NJIT */