Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!werple.apana.org.au!otis.apana.org.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!cronkite.nersc.gov!dancer.ca.sandia.gov!overload.lbl.gov!lll-winken.llnl.gov!sol.ctr.columbia.edu!howland.reston.ans.net!news.sprintlink.net!jaring.my!oasys!othman From: othman@oasys.pc.my (Othman bin Hj. Ahmad) Newsgroups: comp.os.386bsd.bugs Subject: FreeBSD 2.0R fails on npx 387 Message-ID: <T54mwc2w165w@oasys.pc.my> Date: Wed, 30 Nov 94 12:37:16 MAL Distribution: world Organization: Personal,Kota Kinabalu,Sabah,Malaysia Lines: 30 I've tried FreeBSD 2.0R boot disk just now. All devices tested are shown even if they don't exist, cluttering my display. When it detects the devices, its details are not given, like io address and interrupt number, causing me to have difficulty in diagnosing the error. Sometimes the IRQ no could be correct but not its io address. FreeBSD 2.0R detects my Intel 387 on 386DX25 motherboard as "np" but reported an error, so it uses emulation. Please note that 386bsd 0.1 with patchkit installed, detects this 387 correctly. I don't really know if the 387 is actually used or not but my programs run nicely there. I recalled that the FreeBSD 1.1.5 also had problems with some motherboards with 387. Has this been fixed. What actually causes this problem. I'd like to use FreeBSD because of its better modem support but this problem makes me wonder whether I should still keep my vintage 386bsd 0.1 intact. Disclaimer: I only speak for myself. SABAH is Heaven. Perpetual Clear Blue Sky, Sea and Mountains near modern civilisations, but how long will this last?