Date: Mon, 26 Jul 2004 10:00:15 -0700 From: Nate Lawson <nate@root.org> To: Tim Robbins <tjr@freebsd.org> Cc: current@freebsd.org Subject: Re: Floppy disk drive no longer detected Message-ID: <4105389F.9000204@root.org> In-Reply-To: <20040726095929.GA30092@cat.robbins.dropbear.id.au> References: <20040726021326.GA23697@cat.robbins.dropbear.id.au> <20040726095929.GA30092@cat.robbins.dropbear.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Robbins wrote: > On Mon, Jul 26, 2004 at 12:13:26PM +1000, Tim Robbins wrote: >>My floppy disk drive is no longer probed correctly by -CURRENT. I get the >>following message, but none about fd0 (and /dev/fd0 does not exist): >> >>fdc0: <floppy drive controller (FDE)> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 >> >>Previously it probed as: >> >>fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 >>fdc0: FIFO enabled, 8 bytes threshold >>fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >> >>The ACPI DSDT for this system is available at: >>http://people.freebsd.org/~tjr/k8v.txt.bz2 > > Ok, it looks like the FDC device should have a child device for each drive, > but my system's DSDT has none. Could we work around this in the driver by > not using _FDE/_FDI to probe unless the FDC device has at least 1 child with > an _FDI object, or should we add an entry to the quirks table for this > particular BIOS instead? Thanks for the info. I'm working on a fix for this, as well as the case where a child device exists but has no _FDI method. -- -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4105389F.9000204>