Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!bloom-beacon.mit.edu!gatech!sdd.hp.com!hp-pcd!hp-cv!reuter.cse.ogi.edu!netnews.cc.wwu.edu!netnews.nwnet.net!news.u.washington.edu!spleen.apl.washington.edu!user From: kargl@apl.washington.edu (Steven G. Kargl) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2.0.5-ALPHA install Date: Mon, 05 Jun 1995 15:36:22 -0700 Organization: Applied Physics Lab/University of Washington Lines: 41 Message-ID: <kargl-0506951536220001@spleen.apl.washington.edu> 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: nntp3.u.washington.edu In article <3qtvv2$qev@gazette.engr.sgi.com>, minakami@carenath.engr.sgi.com (Michael Minakami) wrote: > In article <3qqugq$93j@agate.berkeley.edu>, jkh@violet.berkeley.edu (Jordan K. Hubbard) writes: > |> >The kernel gets farther now, but there's a new symptom: it either > |> >hangs at the "npx" status line or hangs after saying "changing root > |> >device to sd0a". Nothing works after that point. It looks like all > |> >the device probes before that succeed. > |> > |> Hmmmm. Several things to look for now: > |> > |> 1. Is another device conflicting with you? > |> To find out: Boot with -c and disable all but the devices you need. > |> > |> 2. Is the geometry set correctly? > |> To find out: Boot sysinstall and look at the geometry in the > |> Partition editor. > |> > |> 3. Do you have both IDE and SCSI? If so, you need to boot with: > |> boot: sd(0,a)/kernel > > 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 > to FreeBSD and is a 540MB CP30540. The hang is always after the changing root > message. It is definitely a problem with your 3c509. The device probes for OTHER devices at address 0x300 and these screw up the ep0 driver (3c509). Boot with the -c option and disable any device that might conflict with the 3c509 (ep0 driver) at address 0x300. A short list of drivers: wt0, ie0, mcd0, mcd1, and ed1. Once you're up and running I suggest you build a custom kernel that includes only those devices on your system. -- Steven G. Kargl Applied Physics Laboratory University of Washington Seattle, WA 98105