Subject: port-i386/10602: pnpbios fdc fails to attach, unable to map CTL I/O space
To: None <gnats-bugs@gnats.netbsd.org>
From: None <Anders.Hjalmarsson@economics.gu.se>
List: netbsd-bugs
Date: 07/17/2000 18:21:15
>Number:         10602
>Category:       port-i386
>Synopsis:       pnpbios fdc fails to attach, unable to map CTL I/O space
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 15 16:40:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     Anders Hjalmarsson
>Release:        NetBSD-current 2000-07-14
>Organization:
>Environment:
System: NetBSD econahja.econ.gu.se 1.5B NetBSD 1.5B (ECONAHJA-$Revision: 1.98 $) #180: Sat Jul 15 22:46:32 CEST 2000 econahja@econahja.econ.gu.se:/usr/src/sys/arch/i386/compile/ECONAHJA i386


>Description:
	The pnpbios attachment for fdc does not work on my computer, I
	get the message:
fdc0 at pnpbios0 index 14 (PNP0700)
fdc0: unable to map CTL I/O space

	From an earlier kernel without fdc* at pnpbios? I get the
	following:
PNP0700 (io 3f0-3f5, irq 6, dma 2) at pnpbios0 index 14 ignored

	A quick look at fdc_pnpbios.c seems to indicate that the code
	expects there to be more than one i/o range (3'rd arg to
	pnpbios_io_map is 1 in the failed mapping)

>How-To-Repeat:
	Boot a kernel configured with fdc* at pnpbios?
>Fix:
	Workaround: use the isa attachment instead.
>Release-Note:
>Audit-Trail:
>Unformatted: