From owner-freebsd-questions Thu Oct 17 3:37:16 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FCB037B401 for ; Thu, 17 Oct 2002 03:37:15 -0700 (PDT) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DA8743E7B for ; Thu, 17 Oct 2002 03:37:13 -0700 (PDT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.12.6/8.12.6) with ESMTP id g9HAbBKg089036; Thu, 17 Oct 2002 11:37:11 +0100 (BST) (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost) by happy-idiot-talk.infracaninophile.co.uk (8.12.6/8.12.6/Submit) id g9HAb6nE089035; Thu, 17 Oct 2002 11:37:06 +0100 (BST) Date: Thu, 17 Oct 2002 11:37:06 +0100 From: Matthew Seaman To: Wayne Lubin Cc: freebsd-questions@FreeBSD.ORG Subject: Re: floppy not mounting Message-ID: <20021017103706.GB88261@happy-idiot-talk.infracaninophi> Mail-Followup-To: Matthew Seaman , Wayne Lubin , freebsd-questions@FreeBSD.ORG References: <20021016225521.23532.qmail@web14701.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021016225521.23532.qmail@web14701.mail.yahoo.com> User-Agent: Mutt/1.5.1i X-Spam-Status: No, hits=-9.9 required=5.0 tests=IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT, USER_AGENT_MUTT version=2.41 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 16, 2002 at 03:55:21PM -0700, Wayne Lubin wrote: > As I discussed in an earlier email that the fd0 > device is not showing up on dmesg. Can it be that I > burnt out the floppy drive and now at boot up the > floppy is not being detected? It's possible that your floppy has indeed bitten the dust. Certainly you won't be able to use it from FreeBSD until the kernel probes for it at boot time. You should see both fdc0 and fd0, like this: happy-idiot-talk:~:% grep fdc /var/run/dmesg.boot fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 However, to confirm that it has actually blown up, beg, borrow or steal a bootable floppy from somewhere and see if the box can be persuaded to boot from it. One of the FreeBSD installer disk images would be a good choice, or a memtest86 disk from http://www.memtest86.com/. If the drive is still working, it suggests that somehow it's got into an inconsistent state and can't respond to the kernel's probe attempts. That shouldn't happen --- the kernel should be able to interface with the hardware and put it into a consistent state however it was left. You might find that simply booting from a floppy image resets the drive and that the next time you reboot into FreeBSD it starts working again. Otherwise you should try completely powering down your system --- not just hitting the power switch on the front, but unplug it from the wall and leave it for at least 10 minutes so that any internal capacitance can discharge. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message