Date: Wed, 25 Aug 2004 19:49:49 -0500 From: edwinculp <edwinculp@prodigy.net.mx> To: freebsd-questions@freebsd.org Subject: Re: Re: Message-ID: <b4e7db61f1.b61f1b4e7d@prodigy.net.mx>
next in thread | raw e-mail | index | archive | help
----- Mensaje original ----- De: Steven Friedrich <FreeBSD@InsightBB.com> Fecha: Miércoles, Agosto 25, 2004 5:49 pm Asunto: Re: > On Wednesday 25 August 2004 05:35 pm, edwinculp wrote: > > ----- Mensaje original ----- > > De: Steven Friedrich <FreeBSD@InsightBB.com> > > Fecha: Miércoles, Agosto 25, 2004 3:49 pm > > > > Asunto: Re: > > > On Wednesday 25 August 2004 03:56 pm, Lee Harr wrote: > > > > >I just installed mtools today. I'm tracking 4.10 STABLE and my > > > > >ports tree was updated yesterday. > > > > > > > > > >I get an error: > > > > >root@lightning(p1)/usr/src 114% mdir a: > > > > >Can't open /dev/fd0.720: Device not configured > > > > >Cannot initialize 'A:' > > > > > > > > Does your dmesg mention fd0 ? > > > > something like ... > > > > > > > > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > > > > > > > > _________________________________________________________________> > > > Tired of spam? Get advanced junk mail protection with MSN 8. > > > > http://join.msn.com/?page=features/junkmail > > > > > > > > _______________________________________________ > > > > freebsd-questions@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > To unsubscribe, send any mail to > > > > "freebsd-questions-unsubscribe@freebsd.org" > > > > > > I'm glad you asked. It says: > > > fdc0: cannot reserve I/O port range > > > > This is just a very wild guess but on current there is an issue > with some > > Athlon motherboards w/via chipsets and the dmesg is something like > > > > fdc0: <floppy drive controller> port 0x3f7,0x3f4-0x3f5,0x3f2- > 0x3f3 irq 6 > > drq 2 on acpi0 fdc0: I/O to control range incorrect > > device_attach: fdc0 attach returned 6 > > > > I was told on the Current list that my acpi was on crack :) but > Warner is > > preparing a patch. It's been that was for a while. > > > > Like I said, I doubt it is the same but just in case. I assume > you aren´t > > using Athlon with via chipset, if not I don't think that is the > problem.> > > ed > > > > > I didn't have this problem until recently though, and I haven't > > > changed BIOS > > > settings. > > > > > > Is it conflicting with something new? > > > > > > oh, I recently added device psa to my kernel.. I'll remove it and > > > let the list > > > know... > > > _______________________________________________ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to "freebsd-questions- > > > unsubscribe@freebsd.org" > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "freebsd-questions-unsubscribe@freebsd.org" > > Thanks for the info. > > My moboard is an ASUS P4-533T. I think the problem is loosely > related. I > think the acpi code is looking at too broad a port range or > something... > I discovered that I can "fix" the problem by removing acpi from my > kernel, but > I hope to get a real solution, cause I want ACPI. > > I'm willing to provide more info or run some code for the developer... A solution seems to be coming. I haven't tried it yet and don't even know if 4.10 has device.hints under /boot, but you might try commenting out #hint.fdc.0.at="isa" #hint.fdc.0.port="0x3F0" #hint.fdc.0.irq="6" #hint.fdc.0.drq="2" #hint.fd.0.at="fdc0" #hint.fd.0.drive="0" #hint.fd.1.at="fdc0" #hint.fd.1.drive="1" and rebooting and see if it changes. With acpi enabled, of course. Good luck, ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b4e7db61f1.b61f1b4e7d>