Date: Mon, 9 Oct 2006 18:09:17 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Robert Watson <rwatson@freebsd.org>, Eugene Grosbein <eugen@kuzbass.ru> Subject: Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon Message-ID: <200610091809.17741.jhb@freebsd.org> In-Reply-To: <20061005144852.GA60575@svzserv.kemerovo.su> References: <451F6E8E.8020301@freebsd.org> <20061005130829.A46123@fledge.watson.org> <20061005144852.GA60575@svzserv.kemerovo.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 05 October 2006 10:48, Eugene Grosbein wrote: > On Thu, Oct 05, 2006 at 01:09:27PM +0100, Robert Watson wrote: > > > >It's definetely a regression from 4.11-STABLE that runs fine on this > > >system with ACPI fully enabled > > Hmm, I was wrong about 4.11 using ACPI - it does not use it here really, > it uses "good old" APM. > > > It would be interesting to know how 4.x probes the hardware vs. how it > > apperas in the 6.x dmesg. > > 4.11-STABLE: > > fdc0: <NEC 72065B or clone> 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 > > 6.2-PRERELEASE: > > fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 You have a screwed up BIOS. Listing 0x3f0 twice is what is probably breaking your system. You can probably patch your ASL and build a custom DSDT to get your floppy drive working. Check the manpages and the acpi@ list for more info on doing that. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610091809.17741.jhb>