Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!yarrina.connect.com.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!gatech!news.sprintlink.net!matlock.mindspring.com!usenet From: rsanders@interbev.mindspring.com (Robert Sanders) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2.0.5-ALPHA install Date: 05 Jun 1995 01:16:37 -0400 Organization: /usr/lib/news/organization Lines: 13 Message-ID: <874u25pcy2.fsf@interbev.mindspring.com> References: <87hh69ixsc.fsf@interbev.mindspring.com> <3qoeni$71v@agate.berkeley.edu> <87u4a8jbx7.fsf@interbev.mindspring.com> <3qqugq$93j@agate.berkeley.edu> <3qtvv2$qev@gazette.engr.sgi.com> NNTP-Posting-Host: interbev.mindspring.com In-reply-to: minakami@carenath.engr.sgi.com's message of 5 Jun 1995 04:08:02 GMT X-Newsreader: (ding) Gnus v0.82 On 5 Jun 1995 04:08:02 GMT, minakami@carenath.engr.sgi.com (Michael Minakami) said: > I'm having exactly the same problem. System is a 386 DX/40 with 8MB, Adaptec > 1542B, Etherlink III, and a modem w/16550 UART. The disk is entirely devoted Someone on the freebsd-hackers said that disabling all the devices that might appear at 0x300 fixed the problem for him. I'll try that tomorrow. I haven't tried the -c config prompt yet; I hope it's fairly straightforward. I'm not familiar with all the FreeBSD device names yet. -- Robert