From owner-freebsd-questions@FreeBSD.ORG Mon Apr 21 10:12:14 2003 Return-Path: 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 23DA937B401 for ; Mon, 21 Apr 2003 10:12:14 -0700 (PDT) Received: from sumax.dyndns.org (212-100-182-29.adsl.easynet.be [212.100.182.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2231743FE9 for ; Mon, 21 Apr 2003 10:12:12 -0700 (PDT) (envelope-from chrisp@belgacom.net) Received: by sumax.dyndns.org (Postfix, from userid 1001) id B7322225A; Mon, 21 Apr 2003 19:08:01 +0200 (CEST) Date: Mon, 21 Apr 2003 19:08:01 +0200 From: Chris Pockele To: freebsd-questions@freebsd.org Message-ID: <20030421170801.GA23306@freedaemon.home.lan> Mail-Followup-To: Chris Pockele , freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.8-STABLE i386 Subject: floppy drive problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 17:12:14 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Hello, I've got a 486 laptop running a FreeBSD 4.7-STABLE snapshot from february 4th. Unfortunately its floppy drive is acting weird under FreeBSD: nomad# mount -t msdos /dev/fd0a /mnt fd0c: hard error reading fsbn 0 of 0-3 (ST0 40 ST1 10 ST2 0 cyl 0 hd 0 sec 1) msdos: /dev/fd0a: Input/output error nomad# dd if=/dev/fd0a /mnt dd: unknown operand /mnt nomad# dd if=/dev/fd0a of=/dev/null fd0c: hard error reading fsbn 0 (ST0 40 ST1 10 ST2 0 cyl 0 hd 0 sec 1) dd: /dev/fd0a: Input/output error 0+0 records in 0+0 records out 0 bytes transferred in 7.328928 secs (0 bytes/sec) When I boot with an OpenBSD boot disk and try the same, it shows similar error messages. This is with various disks which are readable on other machine, and even on the same machine under dos/windows, so I presume the drive is not broken. There must be some kind of incompatibility between the drive or controller and the FreeBSD driver. It works under linux, although the linux kernel prints some messages about timeouts and unexpected interrupts. I attached a FreeBSD dmesg (custom kernel - same happens with the GENERIC one), and the dmesg from tomsrtbt (a one-floppy linux distribution which loads a ramdisk image from floppy - you can see the messages when it starts reading that). Does anyone have an idea about how to start debugging or fixing this? -- Chris --T4sUOijqQbZv57TR Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: attachment; filename="dmesg_nomad.txt" Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-STABLE #0: Tue Feb 4 21:45:11 CET 2003 supc@freedaemon.home.lan:/usr/src/sys/compile/LAPTOP Timecounter "i8254" frequency 1193182 Hz CPU: i486DX (486-class CPU) real memory = 8388608 (8192K bytes) avail memory = 5484544 (5356K bytes) Preloaded elf kernel "kernel" at 0xc02e9000. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface isa0: on motherboard orm0: