Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!news.ksu.ksu.edu!news.physics.uiowa.edu!math.ohio-state.edu!howland.reston.ans.net!swrinde!newsfeed.internetmci.com!in2.uu.net!alterdial.uu.net!dweaver From: dweaver@nondum.cleaf.com (David Weaver) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Upgrade trouble Date: 23 Jan 1996 14:36:51 GMT Lines: 34 Message-ID: <4e2rq3$482@alterdial.UU.NET> Reply-To: dweaver@clover.cleaf.com NNTP-Posting-Host: 199.171.82.84 This week I decided to upgrade to 1.1, but I seem to be having some problems. The system has a 1200KB mini-diskette drive (5.25") as fd0 and a 1440KB micro-diskette drive (3.5") as fd1. Both of these drives are attached to an integerated IDE/floppy controller of unknown origin and type. A Conner 200MB IDE drive is also attached to the same adapter. I place the kernel copy floppy in fd0 and reset the system. It detects fdc0 at irq 6, dma 2, which is correct. It correctly detects fd0. The drive light for fd1 comes on and stays on. The drive light for fd0 is off. Having made no mention at all about fd1, the kernel says it's making fd0 the root device. Then: fdcresult: timeout fd0: timeout (st0 21<seek_cmplt> cyl 0) fdcresult: timeout fdcresult: timeout fd0: timeout (st0 21<seek_cmplt> cyl 0) etc.. dumping to dev 201... The rest of the text flashes by too fast to record. Then the system is reset. The fd1 light stays on until the BIOS resets the drives. NetBSD 1.0 detects both of the diskette drives just fine, flashing their lights as it comes up. I'm going to try taking fd1 out of the system since it seems to be confusing the generic kernel somehow. Both kernel copy floppies do the same thing. Has anyone seen anything like this before?